I know its maybe not right here but i’m currently developing vaadin applications that i deploy on jboss, sop maybe someone can help me out.
Auto deploy of war files is activated. So when i upload a newer version of the war file i’ll just upload it to the deployment directory and overwrite the existing version.
Then i get this message:
12:36:10,123 INFO [org.jboss.as.server.deployment]
(MSC service thread 1-1) JBAS015877: Stopped deployment webclient-1.0.0-SNAPSHOT.war (runtime-name: webclient-1.0.0-SNAPSHOT.war) in 8ms
12:36:10,125 INFO [org.jboss.as.server.deployment]
(MSC service thread 1-4) JBAS015876: Starting deployment of "webclient-1.0.0-SNAPSHOT.war" (runtime-name: "webclient-1.0.0-SNAPSHOT.war")
12:36:12,459 WARN [org.jboss.as.dependency.unsupported]
(MSC service thread 1-3) JBAS018568: Deployment "deployment.webclient-1.0.0-SNAPSHOT.war" is using an unsupported module ("org.infinispan:main") which may be changed or removed in future versions without notice.
12:36:12,874 INFO [org.jboss.web]
(ServerService Thread Pool -- 86) JBAS018210: Register web context: /webclient
12:36:13,055 INFO [org.jboss.as.server]
(DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "webclient-1.0.0-SNAPSHOT.war" with deployment "webclient-1.0.0-SNAPSHOT.war"
12:36:17,458 WARNING [com.vaadin.server.DefaultDeploymentConfiguration]
(http-/0.0.0.0:8080-4)
=================================================================
Vaadin is running in DEBUG MODE.
Add productionMode=true to web.xml to disable debug features.
To show debug window, add ?debug to your application URL.
=================================================================
12:36:17,594 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Installed AtmosphereHandler com.vaadin.server.communication.PushHandler mapped to context-path: /*
12:36:17,806 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Auto detecting WebSocketHandler in /WEB-INF/classes/
12:36:17,945 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Installed WebSocketProtocol org.atmosphere.websocket.protocol.SimpleHttpProtocol
12:36:17,958 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Atmosphere is using async support: org.atmosphere.container.Servlet30CometSupport running under container: JBoss Web/7.2.0.Final-redhat-1 using javax.servlet/3.0
12:36:17,986 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Installed Default AtmosphereInterceptor [Android Interceptor Support, SSE Interceptor Support, JSONP Interceptor Support, Long-Polling Padding Interceptor Support, Atmosphere JavaScript Protocol, Browser disconnection detection]
. Set org.atmosphere.cpr.AtmosphereInterceptor.disableDefaults in your xml to disable them.
12:36:17,987 WARNING [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) No BroadcasterCache configured. Broadcasted message between client reconnection will be LOST. It is recommended to configure the org.atmosphere.cache.UUIDBroadcasterCache
12:36:17,988 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Shared ExecutorService supported: true
12:36:17,988 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) HttpSession supported: true
12:36:17,989 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Using BroadcasterFactory: org.atmosphere.cpr.DefaultBroadcasterFactory
12:36:17,990 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Using WebSocketProcessor: org.atmosphere.websocket.DefaultWebSocketProcessor
12:36:17,991 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Using Broadcaster: org.atmosphere.cpr.DefaultBroadcaster
12:36:17,992 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Atmosphere Framework 1.0.18.vaadin1 started.
12:36:17,996 INFO [org.atmosphere.cpr.AtmosphereFramework]
(http-/0.0.0.0:8080-4) Installed AtmosphereInterceptor Track Message Size Interceptor using |.So normally you would think this replaced the old war file with the newer version of the web app.
The problem now is, that when i look at the output in the log file i have the old AND the new version running after this. So it looks like the old war is still somewhere in the cache.
The old jboss versions had a configuration param to clear the cache after an undeploy so it was removed before the new version was deployed. Does anyone of you know how to configure this with jboss as 7?