search

OmnyaRa / log4jdbc-log4j2

Automatically exported from code.google.com/p/log4jdbc-log4j2
0 stars 0 forks source link

Unfriendly error message if using slf4j and logging properties file is missing #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
If the app uses slf4j and doesn't have a log4jdbc.log4j2.properties file with 
the spylogdelegator.name set to the slf4j one, the only error in the logs is a 
NoClassDefFoundError about not being able to initialize 
net.sf.log4jdbc.sql.jdbcapi.DriverSpy. The reason for that is because the 
driver class has a static member variable that calls 
SpyLogFactory.getSpyLogDelegator(), and if that method throws an exception 
(which it would in the above case) the only thing that gets logged is the 
NoClassDefFoundError.

Original issue reported on code.google.com by matthewl...@gmail.com on 10 Apr 2013 at 5:16

GoogleCodeExporter commented 9 years ago

Original comment by frederic...@gmail.com on 12 Apr 2013 at 2:04

GoogleCodeExporter commented 9 years ago 
Thank you for reporting this, the error message has been modified, and new 
integration tests have been added. 
See release 1.11, and svn revision 154.

Original comment by frederic...@gmail.com on 22 Apr 2013 at 11:52