Skip to Content

Java Application Spinning Issue

Hello,

I've been having a performance issue with an application on an NW7.01 Java system. Originally it was developed on NW4 and we've deployed it to a 7.01 system using NWDI and it works as expected, unfortunately our performance issues came along with the migration. It's a custom webdynpro java application that we utilize on Intermec CN3 and CN70 mobile devices in our warehouse wirelessly. The application uses JCO's to transfer the input to our ECC system and perform transactions. The issue we're encountering is that while utilizing the transactions or even traversing through the menu, the devices encounter spinning problems, like a loading screen but more often than the spinning never goes away, and the only way past it is to reset the devices. I'm tackling this problem from the basis side, looking for parameters and logs that may indicate where the problem is originating, if it's occurring within the Java system or within our ECC system and where within those systems is the problem. I'm not seeing any function modules taking extraordinary amounts of time in the RFC queues, and I'm seeing some errors in the server default trace, but they don't quite match up with the timeline of device spinning.

Any parameter changes or suggestions for specific logs to look at are appreciated!

Two of the more common errors that I'm seeing are below:

Text: application [webdynpro/dispatcher] Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.engine.services.httpserver.exceptions.HttpIllegalStateException: Error reading from request body. Cannot read the next body parts. Possible reason is interrupted connection with http client.)].

The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The connection is closed.

Exception id: [0050569D469B01B600000005000010AC00050C022F522CAA]

Text: User Guest, IP address 172.16.248.207

Cannot read request body.

com.sap.engine.services.httpserver.exceptions.HttpIOException: The connection is closed.

  at com.sap.engine.services.httpserver.server.io.HttpInputStream.read(HttpInputStream.java:184)

  at com.sap.engine.services.httpserver.server.RequestImpl.readBodyFromStream(RequestImpl.java:312)

  at com.sap.engine.services.httpserver.server.RequestImpl.getRequestParametersBody(RequestImpl.java:286)

  at com.sap.engine.services.httpserver.server.RequestAnalizer.getRequestParametersBody(RequestAnalizer.java:444)

  at com.sap.engine.services.servlets_jsp.server.lib.WebParseUtils.parseParameters(WebParseUtils.java:199)

  at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletRequestImpl.parseParameters(HttpServletRequestImpl.java:1522)

  at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletRequestImpl.getParameterValues(HttpServletRequestImpl.java:464)

  at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletRequestImpl.getParameter(HttpServletRequestImpl.java:411)

  at com.sap.tc.webdynpro.clientserver.session.RequestManager.setSpnegoParameter(RequestManager.java:938)

  at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:157)

  at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

  at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

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

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

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

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

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

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

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

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

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

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

  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:104)

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Jun 25, 2015 at 07:02 AM

    Hi Noah,

    I have a similar issue with a 7.01 server (in my case it's a Java Servlet and not Web Dynpro).

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

    Did you solve your problem?

    Regards,

    Omri

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 25, 2015 at 07:41 AM

    Hello Noah,

    Error:-com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException

    User has pressed the stop button, or refresh, or browses away too fast before the entire page is fully loaded, or just the browser has decided to close its socket for some reason.

    Then when your application tries to write something into client's response stream, you get this error.

    Have you tried user with SAP_ALL access.

    if not try and let us know.

    Regards

    Anand

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 02, 2015 at 07:02 PM

    Hi Omri and Anand,

    Part of our issue is the browser it appears. We tried switching from the built in intermec browser to the soti browser on our devices and stopped having the issue, however on the new browser occasionally we would experience a loading screen that would never finish loading.
    We are currently living with the issue and didn't switch device browsers, as next year we are replacing our current mobile application with a different solution.

    Anand, we have not tried using a user with SAP_ALL access on the NW java system. The RFC connection back to our ECC system where our function modules are called do utilize that security on the RFC user.

    Thanks!

    -Noah

    Add comment
    10|10000 characters needed characters exceeded