I have a vague feeling this might have been reported already, but I can't find it, so here goes. The SimpleQueueManager and RequestManager timer tasks fail with the following exceptions java.lang.NullPointerException at com.arsdigita.notification.SimpleQueueManager.run(SimpleQueueManager.java:59) at java.util.TimerThread.mainLoop(Timer.java:430) at java.util.TimerThread.run(Timer.java:380) java.lang.NullPointerException at com.arsdigita.notification.RequestManager$1.excurse(RequestManager.java:96) at com.arsdigita.kernel.KernelExcursion.run(KernelExcursion.java:57) at com.arsdigita.notification.RequestManager.run(RequestManager.java:204) at java.util.TimerThread.mainLoop(Timer.java:430) at java.util.TimerThread.run(Timer.java:380) In both case, the offending line is the second one in the following snippet: Session session = SessionManager.getSession(); session.getTransactionContext().beginTxn(); Instrumenting either class with a few log4j statements shows that it is the "session" object that is null. I am at //core-platform/dev/...@37563 or thereabouts.
Is bug 109215 related to this?
I think this was fixed as part of bug 109391.
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future. Moving to ON_QA.