PM01482: MDB NOT PROCESSING MESSAGES DUE TO CONTROL REGION ADJUNCT NOT FULLY UP AND CONNECTED WITH THE SERVANT REGION.

Fixes are available

APAR status

Closed as program error.

Error description

MDB not processing messages due to CRA not fully up and
connected with the SR.

The error is the result of the SR having connected and
attempting to send the "handshake" message before the CRA is
fully up and running.  This error is timing related and can
happen after a server restart, when the SR is connecting with
the CRA.

i.e.: Looking at the CRA trace, we see that the max number of

inflight messages is reached:

> [2009/10/22 19:55:35:899] 8CEE88
com.ibm.ws.wmqra.zdispatcher.EndpointInflightMessageReferences.p
reDispatch() [c=UNK key=P8 (13007002)]

So we wait for notification from the SR that the messages have
been delivered.  However the SR can't send the messageDelivered
segment as the connection has been closed:

ExtendedMessage:
(com.ibm.ws.wmqra.zdispatcher.WASServantConnectionConsumerReposi
tory)
[:/6da36da3] Caught SIException while calling messageDelivered;
com.ibm.wsspi.sib.core.exception.SIConnectionDroppedException:CW
SIJ0047E
: An operation was attempted on a connection that is already
closed.
at
com.ibm.ws.sib.jfapchannel.impl.ConversationImpl.sendInternal(Co
nversationImpl.java:1120)
at
com.ibm.ws.sib.jfapchannel.impl.ConversationImpl.send(Conversati
onImpl.java:1021)
at
com.ibm.ws.sib.comms.common.JFAPCommunicator.jfapSend(JFAPCommun
icator.java:456)
at
com.ibm.ws.wmqra.jfap.WMQRAJFAPCommunicator.messageDelivered(WMQ
RAJFAPCommunicator.java:199)
at
com.ibm.ws.wmqra.zdispatcher.WASServantConnectionConsumerReposit
ory.dispatch(WASServantConnectionConsumerRepository.java:204)

The connection was oringnally closed here:

> [2009/10/22 19:55:35:456] 8C2BE0
com.ibm.ws.wmqra.jfap.WMQRAJFAPCommunicator.errorOccurred()
[c=UNK
key=P8 (13007002)]
FunctionName: errorOccurred
(com.ibm.ws.wmqra.jfap.WMQRAJFAPCommunicator) [:/5b955b95]
SourceId: com.ibm.ws.wmqra.jfap.WMQRAJFAPCommunicator
Category: FINER
ExtendedMessage: Entry;
com.ibm.ws.sib.jfapchannel.JFapConnectionBrokenException:
CWSIJ0056E: An unexpected condition caused a net work connection
to host 10.11.2.100 on port 0 using chain
_OutboundTCPProxyBridgeService to close.
at
com.ibm.ws.sib.jfapchannel.impl.OutboundConnection.invalidateImp
l(OutboundConnection.java:252)

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application Server
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: Messages are not processed because      *
*                      the Adjunct Region (CRA) is not         *
*                      connected.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Adjunct Region (CRA) becomes disconnected from the
Messaging Engine (ME) following startup or restart. This occurs
because the Server Region (SR) has connected to the ME and is
attempting to send a "handshake" message before the CRA has
initialized the Pause Token Element (PET) that is required to
exchange data between the CRA and SR. The subsequent failure
of the handshake causes the SR to disconnect and place a
disconnect notification on the CRA's queue. The CRA eventually
processes the disconnect notification and passes the
disconnected state to the higher channel. The result is that
the connection is closed.

The attempt by the SR to use the uninitialized PET will result
in a first failure data capture (FFDC) containing a
DataspaceInternalErrorException with a reason code of 4 or 32.

At the point where the CRA processes the disconnect
notification the log message will appear:
CWSIJ0056E: An unexpected condition caused a network connection
to host 10.11.2.100 on port 0 using chain
_OutboundTCPProxyBridgeService to close.

This will be followed by the following message when attempts
are made to use the closed connection:

CWSIJ0047E : An operation was attempted on a connection that
is already closed.

Problem conclusion

Processing has been changed so that connect of the SR will be
rejected until the CRA has initialized the Pause Element
Token (PET) and is therefore ready to accept the handshake
message. The reject of the connect in the SR will cause a
connect retry in 10 seconds. Once the PET is initialized, the
connect in the SR will be completed and the subsequent
handshake message will be initiated.

APAR PM01482 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.9 of WebSphere Application Server V7.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM01482
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-17
Closed date
2010-01-19
Last modified date
2010-04-03

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

R700 PSY UK55133
UP10/03/26 P F003

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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM01482: MDB NOT PROCESSING MESSAGES DUE TO CONTROL REGION ADJUNCT NOT FULLY UP AND CONNECTED WITH THE SERVANT REGION.

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

R700 PSY UK55133

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

Share your feedback

Need support?