You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@river.apache.org by "Simon IJskes (JIRA)" <ji...@apache.org> on 2012/10/05 10:24:49 UTC

[jira] [Updated] (RIVER-20) Instrument discovery providers with logging that eases discovery related troubleshooting

     [ https://issues.apache.org/jira/browse/RIVER-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon IJskes updated RIVER-20:
------------------------------

    Assignee:     (was: Mark Brouwer)
    
> Instrument discovery providers with logging that eases discovery related troubleshooting
> ----------------------------------------------------------------------------------------
>
>                 Key: RIVER-20
>                 URL: https://issues.apache.org/jira/browse/RIVER-20
>             Project: River
>          Issue Type: Improvement
>          Components: com_sun_jini_discovery
>    Affects Versions: jtsk_2.1
>            Reporter: Mark Brouwer
>            Priority: Minor
>
> There is room for improvement for logging as currently implemented by many of the discovery providers in the {{com.sun.jini.discovery}} namespace as is indicated in more detail [here|http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200703.mbox/%3c460A33DF.2060302@cheiron.org%3e].
> From that thread one might conclude there is no consensus yet of whether this is necessary, or at what level(s) these additional logging should take place, nevertheless I consider it wise to track this issue and implement this feature in my workspace.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira