[
https://issues.apache.org/jira/browse/LOG4J2-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-1955.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.9
In Git master. Recoded to follow the Reconnect thread pattern from
{{TcpSocketManager}}. Looking for a peer-review.
> 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)
