Tomcat 7 was throwing illegal state exceptions everywhere, even in the manager application, so it was impossible to use the server. In that case atmosphere-runtime.jar was packed in WEB-INF/lib, and removing the application with it from the server immediately solved the problem.
With atmosphere-runtime-native I didn't have this issue, but now I want to migrate my applications from PrimeFaces 4 to 5 and it doesn't works with atmosphere-runtime-native. I remember you helped me in PrimeFaces and Atmosphere forum. Since I still haven't found a solution for PrimeFaces 5 + atmosphere-runtime-native, I'm thinking about trying atmosphere-runtime again, but as the issue I mentioned only happens in production, I'd like to see first if anyone else is using it successfully. Can you share your connector configuration from server.xml? Currently I'm using this: <Connector compressableMimeType="text/html,text/xml,text/css,text/javascript,application/x-javascript,application/javascript" compression="on" connectionTimeout="20000" port="8080" protocol="org.apache.coyote.http11.Http11NioProtocol" redirectPort="8443" /> Thanks 2014-09-03 16:59 GMT-03:00 Howard W. Smith, Jr. <[email protected]>: > I use it, since I am using PrimeFaces Push in my web app. > > what problems are you having? how are you deploying and/or packaging > atmosphere-runtime? > > > > On Wed, Sep 3, 2014 at 3:16 PM, Felipe Jaekel <[email protected]> wrote: > > > Hi, > > > > Does anyone uses atmosphere-runtime in production with TomEE plus 1.7.0? > I > > had some problems when I tried it in a regular Tomcat 7 some time ago. > > > > Thanks > > >
