What does this means? The WebSocket handshake succeeded
When using WebSocket and Jersey, you may see the following warning in the log:
The WebSocket handshake succeeded but the dispatched URI failed Method Not Allowed:405.
The WebSocket connection is still open and client can continue sending messages.That means the WebSocket has successfully connected to Atmosphere and the original request dispatched to the Jersey Resource, but the Jersey resource doesn't defined a @Path that match the WebSocket's URI.
The WebSocket can still be used and it is fully functional.
- Understanding Atmosphere
- Understanding Atmosphere's Annotation
- Understanding AtmosphereResource
- Understanding AtmosphereHandler
- Understanding WebSocketHandler
- Understanding Broadcaster
- Understanding BroadcasterCache
- Understanding Meteor
- Understanding BroadcastFilter
- Understanding Atmosphere's Events Listeners
- Understanding AtmosphereInterceptor
- Configuring Atmosphere for Performance
- Understanding JavaScript functions
- Understanding AtmosphereResourceSession
- Using Atmosphere Jersey API
- Using Meteor API
- Using AtmosphereHandler API
- Using Socket.IO
- Using GWT
- Writing HTML5 Server-Sent Events
- Streaming WebSocket messages
- Configuring Atmosphere's Classes Creation and Injection
- Using AtmosphereInterceptor to customize Atmosphere Framework
- Writing WebSocket sub protocol
- Configuring Atmosphere for the Cloud
- Injecting Atmosphere's Components in Jersey
- Sharing connection between Browser's windows and tabs
- Understanding AtmosphereResourceSession
- Server Side: javadoc API
- Server Side: atmosphere.xml and web.xml configuration
- Client Side: atmosphere.js API
- Getting started with Atmosphere
- Spring, WebSocket and Atmosphere
- Starting with atmosphere framework, GWT and Maven under Eclipse