on ‎2012 Jan 04 6:15 PM
Hi friends,
i am using netweaver system with 700 kernel and it is dual stack. i have shutdown my system, all the instances and process have stopped except the message server. message server is not shutting down. waited for almost an hour. i have cheked the log files dev_ms and dev_disp files. i am getting the following errors.
dev_ms:
[Thr 1728] *** ERROR => MsSCheckConnections: no response from client C2 (192.168.247.128) after 300 secs received [msxxserv.c 3158]
[Thr 1728] *** ERROR => MsSCheckConnections: disconnect now [192.168.247.128] [msxxserv.c 3162]
can you please help me with this....
Request clarification before answering.
Hi,
Please see Note 1532367 - MsSCheckConnections (s-user needed).
Error means that there was no network activity between the message server and a particular application server (running on 192.168.247.128) after ms/keepalive (default: 300) seconds.
This is normally caused by hanging Dispatcher on that particular application server (running on 192.168.247.128).
I'd suggest to check what was happening on that server, on Dispatcher trace file (dev_disp).
As mentioned on the Note, problems during name resolution is one of the common causes.
Regards,
Raquel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please refer SAP Note : 1532367
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello NIshit,
can you check whats running on the IP address Thr 1728 *** ERROR => MsSCheckConnections: disconnect now http://192.168.247.128 http://msxxserv.c 3162
If you can stop what is running on that it should go down.
Regards
Vivek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yeah it got finally stopped, when i clicked stop all tasks for second time. but it still took a very long tym, but can anyone giveme whats the reason for taking such a long tym...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Looks like a client terminal session or connection from app server was still holding up the connection to message server. Please try to figure out is that ip from client terminal or app server.
This issue might happen when you shutdown Central Instance before shutting down application servers or application servers from other host are not stopped properly or being stopped when you attempt to stop Central Instance.
Thanks,
Siva Kumar
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.