Hi,
I've stumbled upon a very weird issue. I have an Atmosphere application on JBoss AS 7, works as expected. Using APR, Tomcat native, Apache front-end HTTP proxy.
Now, when I explicitly set a port-offset in standalone-full.xml (and I reconfigure the Apache front-end HTTP proxy of course), I get the following exception:
06:18:43,166 WARN [org.atmosphere.cpr.AtmosphereFramework] (http-localhost/127.0.0.1:8180-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? 06:18:43,166 ERROR [org.atmosphere.cpr.AtmosphereFramework] (http-localhost/127.0.0.1:8180-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.4.jar:2.1.4]
Anyone any idea why this would happen?
Kind Regards,
Frank.
Upgrading to jbossweb-7.4.2.Final.jar seems to resolve the issue.