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

Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2013/12/17 12:46:07 UTC

[jira] [Updated] (QPID-5429) Java Broker does not always write the reason it cannot start-up to qpid.log

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

Keith Wall updated QPID-5429:
-----------------------------

    Priority: Minor  (was: Major)

> Java Broker does not always write the reason it cannot start-up to qpid.log
> ---------------------------------------------------------------------------
>
>                 Key: QPID-5429
>                 URL: https://issues.apache.org/jira/browse/QPID-5429
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Keith Wall
>            Priority: Minor
>
> If the Java Broker is unable to complete its start-up, for example, because a port it requires is already bound, it writes the exception to standard out.  The error message is not however written to the qpid.log.
> This makes diagnosing startup issues more problematic.  This is especially so for users who have embedded Qpid within other products (containers, job control systems etc), where the plumbing of the standard streams is often misconfigured. 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org