On Mon, Jul 28, 2008 at 10:54 AM, Dick Davies <[EMAIL PROTECTED]> wrote: > On Mon, Jul 28, 2008 at 2:37 PM, Dave <[EMAIL PROTECTED]> wrote: > >> <[EMAIL PROTECTED]> wrote: > >>> "ERROR 2008-07-25 10:24:45,419 CalendarTag:doStartTag - Calendar tag >>> exception >>> java.lang.NullPointerException at >>> org.apache.roller.weblogger.ui.core.tags.calendar.WeblogCalendarModel.computeUrl >>> (WeblogCalendarModel.java:275) >> >> From the looks of the code at line 275, it appears that something is >> going wrong in the database access layer. > >>> We're running Roller 4.0 on Glassfish 2 using DB2 8.1 FP14 as the backend >>> database. >> >> Ah, DB2. I've never tried Roller with DB2. > >>> Any ideas as to where to look to track this problem down? >> >> Are there any errors in the log file immediately before the stack >> trace that you sent?
> > this is the same roller deployment I've been working on. There's nothing else > in the logs, no, and we've got debugging cranked right up (as far as I > can tell). > I'm suspecting something like a locale mismatch with DB2 - is there a way > to enable debugging in JPA (I'm assuming that's the default persistence layer > now in Roller 4.x)? Yes, you can specify DEBUG level logging for almost any part of Roller via your roller-custom.properties file. Here's the default configuration for OpenJPA logging: openjpa.Log=commons log4j.category.openjpa.Tool=WARN log4j.category.openjpa.Runtime=WARN log4j.category.openjpa.Remote=WARN log4j.category.openjpa.DataCache=WARN log4j.category.openjpa.MetaData=WARN log4j.category.openjpa.Enhance=WARN log4j.category.openjpa.Query=WARN log4j.category.openjpa.jdbc.SQL=WARN log4j.category.openjpa.jdbc.JDBC=WARN log4j.category.openjpa.jdbc.Schema=WARN So, to turn on SQL debugging you'd add this to your roller-custom.properties file: log4j.category.openjpa.jdbc.SQL=DEBUG - Dave - Dave
