Watchnet issue

[Albertoduo]

Seems that watchnet, after deleting fields on the device page related to a script, crashes with this error:

 

 

2017-04-21 14:15:51,200 INFO  WATCHNET Server started

2017-04-21 14:15:55,471 ERROR REST {"message":null,"source":"/scripts/","arg":"NullPointer"}

java.lang.NullPointerException

at com.dataton.sm.action.ExternalCommandAction.getParamNames(ExternalCommandAction.java:124)

at com.dataton.sm.action.ExternalCommandAction.getDesiredParams(ExternalCommandAction.java:189)

at com.dataton.sm.model.Script.getPotentialParams(Script.java:137)

at com.dataton.sm.model.Script.getBasicInfo(Script.java:163)

at com.dataton.sm.model.Script.getBasicInfo(Script.java:21)

at com.dataton.sm.model.ScriptGroup$Info.<init>(ScriptGroup.java:51)

at com.dataton.sm.model.ScriptGroup.getBasicInfo(ScriptGroup.java:26)

at com.dataton.sm.model.ScriptGroup.getBasicInfo(ScriptGroup.java:14)

at com.dataton.sm.server.services.Scripts.getScriptListItems(Scripts.java:68)

at com.dataton.sm.server.services.Scripts.getAllScripts(Scripts.java:50)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)

at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151)

at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171)

at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:195)

at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104)

at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:402)

at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:349)

at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:106)

at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:259)

at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)

at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)

at org.glassfish.jersey.internal.Errors.process(Errors.java:315)

at org.glassfish.jersey.internal.Errors.process(Errors.java:297)

at org.glassfish.jersey.internal.Errors.process(Errors.java:267)

at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:318)

at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:236)

at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1010)

at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:373)

at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:382)

at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:345)

at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:220)

at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)

at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)

at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524)

at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)

at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158)

at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)

at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)

at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1090)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)

at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)

at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119)

at org.eclipse.jetty.server.Server.handle(Server.java:517)

at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)

at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242)

at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261)

at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)

at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75)

at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213)

at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)

at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)

at java.lang.Thread.run(Thread.java:745)

 

 

on the script page everything disappear an if I try to create a new script is impossible.

 

Someone encountered this problem?

 

 

thanks

 

[joakim]

Hi,

 

I've investigated the issue and as far as I can see it is caused when a device is deleted or renamed while still being used by a script. The issue is resolved and the fix will be included in the next release of WATCHNET which is due for release shortly. In the meantime, try restarting the server and entering the script page again. If that does not work, try adding a device with the same name, and group affiliation, as the one you removed, and enter the script page again to remove the script actions using that device. Then you can remove the device again.

 

Best,

Joakim

[Albertoduo]

Exactly what I do,

If you remember the name of the device previously removed, all the scripts came back again on the list.

Best is for now to fill all the device list, back up the "spec" file and after that start to create scripts only at the end.

Because I'm starting to control a huge of servers and projectors (pj link), when is scheduled the new release?

Best should be to start from scratch with the new one I think.

 

Thank for the support

[joakim]

Hi,

 

Good to hear the "fix" works to bring back the script page.

I cannot give you an exact date for the new release since a lot of testing remains but it will be shortly, within a few week(s) is the best I can give you.

 

Best,

Joakim