PQ77214: WHEN RUNNING WITH MQ IN BINDINGS MODE NULLPOINTEREXCEPTION THROWN FROM METHOD ZOSSUBJECTHASVALIDUTOKENCREDENTIAL

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When running with MQ in bindings mode (i.e. MQ JMS Connection
Factory TransportType="BINDINGS"), NullPointerException thrown
from zosSubjectHasValidUtokenCredential.
.
In the servant region, the following exception/trace can be seen
from com.ibm.ejs.j2c.poolmanager.FreePool
J2CA0046E: Method createManagedConnectionWithMCWrapper
caught an exception during creation of the ManagedConnection for
resource JMS$XXXXXXXX, throwing ResourceAllocationException.
Original exception: java.lang.NullPointerException
.at com.ibm.ejs.jms.WSJMSManagedConnectionFactory.
                            zosSubjectHasValidUtokenCredential
                       (WSJMSManagedConnectionFactory.java:327)
.at com.ibm.ejs.jms.JMSManagedConnectionFactory.
  createManagedConnection(JMSManagedConnectionFactory.java:398)
.at com.ibm.ejs.j2c.poolmanager.FreePool.
       createManagedConnectionWithMCWrapper(FreePool.java:1104)
   ... followed by more stack trace ...
Local fix
A jar temp fix is available from the L2 support team that can
be made available upon request.  This is an issue on W500103.
This jar file would need to be placed in the
/WebSphere/V5R0M0/AppServer/classes directory and if this is an
ND configuration, also in directory
/WebSphere/V5R0M0/DeploymentManager/classes
.
Jar needs to be ftp'd in binary.
When this APAR is shipped in a PTF and applied, the temp fix
jar file needs to be removed from these classes directories.
.
*** Note for L2 Support ***
Fix is on AQ in directory /u/cb390l2/PQ77214_W500103 as file
w500103.messagingPatch.Aug5.jar
Jar needs to be ftp'd in binary
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Users running with a WebSphere MQ JMS   *
*                      provider Connection Factory resource    *
*                      defined in bindings mode (i.e. with the *
*                      Connection Factory's Transport type     *
*                      property set to "BINDINGS) get a        *
*                      NullPointerException in certain         *
*                      scenarios.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem may show up when starting a server hosting an MDB
application.  It may also occur when running with
application-managed resource authentication selected on the
deployment descriptor of a JMS Connection Factory resource
reference.  The problem may occur in either of these two cases
when either the Listener Port or the JMS Connection Factory
resource reference is mapped onto a WebSphere MQ JMS
bindings mode Connection Factory.

In the servant region, the following exception/trace can be seen
from com.ibm.ejs.j2c.poolmanager.FreePool:

J2CA0046E: Method createManagedConnectionWithMCWrapper
caught an exception during creation of the ManagedConnection for
resource JMS$XXXXXXXX, throwing ResourceAllocationException.
Original exception: java.lang.NullPointerException
at com.ibm.ejs.jms.WSJMSManagedConnectionFactory.
zosSubjectHasValidUtokenCredential
(WSJMSManagedConnectionFactory.java:327)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.
createManagedConnection(JMSManagedConnectionFactory.java:398)
at com.ibm.ejs.j2c.poolmanager.FreePool.
createManagedConnectionWithMCWrapper(FreePool.java:1104)
... followed by more stack trace ...
Problem conclusion
Support has been modified such that objects are now checked to
be non-null before driving methods on them.

APAR PQ77214 is associated with SERVICE LEVEL W500104 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ77214
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-08-06
Closed date 2003-08-30
Last modified date 2003-10-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 UQ79825    UP03/09/10 P F309

  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: swg1PQ77214.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 #: PQ77214
IBM Group: Software Group
Modified date: Oct 3, 2003