PK14442: PMI0023W messages appear in the WebSphere SystemOut.log file when using WebSphere Application Server Version 5.x | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When using message-driven beans (MDBs) running inside of WebSphere Application Server Version 5., the following warning message occassionally appears in the application server's SystemOut.log file: PmiRegistry W PMI0023W: Unable to register PMI module due to duplicate name: <name>Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The warning message PMI0023W may appear * * in WebSphere Application Server for * * z/OS servant output unnecessarily. * * * * Also, the "MDB Stats" DISPLAY WORK * * commands do not work correctly on a * * newly started ListenerPort. * * * * Also, if MDB trace is enabled, a * * second ListenerPort 'stop' command * * can fail. * **************************************************************** * RECOMMENDATION: * **************************************************************** When running with PMI statistics enabled and running MDB applications, an unnecessary message like the following may appear in the servant job output, even though the duplication is caused in this case by WebSphere Application Server for z/OS code attempting to register the module for a second time: PMI0023W: Unable to register PMI module due to duplicate name: <name> Also, a ListenerPort starting after MDB stats collection has been enabled will not display the correct statistics when the DISPLAY WORK command is subsequently issued. This applies to both a new ListenerPort and a ListenerPort stopped then started after the MDB stats collection is enabled through the console command: F <server>,MDBSTATS,ENABLE The display work command: F <server>,DISPLAY,WORK,MDB,STATS will show incorrect values for stats: TIME, TOTAL, EXCS, BLOCKS Also, when MDB tracing is enabled (at the 'debug' trace level, specifically), and a ListenerPort 'stop' command is issued, the 'stop' command can return an error message. Functionally there is no failure since the ListenerPort is already stopped. The user using the Administrative Console to deliver the second 'stop' will get a message in the Administrative Console GUI: "Listener port <name> could not be stopped." The user using wsadmin scripting to deliver the second 'stop' command will get a message like: WASX7015E: Exception running command: "AdminControl.invoke(mylp,"stop")"; exception information: javax.management.RuntimeMBeanException java.lang.NullPointerException: java.lang.NullPointerExceptionProblem conclusion PMI registration is moved strictly to the EJB container so that MDB code does not mistakenly deliver a duplicate registration. MDB Stats enablement processing fixed to cover newly-starting ListenerPorts. MDB tracing fixed to eliminate stop() failure. APAR PK14442 is associated with SERVICE LEVEL W502036 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PK14441 APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK14442.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 #: PK14442
IBM Group: Software Group
Modified date: Aug 21, 2007
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.