on 09-18-2014 9:07 PM
Hi,
When I start my NetWeaver server through command line, it fails with exit code 2. The reason is because the jstart process stops and starts itself a few times. I noticed this behaviour when kicking off the command and then "viewing" the start in sapmmc.
The arguments I am passing into the command line is:
-nr <instance number>
-prot PIPE
-function StartWait 300 0
What happens afterwards is as follows:
StartWait
process jstart J2EE Server not running
After I see "process jstart J2EE Server not running", I immediately view sapmmc and noticed jstart is stopped. A few seconds afterwards, jstart starts and stops again and then starts up successfully.
As a result of this behaviour, starting my NetWeaver server via command line is always unsuccessful. I have to resort to sapmmc.
Any idea on what the problem is? I hope it's clear what I wrote.
Thanks,
Jonathan
hi
please submit trace files from
/usr/sap/SID/J*/work directory
specially DEV* , STD *
regards
Dishant.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check the trace files in the /usr/sap/SID/DVEBMGS<NN>/work directory.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.