You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2017/07/06 00:22:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Gary Gregory updated LOG4J2-1955:
---------------------------------
    Summary: JMS Appender should be able connect to a broker (later) even it is not present at configuration time.  (was: JMS Appender can 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 can 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)