[ http://jira.qos.ch/browse/LBGENERAL-16?page=com.atlassian.jira.plugin.system... ] Joern Huxhorn commented on LBGENERAL-16: ---------------------------------------- No problem. I'm sorry, but I can't reproduce the scenario anymore because we are not using the logback socket appender anymore (but the Lilith one instead) and the software where the problem happened is in production mode so I can't just change the configuration back to a probably faulty one... As I said, I wasn't able to produce the problem in an isolated test case which annoyed me quite a bit ;) I'd suggest to just ignore this problem until a more reasonable/better documented manifestation of it happens to someone. I still think that it is related to the mix of jcl104 and log4j binding. I didn't have the chance to check if it's still happening with jcl instead of jcl104. Again: Sorry that I can't be of greater help concerning this problem...
logback 0.9.8 keeps dropping and recreating connections -------------------------------------------------------
Key: LBGENERAL-16 URL: http://jira.qos.ch/browse/LBGENERAL-16 Project: logback-general Issue Type: Bug Components: build-structure Affects Versions: unspecified Environment: Operating System: All Platform: All Reporter: Joern Huxhorn Assignee: Logback dev list Priority: Blocker
I have a serious problem with logback 0.9.8 that forced me to downgrade to 0.9.7 again. The socket-appender keeps dropping and recreating connections, missing log-events in the process. It does so at least once, i.e. creating a connection without writing a single event and then closing it again immeditaly. I tried to reporduce the behaviour in a simple test program but didn't succeed. Everything is fine in a simple test. In both of our "real" applications, however, this problem is definitly reproducible and just vanishes after a downgrade to 0.9.7. I suspect that the problem is connected to log4j-over-slf4j because that's one of the differences to my small test. We have the following dependencies: <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <scope>compile</scope> </dependency> <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl104-over-slf4j</artifactId> <scope>runtime</scope> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>log4j-over-slf4j</artifactId> <scope>runtime</scope> </dependency> <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-core</artifactId> <scope>compile</scope> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <scope>compile</scope> </dependency> with slf4j 1.4.3 and logback 0.9.8 as version. We use several third-party jars in our apps, e.g. spring, commons-stuff etc., so we have to map both commons-logging as well as log4j to logback. This worked perfectly up to version 0.9.7 but doesn't work anymore! I'm sorry about this rather obscure error report but I'm really quite clueless about the problem myself. I just checked the svn repos and the last socket appender change was done 4 month ago so that can't be responsible... I'll try to investigate this some more but you might already know what's wrong since you know what changed between 0.9.7 and 0.9.8. The problem exists on at least Windows and Solaris, btw.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira