DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35536>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35536


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From [EMAIL PROTECTED]  2005-06-30 21:55 -------
Looking at the source for java.lang.System this looks like a JVM bug.

System.getProperty() first checks if the security manager is null, and if not
calls checkPropertyAccess(). The problem appears to be that the security manager
!= null when the check is done but is null by the next line when
checkPropertyAccess() is called.

It looks like this is possible if another thread calls calls
System.setSecurityManager(null) but you would have to be really unlucky to be
hit by this. I have searched the Tomcat code and nothing calls
System.setSecurityManager() at all.

Since the root cause is a JVM bug and I can't see anything that Tomcat is doing
that might cause this, I am going to resolve this as invalid.

My suggestion for you to progress this is:
- raise a bug report with Sun
- look to see if any of your webapps are setting the security manager

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to