Question Re: Message server dev_ms under /usr/sap/SID/J00/work directory - JAVA system not starting in Technology Q&A

Message server dev_ms under /usr/sap/SID/J00/work directory - JAVA system not starting

senthilsap — Thu, 03 Sep 2020 16:45:12 GMT

Hi,

We are running NW 740 SP18 JAVA stack only, the j2ee is not getting started on our linux server.

No much in the logs.

We noticed the the dev_ms, dev_rd logs are getting created under /usr/sap/SID/J00/work directory, instead of getting created under /usr/sap/SID/SCS01/ work directory.

Can you one guide, why the dev_ms log file is changed here?

Re: Message server dev_ms under /usr/sap/SID/J00/work directory - JAVA system not starting

S_Sriram — Thu, 03 Sep 2020 16:51:44 GMT

Hi Murugan.

Is the system is additional java instance from the main Java CI?

Refer the blog to find the log https://blogs.sap.com/2016/07/11/basic-start-up-troubleshooting-java-the-logical-sequence/

Regards

Re: Message server dev_ms under /usr/sap/SID/J00/work directory - JAVA system not starting

senthilsap — Thu, 03 Sep 2020 18:42:34 GMT

Hi S Sriram,

This is the main instance (primary application server), we don't have any additional application server, the link provided by you don't have the required information for our issue.

Question is why does enque and message server logs gets created under J00 path instead of SCS01 path?

Noticed there is a softlink under work directory for ms.sap<SID>_SCS01 -> /usr/sap/J00/exe/msg_server (this is wrong), does anyone know where I can fix this?

Thanks

Re: Message server dev_ms under /usr/sap/SID/J00/work directory - JAVA system not starting

S_Sriram — Fri, 04 Sep 2020 03:14:11 GMT

Hi Murugan,

Is this Java instance installed in the cluster environment ? if it is yes then follow the SAP help portal link https://help.sap.com/saphelp_nwpi711/helpdata/en/48/0728f74c6a3837e10000000a42189b/frameset.htm

Regards

Re: Message server dev_ms under /usr/sap/SID/J00/work directory - JAVA system not starting

senthilsap — Thu, 10 Sep 2020 12:34:28 GMT

Thank you S Sriram, the issue got resolved, someone had edited the instance profile and hard coded DIR_INSTANCE path, so had to remove it to make it work.