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 2015/12/05 12:44:11 UTC
[jira] [Resolved] (RIVER-274) Improve logging of diagnostic
messages in ServiceDiscoveryManager
[ https://issues.apache.org/jira/browse/RIVER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Firmstone resolved RIVER-274.
-----------------------------------
Resolution: Fixed
Fix Version/s: River_3.0.0
> 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
> Priority: Minor
> Fix For: River_3.0.0
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)