You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/06 00:56:00 UTC

[jira] [Commented] (LOG4J2-1955) JMS Appender should be able connect to a broker (later) even it is not present at configuration time

    [ https://issues.apache.org/jira/browse/LOG4J2-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075721#comment-16075721 ] 

ASF subversion and git services commented on LOG4J2-1955:
---------------------------------------------------------

Commit de7487ed22b03f5c1a73ddb8f8d0f8bc89b8f4d8 in logging-log4j2's branch refs/heads/master from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=de7487e ]

[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
>
> 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)