Various issue with stable/tomcat4

[Arnaud Vandyck]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[Cc'ing to debian-java at lists.debian.org because discussion should go on
this list, pkg-java-maintainers is only for the maintainer fields
purpose, we should add this in the Debian Java FAQ]

I have all the three problems but I thought it was a limitation of
Tomcat, I did not know it's a Debian specific problem.

Our problem is Tomcat4 is no more supported, we all focus on Tomcat5.
Tomcat4 will be patched only if a security problem is discovered.

Can you reproduce these bugs in Tomcat5 in testing/unstable?

Thanks for your report.

Marc SCHAEFER wrote:
> Hi,
> 
> I have the following issues with tomcat4 in stable. Have you experienced
> those ?  I can't find those looking at
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=tomcat4&dist=stable
> 
> Problem 1:
> 
>  - tomcat4 JK connector is only available once all instances have
>    initialized correctly. If the Apache JK connector attempts a
>    connection before JK is ready, tomcat4 hangs forever, Apache reports
>    and internal error without logging it to the error_log
>  
> Problem 2:
> 
>  - tomcat4 cannot be restarted immediately, a delay of at least 2
>    minutes must be observed. This could be due to a missing SO_REUSE
>    socket option for the JK Connector, as this problem doesn't exist
>    for the other connectors (e.g. WWW as used by Apache Proxy)
>  
> Problem 3:
> 
>  - tomcat4 cannot be stopped properly (the init script kills it after
>    some time)
>  
> Version: 4.1.31-3


- --
  .''`.
 : :' :rnaud
 `. `'
   `-
Java Trap: http://www.gnu.org/philosophy/java-trap.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDpos54vzFZu62tMIRAtQxAJ4n1pDg1tcbZYN/PVom3D6wlPtZjwCgl94I
p1ynkHJ4G0OvcVnEdpM7XWI=
=QoNk
-----END PGP SIGNATURE-----