Es schrieb Ralph Einfeldt:
>
> AFAIK the main error is in the jdk 1.3 and 1.4.
> jasper2 just contains (beside other changes) a workaround for
> this bugs.
>
> Have a look at this links: (Require login)
> http://developer.java.sun.com/developer/bugParade/bugs/4414162.html
> http://developer.java
e any problems, but
tomcat4.
Any ideas?
Has anyone experiences with using tomcat4.0.4/jasper2 in a productive
environment?
Is it stable enough?
Thanks in advance,
Timo Carl
--
Timo Carl
Technik & Programmierung
travelchannel GmbH
Kehrwieder 8
D-20457 Hamburg
Telefon +49/40/38617-275
Telefax +49
The problem has been seen on both, ajp13 and ajp12.
We use tomcat-3.2.1.
What do think about using mod_jserv again?
What kind of quality has the T3.3 cvs mod_jk? Is it possible to use it
in a productive environment?
Greetings,
Timo
GOMEZ Henri wrote:
>
> Could you tell us if you're using ajp1
or
writing back to server\n"); write_to_ws = JK_FALSE;<<<<<<<<
> Yesd, I had, I changed to mod_jserv, I'm still waiting for the same answer
> as you do, for the high CPU request of mod_jk...
>
> Guido.
> - Original Message -
> From: "Timo Car
?
Maybe anyone solved that problem?
Greetings and thanks in advance,
Timo Carl
begin:vcard
n:Carl;Timo
tel;fax:++49/40/3703-7759
tel;work:++49/40/3703-7275
x-mozilla-html:FALSE
url:http://www.travelchannel.de
org:G+J travelchannel;Technik
version:2.1
email;internet:[EMAIL PROTECTED]
adr;quoted
