river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramiro Voicu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (RIVER-30) Deadlock Reggie between Java logging and net.jini.jeri.ssl.SslServerEndpointImpl
Date Mon, 25 Jun 2007 23:52:26 GMT

     [ 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.


Mime
View raw message