atmosphere, jboss and primefaces push. Get them to work - maven

I'm trying to get it to work primefaces, jboss eap 6.2 and primefaces push, that is based on atmosphere. I'm fighting with it for quite some time and I'm getting nowhere, so here I am.
So here some info on my configuration. Inside my standalone.xml i've set to true the usenative flag, and this is my web.xml:
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0">
sra-EE
<servlet>
<servlet-name>Push Servlet</servlet-name>
<servlet-class>org.primefaces.push.PushServlet</servlet-class>
<init-param>
<param-name>org.atmosphere.cpr.broadcasterCacheClass</param-name>
<param-value>org.atmosphere.cache.UUIDBroadcasterCache</param-value>
</init-param>
<init-param>
<param-name>org.atmosphere.useNative</param-name>
<param-value>true</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
<async-supported>true</async-supported>
</servlet>
<servlet-mapping>
<servlet-name>Push Servlet</servlet-name>
<url-pattern>/primepush/*</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
<context-param>
<param-name>facelets.FACELETS_SKIP_COMMENTS</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<param-name>javax.faces.PROJECT_STAGE</param-name>
<param-value>Development</param-value>
</context-param>
<context-param>
<param-name>org.primefaces.extensions.DELIVER_UNCOMPRESSED_RESOURCES</param-name>
<param-value>false</param-value>
</context-param>
</web-app>
and inside the pom.xml I have:
<dependency>
<groupId>org.atmosphere</groupId>
<artifactId>atmosphere-runtime</artifactId>
<version>2.1.1</version>
</dependency>
<dependency>
<groupId>org.primefaces</groupId>
<artifactId>primefaces</artifactId>
<version>4.0</version>
</dependency>
on deploy I get this error:
12:05:48,544 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Atmosphere is using org.atmosphere.cpr.DefaultAnnotationProcessor for processing annotation
12:05:48,545 INFO [org.atmosphere.cpr.DefaultAnnotationProcessor] (ServerService Thread Pool -- 11) AnnotationProcessor class org.atmosphere.cpr.DefaultAnnotationProcessor$ServletContainerInitializerAnnotationProcessor being used
12:05:48,546 WARN [org.atmosphere.cpr.DefaultAnnotationProcessor] (ServerService Thread Pool -- 11) Unable to detect annotations. Application may fail to deploy.
12:05:48,547 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Auto detecting atmosphere handlers /WEB-INF/classes/
12:05:48,554 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Auto detecting WebSocketHandler in /WEB-INF/classes/
12:05:48,558 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Installed WebSocketProtocol org.atmosphere.websocket.protocol.SimpleHttpProtocol
12:05:48,560 WARN [org.atmosphere.cpr.DefaultAsyncSupportResolver] (ServerService Thread Pool -- 11) Found multiple containers, please specify which one to use: org.atmosphere.container.JBossWebCometSupport, org.atmosphere.container.TomcatCometSupport, until you do, Atmosphere will use:class org.atmosphere.container.JBossWebCometSupport
12:05:48,562 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Installing Default AtmosphereInterceptor
12:05:48,563 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.CorsInterceptor : CORS Interceptor Support
12:05:48,563 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.CacheHeadersInterceptor : Default Response's Headers Interceptor
12:05:48,565 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.PaddingAtmosphereInterceptor : Browser Padding Interceptor Support
12:05:48,566 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.AndroidAtmosphereInterceptor : Android Interceptor Support
12:05:48,566 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.HeartbeatInterceptor : Heartbeat Interceptor Support
12:05:48,567 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.SSEAtmosphereInterceptor : SSE Interceptor Support
12:05:48,567 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.JSONPAtmosphereInterceptor : JSONP Interceptor Support
12:05:48,568 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.JavaScriptProtocol : Atmosphere JavaScript Protocol
12:05:48,568 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.WebSocketMessageSuspendInterceptor : org.atmosphere.interceptor.WebSocketMessageSuspendInterceptor
12:05:48,568 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.OnDisconnectInterceptor : Browser disconnection detection
12:05:48,569 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) org.atmosphere.interceptor.IdleResourceInterceptor : org.atmosphere.interceptor.IdleResourceInterceptor
12:05:48,569 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Set org.atmosphere.cpr.AtmosphereInterceptor.disableDefaults to disable them.
12:05:48,573 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Using EndpointMapper class org.atmosphere.util.DefaultEndpointMapper
12:05:48,573 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Using BroadcasterCache: org.atmosphere.cache.UUIDBroadcasterCache
12:05:48,574 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Default Broadcaster Class: org.atmosphere.cpr.DefaultBroadcaster
12:05:48,574 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Broadcaster Polling Wait Time 100
12:05:48,574 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Shared ExecutorService supported: true
12:05:48,603 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Messaging Thread Pool Size: Unlimited
12:05:48,604 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Async I/O Thread Pool Size: 200
12:05:48,604 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Using BroadcasterFactory: org.atmosphere.cpr.DefaultBroadcasterFactory
12:05:48,605 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Using WebSocketProcessor: org.atmosphere.websocket.DefaultWebSocketProcessor
12:05:48,605 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) HttpSession supported: false
12:05:48,605 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Atmosphere is using DefaultAtmosphereObjectFactory for dependency injection and object creation
12:05:48,605 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Atmosphere is using async support: org.atmosphere.container.JBossWebCometSupport running under container: JBoss Web/7.2.2.Final-redhat-1
12:05:48,606 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Atmosphere Framework 2.1.1 started.
12:05:48,606 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11)
For Atmosphere Framework Commercial Support, visit
http://www.async-io.org/ or send an email to support#async-io.org
12:05:48,607 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Installed AtmosphereInterceptor Atmosphere LifeCycle with priority AFTER_DEFAULT
12:05:48,608 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Installed AtmosphereInterceptor Track Message Size Interceptor using | with priority AFTER_DEFAULT
12:05:48,609 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 11) Installed AtmosphereInterceptor UUID Tracking Interceptor with priority AFTER_DEFAULT
12:05:48,680 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018565: Replaced deployment "SRA-ear-1.0.ear" with deployment "SRA-ear-1.0.ear"
12:05:48,813 INFO [org.atmosphere.cpr.AtmosphereFramework] (Thread-101) Latest version of Atmosphere's JavaScript Client 2.1.5
12:06:56,257 ERROR [org.atmosphere.container.JBossWebCometSupport] (http-/0:0:0:0:0:0:0:0:8080-1) HttpEvent is null, JBoss APR Not Properly installed
12:06:56,257 WARN [org.atmosphere.cpr.AtmosphereFramework] (http-/0:0:0:0:0:0:0:0:8080-1) Failed using comet support: org.atmosphere.container.JBossWebCometSupport, error: JBoss failed to detect this is a Comet application because the APR Connector is not enabled.
Make sure atmosphere-compat-jboss.jar is not under your WEB-INF/lib and You must use the atmosphere-native-runtime dependency in order to use native Comet Support
there is no context.xml under WEB-INF Is the NIO or APR Connector enabled?
12:06:56,257 ERROR [org.atmosphere.cpr.AtmosphereFramework] (http-/0:0:0:0:0:0:0:0:8080-1) If you have more than one Connector enabled, make sure they both use the same protocol, e.g NIO/APR or HTTP for all. If not, org.atmosphere.container.BlockingIOCometSupport will be used and cannot be changed.: java.lang.IllegalStateException: JBoss failed to detect this is a Comet application because the APR Connector is not enabled.
Make sure atmosphere-compat-jboss.jar is not under your WEB-INF/lib and You must use the atmosphere-native-runtime dependency in order to use native Comet Support
there is no context.xml under WEB-INF
at org.atmosphere.container.JBossWebCometSupport.<clinit>(JBossWebCometSupport.java:49) [atmosphere-runtime-2.1.1.jar:2.1.1]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_05]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_05]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_05]
at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_05]
at org.atmosphere.cpr.DefaultAsyncSupportResolver.newCometSupport(DefaultAsyncSupportResolver.java:225) [atmosphere-runtime-2.1.1.jar:2.1.1]
at org.atmosphere.cpr.DefaultAsyncSupportResolver.resolveMultipleNativeSupportConflict(DefaultAsyncSupportResolver.java:316) [atmosphere-runtime-2.1.1.jar:2.1.1]
at org.atmosphere.cpr.DefaultAsyncSupportResolver.resolveNativeCometSupport(DefaultAsyncSupportResolver.java:300) [atmosphere-runtime-2.1.1.jar:2.1.1]
at org.atmosphere.cpr.DefaultAsyncSupportResolver.resolve(DefaultAsyncSupportResolver.java:279) [atmosphere-runtime-2.1.1.jar:2.1.1]
at org.atmosphere.cpr.AtmosphereFramework.autoDetectContainer(AtmosphereFramework.java:1579) [atmosphere-runtime-2.1.1.jar:2.1.1]
at org.atmosphere.cpr.AtmosphereFramework.init(AtmosphereFramework.java:717) [atmosphere-runtime-2.1.1.jar:2.1.1]
at org.atmosphere.cpr.AtmosphereFramework.init(AtmosphereFramework.java:614) [atmosphere-runtime-2.1.1.jar:2.1.1]
at org.atmosphere.cpr.AtmosphereServlet.configureFramework(AtmosphereServlet.java:91) [atmosphere-runtime-2.1.1.jar:2.1.1]
at org.atmosphere.cpr.AtmosphereServlet.init(AtmosphereServlet.java:80) [atmosphere-runtime-2.1.1.jar:2.1.1]
at org.primefaces.push.PushServlet.init(PushServlet.java:43) [primefaces-4.0.jar:4.0]
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1100) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3591) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3798) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_05]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_05]
at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_05]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
12:06:56,260 WARN [org.atmosphere.cpr.AtmosphereFramework] (http-/0:0:0:0:0:0:0:0:8080-1) Using org.atmosphere.container.BlockingIOCometSupport
I understand that this is not the right way of doing it but... it works, somehow. The problem is if more than one user is using my application atmosphere doesn't seems to understand to who send what, and mess things up.
So I've changed my pom to the following:
<dependency>
<groupId>org.atmosphere</groupId>
<artifactId>atmosphere-runtime-native</artifactId>
<version>2.1.1</version>
</dependency>
<dependency>
<groupId>org.atmosphere.jboss.as</groupId>
<artifactId>jboss-as-websockets</artifactId>
<version>0.5</version>
</dependency
no error on deploy but it doesn't not work. It sends messages but it makes a mess, even with one user. Deploy info:
12:25:34,391 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Atmosphere is using org.atmosphere.cpr.DefaultAnnotationProcessor for processing annotation
12:25:34,392 INFO [org.atmosphere.cpr.DefaultAnnotationProcessor] (ServerService Thread Pool -- 21) AnnotationProcessor class org.atmosphere.cpr.DefaultAnnotationProcessor$BytecodeBasedAnnotationProcessor being used
12:25:34,870 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Auto detecting atmosphere handlers /WEB-INF/classes/
12:25:34,879 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Auto detecting WebSocketHandler in /WEB-INF/classes/
12:25:34,883 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Installed WebSocketProtocol org.atmosphere.websocket.protocol.SimpleHttpProtocol
12:25:34,895 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Installing Default AtmosphereInterceptor
12:25:34,895 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.CorsInterceptor : CORS Interceptor Support
12:25:34,895 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.CacheHeadersInterceptor : Default Response's Headers Interceptor
12:25:34,896 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.PaddingAtmosphereInterceptor : Browser Padding Interceptor Support
12:25:34,897 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.AndroidAtmosphereInterceptor : Android Interceptor Support
12:25:34,897 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.HeartbeatInterceptor : Heartbeat Interceptor Support
12:25:34,898 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.SSEAtmosphereInterceptor : SSE Interceptor Support
12:25:34,898 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.JSONPAtmosphereInterceptor : JSONP Interceptor Support
12:25:34,899 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.JavaScriptProtocol : Atmosphere JavaScript Protocol
12:25:34,899 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.WebSocketMessageSuspendInterceptor : org.atmosphere.interceptor.WebSocketMessageSuspendInterceptor
12:25:34,899 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.OnDisconnectInterceptor : Browser disconnection detection
12:25:34,900 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) org.atmosphere.interceptor.IdleResourceInterceptor : org.atmosphere.interceptor.IdleResourceInterceptor
12:25:34,900 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Set org.atmosphere.cpr.AtmosphereInterceptor.disableDefaults to disable them.
12:25:34,903 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Using EndpointMapper class org.atmosphere.util.DefaultEndpointMapper
12:25:34,904 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Using BroadcasterCache: org.atmosphere.cache.UUIDBroadcasterCache
12:25:34,904 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Default Broadcaster Class: org.atmosphere.cpr.DefaultBroadcaster
12:25:34,904 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Broadcaster Polling Wait Time 100
12:25:34,904 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Shared ExecutorService supported: true
12:25:34,933 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Messaging Thread Pool Size: Unlimited
12:25:34,933 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Async I/O Thread Pool Size: 200
12:25:34,933 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Using BroadcasterFactory: org.atmosphere.cpr.DefaultBroadcasterFactory
12:25:34,933 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Using WebSocketProcessor: org.atmosphere.websocket.DefaultWebSocketProcessor
12:25:34,933 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) HttpSession supported: false
12:25:34,933 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Atmosphere is using DefaultAtmosphereObjectFactory for dependency injection and object creation
12:25:34,933 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Atmosphere is using async support: org.atmosphere.container.JBossWebSocketSupport running under container: JBoss Web/7.2.2.Final-redhat-1
12:25:34,935 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Atmosphere Framework 2.1.1 started.
12:25:34,935 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21)
For Atmosphere Framework Commercial Support, visit
http://www.async-io.org/ or send an email to support#async-io.org
12:25:34,935 INFO [org.atmosphere.cpr.AtmosphereServlet] (ServerService Thread Pool -- 21) AtmosphereServlet with native support for Tomcat 6/7 and JBossWeb Installed.
12:25:34,936 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Installed AtmosphereInterceptor Atmosphere LifeCycle with priority AFTER_DEFAULT
12:25:34,937 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Installed AtmosphereInterceptor Track Message Size Interceptor using | with priority AFTER_DEFAULT
12:25:34,938 INFO [org.atmosphere.cpr.AtmosphereFramework] (ServerService Thread Pool -- 21) Installed AtmosphereInterceptor UUID Tracking Interceptor with priority AFTER_DEFAULT
12:25:35,057 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "SRA-ear-1.0.ear" with deployment "SRA-ear-1.0.ear"
12:25:35,144 INFO [org.atmosphere.cpr.AtmosphereFramework] (Thread-77) Latest version of Atmosphere's JavaScript Client 2.1.5
also, it mess with something once called and my application crashes with the following stack trace:
12:30:50,264 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (http-/0:0:0:0:0:0:0:0:8080-3) JBWEB000238: Exception sending request destroyed lifecycle event to listener instance of class com.sun.faces.config.ConfigureListener: java.lang.UnsupportedOperationException
at javax.faces.context.FacesContext.getExceptionHandler(FacesContext.java:284) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
at javax.faces.event.ExceptionQueuedEventContext.getListenersForEventClass(ExceptionQueuedEventContext.java:262) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
at com.sun.faces.application.ApplicationImpl.invokeComponentListenersFor(ApplicationImpl.java:2102) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:289) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:247) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at org.jboss.as.weld.webtier.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:293) [jboss-as-weld-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at com.sun.faces.application.WebappLifecycleListener.requestDestroyed(WebappLifecycleListener.java:123) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.config.ConfigureListener.requestDestroyed(ConfigureListener.java:348) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:175) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
and this one after a while:
12:33:20,952 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/SRA-web].[FacesServlet]] (http-/0:0:0:0:0:0:0:0:8080-2) JBWEB000236: Servlet.service() for servlet FacesServlet threw exception: java.lang.IllegalStateException: JBWEB000028: getOutputStream() has already been called for this response
at org.apache.catalina.connector.Response.getWriter(Response.java:609) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:191) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at com.sun.faces.context.ExternalContextImpl.getResponseOutputWriter(ExternalContextImpl.java:778) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.context.PartialViewContextImpl.createPartialResponseWriter(PartialViewContextImpl.java:433) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.context.PartialViewContextImpl.access$300(PartialViewContextImpl.java:72) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.context.PartialViewContextImpl$DelayedInitPartialResponseWriter.getWrapped(PartialViewContextImpl.java:577) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at javax.faces.context.PartialResponseWriter.startDocument(PartialResponseWriter.java:115) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
at org.primefaces.context.PrimePartialResponseWriter.startDocument(PrimePartialResponseWriter.java:134) [primefaces-4.0.jar:4.0]
at com.sun.faces.context.AjaxExceptionHandlerImpl.handlePartialResponseError(AjaxExceptionHandlerImpl.java:199) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.context.AjaxExceptionHandlerImpl.handle(AjaxExceptionHandlerImpl.java:124) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) [jsf-impl-2.1.19-redhat-2.jar:2.1.19-redhat-2]
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:593) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
changing the dependency from atmosphere-runtime-native to atmosphere-runtime doesn't change the situazion.
Sorry for filling this page with stack traces :D

I believe (per the docs) that PrimeFaces Push allows you to push messages to all connected clients. At least, it doesn't show in the docs how to direct push messages to specific clients. This can be done with websockets though - you need to track the connected sessions and send messages to just the session for the client that you need to send a message to. See the Websockets section in the EE7 Tutorial here: https://docs.oracle.com/javaee/7/tutorial/websocket005.htm#BABFCGBJ

Related

Class org.springframework.web.context.support.XmlWebApplicationContext not found deploying WAR in Fuse 7.1.0 on EAP

I'm building a maven application packaged as WAR, below the pom.xml and web.xml (camel-version: 2.17.0.redhat-630187, cxf-version: 3.1.12)
<dependencies>
<dependency>
<groupId>org.wildfly.camel</groupId>
<artifactId>wildfly-camel-bom</artifactId>
<version>5.2.0.fuse-710021-redhat-00001</version>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-parent</artifactId>
<version>2.17.0.redhat-630187</version>
<type>pom</type>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-core</artifactId>
<version>2.17.0.redhat-630187</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-cxf</artifactId>
<version>2.17.0.redhat-630187</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-cdi</artifactId>
<version>2.17.0.redhat-630187</version>
</dependency>
<!--
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
<version>4.3.18.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-web</artifactId>
<version>4.3.18.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
<version>4.3.18.RELEASE</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-beans</artifactId>
<version>4.3.18.RELEASE</version>
</dependency>
-->
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-servlet</artifactId>
<version>2.17.0.redhat-630187</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-http4</artifactId>
<version>2.17.0.redhat-630187</version>
</dependency>
</dependencies>
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5">
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>classpath:META-INF/spring/*.xml</param-value>
</context-param>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
<servlet>
<servlet-name>CXFServlet</servlet-name>
<servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>CXFServlet</servlet-name>
<url-pattern>/soap/*</url-pattern>
</servlet-mapping>
</web-app>
I've no problem if I deploy this application on Fuse 6.3.0 on EAP, but when I deploy the WAR on Fuse 7.1.0 on EAP I get this exception
09:08:26,639 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final-redhat-1
09:08:28,395 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1
09:08:28,613 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting
09:08:49,172 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:08:49,207 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 24) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
09:08:49,300 INFO [org.wildfly.security] (ServerService Thread Pool -- 15) ELY00001: WildFly Elytron version 1.1.7.Final-redhat-1
09:08:50,334 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
09:08:50,363 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.5.4.Final-redhat-1
09:08:50,378 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.5.4.Final-redhat-1
09:08:50,441 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 59) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
09:08:50,441 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 44) WFLYRS0016: RESTEasy version 3.0.24.Final-redhat-1
09:08:50,441 INFO [org.jboss.as.security] (ServerService Thread Pool -- 58) WFLYSEC0002: Activating Security Subsystem
09:08:50,457 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 51) WFLYNAM0001: Activating Naming Subsystem
09:08:50,457 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.2.Final-redhat-1
09:08:50,457 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 42) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
09:08:50,457 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 49) WFLYJSF0007: Activated the following JSF Implementations: [main]
09:08:50,508 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 43) WFLYCLINF0001: Activating Infinispan subsystem.
09:08:50,517 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 61) WFLYWS0002: Activating WebServices Extension
09:08:50,599 INFO [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final-redhat-1)
09:08:50,786 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 37) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
09:08:50,849 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 5.0.5.Final-redhat-1
09:08:50,880 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.4.18.Final-redhat-2 starting
09:08:50,911 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2
09:08:50,927 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
09:08:50,974 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
09:08:51,126 INFO [org.jboss.gravia.runtime] (MSC service thread 1-5) Installed: Module[gravia-system:0.0.0]
09:08:51,128 INFO [org.jboss.gravia.runtime] (MSC service thread 1-5) Runtime created: org.wildfly.extension.gravia.service.WildFlyRuntime#6614ab98
09:08:51,152 INFO [org.jboss.gravia.runtime] (MSC service thread 1-5) Installed: Module[org.apache.felix.configadmin:1.8.8]
09:08:51,154 INFO [org.jboss.gravia.runtime] (MSC service thread 1-5) Installed: Module[org.apache.felix.scr:1.6.2]
09:08:51,209 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
09:08:51,210 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
09:08:51,295 INFO [org.jboss.gravia.runtime] (MSC service thread 1-5) Started: Module[org.apache.felix.configadmin:1.8.8]
09:08:51,373 INFO [org.jboss.gravia.runtime] (MSC service thread 1-5) Started: Module[org.apache.felix.scr:1.6.2]
09:08:51,375 WARN [org.jboss.gravia.runtime] (MSC service thread 1-5) Invalid configuration directory: C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\standalone\configuration\gravia\configs
09:08:51,375 INFO [org.wildfly.extension.gravia] (MSC service thread 1-5) Activating Gravia Subsystem
09:08:51,375 INFO [org.wildfly.extension.camel] (MSC service thread 1-8) Activating Camel Subsystem
09:08:51,375 INFO [org.wildfly.extension.camel] (MSC service thread 1-1) Bound camel naming object: java:jboss/camel/CamelContextFactory
09:08:51,375 INFO [org.jboss.gravia.runtime] (MSC service thread 1-5) Installed: Module[gravia-container-wildfly-extension:1.3.1]
09:08:51,375 INFO [org.jboss.gravia.runtime] (MSC service thread 1-5) Started: Module[gravia-container-wildfly-extension:1.3.1]
09:08:51,390 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0014: Creating file handler for path 'C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
09:08:51,406 INFO [org.wildfly.extension.camel] (MSC service thread 1-7) Bound camel naming object: java:jboss/camel/CamelContextRegistry
09:08:51,422 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
09:08:51,422 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
09:08:51,826 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8083
09:08:51,904 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
09:08:52,029 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
09:08:52,885 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
09:08:52,900 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-7) WFLYDM0111: Keystore C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
09:08:52,915 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\standalone\deployments
09:08:52,915 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "hawtio-wildfly-2.0.0.fuse-710018-redhat-00002.war" (runtime-name: "hawtio-wildfly-2.0.0.fuse-710018-redhat-00002.war")
09:08:53,388 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
09:08:54,112 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.1.9.Final-redhat-1 (Apache CXF 3.1.12.redhat-1)
09:09:59,940 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.8.Final-redhat-1
09:10:00,404 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container
09:10:01,954 INFO [io.hawt.HawtioContextListener] (ServerService Thread Pool -- 72) Initialising hawtio services
09:10:01,967 INFO [io.hawt.system.ConfigManager] (ServerService Thread Pool -- 72) Configuration will be discovered via JNDI
09:10:01,967 INFO [io.hawt.jmx.JmxTreeWatcher] (ServerService Thread Pool -- 72) Welcome to hawtio 2.0.0.fuse-710018-redhat-00002 : http://hawt.io/ : Don't cha wish your console was hawt like me? ;-)
09:10:02,618 INFO [io.hawt.system.ProxyWhitelist] (ServerService Thread Pool -- 72) Initial proxy whitelist: [localhost, 127.0.0.1, 10.13.100.70, BLU17425.replynet.prv, b2ctest.ecredit.it]
09:10:02,759 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/hawtio' for server 'default-server'
09:10:02,759 INFO [org.wildfly.extension.camel] (ServerService Thread Pool -- 72) Add Camel endpoint: http://127.0.0.1:8083/hawtio
09:10:02,790 INFO [org.jboss.as.server] (ServerService Thread Pool -- 38) WFLYSRV0010: Deployed "hawtio-wildfly-2.0.0.fuse-710018-redhat-00002.war" (runtime-name : "hawtio-wildfly-2.0.0.fuse-710018-redhat-00002.war")
09:10:02,946 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
09:10:02,946 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
09:10:02,946 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
09:10:02,946 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) started in 97232ms - Started 481 of 709 services (353 services are lazy, passive or on-demand)
09:13:13,052 INFO [org.jboss.as.repository] (External Management Request Threads -- 6) WFLYDR0001: Content added at location C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\standalone\data\content\67\985f81c234622333daf805132413a197e4664e\content
09:13:13,058 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "crif-eurisc-0.0.1-SNAPSHOT.war" (runtime-name: "crif-eurisc-0.0.1-SNAPSHOT.war")
09:13:17,918 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/JBoss/Fuse/jboss-eap-7.1.0/jboss-eap-7.1/bin/content/crif-eurisc-0.0.1-SNAPSHOT.war/WEB-INF/lib/jaxb-core-2.2.11.jar does not point to a valid jar for a Class-Path reference.
09:13:17,937 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/JBoss/Fuse/jboss-eap-7.1.0/jboss-eap-7.1/bin/content/crif-eurisc-0.0.1-SNAPSHOT.war/WEB-INF/lib/jaxb-impl-2.2.11.jar does not point to a valid jar for a Class-Path reference.
09:13:17,987 INFO [org.wildfly.extension.camel] (MSC service thread 1-4) Camel context descriptors found
09:13:18,255 WARN [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0012: Warning while parsing vfs:/C:/JBoss/Fuse/jboss-eap-7.1.0/jboss-eap-7.1/bin/content/crif-eurisc-0.0.1-SNAPSHOT.war/WEB-INF/lib/camel-cdi-2.17.0.redhat-630187.jar/META-INF/beans.xml:18 cvc-elt.1.a: Cannot find the declaration of element 'beans'.
09:13:18,585 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."crif-eurisc-0.0.1-SNAPSHOT.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."crif-eurisc-0.0.1-SNAPSHOT.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "crif-eurisc-0.0.1-SNAPSHOT.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.apache.cxf.transport.servlet.CXFServlet with ClassLoader ModuleClassLoader for Module "org.apache.cxf.impl" from local module loader #7006c658 (finder: local module finder #34033bd0 (roots: C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\modules,C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\modules\system\layers\fuse,C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\modules\system\layers\base))
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:78)
at org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:57)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:106)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:91)
at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:76)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
Caused by: java.lang.NoClassDefFoundError: Lorg/springframework/web/context/support/XmlWebApplicationContext;
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Unknown Source)
at java.lang.Class.getDeclaredFields(Unknown Source)
at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:72)
at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70)
... 10 more
Caused by: java.lang.ClassNotFoundException: org.springframework.web.context.support.XmlWebApplicationContext from [Module "org.apache.cxf.impl" from local module loader #7006c658 (finder: local module finder #34033bd0 (roots: C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\modules,C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\modules\system\layers\fuse,C:\JBoss\Fuse\jboss-eap-7.1.0\jboss-eap-7.1\modules\system\layers\base))]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
... 15 more
09:13:18,585 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 6) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "crif-eurisc-0.0.1-SNAPSHOT.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"crif-eurisc-0.0.1-SNAPSHOT.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"crif-eurisc-0.0.1-SNAPSHOT.war\"
Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.apache.cxf.transport.servlet.CXFServlet with ClassLoader ModuleClassLoader for Module \"org.apache.cxf.impl\" from local module loader #7006c658 (finder: local module finder #34033bd0 (roots: C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules,C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules\\system\\layers\\fuse,C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules\\system\\layers\\base))
Caused by: java.lang.NoClassDefFoundError: Lorg/springframework/web/context/support/XmlWebApplicationContext;
Caused by: java.lang.ClassNotFoundException: org.springframework.web.context.support.XmlWebApplicationContext from [Module \"org.apache.cxf.impl\" from local module loader #7006c658 (finder: local module finder #34033bd0 (roots: C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules,C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules\\system\\layers\\fuse,C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules\\system\\layers\\base))]"}}
09:13:18,585 ERROR [org.jboss.as.server] (External Management Request Threads -- 6) WFLYSRV0021: Deploy of deployment "crif-eurisc-0.0.1-SNAPSHOT.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"crif-eurisc-0.0.1-SNAPSHOT.war\".POST_MODULE" => "WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"crif-eurisc-0.0.1-SNAPSHOT.war\"
Caused by: java.lang.RuntimeException: WFLYSRV0177: Error getting reflective information for class org.apache.cxf.transport.servlet.CXFServlet with ClassLoader ModuleClassLoader for Module \"org.apache.cxf.impl\" from local module loader #7006c658 (finder: local module finder #34033bd0 (roots: C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules,C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules\\system\\layers\\fuse,C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules\\system\\layers\\base))
Caused by: java.lang.NoClassDefFoundError: Lorg/springframework/web/context/support/XmlWebApplicationContext;
Caused by: java.lang.ClassNotFoundException: org.springframework.web.context.support.XmlWebApplicationContext from [Module \"org.apache.cxf.impl\" from local module loader #7006c658 (finder: local module finder #34033bd0 (roots: C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules,C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules\\system\\layers\\fuse,C:\\JBoss\\Fuse\\jboss-eap-7.1.0\\jboss-eap-7.1\\modules\\system\\layers\\base))]"}}
09:13:19,985 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment crif-eurisc-0.0.1-SNAPSHOT.war (runtime-name: crif-eurisc-0.0.1-SNAPSHOT.war) in 1394ms
Have you got any idea? Uncommenting spring dependecies in pom.xml doens't solve.
You're mixing Fuse 6.3 dependencies with Fuse 7.1. You can import the Fuse 7.1 EAP BOM in dependencyManagement like this:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.redhat-fuse</groupId>
<artifactId>fuse-eap-bom</artifactId>
<version>7.1.0.fuse-710019-redhat-00002</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
Then you can refer to the Camel dependencies without needing to explicitly define the <version>. E.g like this:
<dependencies>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-cxf</artifactId>
<scope>provided</scope>
</dependency>
</dependencies>
The EAP container already has the relevant Camel / Spring / CXF dependencies (providing you ran the Fuse EAP installer), so you can set the scope of the dependencies to 'provided'.
You also don't need to use the ContextLoaderListener. Fuse EAP will automatically bootstrap Camel Spring web applications for you whenever it finds a file within the WAR deployment suffixed with camel-context.xml. There are some Camel CXF quickstart examples within the EAP installation directory at quickstarts/camel which demonstrate this.

How to connect to Port 8080 wildfly on Windows server 2012?

i want to connect to port 8080 from a wildfly.
This wilfly is on my windows server 2012.
I can connect to the ISS (80 Port).
I also made rules on the firewall for 8080, but it doesn't work?
Somebody knows how to fix it ? Or what did I forgot?
cheers Ciao
2017-12-19 16:47:47,904 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.1.Final
2017-12-19 16:47:54,842 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
2017-12-19 16:47:55,688 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: Keycloak 3.4.1.Final (WildFly Core 3.0.8.Final) starting
2017-12-19 16:47:55,695 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties:
awt.toolkit = sun.awt.windows.WToolkit
file.encoding = Cp1252
file.encoding.pkg = sun.io
file.separator = \
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.awt.printerjob = sun.awt.windows.WPrinterJob
java.class.path = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\jboss-modules.jar
java.class.version = 52.0
java.endorsed.dirs = C:\Program Files (x86)\Java\jre1.8.0_151\lib\endorsed
java.ext.dirs = C:\Program Files (x86)\Java\jre1.8.0_151\lib\ext;C:\Windows\Sun\Java\lib\ext
java.home = C:\Program Files (x86)\Java\jre1.8.0_151
java.io.tmpdir = C:\Users\ADMINI~1\AppData\Local\Temp\2\
java.library.path = C:\Program Files (x86)\Java\jre1.8.0_151\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;;.
java.net.preferIPv4Stack = true
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = 1.8.0_151-b12
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 1.8
java.util.logging.manager = org.jboss.logmanager.LogManager
java.vendor = Oracle Corporation
java.vendor.url = http://java.oracle.com/
java.vendor.url.bug = http://bugreport.sun.com/bugreport/
java.version = 1.8.0_151
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) Client VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 1.8
java.vm.vendor = Oracle Corporation
java.vm.version = 25.151-b12
javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
jboss.home.dir = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final
jboss.host.name = win-3n1he53opph
jboss.modules.dir = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\modules
jboss.modules.system.pkgs = org.jboss.byteman
jboss.node.name = win-3n1he53opph
jboss.qualified.host.name = win-3n1he53opph
jboss.server.base.dir = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone
jboss.server.config.dir = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\configuration
jboss.server.data.dir = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\data
jboss.server.deploy.dir = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\data\content
jboss.server.log.dir = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\log
jboss.server.name = win-3n1he53opph
jboss.server.persist.config = true
jboss.server.temp.dir = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\tmp
line.separator =
logging.configuration = file:C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\configuration/logging.properties
module.path = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\modules
org.jboss.boot.log.file = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\log\server.log
org.jboss.resolver.warning = true
org.xml.sax.driver = __redirected.__XMLReaderFactory
os.arch = x86
os.name = Windows Server 2016
os.version = 10.0
path.separator = ;
program.name = standalone.bat
sun.arch.data.model = 32
sun.boot.class.path = C:\Program Files (x86)\Java\jre1.8.0_151\lib\resources.jar;C:\Program Files (x86)\Java\jre1.8.0_151\lib\rt.jar;C:\Program Files (x86)\Java\jre1.8.0_151\lib\sunrsasign.jar;C:\Program Files (x86)\Java\jre1.8.0_151\lib\jsse.jar;C:\Program Files (x86)\Java\jre1.8.0_151\lib\jce.jar;C:\Program Files (x86)\Java\jre1.8.0_151\lib\charsets.jar;C:\Program Files (x86)\Java\jre1.8.0_151\lib\jfr.jar;C:\Program Files (x86)\Java\jre1.8.0_151\classes
sun.boot.library.path = C:\Program Files (x86)\Java\jre1.8.0_151\bin
sun.cpu.endian = little
sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
sun.desktop = windows
sun.io.unicode.encoding = UnicodeLittle
sun.java.command = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\jboss-modules.jar -mp C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\modules org.jboss.as.standalone -Djboss.home.dir=C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = Cp1252
sun.management.compiler = HotSpot Client Compiler
sun.os.patch.level =
sun.stderr.encoding = cp850
sun.stdout.encoding = cp850
user.country = US
user.country.format = CH
user.dir = C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\bin
user.home = C:\Users\Administrator
user.language = en
user.language.format = fr
user.name = Administrator
user.script =
user.timezone = Europe/Berlin
user.variant =
2017-12-19 16:47:55,696 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.boot.log.file=C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\log\server.log -Dlogging.configuration=file:C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\configuration/logging.properties
2017-12-19 16:48:10,596 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2017-12-19 16:48:10,643 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 5) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2017-12-19 16:48:10,659 INFO [org.wildfly.security] (ServerService Thread Pool -- 19) ELY00001: WildFly Elytron version 1.1.6.Final
2017-12-19 16:48:10,878 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
2017-12-19 16:48:10,925 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.5.4.Final
2017-12-19 16:48:11,034 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 43) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
2017-12-19 16:48:11,081 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) WFLYSEC0002: Activating Security Subsystem
2017-12-19 16:48:11,159 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) WFLYNAM0001: Activating Naming Subsystem
2017-12-19 16:48:11,175 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) WFLYCLINF0001: Activating Infinispan subsystem.
2017-12-19 16:48:11,190 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 32) WFLYRS0016: RESTEasy version 3.0.24.Final
2017-12-19 16:48:10,972 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.5.4.Final
2017-12-19 16:48:11,690 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final)
2017-12-19 16:48:11,902 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
2017-12-19 16:48:12,246 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 30) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors
2017-12-19 16:48:12,980 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.5.Final
2017-12-19 16:48:13,308 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=5.0.2.Final
2017-12-19 16:48:13,761 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
2017-12-19 16:48:13,925 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.18.Final starting
2017-12-19 16:48:13,925 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
2017-12-19 16:48:13,941 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 44) WFLYUT0014: Creating file handler for path 'C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
2017-12-19 16:48:13,972 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2017-12-19 16:48:13,988 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing.
2017-12-19 16:48:14,004 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host.
2017-12-19 16:48:15,113 INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: Keycloak cumulative patch ID is: base, one-off patches include: none
2017-12-19 16:48:15,160 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
2017-12-19 16:48:15,175 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
2017-12-19 16:48:15,175 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\Administrator\Downloads\keycloak-3.4.1.Final\keycloak-3.4.1.Final\standalone\deployments
2017-12-19 16:48:15,269 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "keycloak-server.war" (runtime-name: "keycloak-server.war")
2017-12-19 16:48:15,332 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
2017-12-19 16:48:15,519 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
2017-12-19 16:48:15,956 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
2017-12-19 16:48:16,222 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
2017-12-19 16:48:16,503 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/KeycloakDS]
2017-12-19 16:48:16,519 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2017-12-19 16:48:18,899 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.8.Final
2017-12-19 16:48:20,122 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 57) WFLYCLINF0002: Started client-mappings cache from ejb container
2017-12-19 16:48:20,169 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0002: Started sessions cache from keycloak container
2017-12-19 16:48:20,169 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 56) WFLYCLINF0002: Started realms cache from keycloak container
2017-12-19 16:48:20,185 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0002: Started authorization cache from keycloak container
2017-12-19 16:48:20,185 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 54) WFLYCLINF0002: Started offlineClientSessions cache from keycloak container
2017-12-19 16:48:20,185 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52) WFLYCLINF0002: Started offlineSessions cache from keycloak container
2017-12-19 16:48:20,185 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 50) WFLYCLINF0002: Started actionTokens cache from keycloak container
2017-12-19 16:48:20,200 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0002: Started keys cache from keycloak container
2017-12-19 16:48:20,200 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 46) WFLYCLINF0002: Started work cache from keycloak container
2017-12-19 16:48:20,200 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 49) WFLYCLINF0002: Started loginFailures cache from keycloak container
2017-12-19 16:48:20,325 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 58) WFLYCLINF0002: Started authenticationSessions cache from keycloak container
2017-12-19 16:48:20,325 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 53) WFLYCLINF0002: Started users cache from keycloak container
2017-12-19 16:48:20,325 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 47) WFLYCLINF0002: Started clientSessions cache from keycloak container
2017-12-19 16:48:23,258 INFO [org.keycloak.services] (ServerService Thread Pool -- 55) KC-SERVICES0001: Loading config from standalone.xml or domain.xml
2017-12-19 16:48:25,934 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0002: Started realmRevisions cache from keycloak container
2017-12-19 16:48:25,950 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0002: Started userRevisions cache from keycloak container
2017-12-19 16:48:25,997 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0002: Started authorizationRevisions cache from keycloak container
2017-12-19 16:48:25,997 INFO [org.keycloak.connections.infinispan.DefaultInfinispanConnectionProviderFactory] (ServerService Thread Pool -- 55) Node name: win-3n1he53opph, Site name: null
2017-12-19 16:48:30,438 INFO [org.keycloak.connections.jpa.updater.liquibase.LiquibaseJpaUpdaterProvider] (ServerService Thread Pool -- 55) Initializing database schema. Using changelog META-INF/jpa-changelog-master.xml
2017-12-19 16:48:32,696 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 55) HHH000204: Processing PersistenceUnitInfo [
name: keycloak-default
...]
2017-12-19 16:48:32,913 INFO [org.hibernate.Version] (ServerService Thread Pool -- 55) HHH000412: Hibernate Core {5.1.10.Final}
2017-12-19 16:48:32,921 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 55) HHH000206: hibernate.properties not found
2017-12-19 16:48:32,931 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 55) HHH000021: Bytecode provider name : javassist
2017-12-19 16:48:33,068 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 55) HCANN000001: Hibernate Commons Annotations {5.0.1.Final}
2017-12-19 16:48:33,522 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 55) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
2017-12-19 16:48:33,556 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 55) HHH000431: Unable to determine H2 database version, certain features may not work
2017-12-19 16:48:33,686 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 55) Envers integration enabled? : true
2017-12-19 16:48:35,004 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool --
This is the standalon print from the wilfly.
Does this help more ? I don't know how i can connect...
FULL Log : https://plnkr.co/UybtGtz1XMTeW5774mS9
fail on browser
By event log Undertow listen on 127.0.0.1:8080, which is local interface.
Try to use following to start wildfly listening on all network interfaces:
bin/standalone.sh -b=0.0.0.0
If it will not work, it will be firewall configuration problem.
Parameter above affects public ports only. To open management too use:
bin/standalone.sh -b=0.0.0.0 -bmanagement=0.0.0.0
Check following blogpost for more info: Bind WildFly to a different IP address, or all addresses on multihomed

MDB Deploys Successfully: Then Won't Even Write to System.out. Why?

I have a Java EE project that ran with WF-8 w/ HornetMQ:
--- Sever side was deployed as an .ear package.
--- Client side is a Java GUI that communicated with the server via JMS messaging.
It all worked when put away.
I’m trying to resurrect it using WF-10 w/ ArtemisMQ, and it’s killing me.
After clearing all the Exceptions dealing with Hornet -> Artemis, here’s where I am:
--- WF Console confirms gotest.ear deploys with no Exceptions. (Console out put on startup pasted below)
--- Client’s Eclipse console output confirms it has a Connection and that it sent an Object Message. (my formatted output is pasted below)
--- Standalone-full.xml shows the Queue my MDB listens to configured. AND WF browser console double confirms it. (Info on WF’s configuration also pasted below)
But my MDB will not write or log to the WF console at all. I.e. not even from its constructor method. And there is no response at all from it's onMessage () to messages sent from the Client.
I’m helpless, because I don’t get Exceptions anywhere to hint at what’s wrong.
Can anyone point me in the right direction?
Help!!
MDB CODE
(I’ve cut it to the bone until I can get it to write or log to the WF console acknowledging it is hearing messages.)
import javax.annotation.PostConstruct;
import javax.annotation.PreDestroy;
import javax.annotation.Resource;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.enterprise.context.ApplicationScoped;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.persistence.Transient;
import org.apache.log4j.Logger;
#MessageDriven(
activationConfig ={
#ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
#ActivationConfigProperty(propertyName="destination", propertyValue="jms/queue/sendToServerQueue"),
#ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue = "Auto-acknowledge"),
})
public class GoMsgBean implements MessageListener {
final Logger logger = Logger.getLogger(GoMsgBean.class.getName());
public GoMsgBean () {
System.out.println("System.out message FROM GoMsgBean Constructor");
logger.info("Logger message FROM GoMsgBean Constructor");
}
#PostConstruct
public void myInit () {
System.out.println("System.out message FROM GoMsgBean PostConstruct");
logger.info("Logger message FROM GoMsgBean PostConstruct");
}
public void onMessage(Message msg) {
System.out.println("System.out message FROM GoMsgBean onMessage()");
logger.info("Logger message FROM GoMsgBean onMessage()");
}
}
STANDALONE-FULL.XML
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0">
<server name="default">
. . .
<jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/>
<jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/>
<jms-queue name="SendToServerQueue" entries="java:jboss/exported/jms/queue/sendToServerQueue"/>
<jms-queue name="SendToClientQueue2" entries="java:jboss/exported/jms/queue/sendToClientQueue2"/>
. . .
<connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/>
<pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>
</server>
</subsystem>
WFLY localhost :9990 Console Configuration Details
Queues/Topics
Name: SendToServerQueue
JNDINames: java:jboss/exported/jms/queue/sendToServerQueue
**Durable?: true**
Selector: <blank>
Connection Factories
Name InVmConnectionFactory
JNDI java:/ConnectionFactory
Name: RemoteConnectionFactory
JNDI java:jboss/exported/jms/RemoteConnectionFactory
Security Settings
Pattern #
Role guest
Address Settings
Pattern #
Diverts No Items!
ECLIPSE CONSOLE OUTPUT (when client GUI opens)
(I’ve added an insane number of System.out.printlns to track what’s happening line by line. Each output string is prefaced by the Class.method () that’s writing the line.)
ECLIPSE CONSOLE OUTPUT when Client is opened
MsgCtrSnd.run () beg
MsgCtrSnd.run () Requesting InitialContext
CONNECTION VARIABLES
key: java.naming.provider.url value: http-remoting://localhost:8080
key: java.naming.factory.initial value: org.jboss.naming.remote.client.InitialContextFactory
key: java.naming.security.principal value: jmsUser
key: java.naming.security.credentials value: jmsUser123!
MsgCtrSnd.run () InitialContext OK: javax.naming.InitialContext#4135c3b
MsgCtrSnd.run () Look up ConnectionFactory with: "jms/RemoteConnectionFactory"
MsgCtrSnd.run () ConnectionFactory: Ok:
org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory
MsgCtrSnd.run () Instantiating Connection
MsgCtrSnd.run () JMS Connection OK:
org.apache.activemq.artemis.jms.client.ActiveMQConnection#4d5d943d
Instantiating Session
MsgCtrSnd.run () JMS Session OK:
ActiveMQSession->ClientSessionImpl
[name=212aa734-90f5-11e7-aa7a-a3fb7876c1f2, username=appUser, closed=false, factory = org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl#2a4fb17b, metaData=(jms-session=,)]#368f2016
MsgCtrSnd.run () Lookup Queue w/ JNDI name: ["jms/queue/sendToServerQueue"]
MsgCtrSnd.run () Queue secured:
ActiveMQQueue[SendToServerQueue]IS NOT NULL
MsgCtrSnd.run () Instantiating Message Producer
MsgCtrSnd.run () Message Producer [IS NOT NULL]
ActiveMQMessageProducer->org.apache.activemq.artemis.core.client.impl.ClientProducerImpl#59474f18
MsgCtrSnd.run () Starting jmsConnection
MsgCtrSnd.run () JMS Send Connection : Ok.
MsgCtrSnd.run () end
ECLIPSE CONOSOLE OUTPUT (when client GUI is used to send message to log in)
Cntrl.executeMenuAction () beg
Cntrl.executeMenuAction () Switching to: Log In
Cntrl.loginSend () beg
Cntrl.loginSend () calling DataDialog.collectData()
Cntrl.loginSend () EntityFieldsCollector ok
Cntrl.loginSend () returned from DataDialog.collectData()
Cntrl.loginSend () EntityFieldsCollector contains 2 entries.
Cntrl.loginSend () key: Member ID: 308486 value: ID
Cntrl.loginSend () key: Member PW 308487 value: PW
Cntrl.loginSend () message center connection ok
MsgCtrSnd.sendMsg () beg
MsgCtrSnd.sendMsg () Action: Log In
MsgCtrSnd.sendMsg () clientHash: aaaaaa
MsgCtrSnd.sendMsg () memberId : ID
MsgCtrSnd.sendMsg () memberPw : PW
MsgCtrSnd.sendMsg () clientUserId : null
MsgCtrSnd.sendMsg () clientUserPw : null
MsgCtrSnd.sendMsg () calling createObjectMessage ()
MsgCtrSnd.sendMsg () ObjectMessage instantiated.
MsgCtrSnd.sendMsg () Object Message object: java.util.ArrayList
MsgCtrSnd.sendMsg () message sent.
MsgCtrSnd.sendMsg () end
Cntrl.loginSend () end
Cntrl.executeMenuAction () end
WILDFLY CONSOLE OUTPUT WHEN GOTEST.EAR IS DEPLOYED ON STARTUP
Calling "C:\ProgramFilesGeo\Wildfly\wildfly-10.1.0.Final\bin\standalone.conf.bat"
Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_121\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "C:\ProgramFilesGeo\Wildfly\wildfly-10.1.0.Final"
JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman"
===============================================================================
INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting
INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.4.0.Final
INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.4.0.Final
INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem
INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem
INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem
INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=4.9.6.Final
INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 1.4.0.Final starting
INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 4.0.21.Final
INFO [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.mariadb.jdbc.Driver (version 1.5)
INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql
INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path 'C:\ProgramFilesGeo\Wildfly\wildfly-10.1.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting
INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/jdbc/gotestdb]
INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:jboss/jdbc/tappdb]
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO.
WARN [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore C:\ProgramFilesGeo\Wildfly\wildfly-10.1.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "GoTest.ear" (runtime-name: "GoTest.ear")
INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory C:\ProgramFilesGeo\Wildfly\wildfly-10.1.0.Final\standalone\deployments
INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=C:\ProgramFilesGeo\Wildfly\wildfly-10.1.0.Final\standalone\data\activemq\journal,bindingsDirectory=C:\ProgramFilesGeo\Wildfly\wildfly-10.1.0.Final\standalone\data\activemq\bindings,largeMessagesDirectory=C:\ProgramFilesGeo\Wildfly\wildfly-10.1.0.Final\standalone\data\activemq\largemessages,pagingDirectory=C:\ProgramFilesGeo\Wildfly\wildfly-10.1.0.Final\standalone\data\activemq\paging)
INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal
INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 66) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 72) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 66) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 72) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: "GoTest.jar")
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6)
INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Read persistence.xml for GoTestDataBase
INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 71) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'GoTest.ear/GoTest.jar#GoTestDataBase'
INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment GoTest.ear
INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 71) HHH000204: Processing PersistenceUnitInfo [
name: GoTestDataBase
...]
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.2.4.Final
INFO [org.hibernate.Version] (ServerService Thread Pool -- 71) HHH000412: Hibernate Core {5.0.10.Final}
INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 71) HHH000206: hibernate.properties not found
INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 71) HHH000021: Bytecode provider name : javassist
INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 71) HCANN000001: Hibernate Commons Annotations {5.0.1.Final}
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-017 [nodeID=e2b89808-fdf2-11e6-9f54-3956fe24eb2d]
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221003: trying to deploy queue jms.queue.SendToServerQueue
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221003: trying to deploy queue jms.queue.DLQ
INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 72) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue jms.queue.SendToClientQueue2
INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 65) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue
INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment GoTest.jar
INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'EnrollerBean' in deployment unit 'subdeployment "GoTest.jar" of deployment "GoTest.ear"' are as follows:
java:global/GoTest/GoTest/EnrollerBean!org.america3.gotest.server.sessionbeans.EnrollerBean
java:app/GoTest/EnrollerBean!org.america3.gotest.server.sessionbeans.EnrollerBean
java:module/EnrollerBean!org.america3.gotest.server.sessionbeans.EnrollerBean
java:global/GoTest/GoTest/EnrollerBean
java:app/GoTest/EnrollerBean
java:module/EnrollerBean
INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'ExiterBean' in deployment unit 'subdeployment "GoTest.jar" of deployment "GoTest.ear"' are as follows:
java:global/GoTest/GoTest/ExiterBean!org.america3.gotest.server.sessionbeans.ExiterBean
java:app/GoTest/ExiterBean!org.america3.gotest.server.sessionbeans.ExiterBean
java:module/ExiterBean!org.america3.gotest.server.sessionbeans.ExiterBean
java:global/GoTest/GoTest/ExiterBean
java:app/GoTest/ExiterBean
java:module/ExiterBean
INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'LoginerBean' in deployment unit 'subdeployment "GoTest.jar" of deployment "GoTest.ear"' are as follows:
java:global/GoTest/GoTest/LoginerBean!org.america3.gotest.server.sessionbeans.LoginerBean
java:app/GoTest/LoginerBean!org.america3.gotest.server.sessionbeans.LoginerBean
java:module/LoginerBean!org.america3.gotest.server.sessionbeans.LoginerBean
java:global/GoTest/GoTest/LoginerBean
java:app/GoTest/LoginerBean
java:module/LoginerBean
INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'LogouterBean' in deployment unit 'subdeployment "GoTest.jar" of deployment "GoTest.ear"' are as follows:
java:global/GoTest/GoTest/LogouterBean!org.america3.gotest.server.sessionbeans.LogouterBean
java:app/GoTest/LogouterBean!org.america3.gotest.server.sessionbeans.LogouterBean
java:module/LogouterBean!org.america3.gotest.server.sessionbeans.LogouterBean
java:global/GoTest/GoTest/LogouterBean
java:app/GoTest/LogouterBean
java:module/LogouterBean
INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'ReplierBean' in deployment unit 'subdeployment "GoTest.jar" of deployment "GoTest.ear"' are as follows:
java:global/GoTest/GoTest/ReplierBean!org.america3.gotest.server.sessionbeans.ReplierBean
java:app/GoTest/ReplierBean!org.america3.gotest.server.sessionbeans.ReplierBean
java:module/ReplierBean!org.america3.gotest.server.sessionbeans.ReplierBean
java:global/GoTest/GoTest/ReplierBean
java:app/GoTest/ReplierBean
java:module/ReplierBean
INFO [org.jboss.as.connector.deployment] (MSC service thread 1-5) WFLYJCA0007: Registered connection factory java:/JmsXA
INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-5) Resource adaptor started
INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-5) IJ020002: Deployed: file://RaActivatoractivemq-ra
INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
INFO [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 2.3.5 (Final)
INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 66) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'GoTest.ear/GoTest.jar#GoTestDataBase'
INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0042: Started message driven bean 'GoMsgBean' with 'activemq-ra.rar' resource adapter
INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 66) HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect
INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 66) Envers integration enabled? : true
INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 71) WFLYCLINF0002: Started client-mappings cache from ejb container
Member.<init>................................beg
Member.<init>................................Hello World. See! I can Log messages again.
Member.<init>................................end
INFO [org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService Thread Pool -- 66) HHH000397: Using ASTQueryTranslatorFactory
INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "GoTest.ear" (runtime-name : "GoTest.ear")
INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151000: awaiting topic/queue creation jms/queue/sendToServerQueue
INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 5392ms - Started 691 of 931 services (430 services are lazy, passive or on-demand)
WILDFLY CONSOLE OUTPUT AFTER DEPLOYEMENT THAT SEEMS TO BE THE PROBLEM.
Note: the next INFO line says the jms/queue/sendToServerQueue is NOT durable, while WF Console says its configured to be durable)
INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter#78712571 destination=jms/queue/sendToServerQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
This is in reference to J. R. Perkins below concerning whether there was a log4j.xml in the deployment. This is another excerpt from WF’s standalone-full.xml I use for logging if I can ever get my MDB to even write to System.out:
<profile>
<subsystem xmlns="urn:jboss:domain:logging:3.0">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter><named-formatter name="COLOR-PATTERN"/></formatter>
</console-handler>
<console-handler name="MY-CONSOLE" autoflush="true">
<formatter><named-formatter name="MY-PATTERN"/></formatter>
<target name="System.out"/>
</console-handler>
<console-handler name="GOTEST-HANDLER">
<level name="INFO"/>
<formatter><named-formatter name="GOTEST-PATTERN"/></formatter>
</console-handler>
. . .
<logger category="org.america3.gotest" use-parent-handlers="false">
<level name="ALL"/>
<handlers><handler name="GOTEST-HANDLER"/></handlers>
</logger>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.jboss.as.config">
<level name="DEBUG"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers><handler name="CONSOLE"/><handler name="FILE"/></handlers>
</root-logger>
<formatter name="PATTERN">
<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>
</formatter>
<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n"/>
</formatter>
<formatter name="MY-PATTERN">
<pattern-formatter pattern="MeMeMe%s%n"/>
</formatter>
<formatter name="GOTEST-PATTERN">
<pattern-formatter pattern="%s%n"/>
</formatter>
</subsystem>
. . .
</profile>
I believe the problem is logged here:
INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151000: awaiting topic/queue creation jms/queue/sendToServerQueue
In other words, the MDB is not fully activated because it can't find the destination "jms/queue/sendToServerQueue". I believe this is because you haven't defined the JNDI bindings properly (since you've only defined an "exported" entry). Try using this:
<jms-queue name="SendToServerQueue" entries="java:jboss/exported/jms/queue/sendToServerQueue java:/jms/queue/sendToServerQueue"/>
Things to do to diagnose issues like this:
Read the log carefully for helpful information.
Check the consumerCount of the queue from which the MDB is supposed to receive messages. If it's 0 then it means there's a problem with the MDB.

Unregistered Web context in Jboss

Whenever I try to run a spring app in wildfly server, it gets deployed succefully but within a instance it gets undeployed. Here is the log:
13:00:28,442 INFO [org.springframework.web.context.ContextLoader] (ServerService Thread Pool -- 29) Root WebApplicationContext: initialization completed in 1027 ms
13:00:28,445 INFO [io.undertow.servlet] (ServerService Thread Pool -- 29) Initializing Spring FrameworkServlet 'dispatcher'
13:00:28,445 INFO [org.springframework.web.servlet.DispatcherServlet] (ServerService Thread Pool -- 29) FrameworkServlet 'dispatcher': initialization started
13:00:28,447 INFO [org.springframework.web.context.support.AnnotationConfigWebApplicationContext] (ServerService Thread Pool -- 29) Refreshing WebApplicationContext for namespace 'dispatcher-servlet': startup date [Mon Jul 17 13:00:28 NPT 2017]; parent: Root WebApplicationContext
13:00:28,447 INFO [org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor] (ServerService Thread Pool -- 29) JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
13:00:28,462 INFO [org.springframework.web.servlet.DispatcherServlet] (ServerService Thread Pool -- 29) FrameworkServlet 'dispatcher': initialization completed in 17 ms
13:00:28,462 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 29) WFLYUT0021: Registered web context: /taml-nbl
13:00:28,494 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "taml-nbl.war" (runtime-name : "taml-nbl.war")
13:00:30,609 INFO [stdout] (default task-21) BfiDAOImplementation:bfiLogo method invoked.
13:00:33,533 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = taml-nbl.war_org.postgresql.Driver_9_4
13:00:33,538 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 28) WFLYUT0022: Unregistered web context: /taml-nbl
13:00:33,542 INFO [io.undertow.servlet] (ServerService Thread Pool -- 28) Destroying Spring FrameworkServlet 'dispatcher'
13:00:33,542 INFO [org.springframework.web.context.support.AnnotationConfigWebApplicationContext] (ServerService Thread Pool -- 28) Closing WebApplicationContext for namespace 'dispatcher-servlet': startup date [Mon Jul 17 13:00:28 NPT 2017]; parent: Root WebApplicationContext
13:00:33,546 INFO [io.undertow.servlet] (ServerService Thread Pool -- 28) Closing Spring root WebApplicationContext
13:00:33,546 INFO [org.springframework.web.context.support.AnnotationConfigWebApplicationContext] (ServerService Thread Pool -- 28) Closing Root WebApplicationContext: startup date [Mon Jul 17 13:00:27 NPT 2017]; root of context hierarchy
13:00:33,547 INFO [org.springframework.context.support.DefaultLifecycleProcessor] (ServerService Thread Pool -- 28) Stopping beans in phase 2147483647
13:00:33,550 INFO [org.springframework.messaging.simp.broker.SimpleBrokerMessageHandler] (ServerService Thread Pool -- 28) Stopping...
13:00:33,552 INFO [org.springframework.messaging.simp.broker.SimpleBrokerMessageHandler] (ServerService Thread Pool -- 28) BrokerAvailabilityEvent[available=false, SimpleBrokerMessageHandler [DefaultSubscriptionRegistry[cache[0 destination(s)], registry[0 sessions]]]]
13:00:33,553 INFO [org.springframework.messaging.simp.broker.SimpleBrokerMessageHandler] (ServerService Thread Pool -- 28) Stopped.
13:00:33,555 INFO [org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor] (ServerService Thread Pool -- 28) Shutting down ExecutorService 'brokerChannelExecutor'
13:00:33,564 INFO [org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler] (ServerService Thread Pool -- 28) Shutting down ExecutorService 'messageBrokerTaskScheduler'
13:00:33,565 INFO [org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor] (ServerService Thread Pool -- 28) Shutting down ExecutorService 'clientOutboundChannelExecutor'
13:00:33,565 INFO [org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor] (ServerService Thread Pool -- 28) Shutting down ExecutorService 'clientInboundChannelExecutor'
13:00:33,597 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment taml-nbl.war (runtime-name: taml-nbl.war) in 67ms
13:00:33,606 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "taml-nbl.war" (runtime-name: "taml-nbl.war")
13:00:38,634 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) WFLYDS0004: Found taml-nbl.war in deployment directory. To trigger deployment create a file called taml-nbl.war.dodeploy
Even If I manually add .dodeploy file in deployment directory, its not working.
I know am late to this party but just wanted to post as there were no answers for this.
I was facing this issue and all i did was,
Cleared everything which was in jboss-tmp folder and boom it worked.

quartz scheduler db lock obtaining issue while on a 2 node cluster

We have implemented Quartz Scheduler 2.2.1 using Spring 4.0.5 . The application starts up fine in a single node , however whenever we try to deploy it to a 2 node cluster , it just hangs while trying to connect to the DB and then the server rolls back the deployment to both of the nodes.
It is interesting to note that the first node to connect Quartz database starts up fine and the 2nd one just hangs , and due to the 2nd deployment timing out, both are rolled back.
Node which works trace snippet:
Working Instance:
16:13:47,116 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 74) Scheduler meta-data: Quartz Scheduler (v2.2.1) 'WHSE12Scheduler' with instanceId 'XTHINK1424639626086'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.springframework.scheduling.quartz.LocalDataSourceJobStore' - which supports persistence. and is clustered.
16:13:47,116 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 74) Quartz scheduler 'WHSE12Scheduler' initialized from an externally provided properties instance.
16:13:47,116 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 74) Quartz scheduler version: 2.2.1
16:13:47,116 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 74) JobFactory set to: com.innotrac.wmsbridge.utils.AutowiringSpringBeanJobFactory#18d058f6
16:13:47,116 DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] (ServerService Thread Pool -- 74) Fetching JDBC Connection from DataSource
16:13:47,116 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 74) dds.Quartz: getConnection(null, WrappedConnectionRequestInfo#1c69b554[userName=Wmsbridge]) [0/50]
16:13:47,147 DEBUG [org.springframework.scheduling.quartz.LocalDataSourceJobStore] (ServerService Thread Pool -- 74) Adding TriggerPersistenceDelegate of type: org.quartz.impl.jdbcjobstore.SimpleTriggerPersistenceDelegate
16:13:47,147 DEBUG [org.springframework.scheduling.quartz.LocalDataSourceJobStore] (ServerService Thread Pool -- 74) Adding TriggerPersistenceDelegate of type: org.quartz.impl.jdbcjobstore.CronTriggerPersistenceDelegate
16:13:47,147 DEBUG [org.springframework.scheduling.quartz.LocalDataSourceJobStore] (ServerService Thread Pool -- 74) Adding TriggerPersistenceDelegate of type: org.quartz.impl.jdbcjobstore.CalendarIntervalTriggerPersistenceDelegate
16:13:47,147 DEBUG [org.springframework.scheduling.quartz.LocalDataSourceJobStore] (ServerService Thread Pool -- 74) Adding TriggerPersistenceDelegate of type: org.quartz.impl.jdbcjobstore.DailyTimeIntervalTriggerPersistenceDelegate
16:13:47,444 DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] (ServerService Thread Pool -- 74) Returning JDBC Connection to DataSource
16:13:47,444 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 74) dds.Quartz: returnConnection(4149d6d, false) [0/50]
16:13:47,444 DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] (ServerService Thread Pool -- 74) Fetching JDBC Connection from DataSource
16:13:47,444 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 74) dds.Quartz: getConnection(null, WrappedConnectionRequestInfo#1c69b554[userName=Wmsbridge]) [0/50]
16:13:47,444 DEBUG [org.quartz.impl.jdbcjobstore.StdRowLockSemaphore] (ServerService Thread Pool -- 74) Lock 'TRIGGER_ACCESS' is desired by: ServerService Thread Pool -- 74
16:13:47,444 DEBUG [org.quartz.impl.jdbcjobstore.StdRowLockSemaphore] (ServerService Thread Pool -- 74) Lock 'TRIGGER_ACCESS' is being obtained: ServerService Thread Pool -- 74
16:13:47,475 DEBUG [org.quartz.impl.jdbcjobstore.StdRowLockSemaphore] (ServerService Thread Pool -- 74) Lock 'TRIGGER_ACCESS' given to: ServerService Thread Pool -- 74
16:13:47,553 DEBUG [org.quartz.impl.jdbcjobstore.StdRowLockSemaphore] (ServerService Thread Pool -- 74) Lock 'TRIGGER_ACCESS' returned by: ServerService Thread Pool -- 74
16:13:47,553 DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] (ServerService Thread Pool -- 74) Returning JDBC Connection to DataSource
......
18:52:18,335 INFO [org.springframework.web.servlet.DispatcherServlet] (ServerService Thread Pool -- 65) FrameworkServlet 'mvc-dispatcher': initialization completed in 1335 ms
18:52:18,335 DEBUG [org.springframework.web.servlet.DispatcherServlet] (ServerService Thread Pool -- 65) Servlet 'mvc-dispatcher' configured successfully
18:52:18,356 DEBUG [org.apache.jasper.compiler] (ServerService Thread Pool -- 65) JBWEB005025: Parent class loader is: ModuleClassLoader for Module "deployment.WmsBridgeScheduler.1.0.0.dev.war:main" from Service Module Loader
18:52:18,364 DEBUG [org.jboss.as.security] (MSC service thread 1-2) Qualified url patterns: {/=PatternInfo[pattern=/,type=3,isOverridden=false,qualifiers=[]]}
18:52:18,543 INFO [org.jboss.as.server] (ServerService Thread Pool -- 64) JBAS018559: Deployed "WmsBridgeScheduler.1.0.0.dev.war" (runtime-name : "WmsBridgeScheduler.1.0.0.dev.war")
2nd Node trace snippet just stops at:
16:13:47,163 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 92) Scheduler meta-data: Quartz Scheduler (v2.2.1) 'WHSE12Scheduler' with instanceId 'XTHINK1424639626210'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
Using job-store 'org.springframework.scheduling.quartz.LocalDataSourceJobStore' - which supports persistence. and is clustered.
16:13:47,163 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 92) Quartz scheduler 'WHSE12Scheduler' initialized from an externally provided properties instance.
16:13:47,163 INFO [org.quartz.impl.StdSchedulerFactory] (ServerService Thread Pool -- 92) Quartz scheduler version: 2.2.1
16:13:47,163 INFO [org.quartz.core.QuartzScheduler] (ServerService Thread Pool -- 92) JobFactory set to: com.innotrac.wmsbridge.utils.AutowiringSpringBeanJobFactory#3e433bf3
16:13:47,163 DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] (ServerService Thread Pool -- 92) Fetching JDBC Connection from DataSource
16:13:47,163 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 92) dds.Quartz: getConnection(null, WrappedConnectionRequestInfo#1640f765[userName=Wmsbridge]) [0/50]
16:13:47,194 DEBUG [org.springframework.scheduling.quartz.LocalDataSourceJobStore] (ServerService Thread Pool -- 92) Adding TriggerPersistenceDelegate of type: org.quartz.impl.jdbcjobstore.SimpleTriggerPersistenceDelegate
16:13:47,194 DEBUG [org.springframework.scheduling.quartz.LocalDataSourceJobStore] (ServerService Thread Pool -- 92) Adding TriggerPersistenceDelegate of type: org.quartz.impl.jdbcjobstore.CronTriggerPersistenceDelegate
16:13:47,194 DEBUG [org.springframework.scheduling.quartz.LocalDataSourceJobStore] (ServerService Thread Pool -- 92) Adding TriggerPersistenceDelegate of type: org.quartz.impl.jdbcjobstore.CalendarIntervalTriggerPersistenceDelegate
16:13:47,194 DEBUG [org.springframework.scheduling.quartz.LocalDataSourceJobStore] (ServerService Thread Pool -- 92) Adding TriggerPersistenceDelegate of type: org.quartz.impl.jdbcjobstore.DailyTimeIntervalTriggerPersistenceDelegate
16:13:47,459 DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] (ServerService Thread Pool -- 92) Returning JDBC Connection to DataSource
16:13:47,459 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 92) dds.Quartz: returnConnection(72b7b5e5, false) [0/50]
16:13:47,475 DEBUG [org.springframework.jdbc.datasource.DataSourceUtils] (ServerService Thread Pool -- 92) Fetching JDBC Connection from DataSource
16:13:47,475 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 92) dds.Quartz: getConnection(null, WrappedConnectionRequestInfo#1640f765[userName=Wmsbridge]) [0/50]
16:13:47,475 DEBUG [org.quartz.impl.jdbcjobstore.StdRowLockSemaphore] (ServerService Thread Pool -- 92) Lock 'TRIGGER_ACCESS' is desired by: ServerService Thread Pool -- 92
16:13:47,475 DEBUG [org.quartz.impl.jdbcjobstore.StdRowLockSemaphore] (ServerService Thread Pool -- 92) Lock 'TRIGGER_ACCESS' is being obtained: ServerService Thread Pool -- 92
16:13:55,477 DEBUG [org.apache.catalina.session] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Start expire sessions StandardManager at 1424639635477 sessioncount 0
Then timing out:
16:18:37,395 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) JBAS013412: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'deploy' at address '[("deployment" => "WmsBridgeScheduler.1.0.0.dev.war")]'
16:18:37,395 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 62) JBAS015870: Deploy of deployment "WmsBridgeScheduler.1.0.0.dev.war" was rolled back with the following failure message: "JBAS013487: Operation timed out awaiting service container stability"
16:18:47,411 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) JBAS013413: Timeout after [5000] seconds waiting for service container stability while finalizing an operation. Process must be restarted. Step that first updated the service container was 'deploy' at address '[("deployment" => "WmsBridgeScheduler.1.0.0.dev.war")]'
16:18:55,753 DEBUG [org.apache.catalina.session] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Start expire sessions StandardManager at 1424639935753 sessioncount 0
16:18:55,753 DEBUG [org.apache.catalina.session] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) End expire sessions StandardManager processingTime 0 expired sessions: 0
If anyone has deployed Quartz Scheduler to a 2 node cluster without any locking issues, I would appreciate any insight into this issue:
Quartz Properties:
org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.isClustered=true
org.quartz.jobStore.clusterCheckinInterval=10000
org.quartz.jobStore.tablePrefix=WHSE12_
org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
org.quartz.threadPool.class=org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount=10
org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread
= true org.quartz.scheduler.userTransactionURL=java:jboss/UserTransaction
org.quartz.scheduler.wrapJobExecutionInUserTransaction = false
org.quartz.jobStore.dontSetAutoCommitFalse=false
org.quartz.scheduler.instanceId=AUTO
org.quartz.jobStore.misfireThreshold=10000
org.quartz.jobStore.useProperties=true
org.quartz.scheduler.interruptJobsOnShutdown=true
org.quartz.scheduler.skipUpdateCheck=true
org.quartz.jobStore.txIsolationLevelSerializable=false
org.quartz.jobStore.acquireTriggersWithinLock=false
org.quartz.plugin.triggHistory.class=org.quartz.plugins.history.LoggingTriggerHistoryPlugin
org.quartz.plugin.triggHistory.triggerFiredMessage=Trigger {1}.{0}
fired job {6}.{5} at {4, date,yyyy-MM-dd HH:mm:ss}
org.quartz.plugin.triggHistory.triggerCompleteMessage=Trigger {1}.{0}
completed firing job {6}.{5} at {4,date, yyyy-MM-dd HH:mm:ss} with
resulting trigger instruction code
Quartz DataSource is JNDI Based which is for Local Transactions and use JTA =false, CCM=false on JBOSS EAP 6.3.0:
<bean id="schedulerFactoryBean" class="org.springframework.scheduling.quartz.SchedulerFactoryBean" destroy-method="destroy" lazy-init="false">
<property name="triggers">
<list>
<ref bean="someTrigger"/>
</list>
</property>
<property name="applicationContextSchedulerContextKey"><value>applicationContext</value></property>
Quartz Properties for the Scheduler
<property name="configLocation" value="classpath:properties/quartz.properties" />
<property name="dataSource" ref="quartzDataSource" />
<property name="schedulerName" value="${jdbc.schedulerName.quartz}" />
<property name="overwriteExistingJobs" value="${jdbc.overwriteExistingJobs.quartz}" />
<property name="autoStartup" value="${jdbc.autoStartup.quartz}" />
<property name="waitForJobsToCompleteOnShutdown" value="${jdbc.waitForJobsToCompleteOnShutdown.quartz}" />
<property name="jobFactory" ref="autowiringSpringBeanJobFactory" />
</bean>
On timing out, I get this:
Caused by: org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6#37427b2a [See nested exception: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6#37427b2a]'
23:14:49,996 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS013413: Timeout after [5000] seconds waiting for service container stability while finalizing an operation. Process must be restarted. Step that first updated the service container was 'add' at address '[("interface" => "management")]'
23:14:50,113 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
23:25:08,221 ERROR [org.springframework.web.context.ContextLoader] (ServerService Thread Pool -- 70) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'schedulerFactoryBean' defined in ServletContext resource [/WEB-INF/spring-infrastructure.xml]: Invocation of init method failed; nested exception is org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6#37427b2a [See nested exception: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6#37427b2a]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1553) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:539) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:475) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:304) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:228) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:300) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:195) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:684) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:760) [spring-context-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482) [spring-context-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:403) [spring-web-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:306) [spring-web-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:106) [spring-web-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.4.8.Final-redhat-4.jar:7.4.8.Final-redhat-4]
at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:59) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:94) [jboss-as-web-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_71]
at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6#37427b2a [See nested exception: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6#37427b2a]
at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:157) [quartz-2.2.1.jar:]
at org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphore.java:113) [quartz-2.2.1.jar:]
at org.quartz.impl.jdbcjobstore.JobStoreCMT.executeInLock(JobStoreCMT.java:238) [quartz-2.2.1.jar:]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJob(JobStoreSupport.java:1086) [quartz-2.2.1.jar:]
at org.quartz.core.QuartzScheduler.addJob(QuartzScheduler.java:969) [quartz-2.2.1.jar:]
at org.quartz.core.QuartzScheduler.addJob(QuartzScheduler.java:958) [quartz-2.2.1.jar:]
at org.quartz.impl.StdScheduler.addJob(StdScheduler.java:268) [quartz-2.2.1.jar:]
at org.springframework.scheduling.quartz.SchedulerAccessor.addJobToScheduler(SchedulerAccessor.java:337) [spring-context-support-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.scheduling.quartz.SchedulerAccessor.addTriggerToScheduler(SchedulerAccessor.java:360) [spring-context-support-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.scheduling.quartz.SchedulerAccessor.registerJobsAndTriggers(SchedulerAccessor.java:298) [spring-context-support-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.scheduling.quartz.SchedulerFactoryBean.afterPropertiesSet(SchedulerFactoryBean.java:514) [spring-context-support-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1612) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1549) [spring-beans-4.0.5.RELEASE.jar:4.0.5.RELEASE]
... 23 more
Caused by: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6#37427b2a
at org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:155)
at org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:395)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_71]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_71]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_71]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_71]
at org.quartz.impl.jdbcjobstore.AttributeRestoringConnectionInvocationHandler.invoke(AttributeRestoringConnectionInvocationHandler.java:73) [quartz-2.2.1.jar:]
at com.sun.proxy.$Proxy36.prepareStatement(Unknown Source)
at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:88) [quartz-2.2.1.jar:]
... 35 more

Resources