GeeCON Prague 2014*
The moose likes Websphere and the fly likes Messaging engine encountered an exception while starting Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Products » Websphere
Bookmark "Messaging engine encountered an exception while starting " Watch "Messaging engine encountered an exception while starting " New topic
Author

Messaging engine encountered an exception while starting

Arulanand Dayalan
Ranch Hand

Joined: Aug 10, 2005
Posts: 124
Hi,
We are facing issues in configuring a Bus in WAS 6.0 in clustered environment. We created Bus and attached three Servers as Bus Members. When start the Server the messaging engines are not getting started. We are getting the below exception,

Caused by: [6/5/09 14:36:27:147 CDT] 00000020 SibMessage E [SCABUS:qa-Node02.qa-Node02-SCABUS] 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.ws.sib.msgstore.persistence.DatasourceWrapperStateException: New connections cannot be provided because the persistence layer has been stopped
at com.ibm.ws.sib.msgstore.persistence.impl.PersistentMessageStoreImpl.start(PersistentMessageStoreImpl.java:188)
at com.ibm.ws.sib.msgstore.impl.MessageStoreImpl.start(MessageStoreImpl.java:1175)
at com.ibm.ws.sib.admin.impl.JsMessagingEngineImpl.start(JsMessagingEngineImpl.java:491)
at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.activate(HAManagerMessagingEngineImpl.java:967)
at com.ibm.ws.sib.admin.impl.JsActivationThread.run(JsActivationThread.java:89)
Caused by: com.ibm.ws.sib.msgstore.persistence.DatasourceWrapperStateException: New connections cannot be provided because the persistence layer has been stopped
at com.ibm.ws.sib.msgstore.persistence.impl.WASConnectionManagerWrapper.getLockConnection(WASConnectionManagerWrapper.java:323)
at com.ibm.ws.sib.msgstore.persistence.impl.WASConnectionManagerWrapper.getConnection(WASConnectionManagerWrapper.java:255)
at com.ibm.ws.sib.msgstore.persistence.impl.DatasourceController.performFirstAction(DatasourceController.java:177)
at com.ibm.ws.sib.msgstore.persistence.impl.TableManager.initialize(TableManager.java:231)
at com.ibm.ws.sib.msgstore.persistence.impl.PersistentMessageStoreImpl.start(PersistentMessageStoreImpl.java:182)
... 4 more


Please let us know what we need to resolve this. Thanks in advance.

Regards,
Arul.
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper

Joined: Aug 26, 2006
Posts: 4968
    
    1

It looks like trouble with the underlying datasource. Is the database started? Can you access your JDBC connections through a JNDI lookup? Is the connection pool configured and running? That's the first place I'd look.

-Cameron McKenzie
Anant Rao
Ranch Hand

Joined: Nov 12, 2004
Posts: 126
When message engine connects to the database it updates with a unique id in the tables. If you try to use the same database for another ME it will throw an exception.

In your case either build a new ME database or rebuild the existing one, it should solve the problem.


Anant

Deepak Pant
Ranch Hand

Joined: Feb 13, 2004
Posts: 443
Another way to troubleshoot this would be to use file based store for message store. This way all the messaging engines will have different file stores. If this config works then you can focus on the datastore issue. If this doesnt work then you have something else messed up as well.

Until next time,
 
GeeCON Prague 2014
 
subject: Messaging engine encountered an exception while starting