JR34012: TRUSTED SESSIONS NOT BEING REMOVED CAUSING 'MAXIMUM NUMBER OF SESSIONS HAS BEEN REACHED' ISSUE.

APAR status

• Closed as fixed if next.

Error description

• The WAS logs show multiple errors "The maximum number of
  sessions has been reached. "Project creation and some other
  operations uses a special trusted session, which cannot be
  removed using the Web Console and which does not timeout. In
  normal operation these sessions should be closed and the
  maximum number of trusted sessions will not be a problem. It
  looks like something is causing these sessions to not be cleaned
  up.  Re-starting WAS will free any trusted sessions and should
  allow project creation to work.
  
  IIS 8.1 on HP-UX 11.23
  

Local fix

• Restart WAS is workaround to clear the sessions.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  The maximum number of sessions has been reached.
  ****************************************************************
  PROBLEM DESCRIPTION:
  Project creation and some other operations use a special
  trustedsession, which cannot be removed using the Web Console
  and  which does not timeout. In normal operation these
  sessions      should be closed and the maximum number of trusted
  sessions willnot be a problem.  However, in some situations
  the Logging Agent will retry its connection (creating a new
  trusted session)without first checking to see if the current
  session is still   active, causing a session leak and
  eventually reaching the      session limit.
  ****************************************************************
  RECOMMENDATION:
  This fix is included in IS 81 FP1.
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R810 PSN

     UP