You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Ramiro Voicu (JIRA)" <ji...@apache.org> on 2007/06/26 01:46:26 UTC
[jira] Created: (RIVER-30) Deadlock Reggie between Java logging and
net.jini.jeri.ssl.SslServerEndpointImpl
Deadlock Reggie between Java logging and net.jini.jeri.ssl.SslServerEndpointImpl
--------------------------------------------------------------------------------
Key: RIVER-30
URL: https://issues.apache.org/jira/browse/RIVER-30
Project: River
Issue Type: Bug
Reporter: Ramiro Voicu
Priority: Minor
There is a deadlock in case logging level for net.jini.jeri.ssl.SslServerEndpointImpl is at least Level.FINE.
Don't know who's to blame ... It seems more like a problem of java.logging package
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-30) Deadlock Reggie between Java logging and
net.jini.jeri.ssl.SslServerEndpointImpl
Posted by "Ramiro Voicu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramiro Voicu updated RIVER-30:
------------------------------
Attachment: patch_river.diff
The patch will only remove the synchronized block in the toString() method
Another solution will be to acquire first the lock for SslServerConnection ... for every logging statement where this object is used as parameter for the LogRecord
> Deadlock Reggie between Java logging and net.jini.jeri.ssl.SslServerEndpointImpl
> --------------------------------------------------------------------------------
>
> Key: RIVER-30
> URL: https://issues.apache.org/jira/browse/RIVER-30
> Project: River
> Issue Type: Bug
> Reporter: Ramiro Voicu
> Priority: Minor
> Attachments: patch_river.diff, reggie.log.SAVE_21Jun
>
>
> There is a deadlock in case logging level for net.jini.jeri.ssl.SslServerEndpointImpl is at least Level.FINE.
> Don't know who's to blame ... It seems more like a problem of java.logging package
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-30) Deadlock Reggie between Java logging and
net.jini.jeri.ssl.SslServerEndpointImpl
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-30:
------------------------------
Component/s: net_jini_jeri
Description: There is a deadlock in case logging level for {{net.jini.jeri.ssl.SslServerEndpointImpl}} is at least {{Level.FINE}}. Don't know who's to blame ... It seems more like a problem of {{java.util.logging}} package. (was: There is a deadlock in case logging level for net.jini.jeri.ssl.SslServerEndpointImpl is at least Level.FINE.
Don't know who's to blame ... It seems more like a problem of java.logging package)
Affects Version/s: jtsk_2.1
> Deadlock Reggie between Java logging and net.jini.jeri.ssl.SslServerEndpointImpl
> --------------------------------------------------------------------------------
>
> Key: RIVER-30
> URL: https://issues.apache.org/jira/browse/RIVER-30
> Project: River
> Issue Type: Bug
> Components: net_jini_jeri
> Affects Versions: jtsk_2.1
> Reporter: Ramiro Voicu
> Priority: Minor
> Attachments: patch_river.diff, reggie.log.SAVE_21Jun
>
>
> There is a deadlock in case logging level for {{net.jini.jeri.ssl.SslServerEndpointImpl}} is at least {{Level.FINE}}. Don't know who's to blame ... It seems more like a problem of {{java.util.logging}} package.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-30) Deadlock Reggie between Java logging and
net.jini.jeri.ssl.SslServerEndpointImpl
Posted by "Ramiro Voicu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramiro Voicu updated RIVER-30:
------------------------------
Attachment: reggie.log.SAVE_21Jun
the stack trace of the JVM ( is for JTSK 2.0.1 ) but it seems the problem is the same for the RIVER SVN trunk
> Deadlock Reggie between Java logging and net.jini.jeri.ssl.SslServerEndpointImpl
> --------------------------------------------------------------------------------
>
> Key: RIVER-30
> URL: https://issues.apache.org/jira/browse/RIVER-30
> Project: River
> Issue Type: Bug
> Reporter: Ramiro Voicu
> Priority: Minor
> Attachments: reggie.log.SAVE_21Jun
>
>
> There is a deadlock in case logging level for net.jini.jeri.ssl.SslServerEndpointImpl is at least Level.FINE.
> Don't know who's to blame ... It seems more like a problem of java.logging package
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.