[
https://issues.apache.org/jira/browse/QPID-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew MacBean resolved QPID-5429.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.27
> 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
> Assignee: Andrew MacBean
> Priority: Minor
> Fix For: 0.27
>
>
> 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.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
