Error while opening NWA of Solution Manager system

[Former Member]

Hello,

We have an Issue in Solution Manager Production system.

While opening the NWA page it takes huge time and  throws below Error.

Network Error (tcp_error)

A communication error occurred: ""

The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.

============================================================================

Other links like System Info etc works properly.

End users while using java part of SPZ does not face.

We have taken the HTTP Watch trace for this and the logs are as follows

00:00:00.000 Network Error                                                                            

+ 0.000                            0.112  922     300     GET    302     Redirect to http://10.8.33.13:51000/webdynpro/dispatcher/sap.com/tc~lm~webadmin~mainframe~wd/WebAdminApp          http://10.8.33.13:51000/nwa

+ 0.114                  2        324.187       987     1061   GET    503    html         http://10.8.33.13:51000/webdynpro/dispatcher/sap.com/tc~lm~webadmin~mainframe~wd/WebAdminApp

                   2                  324.301       1909   1361   2 requests                       

In default trace we observe below Errors

#1.#0017A477202800040000000C00005F5C0004CAE5B40C9755#1348987823888#com.sap.engine.services.r3startup.impl1.dispatcher.R3StartupService##com.sap.engine.services.r3startup.impl1.dispatcher.R3StartupSe

rvice#######SAPEngine_System_Thread[impl:6]_36##0#0#Error##Plain###Couldn't send INVALIDATE_ETAG to R/3 dispatcher. Exception is : java.net.SocketException: Socket closed

        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:120)

        at java.net.SocketOutputStream.write(SocketOutputStream.java:157)

        at com.sap.engine.services.r3startup.dispatcher.SocketThread.sendMessage(SocketThread.java:93)

        at com.sap.engine.services.r3startup.impl1.dispatcher.R3StartupService.invalidateEtag(R3StartupService.java:460)

        at com.sap.engine.services.httpserver.dispatcher.HttpDispatcherFrame.receive(HttpDispatcherFrame.java:492)

        at com.sap.engine.core.service630.context.cluster.message.MessageListenerWrapper.process(MessageListenerWrapper.java:126)

        at com.sap.engine.core.cluster.impl6.ms.MSMessageQueue.process(MSMessageQueue.java:77)

        at com.sap.engine.core.cluster.impl6.ms.MSMessageThread.run(MSMessageThread.java:37)

        at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

        at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:82)

        at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:154)

We have restarted the Java Instance of this and also entire solman system also.

But this issue did solve.

Kindly suggest how should this issue be solved.

Thank you, Regards,

Girish Garje.

[TomCenens]

Hello Girish

Please check / search SCN or use Google to search for relevant historical threads for this issue.

Search for "Couldn't send INVALIDATE_ETAG to R/3 dispatcher"

For example:

http://scn.sap.com/thread/760593

Your J2EE dispatcher fails to send a message to the R/3 dispatcher. Try the solution provided in above thread, the root cause is most likely a communication timeout.

Best regards

Tom