PI90961: LIBERTY ON Z/OS: BATCH JMS DISPATCHER CHANGE TO LAZY ACCESS OF CONNECTION FACTORY.

Fixes are available

APAR status

Closed as program error.

Error description

This APAR is taken to change the batch JMS dispatcher code
to
make lazy access to the connection factory it requires.
Prior to this fix, there is a timing window where the batch
JMS dispatcher news up a ConnectionManager prior to RRS
support being available, if the zosTransaction-1.0 feature
has not yet started.
The problem is externalized as
com.ibm.ws.jbatch.jms.internal.dispatcher.BatchJmsDispatcher
E
CWWKY0213E: Unable to create JMS resource for batch
dispatcher.
The exception is java.lang.IllegalStateException: Native
service
for RRS transactional support is not active or available.
Resource registration is rejected.
at
com.ibm.ejs.j2c.ConnectionManager.<init>(ConnectionManager.j
ava:
204)
..
at
com.ibm.ws.jca.cm.AbstractConnectionFactoryService.createRes
ourc
e(AbstractConnectionFactoryService.java:145)
at
com.ibm.ws.jbatch.jms.internal.dispatcher.BatchJmsDispatcher
.act
ivate(BatchJmsDispatcher.java:288)
..
A trace of the startup will show this error reported prior
to messages that indicate that the RRS support is in place:
--
LogService-363-com.ibm.ws.zos.tx
1
ServiceEvent REGISTERED

ServiceRef:&#163;com.ibm.ws.zos.tx.internal.rrs.RRSServices](id=8
14,
pid=null)
--
The problem might be sensitive to feature order in complex
setups with multiple include files for config.

Local fix

Reordering of features in config might act as a bypass.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server       *
*                  Liberty Batch on z/OS using the JMS         *
*                  dispatcher/executor function                *
****************************************************************
* PROBLEM DESCRIPTION: Unable to initialize the Batch JMS      *
*                      Dispatcher component when it is         *
*                      configured to use a BINDINGS-mode       *
*                      connection factory.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Batch JMS Dispatcher component, used to dispatch batch jobs
(or partitions) via JMS to be consumed and executed on other
"executor" servers, is configured via the
<batchJmsDispatcher> element to reference a JMS connection
factory (by default, one with id="batchConnectionFactory").
When this referenced connection factory is configured to use
BINDINGS mode,
on the z/OS platform, then this server configuration requires
the "zosTransaction-1.0" feature to start the RRS-related
function used by WebSphere connection managmenet.

Because the batch dispatcher component obtains its connection
factory object upon activation, a problem can occur if this
component is activated before certain RRS-related components
provided by the "zosTransaction-1.0" feature.

If the problem timing window occurs, the dispatcher activation
fails with an error message like:

CWWKY0213E: Unable to create JMS resource for batch dispatcher.
The exception is java.lang.IllegalStateException: Native
service
for RRS transactional support is not active or available.
Resource registration is rejected.
at
com.ibm.ejs.j2c.ConnectionManager.<init>(ConnectionManager.java:
204)
..
at
com.ibm.ws.jca.cm.AbstractConnectionFactoryService.createResourc
e(AbstractConnectionFactoryService.java:145)
at
com.ibm.ws.jbatch.jms.internal.dispatcher.BatchJmsDispatcher.act
ivate(BatchJmsDispatcher.java:288)

In an otherwise valid configuration, the jobs or partitions may
dispatch and execute locally (if the necessary application is
deployed locally).

Problem conclusion

The Batch JMS Dispatcher was modified to do a lazy instantiation
of its connection factory resource objects, until the time of
dispatch.   The batch dispatch functions should not be called
until the server has completed startup, by which time the RRS-
related components should have also activated, and which
bypasses the earlier timing window.

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

Temporary fix

Comments

APAR Information

APAR number
PI90961
Reported component name
LIBERTY PROF -
Reported component ID
5655W6514
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-12-01
Closed date
2018-05-22
Last modified date
2018-05-22

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
LIBERTY PROF -
Fixed component ID
5655W6514

Applicable component levels

R850 PSY
UP

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

Document Information

Modified date:
04 May 2022

Tips

PI90961: LIBERTY ON Z/OS: BATCH JMS DISPATCHER CHANGE TO LAZY ACCESS OF CONNECTION FACTORY.

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

R850 PSY

Document Information

Share your feedback

Need support?