This only occurs when Tomcat is started without a SecurityManager and
then later application code sets a SecurityManager.
Please see the following bug report for an explanation of why
that is not a good thing to do:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7052
Thanks for taking the tim
Hi,
the patch below fixes a bug that occasionally causes a NullPointerException in
loadClass() method. The problem was caused by the way the system security
manager was used in this class. For checking if there is a security manager, and
then using the security manager for checking the access, two
This account does not exist
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]