PK05362: SAME-NAMED LISTENER PORTS THAT EXIST ON DIFFERENT MULTIPLE SERVERS CAUSE PROBLEMS WHEN RE-STARTING THESE PORTS

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When the customer attempted to re-start his Message
Listener Port via the admin console, it showed started but
was not. The following message did not ever show up in his log:
Trace: 2005/03/01 21:29:56.560 01 t=8D3410 c=UNK key=P8
   FunctionName: com.ibm.ejs.jms.listener.MsgListenerPort
   SourceId: com.ibm.ejs.jms.listener.MsgListenerPort
   Category: ENTRY
   ExtendedMessage: start
When examining this customer's logs, it was seen that the
Trace: 2005/03/30 15:11:26.105 01 t=7BE210 c=1883.19 key=P8
      FunctionName: com.ibm.ws.management.AdminServiceImpl
      SourceId: com.ibm.ws.management.AdminServiceImpl
      Category: EXIT
      ExtendedMessage: queryNames;
was not returning the expected port name but instead three
results from three different servers. The first one returned
in the list was being used by the admin console code, but
was not the one for the server that was really supposed to be
returned.
Local fix
Make Message Listener Port names unique across all servers.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Starting and stopping Message Listener  *
*                      Ports at the Administrative Console     *
*                      may not work when multiple servers have *
*                      listener ports with the same name.      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Message Listener Port names need not be unique across multiple
application servers.  If multiple servers have listener ports
with the same name and the Administrative Console is used to
start or stop one of these ports (Servers > Application Servers
> serverName > Message Listener Service > Listener Ports), the
start or stop command may not be issued for the desired port.
For example, the Administrative Console may give a message
saying the listener port has been started but the status will
indicate it is stopped.
Problem conclusion
An internal query by the Administrative Console was not
adequately qualified and resulted in commands sometimes being
issued for the wrong listener port.  The internal query has now
been made server-specific, so Listener Port start and stop
commands are directed to the correct resource.

APAR PK05362 is associated with SERVICE LEVEL W502031 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PK05362
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 2005-05-05
Closed date 2005-06-20
Last modified date 2005-07-01

APAR is sysrouted FROM one or more of the following:

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 UK04679    UP05/06/28 P F506

  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: swg1PK05362.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 #: PK05362
IBM Group: Software Group
Modified date: Jul 1, 2005