Knowledge Collection: WebSphere Application Server Messaging Engine startup problems and their solutions

Education


Abstract

This Knowledge Collection is a compilation of links to the most frequently accessed technotes and webcast replays dealing with Common Messaging Engine (ME) starting problems and their solutions.

Most of the Messaging Engine starting problems are caused by either configuration or runtime issues or both. Many of these problems can be resolved on your own very easily without calling IBM Support to open a Problem Management Record (PMR).

This document has good vital information about what are the most common reasons that could lead to a Messaging Engine not being able to start.

Content

Directory of items within this Knowledge Collection

Technotes

Webcast Replays

Other Useful Links for Messaging Engine

Other Knowledge Collections for WebSphere Application Server


Technotes



1. CWSIS1535E The messaging engine's unique id (ME_UUID) does not match that found in the data store. (1608913)
When trying to start a WebSphere Application Server Messaging Engine, it fails to start and in the SystemOut.log you see this error: CWSIS1535E: The messaging engine's unique id does not match that found in the data store.

2. Messaging Engine does not start. No errors or exceptions in the SystemOut.log related to the problem (1609567)
Your WebSphere Application Sever Messaging Engine does not start and you do not see any errors or exceptions in SystemOut.log; not even messages indicating an attempt to start the Messaging Engine.

3. Messaging Engine does not start. Exception: CWSIS1524E, specified data source not found. (1609726)
WebSphere Application Server (WAS) Messaging Engine (ME) does not start. Exception: CWSIS1524E, specified data source not found.

4. Messaging Engine starting problem with the error message: CWSOM1042E (1609496)
Your WebSphere Application Server Messaging Engine is not starting. You see the following errors in SystemOut.log:
CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.PersistenceException: Unexpected exception caught starting persistent message store
CWSOM1042E: ObjectStore=AbstractObjectStore(/ /*)/ (ObjectStore) was asked to allocate space for ManagedObject=ManagedObject(null/null)/Constructed/ (ManagedObject) when it was full.
CWSIS1574E: The file stores permanent store file is full.
CWSOM0003I: ObjectManager using logFile / /Log has shut down.
CWSID0035E: Messaging engine cannot be started; detected error reported

5. CWSIS1519E error occur when Messaging Engine failed to obtain lock on failover in clustering environment (1608885)
Your WebSphere Application Server Message Engine (ME1) did not release a data store lock when it failed. Now a new instance of the Message Engine (ME2) can not obtain the lock and issues message CWSIS1519E: Messaging engine MyCluster.000-MyBus cannot obtain the lock on its data store after fail over to other server in a clustering environment.

6. The messaging engine's instance unique id (INC_UUID) does not match that found in the data store in clustering fail over environment (1608951)
You are seeing the following error message generated in the SystemOut.log during a WebSphere Application Server clustering fail over scenario for your Messaging Engine.
CWSIS1535E: The messaging engine's unique id does not match that found in the data store. ME_UUID=ME1, INC_UUID=INC1, ME_UUID(DB)=ME1, INC_UUID(DB)=INC2 (ME_UUID is same, where as INC_UUID is different in this case)

7. The messaging engine's unique ID does not match that found in the data store (1328985)
In WebSphere, if a bus member is removed and re-added to the same bus, the message engine will not start and errors will be seen in the systemout logs.

8. Messaging Engine fails to start (1407516)
Messaging Engine failed to start with the following error messages in the logs: CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.PersistenceException:
CWSIS1501E: The data source has produced an unexpected exception: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -552, SQLSTATE: 42502, SQLERRMC: WPSADMIN;CREATE SCHEMA...
CWSID0035E: Messaging engine XYZ cannot be started; detected error reported during com.ibm.ws.sib.msgstore.impl.MessageStoreImpl start() 00000028 SibMessage CWSID0027E: Messaging engine XYZ cannot be restarted because a serious error has been reported.

9. CWSOM1017E: Unable to access log file (file store location) while starting Messaging Engine (1609458)
WebSphere Application Server (WAS) Messaging Engine fails to start. The following errors occurred in the SystemOut.log file:
CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.PersistenceException: Unexpected exception caught starting persistent message store:
CWSOM1017E:ObjectManagerState=ObjectManagerState( )/Stopped ManagedObject(0/0)/Ready/ (ObjectManagerState) caught exception= (Exception) trying to locate or create log file name={2}(String).
CWSID0035E: Messaging engine cannot be started; detected error reported during com.ibm.ws.sib.msgstore.impl.MessageStoreImpl start()
CWSID0027E:Messaging engine cannot be restarted because a serious error has been r

10. Unable to access data store due to security reasons while starting Messaging Engine (1610262)
WebSphere Application Server (WAS) Messaging Engine is not starting and the following errors are thrown in the SystemOut.log:
CWSIS1501E, SQL30082N with database security error codes 08001 and -30,082.
CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1501E: The data source has produced an unexpected exception: java.sql.SQLException: SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -30,082

11. CWSIT0019E and CWSIT0103E errors: No suitable messaging engine is available errors returned to application even though Messaging Engine is running (1608705)
CWSIA0241E, CWSIT0019E and CWSIT0103E errors are returned to client . These errors are seen in the SystemOut.log even though Messaging Engine (ME) is running in one of the messaging cluster servers.

12. WebSphere Application Server Service Integration Bus messaging engine startup fails with ORA-28000 error (1610676)
After restarting WebSphere Application Server (WAS), the messaging engine fails to start and throws the following error:
CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.PersistenceException:CWSIS1501E: The data source has produced an unexpected exception: java.sql.SQLException: ORA-28000: the account is locked DSRA0010E: SQL State = 99999, Error Code = 28,000

13. WebSphere Application Server v6.1 Service Integration Bus messaging engine fails to start due to java.lang.ClassNotFoundException (1610048)
On restarting Websphere Application server, messaging engine fails to start and throws java.lang.ClassNotFoundException

14. WebSphere Application Server Service Integration Bus messaging engine startup fails with java.sql.SQLException: ORA-01031:insufficient privileges (1611118)
On restarting Websphere Application Server, the Service Integration Bus messaging engine fails to start due to java.sql.SQLException: ORA-01031:insufficient privileges


Webcast Replays


1. Webcast replay: WebSphere Application Server - Messaging Engine startup problems (7013517)
This IBM WebSphere Support Technical Exchange is designed to address Service Integration Bus Messaging Engine start-up problems and solutions - specifically common Messaging Engine startup failures and how to identify a proper Messaging Engine startup. Solutions to common startup failures are also presented.

2. Webcast replay: WebSphere Application Server - Service Integration Bus Messaging Engine Data Store Connectivity Problems and Solutions (7020333)
This WebSphere Support Technical Exchange is designed to describe how Service Integration Bus Messaging Engines connect to data stores and how to recover from unexpected disconnections from data stores.

3. Webcast replay: WebSphere Application Server - Message Store Overview (7016476)
This WebSphere Support Technical Exchange discusses SIB Message Stores, possible Message Store configurations, how Message Stores work, and common Message Store problems and solutions in WebSphere Application Server.

4. Webcast replay: WebSphere Default Messaging Provider: Concept and Architecture Overview (7019098)
This WebSphere Support Technical Exchange is designed to present an overview of the concepts, architecture of the Service Integration Bus, an implementation of the Default Messaging Provider in WebSphere Application Server V6 and V7.

5. Ask the Experts Replay: Service Integration Bus Scalability Best Practices (7021025)
The Service Integration Bus messaging provider in WebSphere Application Server can scale from a single server up to large environments with multiple clusters. This Ask the Experts session discusses best practices for exploiting the scalability of the Service Integration Bus to improve performance.

6. Webcast replay: SSL Configuration of the Java EE Application Client and the WebSphere Application Server V7 Service Integration Bus (7019792)
This WebSphere Support Technical Exchange is designed to provide a step-by-step walkthru of the SSL configuration for the Java EE Application Client and WebSphere Application Server V7 Service Integration Bus.

7. Webcast replay: External messaging clients for the Service Integration Bus in WebSphere Application Server (7016041)
This WebSphere Support Technical Exchange is designed to offer detailed explanation of the various external messaging clients available for the Service Integration Bus in WebSphere Application Server V6.x and V7.


Other useful links for Messaging Engine


1. Tuning the WebSphere Service Integration Bus Heartbeat Properties (1422114)
What are the properties 'com.ibm.ws.sib.jfapchannel.HEARTBEAT_INTERVAL' and 'com.ibm.ws.sib.jfapchannel.HEARTBEAT_TIMEOUT' and how do you tune them?

2. IBM Service Integration Bus Destination Handler, Version 1.1 (4021439)
A tool to view, move, copy, delete, save and restore messages in the default messaging provider for IBM WebSphere Application Server versions 7.0, 6.1, and 6.0.

3. How to setup a Service Integration Bus to send an MQRFH2 back through WebSphere MQ (1396144)
If a WebSphere Application Server application is configured to accept an MQRFH2 in a Request/Reply message scenario, how do you send an MQRFH2 header back to the ReplyToQueue if the same path may be used for messages where the MQRFH2 cannot be sent back?

4. Current transaction errors occur when you start the server (1237714)
If you restart a server while performing messaging with a service integration bus, you might see the following error message in the system out log file (SystemOut.log) on distributed platforms, or in output of the appropriate job log on z/OS: CWSIP0671E: The destination destination_name on messaging engine messaging_engine_name failed to be initialized for maintaining order. Several instances of this message might occur during server restart.

5. Troubleshooting Service integration in WebSphere Applicaiton Server V7.0
This page in the Information Center provides a starting point for finding information about service integration.

6. Messaging engine troubleshooting tips
Use this set of specific tips in the Information Center to help you troubleshoot problems with service integration messaging engines.




Other Knowledge Collections for WebSphere Application Server


1. Knowledge Collection: Migration planning for WebSphere Application Server (7008724)

2. Knowledge Collection: Migrating to (or from) WebSphere Application Server V8.0 (7008725)

3. Knowledge Collection: Migrating from other Application Servers to WebSphere Application Server (7008729)

4. Knowledge Collection: IBM Support Newsletters (7011428)

5. Knowledge Collection: Java Message Service (JMS) for WebSphere Application Server (7020347)

6. Knowledge Collection: Plug-in for WebSphere Application Server (7021301)

7. Knowledge Collection: Out of Memory OOM for WebSphere Application Server (7021664)

8. Knowledge Collection: Migrating to WebSphere Application Server V8.5 (7008727)

9. Knowledge Collection: Migrating from WebSphere Application Server V6.1 (7008728)

10. Knowledge Collection: Migrating to (or from) WebSphere Application Server V7.0 (7013842)


Definition of a Knowledge Collection
A Knowledge Collection is a focused compilation of links to documents that share a common theme. Knowledge Collections are navigation aids that organize content to help users quickly find relevant information. Knowledge Collections are not designed to be an all-inclusive list of all documents dealing with the specific theme.

Cross reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere MQ Service Integration Technologies /SIB
Business Integration IBM Business Monitor
Business Integration IBM Business Process Manager Standard
Business Integration WebSphere Enterprise Service Bus
Business Integration WebSphere Lombardi Edition
Business Integration WebSphere Partner Gateway Advanced Edition
Business Integration WebSphere Partner Gateway Enterprise Edition
Business Integration WebSphere Process Server
Business Integration WebSphere Service Registry and Repository

Product Alias/Synonym

WebSphere Application Server WAS SIB SIBUS SI BUS

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
Service Integration Technology

Software version:

6.0, 6.0.2, 6.1, 6.1.0.9, 7.0, 8.0, 8.5

Operating system(s):

AIX, HP-UX, IBM i, Linux, Solaris, Windows, i5/OS

Software edition:

Advanced, Base, Express, Network Deployment, Single Server

Reference #:

7036148

Modified date:

2013-01-31

Translate my page

Machine Translation

Content navigation