Something weird that I don’t know what happened.
In my web app log, below message is showed continously.
2012-05-04 11:48:35,109 INFO o.v.d.s.AtmosphereDontPushHandler - You have set an infinite timeout for your comet connection this is not recommended
2012-05-04 11:48:35,125 INFO o.v.d.s.AtmosphereDontPushHandler - Could not handle msg, cm not found. (non-functional) close request??
Below are messages on Vaadin debug window:
Drag title=move, shift-drag=resize, doubleclick title=min/max.Use debug=quiet to log only to browser console.
Starting Vaadin client side engine. Widgetset: com.widgetset.Ikpi_webappWidgetset
Widget set is built on version: 6.7.8
Starting application iKPI-3202683
Vaadin application servlet version: 6.7.8
Application version: NONVERSIONED
inserting load indicator
http://rna02.apr.dhcpcom:8080/iKPI/UIDL/4bb7b1cc-df46-4c45-8fdb-7e2054d1d7d0/null
Creating atmosphere client...
...starting...
No real start here
WS Disconnected
Custom ozonelayerConnectionGuardTimeout timeout value30000
WS Connected
->SERVER: ; p: repaintAll=1&sh=1050&sw=1400&cw=1398&ch=935&vw=1398&vh=935&fr=&tzo=-480&rtzo=-480&dstd=0&dston=false&curdate=1336103352464&wsver=6.7.8; forceSync: false
DEBUG: onHeartbeat
DEBUG: onError
AtmosphereClientException: Unexpected disconnection
WS Connected
->SERVER: ; p: repaintAll=1&sh=1050&sw=1400&cw=1398&ch=935&vw=1398&vh=935&fr=&tzo=-480&rtzo=-480&dstd=0&dston=false&curdate=1336103373465&wsver=6.7.8; forceSync: false
Trying to start a new request while another is active
DEBUG: onHeartbeat
DEBUG: onError
AtmosphereClientException: Unexpected disconnection
WS Connected
->SERVER: ; p: repaintAll=1&sh=1050&sw=1400&cw=1398&ch=935&vw=1398&vh=935&fr=&tzo=-480&rtzo=-480&dstd=0&dston=false&curdate=1336103394484&wsver=6.7.8; forceSync: false
Trying to start a new request while another is active
DEBUG: onbeforediconnected
WS Disconnected
I am using Vaadin v6.7.8 + DontPush OzoneLayer v0.4.8
Does anyone have same issue?
Thank you.
Please try with the latest version. It has several other improvements as well. If it still reproduces, please let me know also the browsers you are using so I can try to reproduce the issue.
I tried dontpush-addon-ozonelayer-1.0.3 with Tomcat v7.0.28, still got same issue.
Below is initial log:
2012-12-04 21:25:38,616 INFO o.atmosphere.cpr.AtmosphereFramework - Installed AtmosphereHandler AtmosphereGwtAtmosphereHandler mapped to context-path: /UIDL
2012-12-04 21:25:38,616 INFO o.atmosphere.cpr.AtmosphereFramework - Auto detecting WebSocketHandler in /WEB-INF/classes/
2012-12-04 21:25:38,710 INFO o.atmosphere.cpr.AtmosphereFramework - Atmosphere is using async support: org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket running under container: Apache Tomcat/7.0.28
2012-12-04 21:25:38,710 INFO o.atmosphere.cpr.AtmosphereFramework - Installed WebSocketProtocol org.atmosphere.websocket.protocol.SimpleHttpProtocol
2012-12-04 21:25:38,710 INFO o.atmosphere.cpr.AtmosphereFramework - Installed Default AtmosphereInterceptor [Android Interceptor Support, SSE Interceptor Support, JSONP Interceptor Support]
. Set org.atmosphere.cpr.AtmosphereInterceptor.disableDefaults in your xml to disable them.
2012-12-04 21:25:38,710 WARN o.atmosphere.cpr.AtmosphereFramework - No BroadcasterCache configured. Broadcasted message between client reconnection will be LOST. It is recommended to configure the HeaderBroadcasterCache.
2012-12-04 21:25:38,710 WARN o.atmosphere.cpr.AtmosphereFramework - Neither TrackMessageSizeInterceptor or TrackMessageSizeFilter are installed. atmosphere.js may receive glued and incomplete message.
2012-12-04 21:25:38,710 INFO o.atmosphere.cpr.AtmosphereFramework - HttpSession supported: false
2012-12-04 21:25:38,710 INFO o.atmosphere.cpr.AtmosphereFramework - Using BroadcasterFactory: org.atmosphere.cpr.DefaultBroadcasterFactory
2012-12-04 21:25:38,710 INFO o.atmosphere.cpr.AtmosphereFramework - Using WebSocketProcessor: org.atmosphere.websocket.DefaultWebSocketProcessor
2012-12-04 21:25:38,710 INFO o.atmosphere.cpr.AtmosphereFramework - Using Broadcaster: org.atmosphere.cpr.DefaultBroadcaster
2012-12-04 21:25:38,710 INFO o.atmosphere.cpr.AtmosphereFramework - Atmosphere Framework 1.0.2 started.
...
With “Chrome 23.0.1271.95 m”, I got:
2012-12-04 21:28:39,106 INFO o.v.d.s.AtmosphereDontPushHandler - You have set an infinite timeout for your comet connection this is not recommended
2012-12-04 21:28:39,121 INFO o.v.d.s.AtmosphereDontPushHandler - Could not handle msg, cm not found. (non-functional) close request??
With IE8, I got:
2012-12-04 21:39:44,038 WARN o.atmosphere.cpr.AtmosphereFramework - Failed using comet support: org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket, error: Tomcat failed to detect this is a Comet application because context.xml is missing or the Http11NioProtocol Connector is not enabled.
If that's not the case, you can also remove META-INF/context.xml and WEB-INF/lib/atmosphere-compat-tomcat.jar Is the Nio or Apr Connector enabled?
2012-12-04 21:39:44,038 WARN o.atmosphere.cpr.AtmosphereFramework - Using org.atmosphere.container.Tomcat7BIOSupportWithWebSocket
2012-12-04 21:39:44,038 INFO o.v.d.s.AtmosphereDontPushHandler - Failed to find resource for [0]
2012-12-04 21:39:45,037 INFO o.v.d.s.AtmosphereDontPushHandler - Failed to find resource for [0]
2012-12-04 21:39:46,069 INFO o.v.d.s.AtmosphereDontPushHandler - Failed to find resource for [0]
Attached is my used jars and error on web page.
Could you kindly help on this?
Really appreciated!
