JMS Service stops automatically

Hi,

We are encountering a strange issue with the Java Method Server's service. The service gets started without any problem but after a while (in 10-15 minutes) it would automatically stop.

As further analysis I found that the Windows event viewer shows following message at the time JMS service stops "The Documentum Java Method Server service terminated unexpectedly. It has done this 1 time(s).".

Also I found that even though the JMS service shows as stopped the URL to check the JMS running status does show the JMS status as running, it means the JMS remains up but the in the window service it shows as down. I also noticed in the Windows Task Manager that the 'dctmservice.exe' task gets killed when the JMS Service goes down while 'java.exe' keeps running which actually represents the JMS.

Below is the environment detail:

CS Version: 6.6

CS OS: Windows 2008 (64 bit)

Database: MS SQL 2005

Please let me know if anyone has any idea on why the JMS Service is getting unexpectedly terminated or is it some known bug in the D6.6.

Would appreciate a reply.

Thanks,

Abhishek Pandey

Find more posts tagged with

Comments

DCTM_Guru

Do you have SP2 applied to your Windows 2008?

rstein

Hi.

Take a look at %DOCUMENTUM%\jboss4.3.0\server\serviceConfig\MethodServer\DmMethodServerService.log. Maybe the process that starts the JMS is failing on its tests and shuts itself down leaving the JMS alive.

Regards,

Roney

meabhishek

Yeah, you are right in saying that the process which invokes the JMS is failing. We are not able to figure out why that process is failing !!

meabhishek

It's SP1 only.

rstein

Sometime after the JMS is started the serviceWrapper tests to verify if JMS is running. If this test fails it will shut itself down. Did you take a look at the DmMethodServerService.log? Does it show any errors?

DCTM_Guru

In the Content Server release notes for 6.6, it states

Windows Server

2008 SP2 (64-bit

version)

This is the tested and officially supported version. So I would apply SP2 and see if the problem still exists.

meabhishek

This problem is on DR environment only, on Prod it works fine; DR is the exact replica of Prod though.

mhtan

Hi Meabhishek, Did you ever dertermine the root cause and what you need to do to resolve the issue? Thanks!

seloum57

Hello,

I've the same issue as you, did you find out a solution ?

meabhishek

As it has been long when I encountered this problem, sorry, I am not able recall the resolution.

It was better had I logged the resolution here itself.