XI Content Import Invalidates Runtime Cache

[Former Member]

Hello Everybody,

We are facing a weird problem with XI Runtime Cache. We imported a few XI Contents from SMP a few days back. After importing them, the XI cache stopped refreshing. The error says 'if_http_client receive http_communication_failure' with error id 'COMMUNICATION'. Our first guess was that somehow the user for HTTP Destination INTEGRATION_DIRECTORY_HMI has been locked. But we checked and the user was OK. Then we searched in SDN and according to similar forum threads, deleted the HTTP destination,recreated it and all. We also skimmed through 'How-To-Guide' on XI caches and found entries to be in synch. But the problem still persists. In IR, Environment->Cache Notifications, we find everything green; but in ID, we find entries which state 'Cache Update Failed' with the same error text as above. But, we didn't do anything in ID!! Has anybody faced a situation similar to this and solved it? We will be glad to hear about it. [And will also make people glad by awarding points! ]

P.S.: We are on NW2004s PI 7.0 SP09.

Thanks and Sincere Regards,

Amitabha

[Former Member]

Uh oh...Forgot My Slogan!!!

"Hail SDN!!!"

[Former Member]

Kindly check if your license is not experied. Automatic Cache updation also fails is license has been experied.

login to SolMan and use tcode SMSY to check the license.

Regards,

Sarvesh

[Former Member]

Hi Sarvesh,

I do not have access to the Solution Manager system; will let you know as soon as I get a BASIS person to do the job. However, from XI system home screen, system->status->License Expiration under SAP System Data tab shows that the licesnse is not expired.

Thanks and Sincere Regards,

Amitabha

[Former Member]

Did to test your http connection >?

[Former Member]

Hi Rajesh,

I did not fully understand your question; However, I guess you are asking for HTTP Destination INTEGRATION_DIRECTORY_HMI Connection Test. Yes we did test it, and the result was ok.

Thanks and Sincere Regards,

Amitabha

[Former Member]

Hello Everyone,

We have digged into the application logs of our XI server, and the discovered the following error:

Sending method return: caught unexpected exception!

Thrown:com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The connection is closed. at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.ensureClientAvailable(ServletOutputStreamImpl.java:560) at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:409) at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:232) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:191) at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:111) at java.io.BufferedWriter.write(BufferedWriter.java:206) at java.io.Writer.write(Writer.java:126) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.setStringBody(HmisServletImpl.java:627) at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:101) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doGet(HmisServletImpl.java:640) 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)

Anybody has any idea what this means?

Thanks and Sincere Regards,

Amitabha

[aashish_sinha]

Hi,

I guess there some access problem at HTTP Destination INTEGRATION_DIRECTORY_HMI Connection test and you are unauthorized person. Check out the permission and try once again.

regards

Aashish

[aashish_sinha]

Also check out this link .. It will help you.

https://websmp204.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf

regards

Aashish

PS : reward point if helped

[Former Member]

Hi Aashish,

Thanks for your valuable input; but we are using PIISUSER as the INTEGRATION_DIRECTORY_HMI user, with all the roles assigned as suggested by SAP. Also, we have tried applying all the remedies that the 'How To..Handle Caches in XI 3.0' document suggests, but the error still persists.

Thanks and Sincere Regards,

Amitabha

[aashish_sinha]

did you checked about SAP_SLD_CONFIGURATOR Role?

[Former Member]

Hello Everybody,

We have solved the problem by ourselves. The problem was with the volume of data and the <b>timeout parameter</b> of the HTTP Destination INTEGRATION_DIRECTORY_HMI. The timeour parameter was set to ICM Default Timeout, which was set to 5 seconds. Since the content import loaded a sizeable chunk of data, the HTTP request was getting timed out after 5 seconds; since it was not getting the response back from Integration Directory within that timeframe. We suspected this activity after digging through the j2ee logs. Setting a higher value to the timeout and then initiating a full cache refresh did the trick for us.

Thanks for all the support from fellow (and senior) SDNers. Awarded points to all the answers which pointed that the problem lies in the HTTP destination.

Thanks and Sincere Regards,

Amitabha

[Former Member]

Hi,

Did u try full cache refresh ?

<b>Cheers,

*RAJ*</b>

[Former Member]

Hi Rajesh,

Yes we tried a full Cache refresh. During full cache refresh, the indication in SXI_CACHE shows yellow for some times, then as we refresh the frame, it shows the same error: 'if_http_client receive http_communication_failure'.

Thanks and Sincere Regards,

Amitabha