Ok, I checked in a fix.
Let me know if it helps.
Costin
On 7 Jun 2002, Jean-Francois Nadeau wrote:
> Hi.
>
> I found something very interesting this morning in catalina.out file.
> Here it is:
>
> java.lang.IllegalStateException: Current state = FLUSHED, new state =
> CODING_END
> at
Hi.
My bug was a known issue:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7725
Effectively, we use HttpServletResponse.sendRedirect in our code.
Thanks a lot,
jeff
On Fri, 2002-06-07 at 09:40, Jean-Francois Nadeau wrote:
> Hi.
>
> I found something very interesting this morning in cata
Hi.
I found something very interesting this morning in catalina.out file.
Here it is:
java.lang.IllegalStateException: Current state = FLUSHED, new state =
CODING_END
at
java.nio.charset.CharsetEncoder.throwIllegalStateException(CharsetEncoder.java:933)
at
java.nio.charset.Charse
>The real issue is why tomcat doesn't send the data. Could you try
>with tomcat4.1 ( or the new coyote-based ajp connector ) ? Is it
>really a deadlock ( tomcat and mod_jk both waiting for input,
>i.e. locked in read ) ? Or it is that tomcat for some reasons
>doesn't send the 'END' message ?
H
Thanks for the patch.
However, there are still few big problems and we really need your
help ( even if you solve your problem ). First, I can't reproduce
it - so it's blind debugging.
I don't think select() is available on all platforms ( for jk2
we could use apr select ), so I doubt we can jus
Hi.
The lock/unlock fix may help but it doesn't fix the problem. I patched
my tree with the jk_mt.h modification and I investigated the bug even
deeper.
The problem was in jk_connect.c, jk_tcp_socket_recvfull, recv call. It
seems that Tomcat 4.03 (I didn't try with CVS head version...) sometimes
Hi,
I found the problem, it seems the lock/unlock were in the wrong order.
Please checkout from head and try again, and let me know if it still
fails.
( thanks for reporting it )
Costin
On 5 Jun 2002, Jean-Francois Nadeau wrote:
> Hi.
>
> I started to load / stress test our web application
Hi.
I started to load / stress test our web application. It is running under
Apache 1.3.22 and Tomcat 4.03 and the mod_jk binary that came with it.
The OS is Linux 2.4.7, RedHat 7.2 without any updates.
I discovered that httpd processes deadlock after a certain amount of
huge requests.
I decide
