qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-5429) Java Broker does not always write the reason it cannot start-up to qpid.log
Date Fri, 10 Jan 2014 08:32:50 GMT

    [ https://issues.apache.org/jira/browse/QPID-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867623#comment-13867623

ASF subversion and git services commented on QPID-5429:

Commit 1557052 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1557052 ]

QPID-5429: [Java Broker] Exceptions causing startup failure now written to qpid.log too

Previously, such exceptions were only written to stderr. This change means that they written
to qpid.log too,
allowing configuration problems etc to be understood by refering to the one file.

> 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

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

View raw message