cancel
Showing results for 
Search instead for 
Did you mean: 

setting up JMS in a clustered SAP WAS 6.40

Former Member
0 Kudos

Hello all,

We are trying to start our app in the clustered SAP WAS 6.30 Patch Level 77737.313 and application start fails with a JMS Error:

Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: JMS error.

at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.loadDestination(ContainerImpl.java:1874)

at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.prepareStart(ContainerImpl.java:717)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:347)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:309)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:308)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.run(ParallelAdapter.java:73)

at com.sap.engine.frame.core.thread.Task.run(Task.java:60)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:72)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:126)

Caused by: javax.jms.JMSException: ConnectionFactory with name com.ttt.jms.TTTTopicFactory does not exist.

Same app starts up fine in a non-clustered environment.

The JMS error says that application can't find the specified JMS Factory name. So it can be an issue with JNDI replication.

The jms deployment descriptors we are using are:

<jms-factories>

<connection-factory>

<connection-factory-type>QueueConnectionFactory</connection-factory-type>

<factory-name>com.ttt.jms.TTTQueueFactory</factory-name>

<context-factory-type>

<link-factory-name>jmsfactory/TTT/com.ttt.jms.TTTQueueFactory</link-factory-name>

<initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>

</context-factory-type>

</connection-factory>

<connection-factory>

<connection-factory-type>QueueConnectionFactory</connection-factory-type>

<factory-name>com.ttt.jms.enterprise.TTTQueueFactory</factory-name>

<context-factory-type>

<link-factory-name>jmsfactory/TTT/com.ttt.jms.enterprise.TTTQueueFactory</link-factory-name>

<initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>

</context-factory-type>

</connection-factory>

<connection-factory>

<connection-factory-type>TopicConnectionFactory</connection-factory-type>

<factory-name>com.ttt.jms.TTTTopicFactory</factory-name>

<context-factory-type>

<link-factory-name>jmsfactory/TTT/com.ttt.jms.TTTTopicFactory</link-factory-name>

<initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>

</context-factory-type>

</connection-factory>

</jms-factories>

<jms-destinations>

<destination>

<connection-factory>com.ttt.jms.TTTTopicFactory</connection-factory>

<destination-name>com.ttt.jms.Topic1</destination-name>

</destination>

<destination>

<connection-factory>com.ttt.jms.TTTQueueFactory</connection-factory>

<destination-name>com.ttt.jms.Queue1</destination-name>

</destination>

<destination>

<connection-factory>com.ttt.jms.TTTQueueFactory</connection-factory>

<destination-name>com.ttt.jms.Queue2</destination-name>

</destination>

<destination>

<connection-factory>com.ttt.jms.enterprise.TTTQueueFactory</connection-factory>

<destination-name>com.ttt.jms.enterprise.Queue1</destination-name>

</destination>

<destination>

<connection-factory>com.ttt.jms.enterprise.TTTQueueFactory</connection-factory>

<destination-name>com.ttt.jms.enterprise.Queue2</destination-name>

</destination>

</jms-destinations>

JMS Provider is configured with JMS server TTT and corresponding 4 queue factories and 1 topic factory.

If you can see anything wrong with this configuration, I would really appreciate your comments.

Maybe there is something specific that must be configured for JMS in a clustered environment?

Thanks.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Yuri:

there may be cluster Q , check once or you should change the values in all cluster servers locally .