Re: Starting and restarting managers

Managers are not designed to be shutdown and restarted. If you are causing your manager to come and go for the JMS support then I don’t think you implemented it correctly. If you look at the tcp socket manager it has a reconnector inside of it to handle retrying the connection. JMS should work

Re: [log4j2] Legacy docs

The Legacy section on the left nav bar contains a link for Log4j 1.x and Log4j 2.3. These two releases (and sites) have special significance. No other releases do. They should not be lost in a sea of other releases. Plus, it would make that left navigation extremely long. Although all the

Jenkins build is back to stable : Log4j 2.x #2837

See

Starting and restarting managers

Hi All, I am thinking about how to best solve cases like https://issues.apache.org/jira/browse/LOG4J2-1955 In a nutshell: Log4j starts but some external resource is not available (like a JMS broker, a database server, and so on) Right now, you're out of luck. You other appenders will keep on

Jenkins build became unstable: Log4j 2.x #2836

See

Re: [log4j2] Legacy docs

Hi, You're talking about something different, the change reports are one thing, the site is another. I am thinking of users that are stuck on an old random release either by direct or transitive dependency. Using the site that matches their version would be quite helpful. No urgent of course.

[jira] [Commented] (LOG4J2-1956) JMS Appender broker password should be a char[], not a String

[ https://issues.apache.org/jira/browse/LOG4J2-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062497#comment-16062497 ] ASF subversion and git services commented on LOG4J2-1956: - Commit

[jira] [Commented] (LOG4J2-1956) JMS Appender broker password should be a char[], not a String

[ https://issues.apache.org/jira/browse/LOG4J2-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062492#comment-16062492 ] ASF subversion and git services commented on LOG4J2-1956: - Commit

[jira] [Closed] (LOG4J2-1956) JMS Appender broker password should be a char[], not a String

[ https://issues.apache.org/jira/browse/LOG4J2-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1956. Resolution: Fixed Fix Version/s: 2.9 In Git master. > JMS Appender broker password should

[jira] [Created] (LOG4J2-1956) JMS Appender broker password should be a char[], not a String

Gary Gregory created LOG4J2-1956: Summary: JMS Appender broker password should be a char[], not a String Key: LOG4J2-1956 URL: https://issues.apache.org/jira/browse/LOG4J2-1956 Project: Log4j 2

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062486#comment-16062486 ] ASF subversion and git services commented on LOG4J2-1934: - Commit

[jira] [Updated] (LOG4J2-1955) JMS Appender can 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: - Description: JMS Appender can connect to a broker (later) even it is not present at

[jira] [Updated] (LOG4J2-1955) JMS Appender can 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 can connect to a broker (later) even it is not present at configuration

[jira] [Resolved] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-1934. -- Resolution: Fixed Fix Version/s: 2.9 I am looking for a code review from the community.

[jira] [Commented] (LOG4J2-1934) JMS Appender does not know how to recover from a broken connection

[ https://issues.apache.org/jira/browse/LOG4J2-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062481#comment-16062481 ] ASF subversion and git services commented on LOG4J2-1934: - Commit

Re: [log4j2] Legacy docs

I only created that so people would be able to find release 2.3 if they needed to use Java 6. My fear is that if we add all the releases there then that will get lost in the noise. BTW - all the releases are listed at http://logging.apache.org/log4j/2.x/changes-report.html

[log4j2] Legacy docs

Hi All, We have a nice "Legacy" section of our site. I think we should track every release there. 2c, Gary

[jira] [Comment Edited] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062464#comment-16062464 ] Gary Gregory edited comment on LOG4J2-1699 at 6/26/17 12:51 AM: {quote}

[jira] [Commented] (LOG4J2-1699) Configurable Log File Permissions with PosixFilePermission

[ https://issues.apache.org/jira/browse/LOG4J2-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062464#comment-16062464 ] Gary Gregory commented on LOG4J2-1699: -- {quote} 1. Is XML Configuration tag should be shortenen,

[jira] [Commented] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

[ https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062463#comment-16062463 ] Gary Gregory commented on LOG4J2-1811: -- Maybe a "Quick Start" section would help. > Log4j 2

[jira] [Resolved] (LOG4J2-1952) log4j doesn't find log4j2.yaml

[ https://issues.apache.org/jira/browse/LOG4J2-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1952. Resolution: Duplicate > log4j doesn't find log4j2.yaml > -- >

[jira] [Updated] (LOG4J2-1952) log4j doesn't find log4j2.yaml

[ https://issues.apache.org/jira/browse/LOG4J2-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1952: --- Issue Type: Documentation (was: Bug) > log4j doesn't find log4j2.yaml >

[jira] [Assigned] (LOG4J2-1952) log4j doesn't find log4j2.yaml

[ https://issues.apache.org/jira/browse/LOG4J2-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1952: -- Assignee: Mikael Ståldal > log4j doesn't find log4j2.yaml >