PK67315: IF APPLICATION SERVERS ARE JOINED TO A CLUSTER, JMS RESOURCES CANNOT BE CREATED AT THE CLUSTER MEMBER SCOPE

Fixes are available

APAR status

Closed as program error.

Error description

On version 6.0.2, trying to create JMS resources at the
cluster member scope will result in a failure.
For example, when creating a WebSphere MQ resource you get a
HTTP 500 Error on the Deployment Manager Administrative Console.
.
And you will see the following in the dmgr SystemOut.log
[7/8/08 7:39:35:238 EDT] 0000024f WebApp        A   SRVE0180I:
[adminconsole] [/ibm/console] [Servlet.LOG]: action:
MQQueueConnectionFactoryDetailForm was null.Creating new form
bean and storing in session
.
.
[7/8/08 7:41:10:051 EDT] 00000248 RequestProces W
org.apache.struts.action.RequestProcessor processException
Unhandled Exception thrown: class java.lang.NullPointerException
.
[7/8/08 7:41:10:068 EDT] 00000248 ServletWrappe E   SRVE0068E:
Could not invoke the service() method on servlet action.
Exception thrown
javax.servlet.ServletException
at org.apache.struts.action.RequestProcessor.processException
(RequestProcessor.java:545)
at org.apache.struts.action.RequestProcessor.
processActionPerform(RequestProcessor.java:486)
at org.apache.struts.action.RequestProcessor.process
(RequestProcessor.java:275)
at org.apache.struts.action.ActionServlet.process
(ActionServlet.java:1486)
.
---- Begin backtrace for Nested Throwables
java.lang.NullPointerException
at com.ibm.ws.console.core.action.GenericAction.
makeChild(GenericAction.java:366)
at com.ibm.ws.console.resources.jms.mqseries.
MQQueueConnectionFactoryDetailAction.
execute(MQQueueConnectionFactoryDetailAction.java:179)
at org.apache.struts.action.RequestProcessor.
processActionPerform(RequestProcessor.java:484)

Local fix

Create the resource at the node or cluster scope.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: JMS resource creation fails at the      *
*                      cluster member scope.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
On version 6.0.2, trying to create JMS resources at the
cluster member scope will result in a failure.

You will see the exception like this in the dmgr SystemOut.log

[7/8/08 7:39:35:238 EDT] 0000024f WebApp        A   SRVE0180I:
[adminconsole] [/ibm/console] [Servlet.LOG]: action:
MQQueueConnectionFactoryDetailForm was null.Creating new form
bean and storing in session
.
.
[7/8/08 7:41:10:051 EDT] 00000248 RequestProces W
org.apache.struts.action.RequestProcessor processException
Unhandled Exception thrown: class java.lang.NullPointerException
.
[7/8/08 7:41:10:068 EDT] 00000248 ServletWrappe E   SRVE0068E:
Could not invoke the service() method on servlet action.
Exception thrown
javax.servlet.ServletException
at org.apache.struts.action.RequestProcessor.processException
(RequestProcessor.java:545)
at org.apache.struts.action.RequestProcessor.
processActionPerform(RequestProcessor.java:486)
at org.apache.struts.action.RequestProcessor.process
(RequestProcessor.java:275)
at org.apache.struts.action.ActionServlet.process
(ActionServlet.java:1486)
.
---- Begin backtrace for Nested Throwables
java.lang.NullPointerException
at com.ibm.ws.console.core.action.GenericAction.
makeChild(GenericAction.java:366)
at com.ibm.ws.console.resources.jms.mqseries.
MQQueueConnectionFactoryDetailAction.
execute(MQQueueConnectionFactoryDetailAction.java:179)
at org.apache.struts.action.RequestProcessor.
processActionPerform(RequestProcessor.java:484)

The cause of this problem is that when an existing server is
added to a cluster, all of the JMSProvider resources from that
server's resources.xml are promoted to the cluster scope.  So,
the providers are moved form the server level resources.xml to
the cluster level resources.xml. The console code assumed that
the JMSProviders were always present in the server's
resources.xml, and this caused the error seen
by the customer.

Problem conclusion

The PK67315 solution gives customers on versions 6.0.2 and 6.1
the ability to create cluster member level JMS resources.
For a resolution of the console's HTTP 500 Error customers see
on version 6.0.2, please see PK89524.

A new option named resourcesScope has been added to the
createCluster and createClusterMember commands.  This option
will allow users to specify what should be done with the
server resources once the server is moved into a cluster.
This new option can take three possible values - 'server',
'cluster', or 'both'.  The 'server' option specifies that the
server's resources should be kept at the server level.  The
'cluster' option specifies that the server's resources should
be moved to the cluster level.  The 'both' option specifies
that server level resources should be copied to the cluster
level.

On Websphere Application Server version 6.0.2, the default
behavior before and after PK67315 is the 'cluster' option
behavior.

On Websphere Application Server version 6.1, the default
behavior before and after PK67315 is the 'both' option.

If customers want to create JMS resources at the cluster
member scope, they will need to create their cluster members
with the 'server' or 'both' options.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.35 and 6.1.0.23.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

```
ZE Fix Error, see PK93059. 2009/09/21
```

Comments

APAR Information

APAR number
PK67315
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-06-09
Closed date
2008-10-20
Last modified date
2010-05-28

APAR is sysrouted FROM one or more of the following:

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

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK67315: IF APPLICATION SERVERS ARE JOINED TO A CLUSTER, JMS RESOURCES CANNOT BE CREATED AT THE CLUSTER MEMBER SCOPE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?