XI / Web Despatcher - connection to URL fails

[Former Member]

At present we are experiencing problems either with the Web Dispatcher, or with the Load Balancing that control http requests between the two nodes in our XI cluster.

In SM59 for HTTP Destination “INTEGRATION_DIRECTORY_HMI”, when we use port 60000 (the WD port) connection tests will sometimes fail and sometimes succeed. If however, we use 50200 (the J2EE Engine port ) it always works.

In addition when we attempt a cache refresh through SXI_CACHE we get the following error:

com.sap.aii.ib.server.abapcache.CacheRefreshException: Connection to system RUNTIME using application RUNTIME lost. Detailed information: Error accessing "http://hbnxisap:60000/run/hmi_service_id_fresh_swcv/int?container=any" with user "PIDIRUSER". Response code is 404, response message is "Not found"

at com.sap.aii.ibdir.server.abapcache.content.CacheSwc.addContent(CacheSwc.java:63)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:360)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:324)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)

at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)

at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.setXmlDataAndBufferSize(CacheRefreshSession.java:121)

at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.<init>(CacheRefreshSession.java:40)

at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.getInstance(CacheRefreshSession.java:54)

at com.sap.aii.ibdir.web.abapcache.CacheRefreshServlet.doGet(CacheRefreshServlet.java:45)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

As a result, our XI Production system has become non-operational.

We urgently require assistance to resolve this. As a workaround one of our XI cluster nodes has been shut down - re-enabling it causes the problem to occur again.

Regards,

Mark

[Former Member]

Check all the service userid & password in exchangeProfile