Calls to Webservice published by XI getting lost

[Former Member]

Hi

We are trying to do a benchmark testing - by calling webservices published on the XI server - from a *net environment.

We have written a windows program that calls the XI webservice- repeatedly 'x' number of times - and the results ( request, response times ) are logged in a text file in the calling windows environment.

Now, what we see here - is surprising - one out of every 5 calls from the *net environment to the XI Webservice does not make it to the XI box ( we do not see these entries as calls/requests to the XI webservice in SXMB_MONI)

we get 2 types of errors in the log file - "Server error" or "The operation has timed-out" - Could we conclude these as getting lost in the network between Windows and the XI box ? Any ideas why we get these two different types of error messages ? Any method to track the messages getting lost inbetween ?

Thank you in advance for your time.

[Former Member · Accepted solution]

Hi

Here are some details of the "server error" that I have mentioned in my case below :

I do not see this error message in the Adapter engine ( RWB) or SXMB_MONI - this error has been trapped by the calling *net application - as a SOAP exception type error returned by XI !!!

*********************************************************

com.sap.engine.services.httpserver.exceptions.HttpIOException: Read timeout. The client has disconnected or a synchronization error has occurred. Read 0 bytes. Expected 338.

at com.sap.engine.services.httpserver.server.io.HttpInputStream.read(HttpInputStream.java(Compiled Code))

at java.io.FilterInputStream.read(FilterInputStream.java(Inlined Compiled Code))

at java.io.PushbackInputStream.read(PushbackInputStream.java(Compiled Code))

at java.io.FilterInputStream.read(FilterInputStream.java(Compiled Code))

at com.sap.aii.messaging.net.MIMEInputSource$MIMEReader.readContent(MIMEInputSource.java(Compiled Code))

at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:343)

at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)

at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:366)

at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))

at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code))

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code))

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code))

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code))

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code))

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code))

at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code))

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code))

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))

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

at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))

}{Stack Trace: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

at WSTestingTool.MatHierCount.MatCount_OBService.MatCount_OB(SalesOrg SalesOrg_MT) in C:\Documents and Settings\Gilder.Israel\My Documents\Visual Studio Projects\EI.TestingSolution\WSTestingTool\Web References\MatHierCount\Reference.cs:line 47

at WSTestingTool.Form1.CallMatHierCount() in c:\documents and settings\gilder.israel\my documents\visual studio projects\ei.testingsolution\wstestingtool\form1.cs:line 160}

[Former Member · Accepted solution]

Hi Karthik,

Check this OSS note and see if it helps you....

807000

Thanks,

Renjith

[Former Member · Accepted solution]

Ranjith

Thanks for the quick response. I checked out the note - the symptom/problem description exactly matches the situation we are facing. An important point to be mentioned here is that we are facing this problem after we upgraded from SP12 to SP13. Ironically, the note mentions that this problem should be solved in SP13 !!! Whereas , we are beginning to see this problem after we upgraded to SP13.

I am not sure whether we have to apply this note - since we are already in SP13....

[Former Member · Accepted solution]

But I am sure , setting the ServletInputStreamTimeout to a higher value is going to solve the problem !!!

[Former Member · Accepted solution]

Karthik,

which SP are you on?? there is a know bug with SP13 ICM , there is a commulative patch available.

we had the same problems with SP13 , apply 868203 and 807000

cheers,

naveen

Message was edited by: Naveen Pandrangi

Message was edited by: Naveen Pandrangi

[Former Member · Accepted solution]

Naveen

We moved recently from SP12 to SP13, we are facing this problem in SP13 right now.

[Former Member · Accepted solution]

Naveen ,

OSS note 807000 mentions that its not valid for SP13 - we just increased the J2EE parameter value mentioned in that note. Please clarify whether this is the only action to be taken for this note.

Thanks for the pointer regarding 868203 - thas was great help !!! Any particular in which the notes should be applied ??

[Former Member · Accepted solution]

Karthik,

Did the note solve ur problem?? this was a bug in SP13.Hope those notes solved ur problems.

Cheers,

naveen

[Former Member · Accepted solution]

Sorry for not getting back earlier. Yes, the note that you had pointed out has solved the problem !!!.Thanks a lot for the help !!!

[Former Member · Accepted solution]

Glad to be Helpful

Cheers,

Naveen