SAP XI/PI: Error restarting JMS subsystem

[fanglin_ye]

Hello,

i'm using SAP XI/PI 7.11. Recently i have met one problem: in the default trace file there is a error, which every 10 mins occurs once.

Error restarting JMS subsystem; will retry in 00:00:10.000.
[EXCEPTION]
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/TopicConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:184)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:489)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:361)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:659)
at com.redwood.scheduler.cluster.messaging.JMSMessaging.loadJndiObject(JMSMessaging.java:784)
at com.redwood.scheduler.cluster.messaging.JMSMessaging.loadConnectionFactory(JMSMessaging.java:801)
at com.redwood.scheduler.cluster.messaging.JMSMessaging.startJMS(JMSMessaging.java:623)
at com.redwood.scheduler.cluster.messaging.JMSMessaging.restartJMS(JMSMessaging.java:866)
at com.redwood.scheduler.cluster.messaging.JMSMessaging.access$6(JMSMessaging.java:830)
at com.redwood.scheduler.cluster.messaging.JMSMessaging$2.run(JMSMessaging.java:510)
at java.lang.Thread.run(Thread.java:708)

who knowns how to resolve the problem. thx.

Best Regards,

Fanglin

[former_member407376]

Hello Fanglin Ye,

after some playing with our test pi (start & stop) this error appeared there too.

After i stopped both server and started them at the same time again the error doesnt appear anymore (for ~ 30 minutes now).

Because this error doesnt appear in our test pi till i stopped an single applicationserver it think it will appear again when i stop one server.

I will try to recreate this situation and update my post.

Best Regards

Tobias Rode

_________________________________________________________________

Here my new information:

I was able to recreate this error. First some information about our system:

2x applicationserver abap+java

1x abap central services

1x java central services

1x abap replicated

1x java replicated

I was able to stop the second applicationserver and start it again.      -> No error appears.

Stop the first applicationserver and start it again.                              -> The jms error appears.

I had to stop both server and start them again to fix the error.

During my tests i get this situation on server 1 and server 2. I think there are some java components or application which run primary on one server. If i stop this server the remaining server isn't able to start this parts and/or is not able to take over all this functions.

Message was edited by: Tobias Rode

[former_member407376]

Hello Fanglin Ye,

we have since 6-8 month the same problem. Cause there are no impacts to our PI 7.11 we just ignored this "Error".

I looked into our enqueuetable, but there are only locks which generated during the last server reboot.

So the sap note posted by Ram pranav was not the solution in our case.

Best Regards

Tobias Rode

[Former Member]

Check sap note 1230216

(JMS) Dangling JMS Lock in the Enqueue server - Technology Troubleshooting Guide - SCN Wiki

What is the version of Legacy JMS server.

[fanglin_ye]

Hi Ram,

could you please tell me how to find the version of the legacy JMS server?

Best regards,

Fanglin Ye

[Former Member]

We need to ask legacy team for there JMS version. There might be specific issues with versions. We can find more on ibm help portal.

Are you connecting to topic or queue (Observed in error description : jmsfactory/default/TopicConnectionFactory)

Did you install all the legacy jar files in PI.