RE: Problem with mod_jk and ajp13

2001-02-01 Thread Peter Dai

Thanks Keith.

I would not go to 3.3 for the time being.  Is there a patch for 3.2.1?

Peter

-Original Message-
From: Keith Wannamaker [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 4:15 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem with mod_jk and ajp13


Hi Peter, this may be related to a problem that was fixed recently
in CVS.  Please try a nightly 3.3 build:
http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3/

Keith

-Original Message-
From: Peter Dai [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 6:43 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem with mod_jk and ajp13


Dan,

Thanks for the help.  I changed to tomcat 3.2.1 and it worked for large size
POST with
parameters.

However, it still fails for POST with object, and here is the stack trace:

Thanks,
Peter


java.io.StreamCorruptedException: Caught EOFException while reading the
stream header
at
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:727)
at java.io.ObjectInputStream.init(ObjectInputStream.java:165)
at
com.oplink.servlets.ObjectRequestServlet.doPost(ObjectRequestServlet.java:82
)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




Re: Problem with mod_jk and ajp13

2001-01-31 Thread Dan Milstein

Peter,

There was a bug with POST size  8K.  This has been fixed in the 3.2 and 3.3
branches in cvs.  I am almost certain that it was fixed in the 3.2.1 release
available at:

http://jakarta.apache.org/site/binindex.html

If you are using the 3.2.1 release and are still seeing this problem, please
let me know.

-Dan

Peter Dai wrote:
 
 Hi There,
 
 Has anyone seen this problem.
 
 1) I hava been doing applet-servlet communication with both parameters and
 object, it has been working nicely for any size(upto ~50K) of the request in
 my application.
 
 2) Then I tried mod_jk /  ajp13.  For small requests, it worked fine.  But
 for large request, I got the following error:
 The request came in as a POST, so the size limitation for GET does not
 apply.
 
 3) Looks like mod_jk and ajp13 can not handle large size POST request.
 
 Thanks for anyone who can help
 
 Peter Dai
 
 2001-01-31 02:02:55 - Ctx( /dev ): Exception in: R( /dev +
 /servlet/ManagerServlet + null) - java.lang.ArrayIndexOutOfBoundsException
 at
 org.apache.tomcat.service.connector.Ajp13ConnectorRequest.doRead(Ajp13Connec
 torRequest.java, Compiled Code)
 at
 org.apache.tomcat.service.connector.Ajp13ConnectorRequest.doRead(Ajp13Connec
 torRequest.java, Compiled Code)
 at
 org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServletInpu
 tStream.java, Compiled Code)
 at
 org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServletInputS
 tream.java, Compiled Code)
 at javax.servlet.http.HttpUtils.parsePostData(HttpUtils.java:235)
 at org.apache.tomcat.util.RequestUtil.readFormData(RequestUtil.java,
 Compiled Code)
 at
 org.apache.tomcat.core.RequestImpl.handleParameters(RequestImpl.java,
 Compiled Code)
 at
 org.apache.tomcat.core.RequestImpl.getParameterValues(RequestImpl.java,
 Compiled Code)
 at org.apache.tomcat.core.RequestImpl.getParameter(RequestImpl.java,
 Compiled Code)
 at
 org.apache.tomcat.facade.HttpServletRequestFacade.getParameter(HttpServletRe
 questFacade.java, Compiled Code)
 at com.oplink.servlets.ManagerServlet.doGet(ManagerServlet.java,
 Compiled Code)
 at com.oplink.servlets.ManagerServlet.doPost(ManagerServlet.java,
 Compiled Code)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at
 org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java,
 Compiled Code)
 at org.apache.tomcat.core.Handler.service(Handler.java, Compiled
 Code)
 at
 org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java, Compiled
 Code)
 at
 org.apache.tomcat.core.ContextManager.internalService(ContextManager.java,
 Compiled Code)
 at
 org.apache.tomcat.core.ContextManager.service(ContextManager.java, Compiled
 Code)
 at
 org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection
 (Ajp13ConnectionHandler.java, Compiled Code)
 at
 org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java,
 Compiled Code)
 at
 org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java,
 Compiled Code)
 at java.lang.Thread.run(Thread.java:479)
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]

-- 

Dan Milstein // [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




RE: Problem with mod_jk and ajp13

2001-01-31 Thread Peter Dai

Dan,

Thanks for the help.  I changed to tomcat 3.2.1 and it worked for large size
POST with
parameters.

However, it still fails for POST with object, and here is the stack trace:

Thanks,
Peter


java.io.StreamCorruptedException: Caught EOFException while reading the
stream header
at
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:727)
at java.io.ObjectInputStream.init(ObjectInputStream.java:165)
at
com.oplink.servlets.ObjectRequestServlet.doPost(ObjectRequestServlet.java:82
)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java,
Compiled Code)
at org.apache.tomcat.core.Handler.service(Handler.java, Compiled
Code)
at
org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java, Compiled
Code)
at
org.apache.tomcat.core.ContextManager.internalService(ContextManager.java,
Compiled Code)
at
org.apache.tomcat.core.ContextManager.service(ContextManager.java, Compiled
Code)
at
org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection
(Ajp13ConnectionHandler.java, Compiled Code)
at
org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java,
Compiled Code)
at
org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java,
Compiled Code)
at java.lang.Thread.run(Thread.java:479)
-Original Message-
From: Dan Milstein [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 2:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Problem with mod_jk and ajp13


Peter,

There was a bug with POST size  8K.  This has been fixed in the 3.2 and 3.3
branches in cvs.  I am almost certain that it was fixed in the 3.2.1 release
available at:

http://jakarta.apache.org/site/binindex.html

If you are using the 3.2.1 release and are still seeing this problem, please
let me know.

-Dan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]




RE: Problem with mod_jk and ajp13

2001-01-31 Thread Keith Wannamaker

The fix is in cvs for both 3.2 and 3.3, I only recommended
3.3 because it has a nightly build.  If you already have
the source, it is just a minor change.  The patch is here:
http://www.apache.org/~keith/jk/signed_error/
(see #8)  Again, I don't know for sure that is your problem
but it is possible.

Keith

-Original Message-
From: Peter Dai [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 7:56 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem with mod_jk and ajp13


Thanks Keith.

I would not go to 3.3 for the time being.  Is there a patch for 3.2.1?

Peter

-Original Message-
From: Keith Wannamaker [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 4:15 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem with mod_jk and ajp13


Hi Peter, this may be related to a problem that was fixed recently
in CVS.  Please try a nightly 3.3 build:
http://jakarta.apache.org/builds/jakarta-tomcat/nightly-3.3/

Keith

-Original Message-
From: Peter Dai [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 6:43 PM
To: [EMAIL PROTECTED]
Subject: RE: Problem with mod_jk and ajp13


Dan,

Thanks for the help.  I changed to tomcat 3.2.1 and it worked for large size
POST with
parameters.

However, it still fails for POST with object, and here is the stack trace:

Thanks,
Peter


java.io.StreamCorruptedException: Caught EOFException while reading the
stream header
at
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:727)
at java.io.ObjectInputStream.init(ObjectInputStream.java:165)
at
com.oplink.servlets.ObjectRequestServlet.doPost(ObjectRequestServlet.java:82
)



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]