[Bug 118] New: Console appender stops working after using paramter logging

http://bugzilla.qos.ch/show_bug.cgi?id=118 Summary: Console appender stops working after using paramter logging Product: Console Plugin Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: critical Priority: P1 Component: interface AssignedTo: logback-dev@qos.ch ReportedBy: graham@crazysquirrel.com I'm pretty new to LOGBack but I've come across what appears to be a fairly major failing in the Eclipse console plugin. The first time a parameter replacing log message is used the console plugin stops working and doesn't log any further messages. I haven't written a simplified test case yet but here are three lines from my code that reliably trigger the problem: //This line appears in the console pluging and the standard tomcat console logger.debug( "Loading foo: " + foo ); //Neither of these two lines appear in the console plugin but do appear in the //standard tomcat console logger.debug( "Loading foo {} bar {} for baz {}", new Object[]{ foo, bar, baz} ); logger.debug( "Loading bar: " + bar ); -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.qos.ch/show_bug.cgi?id=118 noreply.sebastien@qos.ch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #1 from noreply.sebastien@qos.ch 2008-01-13 13:12 ------- Hello Graham, Thanks for your feedback! I haven't been able to reproduce this. On my side, your calls are logged correctly in the Eclipse view. Which version of logback are you using? Please give me the version that is in your classpath, but also the version that is in the logback plugin. You can see which version is used by the plugin by looking at the following directory: ECLIPSE_INSTALL_DIR/plugins/ch.qos.logback.eclipse_1.0.1/lib Cheers -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.qos.ch/show_bug.cgi?id=118 ------- Comment #2 from graham@crazysquirrel.com 2008-01-16 16:12 ------- Hi, I've read up a bit more and I'm not sure this isn't user error on my part. I noticed in the documentation is states that SocketAppenders don't use formatters because the objects to be logged are serialized and sent over the wire. Some of the variable objects I passed in weren't serializable. I suspect what is happening is a serialization exception is being thrown which is closing the socket and stopping any further log messages (even ones that can be serialized) from getting though. I'm using logback 0.9.3 with slf4j 1.3.0 - these are the only versions I've ever downloaded. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.qos.ch/show_bug.cgi?id=118 ------- Comment #3 from matt.fowles@gmail.com 2008-01-16 16:19 ------- I would say that is still a bug, if objects passed in are not serializable, they should be forced to strings and those should be serialized. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.qos.ch/show_bug.cgi?id=118 ------- Comment #4 from noreply.ceki@qos.ch 2008-01-16 17:11 ------- This bug is probably relateed to bug #100. See http://bugzilla.qos.ch/show_bug.cgi?id=100 -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.qos.ch/show_bug.cgi?id=118 ------- Comment #5 from noreply.sebastien@qos.ch 2008-01-16 20:34 ------- Matt, You're right, this is a bug. I'll speak with Ceki friday about what we should do and keep you informed. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.qos.ch/show_bug.cgi?id=118 ------- Comment #6 from noreply.sebastien@qos.ch 2008-01-19 09:55 ------- Hello Graham, I've spoken with Ceki. The SocketAppender will be modified for the next release of logback. Thanks for your feedback! -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.qos.ch/show_bug.cgi?id=118 ------- Comment #7 from joern@huxhorn.de 2008-01-28 12:53 ------- Hi guys. I really think this should be fixed in LoggingEvent instead of SocketAppender because LoggingEvent implements Serializable and breaks the contract in case of non-serializable parameters. The SocketAppender workaround I appended to bug #100 is just that - a workaround for the original problem. Please take a look at the patch I added to bug #100. Thanks, Joern. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.qos.ch/show_bug.cgi?id=118 noreply.ceki@qos.ch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DUPLICATE ------- Comment #8 from noreply.ceki@qos.ch 2008-03-13 01:54 ------- *** This bug has been marked as a duplicate of bug 100 *** -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
participants (1)
-
bugzilla-daemon@pixie.qos.ch