Thanks a lot Howard and Romain for your suggestions.
Unfortunately I still have the problem.
With Atmosphere JARs inside the application’s WAR I obtain these logs:
INFO: ------------------------- localhost -> /wsk_test
Jul 08, 2013 12:13:34 PM org.apache.openejb.config.ConfigurationFactory
configureApplication
INFO: Configuring enterprise application:
/home/Users/stefano/Develop/apache-tomee-plus-1.5.2/webapps/wsk_test
Jul 08, 2013 12:13:34 PM org.apache.openejb.config.AppInfoBuilder build
INFO: Enterprise application
"/home/Users/stefano/Develop/apache-tomee-plus-1.5.2/webapps/wsk_test"
loaded.
Jul 08, 2013 12:13:34 PM org.apache.openejb.assembler.classic.Assembler
createApplication
INFO: Assembling app:
/home/Users/stefano/Develop/apache-tomee-plus-1.5.2/webapps/wsk_test
Jul 08, 2013 12:13:34 PM org.apache.openejb.cdi.CdiBuilder initSingleton
INFO: Existing thread singleton service in SystemInstance():
org.apache.openejb.cdi.ThreadSingletonServiceImpl@150421e7
Jul 08, 2013 12:13:34 PM org.apache.openejb.cdi.OpenEJBLifecycle
startApplication
INFO: OpenWebBeans Container is starting...
Jul 08, 2013 12:13:34 PM org.apache.webbeans.plugins.PluginLoader startUp
INFO: Adding OpenWebBeansPlugin : [CdiPlugin]
Jul 08, 2013 12:13:34 PM org.apache.webbeans.plugins.PluginLoader startUp
INFO: Adding OpenWebBeansPlugin : [OpenWebBeansJsfPlugin]
Jul 08, 2013 12:13:34 PM org.apache.openejb.cdi.BeansDeployer
validateInjectionPoints
INFO: All injection points are validated successfully.
Jul 08, 2013 12:13:34 PM org.apache.openejb.cdi.OpenEJBLifecycle
startApplication
INFO: OpenWebBeans Container has started, it took 12 ms.
Jul 08, 2013 12:13:34 PM org.apache.openejb.assembler.classic.Assembler
createApplication
INFO: Deployed
Application(path=/home/Users/stefano/Develop/apache-tomee-plus-1.5.2/webapps/wsk_test)
Jul 08, 2013 12:13:34 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/home/Users/stefano/Develop/apache-tomee-plus-1.5.2/webapps/docs
Jul 08, 2013 12:13:35 PM org.apache.tomee.catalina.TomcatWebAppBuilder init
It seems that Atmosphere is not initialized and it doesn’t work.
However with Atmosphere JARs inside TomEE lib I obtain:
INFO: ------------------------- localhost -> /wsk_test
Jul 08, 2013 12:16:31 PM org.apache.openejb.config.ConfigurationFactory
configureApplication
INFO: Configuring enterprise application:
/home/Users/stefano/Develop/apache-tomee-plus-1.5.2.atmos/webapps/wsk_test
Jul 08, 2013 12:16:31 PM org.apache.openejb.config.AppInfoBuilder build
INFO: Enterprise application
"/home/Users/stefano/Develop/apache-tomee-plus-1.5.2.atmos/webapps/wsk_test"
loaded.
Jul 08, 2013 12:16:31 PM org.apache.openejb.assembler.classic.Assembler
createApplication
INFO: Assembling app:
/home/Users/stefano/Develop/apache-tomee-plus-1.5.2.atmos/webapps/wsk_test
Jul 08, 2013 12:16:31 PM org.apache.openejb.cdi.CdiBuilder initSingleton
INFO: Existing thread singleton service in SystemInstance():
org.apache.openejb.cdi.ThreadSingletonServiceImpl@177e93e6
Jul 08, 2013 12:16:31 PM org.apache.openejb.cdi.OpenEJBLifecycle
startApplication
INFO: OpenWebBeans Container is starting...
Jul 08, 2013 12:16:31 PM org.apache.webbeans.plugins.PluginLoader startUp
INFO: Adding OpenWebBeansPlugin : [CdiPlugin]
Jul 08, 2013 12:16:31 PM org.apache.webbeans.plugins.PluginLoader startUp
INFO: Adding OpenWebBeansPlugin : [OpenWebBeansJsfPlugin]
Jul 08, 2013 12:16:31 PM org.apache.openejb.cdi.BeansDeployer
validateInjectionPoints
INFO: All injection points are validated successfully.
Jul 08, 2013 12:16:31 PM org.apache.openejb.cdi.OpenEJBLifecycle
startApplication
INFO: OpenWebBeans Container has started, it took 8 ms.
Jul 08, 2013 12:16:31 PM org.apache.openejb.assembler.classic.Assembler
createApplication
INFO: Deployed
Application(path=/home/Users/stefano/Develop/apache-tomee-plus-1.5.2.atmos/webapps/wsk_test)
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework
autoDetectAtmosphereHandlers
INFO: Auto detecting atmosphere handlers /WEB-INF/classes/
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework
autoDetectWebSocketHandler
INFO: Auto detecting WebSocketHandler in /WEB-INF/classes/
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework
loadWebSocketFromPath
INFO: Installed WebSocketProtocol
org.atmosphere.samples.chat.WebSocketChat@5e73a225
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework
autoDetectContainer
INFO: Atmosphere is using async support:
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket running under
container: Apache Tomcat (TomEE)/7.0.37
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.DefaultBroadcaster <init>
INFO: /* support Out Of Order Broadcast: false
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework
addAtmosphereHandler
INFO: Installed AtmosphereHandler org.atmosphere.cpr.AtmosphereFramework$4
mapped to context-path: /*
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework
configureAtmosphereInterceptor
INFO: Installed Default AtmosphereInterceptor [Android Interceptor Support,
SSE Interceptor Support, JSONP Interceptor Support, Atmosphere JavaScript
Protocol, Browser disconnection detection]. Set
org.atmosphere.cpr.AtmosphereInterceptor.disableDefaults in your xml to
disable them.
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework init
WARNING: No BroadcasterCache configured. Broadcasted message between client
reconnection will be LOST. It is recommended to configure the
org.atmosphere.cache.UUIDBroadcasterCache
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework init
INFO: Shared ExecutorService supported: true
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework init
INFO: HttpSession supported: false
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework init
INFO: Using BroadcasterFactory: org.atmosphere.cpr.DefaultBroadcasterFactory
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework init
INFO: Using WebSocketProcessor:
org.atmosphere.websocket.DefaultWebSocketProcessor
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework init
INFO: Using Broadcaster: org.atmosphere.cpr.DefaultBroadcaster
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework init
INFO: Atmosphere Framework 1.0.13 started.
Jul 08, 2013 12:16:32 PM org.atmosphere.cpr.AtmosphereFramework init
INFO:
For Commercial Support, visit
http://www.async-io.org/ or send an email to [email protected]
Jul 08, 2013 12:16:32 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/home/Users/stefano/Develop/apache-tomee-plus-1.5.2.atmos/webapps/docs
Jul 08, 2013 12:16:32 PM org.apache.tomee.catalina.TomcatWebAppBuilder init
Now it seems that Atmosphere is initialized, in fact it works.
I’ll try to investigate a little more.
Any suggestions are welcome.
- Stefano
Romain Manni-Bucau wrote
> Hi
>
> Add openejb.classloader.force-load=org.apache.catalina (if im not mistaken
> on the key name) it should work
> Le 5 juil. 2013 18:38, "stx_g" <
> stx_g@
> > a écrit :
>
>> Hi,
>>
>> I’m working on a new project where I need to use web sockets. I’ve just
>> made some test code using Atmosphere under Tomcat7 and it seems it works
>> very well.
>>
>> But I’d like to use TomEE+.
>>
>> Exactly the same WAR that works under Tomcat7, doesn’t work under
>> TomEE+
>> 1.5.2. I’ve also tried with the latest snapshot of TomEE 1.6.0 but ..
>> nothing.
>>
>> Then I read this thread:
>>
>>
>> http://openejb.979440.n4.nabble.com/TomEE-1-5-1-java-lang-NoClassDefFoundError-org-apache-catalina-CometProcessor-td4659217.html
>>
>> Now, if I copy Atmosphere’s JARs in the TomEE lib the problem
>> disappear.
>>
>> Don’t you have this kind of problem?
>>
>>
>> Thanks.
>>
>>
>> - Stefano
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://openejb.979440.n4.nabble.com/Websocket-in-TomEE-tp4664043p4664131.html
>> Sent from the OpenEJB User mailing list archive at Nabble.com.
>>
--
View this message in context:
http://openejb.979440.n4.nabble.com/Websocket-in-TomEE-tp4664043p4664139.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
