[
https://issues.apache.org/jira/browse/LOG4J2-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078752#comment-16078752
]
ASF subversion and git services commented on LOG4J2-1955:
---------------------------------------------------------
Commit 55f80f35060d60788393714514b1c27aa5773095 in logging-log4j2's branch
refs/heads/master from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=55f80f3 ]
[LOG4J2-1934] JMS Appender does not know how to recover from a broken
connection.
[LOG4J2-1955]JMS Appender should be able connect to a broker (later)
even it is not present at configuration time.
> JMS Appender should be able connect to a broker (later) even it is not
> present at configuration time
> ----------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1955
> URL: https://issues.apache.org/jira/browse/LOG4J2-1955
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Fix For: 2.9
>
>
> JMS Appender should be able connect to a broker (later) even it is not
> present at configuration time.
> The use case is:
> # Start an application using Log4j.
> # The JMS broker is not running
> # Log4j does not log events to JMS
> # The broker is started
> # Log4j still does not log events to JMS
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
