DO NOT REPLY [Bug 23180] - Deadlock in classloader while loading JSSE

2005-02-28 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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=23180


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WONTFIX




--- Additional Comments From [EMAIL PROTECTED]  2005-02-28 21:57 ---
Since the root cause is a JDK issue and there has been no response to Tim's
question, I am resolving this as WONTFIX.

-- 
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]



DO NOT REPLY [Bug 23180] - Deadlock in classloader while loading JSSE

2004-02-08 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23180

Deadlock in classloader while loading JSSE





--- Additional Comments From [EMAIL PROTECTED]  2004-02-09 00:37 ---
Does this error still occur in 4.1.30? I thought some jsse like patches were
applied since 4.1.24 but can't remember the specifics.

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



DO NOT REPLY [Bug 23180] - Deadlock in classloader while loading JSSE

2003-09-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23180

Deadlock in classloader while loading JSSE





--- Additional Comments From [EMAIL PROTECTED]  2003-09-18 10:07 ---
I agree in that the deadlock seems to be related only to JDK internal 
implementation. Anyway, the problem appears when a request is processed before
the SSL connector initialization is finished.

Is there any possibility of avoiding it by not accepting any request until all
connectors are initialized? Could I force this behaviour through a valve or a 
filter or simething like this?

I can upgrade my JDK, but it is not always possible or easy to do so in a 
customer host.

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



DO NOT REPLY [Bug 23180] - Deadlock in classloader while loading JSSE

2003-09-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23180

Deadlock in classloader while loading JSSE

[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Deadlock in |Deadlock in classloader
   |WebAppClassLoader   |while loading JSSE



--- Additional Comments From [EMAIL PROTECTED]  2003-09-18 08:08 ---
I don't think Tomcat has anything to do with that problem. JSSE is always loaded
by the system classloader (as proven by your stack traces). The locked objects
are also related to the system classloader, which (of course) Tomcat doesn't
attempt to sync on.

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