Wow, interesting, now I am getting the following error in my server log (first time ever)
Jan 31, 2013 10:49:07 AM org.atmosphere.cpr.AtmosphereFramework doCometSupport WARNING: Failed using comet support: org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket, error: Tomcat failed to detect this is a Comet application because context.xml is missing or the Http11NioProtocol Connector is not enabled. If that's not the case, you can also remove META-INF/context.xml and WEB-INF/lib/atmosphere-compat-tomcat.jar Is the Nio or Apr Connector enabled? Jan 31, 2013 10:49:07 AM org.atmosphere.cpr.AtmosphereFramework doCometSupport WARNING: Using org.atmosphere.container.Tomcat7BIOSupportWithWebSocket and many many attempts/occurrences of the following: Jan 31, 2013 10:51:13 AM org.atmosphere.container.BlockingIOCometSupport action SEVERE: Unable to resume the suspended connection Jan 31, 2013 10:51:13 AM org.atmosphere.container.BlockingIOCometSupport action SEVERE: Unable to resume the suspended connection Jan 31, 2013 10:51:25 AM org.atmosphere.container.BlockingIOCometSupport action SEVERE: Unable to resume the suspended connection someone else reported this/similar at URL below https://groups.google.com/forum/?fromgroups=#!topic/atmosphere-framework/wx9HC2Xef0o Since I didn't see this while running tomcat7 APR, I wonder if I need to configure APR. On Thu, Jan 31, 2013 at 10:09 AM, Howard W. Smith, Jr. < [email protected]> wrote: > Smiling... not tomee related but tomcat. I like that response! :) > > I'll have to research that. I was waiting for your response to let you > know that I'm going to run 'without' APR, and 'maybe' do some research to > see if I really need or could benefit from APR/tcnative, because as I see > it, this issue was due to the fact that I was using tomcat APR, and tomcat > APR and atmosphere was not 'jelling' together well under my 'previous' > config of tomcat7exe (windows service) running tomee. > > since I'm waiting patiently for Atmosphere 1.0.10, I'm going to continue > to use the 'stable' Atmosphere 1.0.6 version that works well with my other > dependencies, unless i get tempted and look at issues fixed by Atmosphere > 1.0.7/8/9. :) > > i will keep you all posted. as always, thank you TomEE committers! > > > On Thu, Jan 31, 2013 at 9:59 AM, Romain Manni-Bucau <[email protected] > > wrote: > >> %PATH% -> apr >> >> then regarding perf it is not tomee related but tomcat >> >> it enhances perf in some cases and degrades them in some others...depends >> the app >> >> *Romain Manni-Bucau* >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* >> *Blog: **http://rmannibucau.wordpress.com/*< >> http://rmannibucau.wordpress.com/> >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* >> *Github: https://github.com/rmannibucau* >> >> >> >> 2013/1/31 Howard W. Smith, Jr. <[email protected]> >> >> > add it to your win %PATH% ? 'it' = ? it = tomee/bin folder to %PATH% ? >> > >> > will not make app faster in all cases? so, tomee (committers) does not >> > recommend use of APR for faster performance? please let me know, >> because if >> > I remove APR, then I'm assuming APR = tomcat native, and that already >> > (along with other changes made today or this morning) resolves the issue >> > where tomee (or tomcat7 service) does not 'stop' unexpectedly because of >> > some conflict between atmosphere and tcnative. >> > >> > >> > >> > On Thu, Jan 31, 2013 at 9:49 AM, Romain Manni-Bucau >> > <[email protected]>wrote: >> > >> > > add it to your win %PATH% >> > > >> > > but you know it will not make your app faster in all cases? >> > > >> > > the message is a bit wrong on that point >> > > >> > > *Romain Manni-Bucau* >> > > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* >> > > *Blog: **http://rmannibucau.wordpress.com/*< >> > > http://rmannibucau.wordpress.com/> >> > > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* >> > > *Github: https://github.com/rmannibucau* >> > > >> > > >> > > >> > > 2013/1/31 Howard W. Smith, Jr. <[email protected]> >> > > >> > > > Okay, this has always concerned me, even when I see this in the log >> on >> > my >> > > > development machine, which uses tomee startup scripts, when I start >> > tomee >> > > > via Netbeans - Servers - right-click TomEE, and select Start or >> Stop. >> > > > >> > > > >> > > > When I use tomcat7/bin service.bat to install 'tomcat7' default >> windows >> > > > service, I see the following in the log (APR is loaded successfully, >> > > > always) >> > > > >> > > > 2013-01-31 01:57:12 Commons Daemon procrun stderr initialized >> > > > Jan 31, 2013 1:57:17 AM >> org.apache.catalina.core.AprLifecycleListener >> > > init >> > > > INFO: Loaded APR based Apache Tomcat Native library 1.1.24 using APR >> > > > version 1.4.6. >> > > > Jan 31, 2013 1:57:17 AM >> org.apache.catalina.core.AprLifecycleListener >> > > init >> > > > INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters >> > > > [false], random [true]. >> > > > Jan 31, 2013 1:57:19 AM >> org.apache.catalina.core.AprLifecycleListener >> > > > initializeSSL >> > > > INFO: OpenSSL successfully initialized (OpenSSL 1.0.1c 10 May 2012) >> > > > >> > > > >> > > > But when I use tomee/bin service.bat to install tomee windows >> service >> > > (and >> > > > when I start tomee server via Netbeans/tomee mgr scripts), I see the >> > > > following on development server (and now on production server) >> > > > >> > > > 2013-01-31 09:01:41 Commons Daemon procrun stderr initialized >> > > > Jan 31, 2013 9:01:43 AM >> org.apache.catalina.core.AprLifecycleListener >> > > init >> > > > INFO: The APR based Apache Tomcat Native library which allows >> optimal >> > > > performance in production environments was not found on the >> > > > java.library.path: >> > > > >> > > > >> > > >> > >> D:\apache-tomee-plus-1.5.2-SNAPSHOT\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;. >> > > > >> > > > Please advise how i can get APR loaded successfully using tomee >> > > > scripts/service/etc... >> > > > >> > > > >> > > > On Thu, Jan 31, 2013 at 9:24 AM, Howard W. Smith, Jr. < >> > > > [email protected]> wrote: >> > > > >> > > > > Okay, now that I'm using tomee service exe, as per Romain's >> > suggestion, >> > > > > and already updated max perm size as per Mark's suggestion and >> > > restarted >> > > > > server on production server... a quick update: >> > > > > >> > > > > 1. Downloaded, installed, and >> > > > > running apache-tomee-1.5.2-20130130.041108-54-plus.zip on >> production >> > > > server >> > > > > (Windows Server 2008 64bit 32GB RAM) >> > > > > >> > > > > 2. Also added -Dtomee.keep-server-info=true, as Romain suggested >> > > earlier >> > > > > >> > > > > 3. Reverted to and running Atmosphere 1.0.6; why? because from >> what I >> > > > > remember/witnessed, tomee/tomcat7 service stopped unexpectedly >> with >> > > > > Atmosphere 1.0.8, 1.0.9, and 1.0.6 (in that order) without the >> > > > > -Dtomee.keep-server-info=true, when running with tomee >> 1.5.2-SNAPSHOT >> > > > build >> > > > > 2013-01-28 between the dates of 2013-01-28 and 2013-01-30 >> > > > > >> > > > > 4. Even though the web app (and tomee) has not been under load >> (yet, >> > > > > today) like it was yesterday morning and afternoon, I have not >> seen >> > > > issue # >> > > > > 1 (tomee stopping, unexpectedly, with core dump) or # 2 >> (atmosphere >> > > > "(TomEE)/7" >> > > > > numberFormatException), as mentioned/discussed in OP and >> throughout >> > > this >> > > > > thread, ever since I added -Dtomee.keep-server-info=true >> > > > > >> > > > > 5. Actually, I am considering re-adding Atmosphere 1.0.8 or 1.0.9 >> to >> > > the >> > > > > mix, just to see/confirm if tomee will stop, unexpectedly, with a >> > > > > resulting-core-dump in tomee/bin like it did (at least) 3 times in >> > > > > tomcat7/bin, when this issue occurred in the last 3 days. >> > > > > >> > > > > 6. still waiting patiently for Atmosphere 1.0.10 to be released, >> > which >> > > > > includes fix for atmosphere "(TomEE)/7" numberFormatException, >> along >> > > with >> > > > > other fixes that was targeting PrimeFaces Push (PrimeFaces >> > > 3.5-SNAPSHOT) >> > > > > and non-PrimeFaces-Push users (I assume). >> > > > > >> > > > > >> > > > > >> > > > > On Thu, Jan 31, 2013 at 6:20 AM, Romain Manni-Bucau < >> > > > [email protected] >> > > > > > wrote: >> > > > > >> > > > >> tomcat supports websockets but no link with atmosphere (maybe >> > > > classloader >> > > > >> issue in your app, check deps) >> > > > >> >> > > > >> maybe try using tomee service exe instead of tomcat ones too >> > > > >> >> > > > >> *Romain Manni-Bucau* >> > > > >> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* >> > > > >> *Blog: **http://rmannibucau.wordpress.com/*< >> > > > >> http://rmannibucau.wordpress.com/> >> > > > >> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* >> > > > >> *Github: https://github.com/rmannibucau* >> > > > >> >> > > > >> >> > > > >> > > >> > >> > >
