IDP_JMS_Bus / messaging engine failure on new install

[Mark_Lindberg]

Greetings:

I am trying to get a new install of 8.2 in a WebSphere 6.1 Win 2003 / SQLServer clustered environment up and running.

Currently the IDP_JMS_Bus will not start, and the SystemOut messages point to "No Messaging Engines running".

I have tried to start the engine, to no avail over multiple reboots.

This install took a number of tries to complete due to installation errors.

The first message in SystemOut around this is:

[5/12/10 10:52:40:359 CDT] 0000003a SibMessage    W   [:] CWSIV0775W: The creation of a connection for destination adobe_PECommandQueue on bus IDP_JMS_Bus for endpoint activation [com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation@39723972 <active=true> <connections={}> <messageEndpointFactory=com.ibm.ejs.container.MessageEndpointFactoryImpl@9496c24e> <endpointConfiguration=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl$JmsJcaEndpointConfigurationImpl@1642750442 <JmsJcaActivationSpecImpl.this=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl@1866755908 <userName=null> <password=null> <xaRecoveryAlias=null> <destination=queue://adobe_PECommandQueue?deliveryMode=Persistent&busName=IDP_JMS_Bus> <durableSubscriptionHome=null> <destinationType=javax.jms.Queue> <messageSelector=null> <acknowledgeMode=Auto-acknowledge> <subscriptionDurability=NonDurable> <shareDurableSubscriptions=InCluster> <clientId=null> <subscriptionName=null> <maxBatchSize=1> <maxConcurrency=10> <busName=IDP_JMS_Bus> <shareDataSourceWithCMP=false> <targetTransportChain=null> <readAhead=Default> <target=null> <targetType=BusMember> <targetSignificance=Preferred> <providerEndpoints=null>]>]> <endpointInvoker=com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl@68f268f2> <workManager=com.ibm.ejs.j2c.work.WorkManagerImpl@170e170e> <endpointMethodTransactional=true> <remoteConnection=null> <remoteDestination=true> <timer=java.util.Timer@4c0c4c0c>] failed with exception com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus IDP_JMS_Bus running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=IDP_JMS_Bus, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundBasicMessaging, proximity=Bus..

Then:

[5/12/10 10:52:46:266 CDT] 0000003b SibMessage    W   [:] CWSIV0775W: The creation of a connection for destination Default.Topic.Space on bus IDP_JMS_Bus for endpoint activation [com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation@12521252 <active=true> <connections={}> <messageEndpointFactory=com.ibm.ejs.container.MessageEndpointFactoryImpl@7aff2ec6> <endpointConfiguration=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl$JmsJcaEndpointConfigurationImpl@303436310 <JmsJcaActivationSpecImpl.this=[com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl@1680368680 <userName=null> <password=null> <xaRecoveryAlias=null> <destination=topic://adobe_TaskEventTopic?busName=IDP_JMS_Bus> <durableSubscriptionHome=null> <destinationType=javax.jms.Topic> <messageSelector=null> <acknowledgeMode=Auto-acknowledge> <subscriptionDurability=NonDurable> <shareDurableSubscriptions=InCluster> <clientId=null> <subscriptionName=null> <maxBatchSize=1> <maxConcurrency=10> <busName=IDP_JMS_Bus> <shareDataSourceWithCMP=false> <targetTransportChain=null> <readAhead=Default> <target=null> <targetType=BusMember> <targetSignificance=Preferred> <providerEndpoints=null>]>]> <endpointInvoker=com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl@12441244> <workManager=com.ibm.ejs.j2c.work.WorkManagerImpl@170e170e> <endpointMethodTransactional=false> <remoteConnection=null> <remoteDestination=true> <timer=java.util.Timer@12bc12bc>] failed with exception com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus IDP_JMS_Bus running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=IDP_JMS_Bus, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundBasicMessaging, proximity=Bus..

This is followed by numerous connection creation failure messages.

Can anyone provide pointers on how to correct this installation?

I have received advice to down the cluster, delete the SIB tables, and restart the cluster, but I do not want to try this without some verification that that is advisable.

Thank You in advance!

Mark

[JayanKandathil]

A "messaging engine" is hosted by a WebSphere application "server" instance or cluster of instances.  In the case of a LiveCycle cluster, we recommend that a separate appserver cluster be created to host just the WebSphere messaging engine.

Is that done?  Have you started that JMS cluster (it is separate from the cluster you create for LiveCycle)?

[Mark_Lindberg]

Hello Jayan:

Thanks for your reply.

For an overview, the cluster is made of 2 cells lc8_jms_cluster, and lc8_cluster

From the WebSphere console, all members are up and running.

Does this answer your question?

Thanks Again.

Mark

[JayanKandathil · Accepted solution]

If that's the case, it looks like the messaging engine is having trouble getting an exclusive lock on its mesage store tables in the DB (that all start with SIB*):

http://blogs.adobe.com/livecycle/2007/07/what_are_those_sibtables_in_my.html

Since this is a new install, you can safely drop them.  Shut down the JMS cluster members, drop all SIB tables, and then start them.  Watch the SystemOut.log of the cluster members for messages that tell you that the messaging engine has acquired an exclusive lock on the tables.  Only one of the cluster members will have this (since the messaging engine is a singleton and can run on either but not both of the JMS cluster members).  If you see that message, check the DB - the SIB tables should be re-created, and you should no longer have this partcular trouble.

Essentially, the MEUUID in the SIBOWNER table and the Messaging Engine's UUID (as determined from the WAS console) should match.

[Mark_Lindberg]

Dropping the tables, and restarting the cluster started the Bus and Engine.

Thank You Jayan