Monday, February 13, 2012

Three Intermittent Issues

We have three Tools related issues we are continuing to work on.  The first is something that we thought was solved.  Users intermittently get http 501 errors.  In "External Applicants and Browsers" we addressed AJAX issues, including the 501 error.  The PeopleSoft Experts blog entry has a great deal of information about issue and the Microsoft registry fix.  Microsoft documents the error as a problem for IE 7 & 8 users on Windows XP.  We had IE 7 users on XP, applied the registry patch, and all was good.  But now users upgrading to Windows 7, using IE 8, and having the problem again.  This issue may be related to bug 11870611.

The second issue we are seeing is that a user is actively using PeopleSoft and their session times out.  It's not a common occurrence.  The user has used the New Window link to open a second window.  This issue could be related to report ID 13096404.

The last one is where users are stuck in a processing state.  They can sit at a page for ten minutes or longer, and it will stay in processing.  But if they log out and log back in, they can complete the transaction right away.  I thought that this issue was related to bug 11625722, but support said that bug doesn't relate to us since we are on Tools 8.51.13.  They have us cleaning up some errors in the application server logs.  I'll be surprised if it makes any difference.

Update:
See the later post on the 501/AJAX error here.

2nd Update
See the latest users stuck in processing here.

3rd Update: See Stuck-in-Processing Solved

5 comments:

  1. We are facing an issue similar to your # 3 with PT 8.51.14. Were you able to resolve it?

    ReplyDelete
    Replies
    1. We are at the point where we would need to apply the latest Tuxedo patch before the case gets forwarded to development at Oracle. Since we are in the middle of upgrading from 8.9 to 9.1, we are thinking hard about whether to do it or not. I think there's a 1% chance that the Tuxedo patch will address the problem. It's just a step that development is making us do before they will take the issue seriously. It wouldn't be extensive testing for us to put in a Tuxedo patch, but time is tight with the upgrade.

      Our work-around for the users has been, if you sit there a minute processing, logout and log back in.

      Delete
    2. I just heard from Oracle that it's fixed in 8.51.17. See report ID 13865710 in the release notes.

      Delete
  2. We are having the same issues as you mentioned above. We had Oracle SR's open and they closed it with no fault found. Consulting said it was a network issue. This is very helpful.
    Please keep this blog posted if you have any updates on all the three issues. Were you able to find out anything on the second issue where a "new window" link was used?

    ReplyDelete
  3. Two days ago we patched up to 8.51.21. I'll update based on what we see. Here are some bug fixes that may address the untimely session time-out.

    Bug listed as fixed in 8.51.15
    13245017
    BACKPORT Bug TO 8.51 RELEASE
    "BACKPORT Bug TO 8.51 RELEASE (backport of Bug 13090645 : JOLT SESSION THOURGH TIME OUT ERROR UNDER PAGELET PARALLEL LOADING )"

    Bug listed as fixed in 8.51.17:
    13079530
    8.51 PATCH TIMEOUT BEHAVIOR
    PIA - time outs for pia were not functioning correctly. This has been resolved here so PIA only times out when it should.

    Bug listed as fixed in 8.51.18
    13811451
    8.51-18A PATCH TIMEOUT BEHAVIOR
    PIA TIMEOUT BEHAVIOR fixed so the user is not timed out unnecessarily

    ReplyDelete