While testing the upcoming release of Wicket 6-beta2, I tried testing
the websockets example, but it fails with the following serverside
error (using mvn jetty:run)
ERROR - AsynchronousProcessor - failed to timeout resource null
java.lang.NullPointerException
at
org.atmosphere.cpr.AsynchronousProcessor.timedout(AsynchronousProcessor.java:354)
at
org.atmosphere.cpr.AsynchronousProcessor$AsynchronousProcessorHook.timedOut(AsynchronousProcessor.java:578)
at
org.atmosphere.websocket.WebSocketProcessor.close(WebSocketProcessor.java:216)
at
org.atmosphere.container.JettyWebSocketHandler.onClose(JettyWebSocketHandler.java:132)
at
org.eclipse.jetty.websocket.WebSocketConnectionD00.onClose(WebSocketConnectionD00.java:227)
at
org.eclipse.jetty.websocket.WebSocketServletConnectionD00.onClose(WebSocketServletConnectionD00.java:99)
at
org.eclipse.jetty.server.AbstractConnector.connectionClosed(AbstractConnector.java:1145)
at
org.eclipse.jetty.server.nio.SelectChannelConnector.endPointClosed(SelectChannelConnector.java:274)
at
org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager.endPointClosed(SelectChannelConnector.java:301)
at
org.eclipse.jetty.io.nio.SelectorManager$SelectSet.destroyEndPoint(SelectorManager.java:848)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.doUpdateKey(SelectChannelEndPoint.java:585)
at
org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:463)
at
org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:285)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538)
at java.lang.Thread.run(Thread.java:680)
ERROR - Jetty8WebSocket - WebSocket Redirect not supported
Is this expected (@papegaaij) behavior in that Safari is not yet a
supported platform for atmosphere?
As wicket-atmosphere is experimental, I don't want this to hold back
the release, so expect a vote coming up soon...
Martijn
