WSVR0003E: Server jmsserver failed to start com.ibm.ws.exception.ConfigurationError: MessageListenerService - no thread pool defined
 Technote (troubleshooting)
 
Problem(Abstract)
If the Listener Port is defined on the JMS Server Message Listener Service, the server.xml file for the JMS Server becomes corrupt and the JMS Server fails to start with the following exception:

WSVR0003E: Server jmsserver failed to start
com.ibm.ws.exception.ConfigurationError: MessageListenerService - no thread pool defined.
 
Symptom
The error message:

[3/29/04 23:16:56:618 GMT] 18cb3a SecurityCompo I SECJ0309I: Java 2 Security is disabled.

[3/29/04 23:16:56:634 GMT] 18cb3a SecurityCompo I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
[3/29/04 23:16:56:678 GMT] 18cb3a SecurityCompo I SECJ0240I: Security service initialization completed successfully
[3/29/04 23:16:57:714 GMT] 18cb3a WsServer E WSVR0003E: Server jmsserver failed to start
com.ibm.ws.exception.ConfigurationError: MessageListenerService - no thread pool defined
at com.ibm.ws.runtime.component.MessageListenerImpl.initialize(MessageListenerImpl.java:68)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:706)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:632)
at com.ibm.ws.runtime.component.ApplicationServerImpl.initialize(ApplicationServerImpl.java:77)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:706)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:643)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

 
Cause
The ListenerPort must be defined under the Application Server Message Listener Service, not under the JMS Server Message Listener Server.
 
Resolving the problem
To fix this problem, modify the server.xml file for the JMS Server.


The server.xml file is located in:

Install_Root \config\cells\<cell-name>\nodes\<node-name>\servers\jmsserver\server.xml

Look for the following entry and remove it manually:

<services
xmi:type="applicationserver.ejbcontainer.messagelistener:MessageListenerService" xmi:id="MessageListenerService_1080600019019" enable="true"/>

Follow the IBM® WebSphere® Application Server V5.0 Information Center instructions for Administering listener ports ( Add/Modify/start/stop Listener Port).

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): Windows
Software version: 5.1.1
Software edition:
Reference #: 1176216
IBM Group: Software Group
Modified date: Aug 16, 2004