PQ97253: Message Driven Bean listener ports do not attempt to restart following an "Enlist failed" JMS exception

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
After the following error messages appear in the WebSphere
Application Server system log:

ConnectionEve A J2CA0056I: The Connection Manager received a
   fatal connection error from the Resource Adaptor for
   resource  <name>.  The exception which was received is
   javax.jms.JMSException: Enlist failed

the Message Driven Beans (MDBs) named in the errors stop
receiving messages. However, the listener port associated with
the MDB is still running.
.
This apar also address a problem with the following
informational messages not coming out in the joblog when
MDB Listener  is stopped or started successfuly.

.
WMSG0042I: MDB Listener {0} started successfully for
JMSDestination {1}
.                                                             .
WMSG0043I: MDB Listener {0} stopped successfully for
JMSDestination {1}
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: There is no easy way to tell from the   *
*                      job log that a Message Listener Port    *
*                      has started successfully or that a      *
*                      Message Listener Port has stopped       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Messages to the job log informing the user that a listener
port has started or stopped would be useful.
Problem conclusion
We now issue an informational message, WMSG0042I, to the job log
when a Message Listener Port has started successfully.  We
issue the WMSG0043I message when the Listener Port has stopped
and instruct the user to look for exceptions previous to this
message if the listener port has stopped unexpectedly.

We also added the new message, WMSG0058I, to appear in the event
that an MDBListener restart has been scheduled, and the new
message, WMSG0059E, to appear in the event that the MDBListener
retry limit has been reached.

APAR PQ97253 is associated with SERVICE LEVEL W502026 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ97253
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 2004-11-16
Closed date 2005-03-21
Last modified date 2007-08-21

APAR is sysrouted FROM one or more of the following:
PQ97251

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 UK01700    UP05/03/24 P F503

  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: swg1PQ97253.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 #: PQ97253
IBM Group: Software Group
Modified date: Aug 21, 2007