-
-
Notifications
You must be signed in to change notification settings - Fork 751
Apache and Tomcat default ports with websocket transport
Apache and Tomcat default ports for non-SSL environment web sockets are getting closed out, this behavior is observed in both apache fronting in load balancing or tomcat running as standalone.
will notice an error at client side ?X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.1.2-jquery&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&X-Cache-Date=0&X-atmo-protocol=true&selector=' failed: Failed to inflate a frame jquery.atmosphere.js?bust=V5:928
Cause was end user machine of the web socket application having Trend Micro agent running.
I have found that trend micro agent also monitor and use default ports like 80 and 8080.. internally which is closing out
you have three options to overcome this problem :
-
turn off trend micro agent
-
there are ways to change trend micro default ports
-
change the port on apache /tomcat from 80/8080 to 800/8081 like that it works fine.
- 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