5 Replies Latest reply on Aug 8, 2011 9:37 PM by user1316343

    Frequent Kickouts (logoffs) since upgrade to 8.51 - also occurance of 404

      Since we upgraded to PT8.51, our users have been experiencing involuntary kickouts, or signoffs, sporadically. While working on a page, usually when they go to save, they are immediatley logged off and redirected to the signon screen. Sometimes they have multiple windows (browsers) open, other times they seem to only have one. We also have notices of people getting 404 errors while trying to view attachments, as if they are being directed to the wrong app server to view the image (the image resides on only one). For some people, these issues happen a few times a day. For others, it has been reported to happend 15-30 times.

      I've seen a few comments posted on different sites of others with the same kickout issue, but have yet to find a solution.

      Our Environment:
      1) We are running our app servers and web severs on two physical 64-bit windows servers.
      2) Each server hosts one App Server and one Web Server, but the app servers are NOT dedicated to their corresponding web server.
      3) We have an F5 load balancer in front of the Web Servers, and each web server is configured to balance their load across both available App Servers.
      This environment was built for the upgrade, as we migrated from old 32-bit hardware thatwas retired with the upgrade.

      Without anything to support this, I believe that the kickouts and the 404 errors are related to session stickiness. I can reproduce the effect by opening multiple windows until I get two on different app servers (which I can see by pressing CTRL-J in the browser). As soon as I see that I have two on different servers, whatever I do next kicks me out. But why would I be allowed to get into this state in the first place? The F5 configuration hasn't changed with the upgrade (aside from pointing to different servers), but we just started putting App Servers and Web Servers on the same physical boxes. I believe this is an incorrect configuration somewhere, but no one our admistrative team can determine where.

      Does anyone have any ideas what could be causing?

      [PT851 851 PeopleTools Upgrade kickouts signouts signoffs kickoffs 404 HTML_404 involuntary session_stickiness]

      Edited by: 876754 on Aug 2, 2011 11:09 AM
        • 1. Re: Frequent Kickouts (logoffs) since upgrade to 8.51 - also occurance of 404
          Which dot release of 8.51 are you on? I.e. 8.51.xx?
          • 2. Re: Frequent Kickouts (logoffs) since upgrade to 8.51 - also occurance of 404
            If you are using Weblogic, have a look into that note :
            *Troubleshooting WebLogic Issues [ID 649428.1] -- TroubleShooting_WebLogic_103.pdf, issue #3: Issues with Session Stickiness*+
            The symptoms are similar (if not same) as yours, they are few recommandations to follow.

            • 4. Re: Frequent Kickouts (logoffs) since upgrade to 8.51 - also occurance of 404
              Have you checked the doc I linked earlier ?

              • 5. Re: Frequent Kickouts (logoffs) since upgrade to 8.51 - also occurance of 404
                Make sure you have applied all available PeopleTools patches. We have seen this in 8.50. Some was fixed in tools updates/patches but we have had to work though a couple customizations and workarounds with Oracle to resolve some. I am not sure they are related to your problem exactly as many of ours had to do with using the PS Portal to expose content in other PS Apps (Campus Solutions 9.0).

                Another item that may get you in an upgrade are java script cached in users browsers that had been changed but the browsers were not aware of it. We found other customers that solved this by updating the cache directories in the Web Profile configuration and restarting PIA. We changed cache to cache85020 and change it to the next version each upgrade. Works to make browsers reload the files since they are in a different path and we do not have to try and get all users to clear cache properly.

                I am not sure about where you are balancing trafffic with the F5, but we only balance the traffic from users to the web servers and let the web servers connect to the app servers. We were advised to go with the old style connect strings in the configuration.properties of host:port,host:port,host:port and not the new options as they may have issues still, but they only had thin evidence for that, but we went that way all the same.

                Also search Oracle support for kick out, 8.50, 8.51 known issues as there are several there. I an not sure how many will be relevant to 8.51.

                We and your users have been through this pain and still see it on some occasions, I am not sure there is a single cause, but several places they are checking sessions and cookies and different issues that arise.

                We are also having a hard time knowing if all our kick outs are related to our use of Portal. In our case what happens in the session timers and timeouts all run in the target Iframe and target application. Users can stay there all day if they never click back on a Portal link, but if they do and the session time has expired in Portal (regardless of activity in the remote app) they are instantly without warning kicked out into a login page. That happens because there is no Portal timer to warn them or to see their activity in the remote app. So they are actually out of the Portal at the timeout for that, but won't know it until they click back, and it will see like they were actively working and all of sudden the app kicked them out.