Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Messaging engine encountered an exception while starting

 
Ranch Hand
Posts: 128
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
author and cow tipper
Posts: 5006
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Ranch Hand
Posts: 126
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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

 
Ranch Hand
Posts: 446
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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,
 
I'm not sure if I approve of this interruption. But this tiny ad checks out:
Garden Master Course kickstarter
https://coderanch.com/t/754577/Garden-Master-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic