2010/1/19 jean-frederic clere <jfcl...@gmail.com>:
> The candidates binaries are available here:
> http://people.apache.org/~jfclere/tomcat-6/v6.0.24/
>
> According to the release process, the 6.0.24 tag is:
> [ ] Broken
> [ ] Alpha
> [ ] Beta
> [ ] Stable
>

Tested
apache-tomcat-6.0.24.exe
apache-tomcat-6.0.24-windows-x86.zip

Environment: JRE 6u17 on WinXP 32-bit
Tested with and without Tomcat-Native 1.1.19, with and without Security Manager.


When running with Security Manager I stumbled upon the following:
if I start with a pristine installation (from a zip file), and the
first page that I access is

http://localhost:8080/examples/jsp/jsp2/el/implicit-objects.jsp?foo=bar

I receive AccessControlException.

The stack trace is the same as in Bug 48438, mentioning
"ProtectedFunctionMapper.getMapForFunction()" as the place where class
loading was forbidden, but this time it is a perfectly valid JSP where
it is observed.

If I refresh the page, I can get a NoClassDefFoundError, but unless I
restart Tomcat and access some other JSP first  I cannot get rid of
the error.

Looks like a showstopper.



Other issues that I observed are minor.

1) When stopping Tomcat Windows service,
not all of the shutdown sequence log messages reach the log. I see
only "Stopping service Catalina", but not the "Stopping Coyote"
message.

It looks like the JVM shutdown hook that shuts down the logging
subsystem is started before the server thread stops. (Maybe some
Thread.join() call will fix the issue).

None of the messages before the shutdown sequence are lost, so I think
it is a minor issue.


2) When running with Tomcat-native 1.1.19 on Windows
when shutting down Tomcat (either with shutdown.bat or stopping a
service) I either
a) observe an Error message in the log  (as the last message in the
shutdown sequence), or
b) hs_err_pidNNNN.log is generated, reporting an EXCEPTION_ACCESS_VIOLATION.

When running as a service you'll only observe b), because of the
logging issue that I described above. The error location is in
org.apache.tomcat.jni.Socket.accept

I think it is a minor issue, because it only happens on shutdown. I'll
file a Bugzilla issue with more details.



Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to