PQ74005: WSADMIN creating a config that prevents WAS restarting when creating a ListenerPort | |||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description I'm creating a ListenerPort within my server's Message Listener Service. The command "$AdminConfig required ListenerPort" returns name, connectionFactoryJNDIName and destinationJNDIName. Creating a ListenerPort with only these 3 attributes will appear to have been successfull. However when the server is stopped and restarted, the server actually refuses to start. The systemOut.log contains this: [13/01/03 15:50:46:078 GMT] 6a64981d WsServer E WSVR0003E: Server server1 failed to start java.lang.NullPointerException at com.ibm.ejs.jms.listener.MsgListenerPort.<init>(MsgListenerPort. java:123 ) at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.initialize(MDBLi stenerMa nagerImpl.java:159) at com.ibm.ws.runtime.component.MessageListenerImpl.initialize(Mess ageListe nerImpl.java:106) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(C ontainer Impl.java:507) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents( Containe rImpl.java:432) at com.ibm.ws.runtime.component.EJBContainerImpl.initialize(EJBCont ainerImp l.java:323) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(C ontainer Impl.java:507) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents( Containe rImpl.java:443) at com.ibm.ws.runtime.component.ApplicationServerImpl.initialize(Ap plicatio nServerImpl.java:68) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(C ontainer Impl.java:507) at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents( Containe rImpl.java:443) at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.ja va:95) at com.ibm.ws.runtime.WsServer.start(WsServer.java:126) at com.ibm.ws.runtime.WsServer.main(WsServer.java:232) at java.lang.reflect.Method.invoke(Native Method) at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94) [13/01/03 15:50:46:125 GMT] 6a64981d WsServer E WSVR0009E: Error occurred during startup Because the server has not started, it is not possable toLocal fix administer the server, via the wsadmin command or GUI. In fact the only way to get the server running again is to find the relavent xml file and remove the definition of the ListenerPort. Through, less than painstaking, trial and error , I I discovered that the missing attribute is a StateManageable object. This object has the required attribute initialState, an enumerable type of either START or STOP. Creating this object with the ListenerPort as parent, solves the problem. LOCAL FIX:ン Manually Edit config to remove the ListenerPort definitionProblem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users of the * * wsadmin client * **************************************************************** * PROBLEM DESCRIPTION: Application Server does not start * * after create ListenerPort with wsadmin * **************************************************************** * RECOMMENDATION: * **************************************************************** Customer creates a ListenerPort within server's Message Listener Service. The wsadmin command "$AdminConfig required ListenerPort" returns name, connectionFactoryJNDIName and destinationJNDIName. Creating a ListenerPort with only these 3 attributes will appear to have been successfull, however the server failed to start/restart. The systemOut.log contains this: [13/01/03 15:50:46:078 GMT] 6a64981d WsServer E WSVR0003E: Server server1 failed to start java.lang.NullPointerException at com.ibm.ejs.jms.listener.MsgListenerPort.(MsgListenerPort. java:123).Problem conclusion Root cause is missing attribute StateManageable object. Solution provided in this fix creates a template for ListenerPort, so that if the StateManageable attribute is not set, it will create one for user with initialState START.Temporary fix pq74005_fix.jarComments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ74005
IBM Group: Software Group
Modified date: Jul 1, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.