java.lang.NullPointerException

[Former user]

I get this about 50% of the time I reboot any of my 20 nodes. It seems to be worst than before.

The solution seems to be delete *.nxt and restart server.

From what I understand it's related to some or all the .nxt files being corrupted.

Could you handle this error by simply duping the existing .nxt files and re-downloading automatically from the network without making me delete files and restart the server manually?

[abuelau]

From the log:

[2014-01-13 08:06:00.779] Loading blocks... [2014-01-13 08:06:01.694] 10: java.io.StreamCorruptedException: invalid type code: 00 2014-01-13 08:06:01.731:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@2a80364e{/,file:/var/nxt/webapps/root/,AVAILABLE}{/root} 2014-01-13 08:06:01.785:INFO:oejs.ServerConnector:main: Started ServerConnector@56f86d9e{HTTP/1.1}{0.0.0.0:7874} 2014-01-13 08:06:02.498:INFO:oejs.ServerConnector:main: Started ServerConnector@2410fbf9{SSL-http/1.1}{0.0.0.0:7875} [2014-01-13 09:04:13.983] 15: java.lang.NullPointerException [2014-01-13 09:04:21.623] 15: java.lang.NullPointerException [2014-01-13 09:04:24.234] 15: java.lang.NullPointerException [2014-01-13 09:04:30.401] 15: java.lang.NullPointerException [2014-01-13 09:04:34.216] 15: java.lang.NullPointerException [2014-01-13 09:04:34.727] 15: java.lang.NullPointerException [2014-01-13 09:04:42.883] 15: java.lang.NullPointerException [2014-01-13 09:04:51.588] 15: java.lang.NullPointerException

[nxt-ext]

Check script exists.

If you don't use nxt-kit, just make yours based on it and cron that one.

[Jean-Luc Picard]

This would be fixing the symptom and not the problem. The problem is that your nxt files get corrupted on shutdown because the shutdown scripts don't allow enough time for the java process to exit cleanly. This is what needs to be fixed, and if not it will only get worse when I switch from using serialized java objects to a real database, then the database may get corrupted. Somehow you need to wait longer for the java process to exit. When using Ctrl-C or kill -SIGTERM and give it enough time to exit, I have never seen corrupted nxt files with recent version, haven't had to use kill -9 in a long time.