BrokerCommandFailedException when starting V5.0 Application Server with embedded messaging broker
 Technote (troubleshooting)
 
Problem(Abstract)
On Windows® platforms, if you use the Administrator user ID for the WebSphere® Application Server V5.0 embedded messaging event broker, starting the Application Server listener port might result in a BrokerCommandFailed exception. The error occurs during openSubscription.
 
Cause
Full text of the error message:

[8/1/03 10:38:45:250 EDT] 1b2c6c1a MDBListenerIm W WMSG0019E:
Unable to start MDB Listener StateEightTopic, JMSDestination jms/MainTopic :
com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: 3008
Reason code 3008

This is a WebSphere Application Server embedded messaging broker limitation.
 
Resolving the problem
The Event Broker supports user IDs of only twelve characters for Windows® platforms and eight characters for any other platform. The advice in the Event Broker manual is to create user IDs that are a maximum of eight characters, unless you know that the network includes only Windows, in which case you can use a maximum of twelve.
 
 
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 2 Connectivity (J2C)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1137325
IBM Group: Software Group
Modified date: Aug 9, 2004