There have been several PeopleSoft Timeout problems that have impacted various levels of 8.50, 8.51, and 8.52. Indications are all these problems are fixed now. According to Oracle, the code has also been fixed in 8.50.25, 8.51.17, 8.52.07, and 8.53. I’m sure a new problem will pop up at some point though.
The first problem which I consider the most dangerous, is that the timeout warning process breaks down and causes a users browser to repeatedly request the timeout warning pop-up page. It looks like this particular problem impacts 8.50.22, 8.50.23, and 8.50.24. It looks like it also impacts 8.51.12 – 8.51.16 and 8.52.00 – 8.52.06. I don’t have the 8.51 or 8.52 versions running, however looking at the code delivered in the 8.51.16 and 8.52.06 patches, the problem code does exist. I know 8.52.07 does not have the bad code because I do have access to an environment at that level. This was actually put in as a fix for another problem, which I’ll mention later. It was put into 8.50.22, 8.51.12, and 8.52.00.
Users may have their PC’s hang as the browser takes CPU to 100% requesting the timeout warning page. Or if you have access logging turned on and you review the web server access log you will see hundreds to thousands of requests for the warning page from a single IP repeatedly in quick succession. In some cases this can cause the web server to crash. In other cases I’ve heard of it maxing out jolt connections on the app server. Oracle has a work around posted [ID 1405219.1].
Another problem is that time outs across windows/tabs are not synched. This one I think has existed for a long time actually. Oracle indicates that there was a bug in 8.4x that they did not fix which allowed users to not be timed out of idle windows but since it was a bug, it was fixed in the 8.50 release. I’m not sure what 8.4x releases that bug impacted. Good news is it’s fixed moving forward. Oracle says this about the behavior.
In PT8.4, if end user is active in one browser window, but lets the other window remain idle and timeout, the end user could continue in active window. This was a bug: 11558697 in PT8.4 and incorrect behavior. Many customers prefer the incorrect behavior in PT8.4; however, that behavior was a bug. The timeout behavior in PT8.50 is correct and development will not revert back to PT8.4 timeout behavior.