You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Peter Firmstone (JIRA)" <ji...@apache.org> on 2010/09/12 10:46:33 UTC

[jira] Commented: (RIVER-274) Improve logging of diagnostic messages in ServiceDiscoveryManager

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

Peter Firmstone commented on RIVER-274:
---------------------------------------

This patch seems to have found it's way into the current ServiceDiscoveryManager, version, perhaps someone added it and forgot to close the issue?  I've checked, it's all in there.

Peter.

> Improve logging of diagnostic messages in ServiceDiscoveryManager
> -----------------------------------------------------------------
>
>                 Key: RIVER-274
>                 URL: https://issues.apache.org/jira/browse/RIVER-274
>             Project: River
>          Issue Type: Improvement
>          Components: net_jini_lookup
>    Affects Versions: jtsk_2.1
>            Reporter: Mark Brouwer
>            Assignee: Brian Murphy
>            Priority: Minor
>         Attachments: river-274.patch
>
>
> When troubleshooting {{ServiceDiscoveryManager}} one can set the logger {{net.jini.lookup.ServiceDiscoveryManager}} to {{FINEST}} but no information is logged related to a {{ServiceEvent}} received from a lookup service. One has to resort often to a remote debugger to get the details, all one can see is that certain tasks are created and have finished.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.