Embedded JMS provider

Use the resources listed below to determine the cause of problems that occur when using the embedded JMS provider within WebSphere Application Server.

• Ensure that you do not have a WebSphere Application Server Version 5.1 instance running with the same instance name as your Version 5.0.x instance. If you do have a Version 5 instance with the same name as a Version 5.1 instance, the following error appears in the SystemOut.log file when you try to start the second instance:

  Starting the Queue Manager
  Start Queue Manager command failed with exit code: 24

  See Use embedded JMS with your applications in the Administration topic for more information.

• Check the application server standard output and standard error log files for errors. For information on the application server log files and where they are located, see WebSphere Application Server log files.

• If you are using publish/subscribe messaging model, check the WebSphere Embedded Messaging publish and Subscribe (WEMPS) event log. The file name of the log is wemps_event.log and the file is located in Integrated File System directory /QIBM/UserData/WebAS5/wemps/log

• Read the release notes. WebSphere Application Server Release Notes (http://publib.boulder.ibm.com/was400/docs/relnotes502.html) .

• Check the WebSphere Application Server FAQ database .

• Refer to the WebSphere Application Server for iSeries newsgroup .
  This iSeries Technical Support Web-based forum is dedicated to WebSphere Application Server for iSeries.

• Contact IBM support. For more information, see Get support for WebSphere Application Server.