Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Solved Upgraded H2 to SQL - ran succesfully but now "server errors" occuring
-
My install was running a little sluggishly recently so I decided on a few improvements. I allocated more heap space to java and I have just upgraded the database to MYSQL from H2. The improvement in all around speed is amazing!!
Everything seemed to have run smoothly. I can query the database and see data-points created etc.However when toggling a data point on/off I am receiving "server error has occurred" warnings. Making changes to the data-point settings is bringing up the same error.
ERROR 2015-04-22 16:39:28,718 (com.serotonin.m2m2.web.dwr.util.ExceptionDetectionFilter.doFilter:38) - DWR invocation exception java.lang.NullPointerException at com.serotonin.m2m2.web.mvc.rest.v1.model.pointValue.PointValueTimeModel.<init>(PointValueTimeModel.java:54) at com.serotonin.m2m2.web.mvc.rest.v1.publisher.pointValue.PointValueWebSocketPublisher.pointTerminated(PointValueWebSocketPublisher.java:149) at com.serotonin.m2m2.rt.RuntimeManager.stopDataPoint(RuntimeManager.java:430) at com.serotonin.m2m2.rt.RuntimeManager.saveDataPoint(RuntimeManager.java:339) at com.serotonin.m2m2.web.dwr.DataPointDwr.toggle(DataPointDwr.java:89) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.directwebremoting.impl.ExecuteAjaxFilter.doFilter(ExecuteAjaxFilter.java:34) at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:428) at com.serotonin.m2m2.web.dwr.util.TranslationsFilter.doFilter(TranslationsFilter.java:37) at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:428) at com.serotonin.m2m2.web.dwr.util.ExceptionDetectionFilter.doFilter(ExceptionDetectionFilter.java:26) at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:428) at com.serotonin.m2m2.web.dwr.util.DwrPermissionFilter.doFilter(DwrPermissionFilter.java:38) at org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:428) at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:431) at org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:283) at org.directwebremoting.servlet.PlainCallHandler.handle(PlainCallHandler.java:52) at org.directwebremoting.servlet.UrlProcessor.handle(UrlProcessor.java:101) at org.directwebremoting.servlet.DwrServlet.doPost(DwrServlet.java:146) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1667) at org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:83) at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:300) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) 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:577) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:485) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:290) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:606) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:535) at java.lang.Thread.run(Unknown Source) ERROR 2015-04-22 16:40:27,815 (org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.handleTransportError:61) - Transport error for WebSocket session id=1e12a4 java.net.SocketTimeoutException: Timeout on Read at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onReadTimeout(AbstractWebSocketConnection.java:526) at org.eclipse.jetty.io.AbstractConnection.onFillInterestedFailed(AbstractConnection.java:173) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillInterestedFailed(AbstractWebSocketConnection.java:496) at org.eclipse.jetty.io.AbstractConnection$ReadCallback$1.run(AbstractConnection.java:582) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:606) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:535) at java.lang.Thread.run(Unknown Source) ERROR 2015-04-22 16:40:28,239 (org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.handleTransportError:61) - Transport error for WebSocket session id=161de66 java.net.SocketTimeoutException: Timeout on Read at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onReadTimeout(AbstractWebSocketConnection.java:526) at org.eclipse.jetty.io.AbstractConnection.onFillInterestedFailed(AbstractConnection.java:173) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillInterestedFailed(AbstractWebSocketConnection.java:496) at org.eclipse.jetty.io.AbstractConnection$ReadCallback$1.run(AbstractConnection.java:582) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:606) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:535) at java.lang.Thread.run(Unknown Source) ERROR 2015-04-22 16:40:28,411 (org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.handleTransportError:61) - Transport error for WebSocket session id=b59ed5 java.net.SocketTimeoutException: Timeout on Read at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onReadTimeout(AbstractWebSocketConnection.java:526) at org.eclipse.jetty.io.AbstractConnection.onFillInterestedFailed(AbstractConnection.java:173) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillInterestedFailed(AbstractWebSocketConnection.java:496) at org.eclipse.jetty.io.AbstractConnection$ReadCallback$1.run(AbstractConnection.java:582) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:606) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:535) at java.lang.Thread.run(Unknown Source)
After going for a quick coffee break, I came back and could toggle on/off, save data-point changes!! It seemed to have resolved itself.
Any insight into what is happening here would be greatly appreciated.
Thanks in advance,
Dominic
-
@Dominic.Irl said:
What version of Mango is this? I think something may have gone wrong with the conversion of the units for data points but I'm pretty sure this issue was fixed in the latest version. -
Hi Joel,
It is version 2.5.0.
I have figured it out. I had public-dashboards open with the data points being visualised via the API to a local web page. The data points that were being utilised on the page were the points that were giving me an error when I went to amend them. Simply closing the open web page allowed me to edit the data points without error.Dominic