- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-485) Status Listener configured from Java System property is lost when Configuration file has scan="true" attribute.
by Paweł Stokowiec (JIRA) 05 Jun '15

05 Jun '15

1 0

Syslog appender: RFC 5424 and TCP support
by Guillaume Turri 04 Jun '15

04 Jun '15

Hi, I have an application which uses logback, and which needs to log in a syslog using TCP, and to be compliant with RFC 5424. Though, as far as I understand, those features aren't supported in logback, a patch has been proposed a few years ago [1]. To put it short: * Is there something preventing this patch from being merged? * If the only impediment is that merging it results in several conflicts, would it help if I propose to rebase it? * Is there a way for me to do what I want without this patch (for example using a SocketAppender, and with a well configured layout)? Regards, Guillaume [1]: http://jira.qos.ch/browse/LOGBACK-588

1 0

[JIRA] (LOGBACK-1075) Logback can't read project property resource running as a module in WildFly
by Janario Oliveira (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-1076) Logback can't load custom project appender running as a module in WildFly
by Janario Oliveira (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-1076) Logback can't load custom project appender running as a module in WildFly
by Janario Oliveira (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-1075) Logback can't read project property resource running as a module in WildFly
by Janario Oliveira (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-1074) Undertow web server support
by Eduard Dudar (JIRA) 30 May '15

30 May '15

1 0

[JIRA] (LOGBACK-315) support groovy configuration in logback-access
by Eduard Dudar (JIRA) 29 May '15

29 May '15

1 0

JMSQueueAppender and JMSTopicAppender implements many common code
by Ramon Gordillo 27 May '15

27 May '15

Hi. I am extending some classes for JMS logging, and I want to share my thoughts. 1) Queue and Topic Appender share a lot of common code. The only difference is at JMS level (for example, QueueSession and TopicSession). So I wonder if it is possible to implement the common code at parent level (JMSAppenderBase), using common methods (like getter getSession) and override those common methods in the children. Example: Current code (JMSQueueAppender): ObjectMessage msg = queueSession.createObjectMessage(); Serializable so = pst.transform(event); msg.setObject(so); queueSender.send(msg); Proposed code (on JMSAppenderBase): ObjectMessage msg = getSession().createObjectMessage(); Serializable so = pst.transform(event); msg.setObject(so); getSender().send(msg); Proposed code (on JMSQueueAppender): public Session getSession(){ return getQueueSession() } Proposed code (on JMSTopicAppender): public Session getSession(){ return getTopicSession() } and same for getSender(). 2) JMS Serialization can only send ObjectMessage. Following the same approach as encoders, it will be very useful to provide other kind of serialization, like MapMessage, TextMessage + Headers, etc. Currently, I have done exactly this in my project but manually overriding the methods. Configuring the serialization through configuration will be more elegant and extensible. Please, share your thoughts. Regards. Ramon

1 0

[JIRA] (LOGBACK-1073) Use a WatchService for reconfiguration
by Steffen Brüntjen (JIRA) 27 May '15

27 May '15

1 0