Websphere crash with POST size > 16384

[Jerry Napoli]

The websphere servlet engine consistently crashes when I issue a POST to a
servlet where the content length of the post is greater than 16384 bytes.
I've tried changing several configuration parameters including the
connection protocols -- Named Pipes, TCP/IP, Java Sockets -- with the same
results. In fact, when using either named pipes or TCP/IP, the application
server actually crashes (Access violation).

I wrote a test servlet which simply reads the InputStream from the
HttpServletRequest byte by byte. On attempting to read the 16385'th byte
from the stream, an IOException is thrown from within the servlet engine
classes:

(using Java Sockets for the transport here)
Caught throwable in doPost() : bytes read thusfar = 16384
java.io.IOException: Buffer too small
at java.io.IOException.<init>(IOException.java:49)
at
com.ibm.servlet.engine.oselistener.outofproc.ServerMessage.getNextFieldIntoA
rray(ServerMessage.java:246)
at
com.ibm.servlet.engine.oselistener.outofproc.OOPServiceStub.sendRead(OOPServ
iceStub.java:318)
at
com.ibm.servlet.engine.oselistener.outofproc.JOOPServerConnection.read(JOOPS
erverConnection.java:221)
at com.ibm.servlet.engine.srp.SRPConnection.read(SRPConnection.java:164)
at com.ibm.servlet.engine.srt.SRTInputStream.read(SRTInputStream.java:74)
at
com.ibm.servlet.engine.srt.http.HttpInputStream.fill(HttpInputStream.java:43
8)
at
com.ibm.servlet.engine.srt.http.HttpInputStream.read(HttpInputStream.java:24
8)
at java.io.InputStream.read(InputStream.java:97)
at java.io.InputStreamReader.fill(InputStreamReader.java(Compiled Code))
at java.io.InputStreamReader.read(InputStreamReader.java:242)
at java.io.BufferedReader.fill(BufferedReader.java:139)
at java.io.BufferedReader.read(BufferedReader.java(Compiled Code))
at com.kforce.nis.TestServlet.doPost(TestServlet.java:72)
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:626)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycl
eServlet.java:160)
at
com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServle
t.java:287)
at
com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycle
Servlet.java:105)
at
com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:36
0)
at
com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletMan
ager.java:775)
at
com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManag
er.java:701)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(W
ebAppRequestDispatcher.java:404)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequest
Dispatcher.java:203)
at
com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestD
ispatcher.java:107)
at
com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.
java:77)
at
com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedIn
vocation.java:67)
at
com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequ
estProcessor.java:155)
at
com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener
.java:300)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp$ServiceRunnable.run(SQ
EventListenerImp.java:230)
at
com.ibm.servlet.engine.oselistener.SQEventListenerImp.notifySQEvent(SQEventL
istenerImp.java:104)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQEventSource.notifyEvent(SQE
ventSource.java:212)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.notifyService(SQWrapperEventSource.java:353)
at
com.ibm.servlet.engine.oselistener.serverqueue.SQWrapperEventSource$SelectRu
nnable.run(SQWrapperEventSource.java:220)
at
com.ibm.servlet.engine.oselistener.outofproc.OutOfProcThread$CtlRunnable.run
(OutOfProcThread.java:248)
at java.lang.Thread.run(Thread.java:481)

Is there some other crazy setting that needs to be changed?
I'm running Websphere 3.5.3 with fixpack 3 under domino 5.0.7. Any help
here would be greatly appreciated!

Thanks in advance,
Jerry