Re: WASMessageRouterServlet in WebSphere

David-
ServletRequest getContentLength returns a signed int (with a +64k limit)
http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/ServletRequest.html#getContentLength()
(same information can be obtained via HTTP Variable CONTENT_LENGTH)

Would probably make sense for the client to parse the incoming request stream to < 64k at a time..
(JDK 1.2 restriction)

Anyone else??

-Martin
  ----- Original Message ----- 
  From: David Smith 
  To: Soap-User 
  Sent: Thursday, June 10, 2004 9:14 PM
  Subject: WASMessageRouterServlet in WebSphere


  I'm working on a Web Service in WebSphere where I accept and upload from a Desktop VB client. It works with normal transactions. However, when I try to upload a large transaction (about 91k) the WASMessageRouterServlet is throwing SAXParserExceptions before my service ever gets called.

  Are there any limitations to the size of a request that can be sent in? Has anybody ever experienced anything like this? I'm using WebSphere version 4.03. I've also reproduced it on WebSphere Studio 5.0.


  Dave