Tomcat WebSockets issues and workaround
The Tomcat WebSocket implementation is new and contains some issues. If you are using Atmosphere 1.0.0, make sure you read the following:
Connection gets closed after 20000 Workaround: Increase the value of connectionTimeout of the connector in server.xml Fixed in Tomcat 7.0.30 and up.
Sporadic NPE Workaround: No workaround, Atmosphere will handle the disconnection and recover from it)
ClassCastException with Spring Workaround: Upgrade Atmosphere 2.0.0
Firefox 10, Safari 5.x doesn't work with Tomcat 7.0.27 and up
- Understanding Atmosphere
- Understanding @ManagedService
- Using javax.inject.Inject and javax.inject.PostConstruct annotation
- 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
- Improving Performance by using the PoolableBroadcasterFactory
- Using Atmosphere Jersey API
- Using Meteor API
- Using AtmosphereHandler API
- Using Socket.IO
- Using GWT
- Writing HTML5 Server-Sent Events
- Using STOMP protocol
- 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
- Manage installed services
- 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