[
https://issues.apache.org/jira/browse/QPID-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8694:
-
Description:
When an exception happens in logger itself, it is handled by
BrokerLoggerStatusListe
[
https://issues.apache.org/jira/browse/QPID-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17981692#comment-17981692
]
ASF subversion and git services commented on QPID-8694:
---
Commit 60d4
vavrtom merged PR #287:
URL: https://github.com/apache/qpid-broker-j/pull/287
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@qpid.apach
[
https://issues.apache.org/jira/browse/QPID-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka resolved QPID-8694.
--
Resolution: Implemented
> [Broker-J] BrokerLoggerStatusListener produces repeated stacktraces
>
[
https://issues.apache.org/jira/browse/QPIDJMS-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy A. Bish closed QPIDJMS-609.
---
Resolution: Information Provided
> Qpid JMS 2.3.0: setClientID() Hangs Indefinitely at
> B
[
https://issues.apache.org/jira/browse/QPIDJMS-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17982789#comment-17982789
]
Timothy A. Bish commented on QPIDJMS-609:
-
Options for controlling the failover
