You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Senaka Fernando (JIRA)" <qp...@incubator.apache.org> on 2008/05/19 22:29:55 UTC
[jira] Created: (QPID-1074) Log Configuration Watcher in Java
Broker halts on invalid log4j.xml
Log Configuration Watcher in Java Broker halts on invalid log4j.xml
-------------------------------------------------------------------
Key: QPID-1074
URL: https://issues.apache.org/jira/browse/QPID-1074
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Senaka Fernando
Log Configuration Watcher in Java Broker halts on invalid log4j.xml. This issue is discussed on the Qpid Developer list in detail. See [1] for more details.
[1] http://markmail.org/message/omnpk66vqvajgqh3
Regards,
Senaka
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1074) Log Configuration Watcher in Java
Broker halts on invalid log4j.xml
Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-1074:
-----------------------------------
Fix Version/s: (was: M4)
> Log Configuration Watcher in Java Broker halts on invalid log4j.xml
> -------------------------------------------------------------------
>
> Key: QPID-1074
> URL: https://issues.apache.org/jira/browse/QPID-1074
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
> Reporter: Senaka Fernando
> Priority: Minor
>
> Log Configuration Watcher in Java Broker halts on invalid log4j.xml. This issue is discussed on the Qpid Developer list in detail. See [1] for more details.
> [1] http://markmail.org/message/omnpk66vqvajgqh3
> Regards,
> Senaka
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-1074) Log Configuration Watcher in Java
Broker halts on invalid log4j.xml
Posted by "scott deboy (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598327#action_12598327 ]
scott deboy commented on QPID-1074:
-----------------------------------
Submitted bugzilla issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=45042
> Log Configuration Watcher in Java Broker halts on invalid log4j.xml
> -------------------------------------------------------------------
>
> Key: QPID-1074
> URL: https://issues.apache.org/jira/browse/QPID-1074
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
> Reporter: Senaka Fernando
> Priority: Minor
>
> Log Configuration Watcher in Java Broker halts on invalid log4j.xml. This issue is discussed on the Qpid Developer list in detail. See [1] for more details.
> [1] http://markmail.org/message/omnpk66vqvajgqh3
> Regards,
> Senaka
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-1074) Log Configuration Watcher in Java
Broker halts on invalid log4j.xml
Posted by "Senaka Fernando (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Senaka Fernando updated QPID-1074:
----------------------------------
Priority: Minor (was: Major)
Issue Type: Task (was: Bug)
It is was observed that the actual problem lies within the log4j implementation, and not within Qpid. We need to sort this out with log4j.
I'm therefore changing the issue type to Task and reducing the priority to minor.
Regards,
Senaka
> Log Configuration Watcher in Java Broker halts on invalid log4j.xml
> -------------------------------------------------------------------
>
> Key: QPID-1074
> URL: https://issues.apache.org/jira/browse/QPID-1074
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
> Reporter: Senaka Fernando
> Priority: Minor
>
> Log Configuration Watcher in Java Broker halts on invalid log4j.xml. This issue is discussed on the Qpid Developer list in detail. See [1] for more details.
> [1] http://markmail.org/message/omnpk66vqvajgqh3
> Regards,
> Senaka
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.