PQ79482: ON SERVER INITIALIZATION MDBLISTENER FAILS TO CONNECT TO MQ DUE TO INCOMPLETE SECURITY INITIALIZATION.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
On server initialization for WebSphere V5.0 MDBListener fails to
connect to MQ due to incomplete security initialization.
The following errors are seen in the servant:
.
Trace: 2003/10/06 10:41:42.014 01 t=9F9588 c=UNK key=P8 (1300700
FunctionName: com.ibm.ejs.j2c.ThreadIdentitySecurityHelper
SourceId: com.ibm.ejs.j2c.ThreadIdentitySecurityHelper
Category: ERROR
ExtendedMessage: J2CA0079E: Method ThreadIdentitySecurityHelper.
finalizeSubject() has detected an internal illegal state and is
throwing an IllegalStateException. The exception is:
java.lang.IllegalStateException: The InvocationSubject and the
ReceivedSubject both returned null from the ContextManager
.
at com.ibm.ws.security.auth.j2c.WSLocalzOSExtensionImpl.
getLocalOSInvocationSubject(WSLocalzOSExtensionImpl.java:110)
at com.ibm.ejs.j2c.ThreadIdentitySecurityHelper.finalizeSubject
(ThreadIdentitySecurityHelper.java:369)
MD18185
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Failure when server is starting up      *
*                      MDB application.  Unable to create      *
*                      connections needed by MDB Listener      *
*                      due to Security problems.               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During server startup, when the server starts MDB applications,
it creates connections to the Connection Factory specified in
the MDB Listener Port, using the standard JMS
createQueueConnection(), createTopicConnection() APIs.  A bug
with respect to the JNDI environment results in an invalid
path through WebSphere for z/OS security, at the time of
creating these JMS Connections, and an exception is thrown.

Error traces may include ones like the following:

Trace: 2003/10/06 10:41:42.006 01 t=9F9588 c=UNK key=P8
FunctionName: com.ibm.ws.security.auth.j2c
.WSLocalzOSExtensionImpl
SourceId: com.ibm.ws.security.auth.j2c.WSLocalzOSExtensionImpl
Category: ERROR
ExtendedMessage: security.auth.j2c.invalidSubject
error message: BBOO0223I security.auth.j2c.invalidSubject
com.ibm.ws.
ecurity.auth.j2c.WSLocalzOSExtensionImpl
om.ibm.ws.securi.auth.j2c.WSLocalzOSExtensionImpl

Trace: 2003/09/29 11:21:32.075 01 t=9CEBF8 c=UNK key=P8
FunctionName: com.ibm.ejs.jms.listener.WS390MDBListenerImpl
SourceId: com.ibm.ejs.jms.listener.WS390MDBListenerImpl
Category: WARNING
ExtendedMessage: WMSG0019E: Unable to start MDB Listener XXXXX,
JMSDestination jms/xxxxx : javax.jms.JMSException: Failed to
create queue connection

Trace: 2003/09/29 11:21:32.067 01 t=9CEBF8 c=UNK key=P8
 FunctionName: com.ibm.ejs.j2c.ThreadIdentitySecurityHelper
 SourceId: com.ibm.ejs.j2c.ThreadIdentitySecurityHelper
 Category: ERROR
 ExtendedMessage: J2CA0079E: Method
ThreadIdentitySecurityHelper.finalizeSubject() has detected an
internal illegal state and is throwing an IllegalStateException.
The exception is: java.lang.IllegalStateException: The
InvocationSubject and the ReceivedSubject both returned null
from the ContextManager
Problem conclusion
JNDI problem fixed so that createQueueConnection() and
createTopicConnection() take proper paths through WAS zOS
Connection Management and WebSphere for z/OS Security.

APAR PQ79482 is associated with SERVICE LEVEL W502000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ79482
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-10-10
Closed date 2003-12-07
Last modified date 2004-01-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ82902    UP03/12/15 P F312

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ79482.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 #: PQ79482
IBM Group: Software Group
Modified date: Jan 3, 2004