see my responses inline, below.
On Thu, Sep 4, 2014 at 12:59 PM, Felipe Jaekel <[email protected]> wrote: > 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. > hmmm, what do you mean, when you say that it was impossible to use the server? server == tomcat7 or tomee 1.x? what do you mean when you say, removing the application with it from the server immediately solved the problem? application = WAR that includes primefaces + atmosphere-runtime JAR ? server = tomcat7 or tomee 1.x ? > > 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 think you were running atmosphere-runtime-native and primefaces 4 with tomcat7 (and not tomee 1.x), right? > > 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. > i would assume that primefaces 5 + atmosphere-runtime-native will work, if/since primefaces 4 + atmosphere-runtime-native + your server/app config. i have been using primefaces 4 and 5 + atmosphere-runtime JAR + tomee 1.5.1, 1.6.x, and 1.7.0. I include atmosphere-runtime JAR in my WAR file, and I do not use atmosphere-compat JARs, and I use websocket instead of COMET. > > 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" /> > > below, is my <connector> in server.xml, <Connector port="8080" protocol="org.apache.coyote.http11.Http11NioProtocol" maxThreads="150" connectionTimeout="20000" acceptorThreadCount="2" redirectPort="8443" socket.directBuffer="false"/> and my web.xml has the following: <servlet> <servlet-name>Push Servlet</servlet-name> <servlet-class>org.primefaces.push.PushServlet</servlet-class> <load-on-startup>1</load-on-startup> <init-param> <param-name>org.atmosphere.cpr.broadcasterCacheClass</param-name> <param-value>org.atmosphere.cache.UUIDBroadcasterCache</param-value> </init-param> <async-supported>true</async-supported> </servlet> <servlet-mapping> <servlet-name>Push Servlet</servlet-name> <url-pattern>/primepush/*</url-pattern> </servlet-mapping> > 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 > > > > > >
