Closed GoogleCodeExporter closed 8 years ago
This is not a log4jdbc issue. It appears that your framework may be using
log4jdbc-remix or some other log4jdbc derivative.
You can tell this because in the exception stack trace, the class that is
throwing the null pointer exception is DefaultResultSetCollector which does not
exist in log4jdbc.
Original comment by arthur.b...@gmail.com
on 6 Dec 2013 at 12:45
Sorry. I mistake you with log4jdbc-log4j2.
Original comment by kauedb
on 6 Dec 2013 at 2:50
Original issue reported on code.google.com by
kauedb
on 5 Dec 2013 at 9:57