Problem with incoming data after updating to 3.7

flpnone8 years ago

Hi,

I updated Traccar server to version 3.7 and all incoming data from trackers stopped. The server disconnects tcp connection immediately and logs error "Failed to initialize an accepted socket", please see attached log. If I downgrade back to 3.6, everything works fine. Any idea what could be the problem?


STATUS | wrapper  | 2016/09/23 08:43:15 | Launching a JVM...
INFO   | jvm 1    | 2016/09/23 08:43:15 | WrapperManager: Initializing...
INFO   | jvm 1    | 2016/09/23 08:43:16 | [WrapperSimpleAppMain] INFO com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Started.
INFO   | jvm 1    | 2016/09/23 08:43:17 | INFO 9/23/16 8:43 AM: liquibase: Clearing database change log checksums
INFO   | jvm 1    | 2016/09/23 08:43:17 | INFO 9/23/16 8:43 AM: liquibase: Successfully acquired change log lock
INFO   | jvm 1    | 2016/09/23 08:43:17 | INFO 9/23/16 8:43 AM: liquibase: Successfully released change log lock
INFO   | jvm 1    | 2016/09/23 08:43:17 | INFO 9/23/16 8:43 AM: liquibase: Successfully acquired change log lock
INFO   | jvm 1    | 2016/09/23 08:43:20 | INFO 9/23/16 8:43 AM: liquibase: Reading from track.DATABASECHANGELOG
INFO   | jvm 1    | 2016/09/23 08:43:20 | INFO 9/23/16 8:43 AM: liquibase: Reading from track.DATABASECHANGELOG
INFO   | jvm 1    | 2016/09/23 08:43:20 | INFO 9/23/16 8:43 AM: liquibase: Successfully released change log lock
INFO   | jvm 1    | 2016/09/23 08:43:20 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.util.log - Logging initialized @4618ms
INFO   | jvm 1    | 2016/09/23 08:43:20 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.server.Server - jetty-9.2.19.v20160908
INFO   | jvm 1    | 2016/09/23 08:43:22 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@3732cf50{/api,null,AVAILABLE}
INFO   | jvm 1    | 2016/09/23 08:43:22 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.server.ServerConnector - Started ServerConnector@23d90ed5{HTTP/1.1}{0.0.0.0:8082}
INFO   | jvm 1    | 2016/09/23 08:43:22 | [WrapperSimpleAppMain] INFO org.eclipse.jetty.server.Server - Started @6433ms
INFO   | jvm 1    | 2016/09/23 08:43:46 | Sep 23, 2016 8:43:46 AM org.jboss.netty.channel.socket.nio.AbstractNioSelector
INFO   | jvm 1    | 2016/09/23 08:43:46 | WARNING: Failed to initialize an accepted socket.
INFO   | jvm 1    | 2016/09/23 08:43:46 | java.lang.NullPointerException: handler
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.<init>(DefaultChannelPipeline.java:725)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at org.jboss.netty.channel.DefaultChannelPipeline.addLast(DefaultChannelPipeline.java:100)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at org.traccar.BasePipelineFactory.getPipeline(BasePipelineFactory.java:233)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at org.jboss.netty.channel.socket.nio.NioServerBoss.registerAcceptedChannel(NioServerBoss.java:134)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at org.jboss.netty.channel.socket.nio.NioServerBoss.process(NioServerBoss.java:104)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at org.jboss.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
INFO   | jvm 1    | 2016/09/23 08:43:46 |       at java.lang.Thread.run(Thread.java:745)
INFO   | jvm 1    | 2016/09/23 08:43:46 |
Anton Tananaev8 years ago

There was a bug. I just fixed it. Try to add following line to the config:

<entry key='event.ignitionHandler'>true</entry>
flpnone8 years ago

Ok, it's working now with the config change you suggested. Thanks!

Anton Tananaev8 years ago

For future updates, you should update config file with new release as well.

flpnone8 years ago

Just to let you know, event.ignitionHandler was in the config file, but value was false.

Anton Tananaev8 years ago

Not sure why it was false. In the original config it should be true.