OK, so the tracking is working fine, but every now and then when I configure a report I get error messages in the wrapper log file and no output is displayed in the GUI. Anyone getting anything similar?
Messages are:
INFO | jvm 1 | 2016/10/26 18:12:40 | Oct 26, 2016 6:12:40 PM org.glassfish.jersey.server.ServerRuntime$Responder writeResponse
INFO | jvm 1 | 2016/10/26 18:12:40 | SEVERE: An I/O error has occurred while writing a response message entity to the container output stream.
INFO | jvm 1 | 2016/10/26 18:12:40 | org.glassfish.jersey.server.internal.process.MappableException: org.eclipse.jetty.io.EofException
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:92)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:162)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1130)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:711)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:444)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:434)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:329)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:473)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:427)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:388)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:341)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:228)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.Server.handle(Server.java:499)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
INFO | jvm 1 | 2016/10/26 18:12:40 | at java.lang.Thread.run(Thread.java:745)
INFO | jvm 1 | 2016/10/26 18:12:40 | Caused by: org.eclipse.jetty.io.EofException
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:192)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:408)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.io.WriteFlusher.write(WriteFlusher.java:302)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.io.AbstractEndPoint.write(AbstractEndPoint.java:129)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.server.HttpConnection$SendCallback.process(HttpConnection.java:702)
INFO | jvm 1 | 2016/10/26 18:12:40 | at org.eclipse.jetty.util.IteratingCallback.processing(IteratingCallback.java:246)
Are you using latest official release without any modifications?
Hi Anton,
Yep, 3.7, stock standard.
Pete
It seems like connection was closed by the browser. Not sure about the reason. Have you check browser developer console?
I had the console set to clear log on page reload. I've set it to save log and will monitor. I opened up using explorer and had no issues yet. Reloaded on Chrome and it worked ok. It's happened more than once so I'll continue to monitor and update the thread if I find anything.
Thanks for your help so far.
Pete
OK, here is the output from the console when it happened again:
app.min.js?_dc=1477467460960:156 Uncaught TypeError: Cannot read property 'length' of null
loadReport @ app.min.js?_dc=1477467460960:156
fire @ ext-all.js:22
dispatch @ ext-all.js:22
a.doFireEvent @ ext-all.js:22
fireEventArgs @ ext-all.js:22
fireEvent @ ext-all.js:22
onProxyLoad @ ext-all.js:22
triggerCallbacks @ ext-all.js:22
setCompleted @ ext-all.js:22
setException @ ext-all.js:22
setException @ ext-all.js:22
processResponse @ ext-all.js:22
(anonymous function) @ ext-all.js:22
callback @ ext-all.js:22
onComplete @ ext-all.js:22
abort @ ext-all.js:22onTimeout @ ext-all.js:22
(anonymous function) @ ext-all.js:22
(anonymous function) @ ext-all.js:22
Please try it with "debug.html" instead.
Uncaught TypeError: Cannot read property 'length' of nullload MapController.js:151
Report @ MapController.js:151
fire @ ext-all-debug.js:20226
dispatch @ ext-all-debug.js:54609
prototype.doFireEvent @ ext-all-debug.js:54762
fireEventArgs @ ext-all-debug.js:20986
fireEvent @ ext-all-debug.js:20945
onProxyLoad @ ext-all-debug.js:89380
triggerCallbacks @ ext-all-debug.js:77731
setCompleted @ ext-all-debug.js:77699
setException @ ext-all-debug.js:77724
setException @ ext-all-debug.js:86711
processResponse @ ext-all-debug.js:86692
(anonymous function) @ ext-all-debug.js:87281
callback @ ext-all-debug.js:8442
onComplete @ ext-all-debug.js:25177
abort @ ext-all-debug.js:24895
onTimeout @ ext-all-debug.js:24398
(anonymous function) @ ext-all-debug.js:6680
(anonymous function) @ ext-all-debug.js:6870
12VM300:35 WebSocket connection to 'ws://gps.clydenorth.com/debug.htmlapi/socket' failed: Error during WebSocket handshake: Unexpected response code: 404
WrappedWebSocket @ VM300:35
WrappedWebSocket @ VM306:35
asyncUpdate @ Root.js:112
socket.onclose @ Root.js:115
It looks like your report is empty. Check network request and response as well.
Hi Anton
Looking at the network response / requests, look like it times out after exactly 30 seconds. I've tried on a Raspberry Pi and a low powered NAS. I presume the major reason is the low powered hardware. If I reduce my report parameters (ie: a finding a route that was a couple of hours, instead of a day) I have no issues.
Pete
Looks like it is performance problem. Each browser has a limitation on networks requests time, so if request takes too long, it times out.
OK, so the tracking is working fine, but every now and then when I configure a report I get error messages in the wrapper log file and no output is displayed in the GUI. Anyone getting anything similar?
Messages are: