#695 Null pointer with stack trace

[Jon Schewe (BBN)]

I see this in my log from time to time. With version 5 I've been getting stack traces on most of the exceptions. However here is one that I'm not getting a stack trace from. I've added some context to the log messages, if that helps. Do you have a default exception handler? If not you may want to set one up so that it always logs the full stack trace. An example of one is here: https://github.com/jpschewe/fll-sw/blob/master/scoring/src/fll/util/GuiExceptionHandler.java

2018-12-14 13:50:38,908 INFO [CaldavConnection-38018] davmail.connection - LOGON - 0:0:0:0:0:0:0:1:38018 USER
2018-12-14 13:50:40,792 INFO [CaldavConnection-38016] davmail.connection - LOGON - 0:0:0:0:0:0:0:1:38016 USER
2018-12-14 13:50:41,518 ERROR [CaldavConnection-38016] davmail - java.lang.NullPointerException
java.lang.NullPointerException
2018-12-14 13:50:42,518 INFO [CaldavConnection-38016] davmail.connection - DISCONNECT - 0:0:0:0:0:0:0:1:38016
2018-12-14 13:50:42,929 INFO [davmail.caldav.CaldavServer] davmail.connection - CONNECT - 0:0:0:0:0:0:0:1:38032
2018-12-14 13:50:43,466 INFO [CaldavConnection-38012] davmail.connection - LOGON - 0:0:0:0:0:0:0:1:38012 USER

[Mickael Guessant]

The awt catcher wouldn't help much: this happens on a CaldavConnection thread
=> best bet is to find the place where the exception is thrown/catched to fix the log statement

[Mickael Guessant]

Reported nullpointerexception fixed, please report again if you find new ones with 5.1.0