on 01-20-2014 11:49 AM
Hello,
I have downloaded a SAP demo system. Which is SAP 7.31 NW Java instance on Suse Linux.
Every thing went fine and server also started earlier.
But today when I tried to start this server I get below SAP status:
20.01.2014 17:15:10
GetProcessList
OK
0 name: igswd_mt
0 description: IGS Watchdog
0 dispstatus: GREEN
0 textstatus: Running
0 starttime: 2014 01 20 16:43:00
0 elapsedtime: 0:32:10
0 pid: 14127
1 name: jstart
1 description: J2EE Server
1 dispstatus: GRAY
1 textstatus: Stopped
1 starttime:
1 elapsedtime:
1 pid: 14126
20.01.2014 17:15:15
GetProcessList
OK
0 name: enserver
0 description: EnqueueServer
0 dispstatus: GREEN
0 textstatus: Running
0 starttime: 2014 01 20 16:42:47
0 elapsedtime: 0:32:28
0 pid: 12506
1 name: msg_server
1 description: MessageServer
1 dispstatus: GREEN
1 textstatus: Running
1 starttime: 2014 01 20 16:42:47
1 elapsedtime: 0:32:28
1 pid: 12505
2 name: gwrd
2 description: Gateway
2 dispstatus: GREEN
2 textstatus: Running
2 starttime: 2014 01 20 16:42:47
2 elapsedtime: 0:32:28
2 pid: 12507
As you see above, everything is in green status but J2EE server is Gray and Stopped.
When I opened SAP management console I found below error :
Connection to instance <instance name> failed. COnnection refused.
Exception : Connection timed out.
Please throw your valuable inputs.
Please check/attach dev_w0 log file.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My apologies. You uploaded correct file dev_server0. Can you also upload std_server0.out file? Relevant SAP KBA
Hi,
As per the std_server.out...
Loading [ThreadManager]... [689] ms
Loading [ClassLoaderManager]... [117] ms
Loading [ClusterManager]...
FATAL: Server process failed to start; manager [ClusterManager] could not be started
So you would be able to see more error in the default trace ..Please check the default trace or post it.
Most of the time it can be issue with the port..
Can you also provide me the details of SERVERCORE patch installed on the server.
Thanks
RishI abrol
Hi,
Please check if you can see the error described in the following KBA in the default traces
1840741 - J2EE System failed with error "Cannot open Join Port"
If yes, please apply the solution given. Default traces are located under /usr/sap/<SID>/<instance>/j2ee/cluster/server0/log.
Regards,
Asha
I have attached the default trace file for 20th Jan (Yesterday).
The trace is only for time stamp when I faced this error.
Looking at the logs it seems it was not able to reach localhost....
No idea about what could be the reason.
Later yeaterday I tried to again start it and then it worked....
Lot of times it gives me such issues.
For example today when I am trying to start the server it is in Yellow state since long. (Indefinite Yellow state)
I have posted today default trace also.
Please go through both the log files as both are different issues I believe.
Issue 1 : Gray and stoipped state of J2ee Server (Default Trace 20 Jan.txt)
Issue 2 : Yellow indefinite state of server. (Default Trace 21 Jan.txt)
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.