PQ82061: TR.AUDIT IN METHOD CLEARCALLERCONTEXT IN CONTEXTMANAGERIMPL.JAVASHOULD DISPLAY A MESSAGE NUMBER FOR CUSTOMERS TO LOOK UP.

APAR status
Closed as fixed if next.

Error description
Customer received the following error message,
.
BBOO0223I Internal Error. Thread Id reset onrequest exit. Some
methods may have not reset thread identities, contact your IBM
support
.
This is a trace audit in the websphere security code in method
clearCallerContext( ) for ContextManagerImpl.java. This code
needs to be changed to display a regular message with an
explanation and user action according to a message number so
customers can look this up.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS.                               *
****************************************************************
* PROBLEM DESCRIPTION: Audit messages do not display message   *
*                      number for customer to look up in the   *
*                      publications or in the InfoCenter.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Audit messages coming from ContextManagerImpl class don't have
a message number in them. Customers cannot look up for those
messages in the publications or the InfoCenter.
These are the audit messages without a message number:
a)
  "Internal Error. ContextManagerImpl.initializeSystemContext
   cannot obtain NSC for Server credential on new thread"

b)
  "Internal Error. Thread Id reset on request exit. Some methods
   may have not reset thread identities, contact your
   IBM support"

c)
   "Fatal Error. Killing thread because security Identity on
    thread cannot be reset"

d) "StateOfSecurity in Illegal State."

e) "Internal Error. Contact your IBM Support representative"
Problem conclusion Temporary fix Comments
Message numbers will be added in the next release to the audit
messages mentioned above so that customer can look for them in
the InfoCenter or in the publications.

a)
#Internal Error. ContextManagerImpl.initializeSystemContext
#cannot obtain NSC for Server credential on new thread
#Issued by: WebSphere for z/OS
#Explanation: initializeSystemContext cannot obtain Native
#             SecurityContext from Server credential on the
#             new thread.
#Programmer response: This is an internal error, contact your
#                     service representative if the problems
#                     persist.

b)
#Internal Error. Thread Id reset on request exit. Some methods
#may have not reset thread identities, contact your IBM
#support
#Issued by: WebSphere for z/OS
#Explanation: Some methods may have not successfully reset the
#             thread identities in the servant --
#             ContextManagerImpl.clearCallerContext
#Programmer response: This is an internal error, contact your
#                     service representative if the problems
#                     persist.

c)
#Fatal Error. Killing thread because security Identity on
#thread cannot be reset
#Issued by: WebSphere for z/OS
#Explanation: The process was not able to reset the identity
#             in the thread, therefore the thread was stopped.
#Programmer response: This is an internal error, contact your
#                     service representative if the problems
#                     persist.

d)
#StateOfSecurity in Illegal State
#Issued by: WebSphere for z/OS
#Explanation: Unable to obtain the security state of the
#             thread inside getThreadIdToken().
#Programmer response: This is an internal error, contact your
#                     service representative if the problems
#                     persist.

e)
#Internal Error. Contact your IBM Support representative
#Issued by: WebSphere for z/OS
#Explanation: Unable to obtain the security state of the
#             thread inside setThreadIdToken().
#Programmer response: This is an internal error, contact your
#                     service representative if the problems
#                     persist.

This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered in a WebSphere Application Server for z/OS release
within the next 18 months.
APAR information
APAR number PQ82061
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-12-11
Closed date 2004-02-03
Last modified date 2004-02-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Publications Referenced

Fix information

Applicable component levels
R500 PSN    UP


Document Information


Current web document: swg1PQ82061.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ82061
IBM Group: Software Group
Modified date: Feb 3, 2004