PM98753: BINDINGS THEN CLIENT CONNECTION FACTORY DOES NOT WORK AS EXPECTED WITH LISTENER PORTS

Fixes are available

APAR status

Closed as program error.

Error description

A listener port configured in ASF mode with a BINDINGS then
CLIENT connection factory does not reconnect with either the
CLIENT mode connection (when in BINDINGS mode) or the BINDINGS
mode connection (when in CLIENT mode) when a broken connection
Exception occurs in the Control Region.

Instead, the listener in the Control Region continues to
attempt to connect to the Queue Manager it first connected to.

Also, when connected in CLIENT mode, restarting the listener
port does not cause the listener port to connect in BINDINGS
mode if a BINDINGS mode connection is possible.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V8.5 Listener Ports with WebSphere   *
*                  MQ JMS.                                     *
****************************************************************
* PROBLEM DESCRIPTION: Listener port configured with BINDINGS  *
*                      then CLIENT Connection Factory fails    *
*                      to reconnect after broken connection.   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem is that the listener in the Control Region does not
have access to the BINDINGS then CLIENT logic encapsulated in
the managed connection factory in the Servant Region.  As a
result, when a broken connection occurs, the Control Region
listener attempts to reconnect only with the unmanaged
connection factory first passed from the Servant Region
(which has not BINDINGS then CLIENT logic).
Broken connections may not be noticed in the servant region
because the connection used to get messages is idle until a
MessageReference is received from the Control Region.

Problem conclusion

The solution is to:

1) Trigger a restart of the listener port if the connection
with the Queue Manager is detected to be broken in the Control
Region.
2) When the listener port is starting in the Servant Region,
and BINDINGS then CLIENT is configured on the connection
factory, the first connection created is destroyed.  This
ensures that the connection is working (and is not a broken
connection from the pool).

To ensure BINDINGS then CLIENT will always reconnect
if possible when the connection to the queue manager is
broken, the connection factory should either only be used by
the listener port, or have a purge policy of entire pool.

APAR PM98753 is currently targeted for inclusion in Fix Pack
8.5.5.2 of WebSphere Application Server V8.5.5.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

In addition, please refer to URL:
http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack PTF information.

Temporary fix

Comments

APAR Information

APAR number
PM98753
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-10-09
Closed date
2013-10-16
Last modified date
2013-10-16

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
WEBSPHERE FOR Z
Fixed component ID
5655I3500

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:
28 April 2022

Tips

PM98753: BINDINGS THEN CLIENT CONNECTION FACTORY DOES NOT WORK AS EXPECTED WITH LISTENER PORTS

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?