March 2013 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-817) java.nio.channels.ClosedChannelException in logback 1.0.10
by Ceki Gulcu (JIRA) 26 Mar '13

26 Mar '13

1 0

[JIRA] (LOGBACK-819) support socket server configuration using JoranConfigurator
by Carl Harris (JIRA) 26 Mar '13

26 Mar '13

1 0

[JIRA] (LOGBACK-818) add support for SSL-enabled socket appender and server
by Carl Harris (JIRA) 26 Mar '13

26 Mar '13

1 0

[JIRA] (LOGBACK-817) java.nio.channels.ClosedChannelException in logback 1.0.10
by leon (JIRA) 26 Mar '13

26 Mar '13

1 0

Webshpere using QOS logback: log-files are locked for rolling
by regards, Oleg 26 Mar '13

26 Mar '13

Hello to everyone! I don't know - whether anyboby asked about that or not, but I've not found the solution for my issue by serfing internet. My issue id described here - http://stackoverflow.com/questions/15628546/webshpere-and-qos-logback-log-f… And I repost it here: We are using WebSphere app server for our application, and "logback" logging framework for managing our log files. Seemed everithing was working fine but recently we detected unacceptable behavior of file rolling. For the first starting of our application on WebSphere rolling log files (by size and by days) works good, but when we stop application - current log file is locked by java.exe(IBM WAS) process and when we start application over again - rolling logs does not work because of previous locking. When I looked on the file throu windows Unlocker i was surprised - there were 2 processes which locks current file. And if we stop app and start it again - there will be 3 java.exe that lock current log file, although in the task manager running only one process. Sometimes I catch OutOfMemory error during such "testing". So that, we have very big log file at the end. (20GB and more) I've found some similar problems but with log4j rolling. And there are no any explanation why it was so - just one was like - log4j is not recommended for websphere. And seems problem not exactly in "logger" at all. So, is there anybody who could answer 2 questions - Why does WebSphere lock file and not release it, when application has been already stopped??? How to release (or say to WebSphere not to lock) locking of the log file when application is stopped in a right way(without using cheats like Unlocker, Task Manager, etc.)? Thanks for attention... any help would be appreciated. regards, Oleg.

1 0

[qos-ch/logback] e55752: use concurrentHashMap
by Ceki Gulcu 25 Mar '13

25 Mar '13

Branch: refs/heads/simpleloggerperf Home: https://github.com/qos-ch/logback Commit: e55752559c2400b23e642066ec100449760d36e8 https://github.com/qos-ch/logback/commit/e55752559c2400b23e642066ec10044976… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-03-25 (Mon, 25 Mar 2013) Changed paths: M logback-classic/src/test/java/org/slf4j/impl/SimpleLoggerFactory.java Log Message: ----------- use concurrentHashMap

1 0

[qos-ch/logback] d41b80: minor changes
by Ceki Gulcu 25 Mar '13

25 Mar '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: d41b804b270ed31a3f2338b2218d51fdc306fa2e https://github.com/qos-ch/logback/commit/d41b804b270ed31a3f2338b2218d51fdc3… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-03-25 (Mon, 25 Mar 2013) Changed paths: M logback-core/src/test/java/ch/qos/logback/core/rolling/RenameUtilTest.java M logback-site/src/site/pages/job.html Log Message: ----------- minor changes Commit: 281551b037fba6ae59f3fda8857193c1777c403a https://github.com/qos-ch/logback/commit/281551b037fba6ae59f3fda8857193c177… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-03-25 (Mon, 25 Mar 2013) Changed paths: M logback-access/pom.xml M logback-classic/pom.xml M logback-core/pom.xml M logback-examples/pom.xml M logback-site/pom.xml M pom.xml Log Message: ----------- start work on 1.0.12-SNAPSHOT Compare: https://github.com/qos-ch/logback/compare/28a154ddf844...281551b037fb

1 0

[qos-ch/logback] 615671: ongoing work on LOGBACK-791
by Ceki Gulcu 25 Mar '13

25 Mar '13

Branch: refs/heads/LOGBACK_791 Home: https://github.com/qos-ch/logback Commit: 6156712d425049a5aec7a066cb26cb2205a780d3 https://github.com/qos-ch/logback/commit/6156712d425049a5aec7a066cb26cb2205… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2013-03-25 (Mon, 25 Mar 2013) Changed paths: M logback-access/src/main/java/ch/qos/logback/access/joran/action/ConfigurationAction.java M logback-classic/src/main/java/ch/qos/logback/classic/joran/action/ConfigurationAction.java M logback-classic/src/test/java/ch/qos/logback/classic/net/SocketAppenderTest.java M logback-core/src/main/java/ch/qos/logback/core/BasicStatusManager.java M logback-core/src/main/java/ch/qos/logback/core/status/OnConsoleStatusListener.java M logback-core/src/main/java/ch/qos/logback/core/status/StatusManager.java Log Message: ----------- ongoing work on LOGBACK-791

1 0

[JIRA] (LOGBACK-791) Design issue: Should an OnConsoleStatusListener be addable to the StatusManager if there already is one?
by Ceki Gulcu (JIRA) 25 Mar '13

25 Mar '13

1 0

[qos-ch/logback]
by ceki 25 Mar '13

25 Mar '13

Branch: refs/tags/v_1.0.11 Home: https://github.com/qos-ch/logback

1 0