Java.lang.IllegalStateException when trying to load graphic from KM

Question

Hello,
I'm currently facing the following problems.We have a bunch of SVG graphics in a KM-Repository which are displayed to the user. The graphics are embedded in a JSP file. In most of the cases this works fine, but for users with a low bandwith this does not work. An error message is written to the logfile which looks like that:
serving request (-> 500) - java.lang.IllegalStateException: GET on
http://ourserver.com/irj/go/km/docs/ourRepository/myGraphic.svg expected 377950 bytes, but got
262144 bytes and wrote 196608 bytes. The exception message is: Write timeout. HTTP client read
timeout or callback from dispatcher not received for [120000] milliseconds. -
com.sap.engine.services.httpserver.exceptions.HttpIOException: Write timeout. HTTP client read
timeout or callback from dispatcher not received for [120000] milliseconds.
     at com.sap.engine.services.httpserver.server.ResponseImpl.sendResponse(ResponseImpl.java:280)
     at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:440)
     at com.sap.engine.services.servlets_jsp.server.runtime.client.ServletOutputStreamImpl.write(ServletOutputStreamImpl.java:234)
     at com.sapportals.wcm.protocol.webdav.server.WDGetHandler.copy(WDGetHandler.java:744)
     at com.sapportals.wcm.protocol.webdav.server.WDGetHandler.internalHandleWDGetHandler.java:691)
at com.sapportals.wcm.protocol.webdav.server.WDGetHandler.handle(WDGetHandler.java:263)
     at com.sapportals.wcm.protocol.webdav.server.WDServlet.doGet(WDServlet.java:791)
     at com.sapportals.wcm.protocol.webdav.server.WDServlet.service(WDServlet.java:483)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)+
     at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:333)+
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) ...
Some more facts:
The problem occors on different graphics
The values 262144 and 196608 (from but got 262144 bytes and wrote 196608 bytes) come up in most cases, but sometimes they vary. But all values have in common, that they are a multiple of 4096 (which is the setting of the parameter ServletsLongDataTransferCallbackSize.
According to the SAP Notes 1014039 and 807000 I adapted some settings in our Testsystem:
ServletsLongDataTransferCallbackSize: 1024 (which was set to 4096 before)
ServletInputStreamTimeout: 1728000000 (which was set to 180000 before)
ServletsLongDataTransferTimeout: 1728000000 (which was set to  120000 before)
Unfortunatelly setting those parameters didn't fix the problem.
Does anybody have a clue what I can do? And just for my understanding, what exactly does the parameter, that I have set, effect. The initial values of 180000 (3 Minutes) seem to be enough. Loading 377950 bytes should take much less that 3 Minutes even with a slow connection?
Kind regards,
dominik
Edited by: Dominik Fried on Mar 30, 2009 1:34 PM
Edited by: Dominik Fried on Mar 30, 2009 1:45 PM

Answer 1

Hi,
We are facing exactly the same issue with KM.
Can anyone assist us?
Thanks in advance,
Regina