river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Firmstone (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RIVER-30) Deadlock Reggie between Java logging and net.jini.jeri.ssl.SslServerEndpointImpl
Date Sat, 05 Dec 2015 09:01:10 GMT

    [ https://issues.apache.org/jira/browse/RIVER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042763#comment-15042763
] 

Peter Firmstone commented on RIVER-30:
--------------------------------------

The session field has been made final in River 3.0.0, so the synchronized block can be removed
safely.  This will be fixed in 3.0.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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message