Error while uploading Binary File in Websphere 4.0.2 using O'reilly Multipart

[Nitin]

I have written a servlet using O'reilly's Multipart package(cos.jar -
latest version i.e. 27.5.2002), to upload files
on the server. I deployed it on WAS 4.0.2 on Windows. It worked fine.
I tried to deploy the same on WAS 4.0.2 in Domino5.0/AIX environment
and I got the following exception when I tried to upload binary files.
It creates the file with no data. But the ascii files gets uploaded
properly.

Following is the stacktrace for the same.

java.io.IOException: unexpected end of part
at com.oreilly.servlet.multipart.PartInputStream.fill(PartInputStream.java:96)
at com.oreilly.servlet.multipart.PartInputStream.read(PartInputStream.java:179)
at com.oreilly.servlet.multipart.PartInputStream.read(PartInputStream.java:152)
at com.oreilly.servlet.multipart.FilePart.write(FilePart.java:201)
at com.oreilly.servlet.multipart.FilePart.writeTo(FilePart.java:160)
at com.oreilly.servlet.MultipartRequest.<init>(MultipartRequest.java:245)
at com.oreilly.servlet.MultipartRequest.<init>(MultipartRequest.java:148)
at de.resource.userreg.union.SaveVisCardServlet.doPost(SaveVisCardServlet.java:138)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:159)
at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:286)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:106)
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:499)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:278)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:105)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:67)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:123)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:122)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:313)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:242)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)

[smogu]

The was 4.0.2 has a bug in the web server plugin :)
at least with ibm httpd (apache) server. (upgrade to 4.0.4)
Maybe it's also in the Domino environment ... :)

see e.g.
http://www.servlets.com/soapbox/bugs.html