shindig-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanton Sievers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SHINDIG-1974) Locked domain services should specify the container when logging warnings
Date Thu, 01 May 2014 12:06:15 GMT

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

Stanton Sievers updated SHINDIG-1974:
-------------------------------------

    Labels: logging serviceability  (was: )

> Locked domain services should specify the container when logging warnings
> -------------------------------------------------------------------------
>
>                 Key: SHINDIG-1974
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1974
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>    Affects Versions: 2.5.1
>            Reporter: Stanton Sievers
>              Labels: logging, serviceability
>
> This came up on the [Apache Rave list|http://markmail.org/thread/ss2yxxwowdvhs5pq].
> Warnings were being seen from the HashLockedDomainService relating to the "default" container
and the user thought they were errors from their own named container.  When logging these
warnings, the locked domain services should specify the container for which the warning is
being logged to aid in debugging.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message