I am trying to load NHaystack onto an FX20 JACE running Niagara version 3.7.106.1. When I dropped the NHaystackService onto the "/Services" folder I get the error below. Does anyone know what is wrong and/or how to fix this?
Thanks,
ERROR [10:18:06 17-Jan-14 PST][sys.service] Service start failed: N Haystack Service
java.lang.NullPointerException
at org.projecthaystack.HDateTime.make(HDateTime.java:68)
at org.projecthaystack.HDateTime.make(HDateTime.java:61)
at org.projecthaystack.HDateTime.now(HDateTime.java:82)
at org.projecthaystack.server.HServer.(HServer.java:412)
at nhaystack.server.NHServer.(NHServer.java:39)
at nhaystack.server.BNHaystackService.createServer(BNHaystackService.java:546)
at nhaystack.server.BNHaystackService.serviceStarted(BNHaystackService.java:380)
at com.tridium.sys.service.ServiceManager.startService(ServiceManager.java)
at com.tridium.sys.service.ServiceManager.register(ServiceManager.java)
at com.tridium.sys.schema.ComponentSlotMap.mount(ComponentSlotMap.java)
at com.tridium.sys.schema.ComponentSlotMap.parent(ComponentSlotMap.java)
at com.tridium.sys.schema.ComponentSlotMap.add(ComponentSlotMap.java)
at javax.baja.sync.AddOp.commit(AddOp.java)
at javax.baja.sync.SyncBuffer.commitOp(SyncBuffer.java)
at javax.baja.sync.SyncBuffer.commit(SyncBuffer.java)
at com.tridium.fox.sys.broker.BBrokerChannel.syncToMaster(BBrokerChannel.java)
at com.tridium.fox.sys.broker.BBrokerChannel.circuitOpened(BBrokerChannel.java)
at com.tridium.fox.sys.BFoxConnection.circuitOpened(BFoxConnection.java)
at com.tridium.fox.session.SessionCircuits$ServiceThread.run(SessionCircuits.java)
Mike JarmyFri 17 Jan 2014
I think I know what's going on here. I see that the timestamp on the ERROR message says that the station's timezone is set to "PST".
"PST" is a "Three-letter time zone ID". I didn't actually know that Java supported timezone's of that type until just now. It appears they have been deprecated since JDK 1.2, and their use is strongly discouraged.
So the error is occuring inside haystack-java because it doesn't know how to decode "PST" -- we've never seen that one before.
Can you trying changing the timezone value for the server that the station is running on? You have to change this setting on the OS itself.
Is the server a Jace? If it is, then you should be able to change the timezone via the "Platform Administration" view in the AX Workbench Platform tools.
If its not a Jace, then I assume you are running Windows or Linux. IIRC for those OSs you have to change the timezone at the OS level, not via the AX Platform tools (I could be wrong here though, does anyone know?).
In either case, you'll want to change the server timezone to a valid Olson timezone, which in your case is probably "America/Los_Angeles".
Rick TijeroWed 22 Jan 2014
I switched the timezone to "Americal/Los_Angeles" and it loaded fine. Thank you Mike.
Rick Tijero Fri 17 Jan 2014
Hi,
I am trying to load NHaystack onto an FX20 JACE running Niagara version 3.7.106.1. When I dropped the NHaystackService onto the "/Services" folder I get the error below. Does anyone know what is wrong and/or how to fix this?
Thanks,
Mike Jarmy Fri 17 Jan 2014
I think I know what's going on here. I see that the timestamp on the ERROR message says that the station's timezone is set to "PST".
"PST" is a "Three-letter time zone ID". I didn't actually know that Java supported timezone's of that type until just now. It appears they have been deprecated since JDK 1.2, and their use is strongly discouraged.
So the error is occuring inside haystack-java because it doesn't know how to decode "PST" -- we've never seen that one before.
Can you trying changing the timezone value for the server that the station is running on? You have to change this setting on the OS itself.
Is the server a Jace? If it is, then you should be able to change the timezone via the "Platform Administration" view in the AX Workbench Platform tools.
If its not a Jace, then I assume you are running Windows or Linux. IIRC for those OSs you have to change the timezone at the OS level, not via the AX Platform tools (I could be wrong here though, does anyone know?).
In either case, you'll want to change the server timezone to a valid Olson timezone, which in your case is probably "America/Los_Angeles".
Rick Tijero Wed 22 Jan 2014
I switched the timezone to "Americal/Los_Angeles" and it loaded fine. Thank you Mike.