Are you saying, does it work without tomee 1.5.2 SNAPSHOT integrated? I
have not tested that, but atmosphere does work with recent builds of TomEE
1.5.2 SNAPSHOT, but it core dumps unexpectedly, under load or after some
time has passed. I'm waiting to see if it core dumps unexpectedly again
after
...@gmail.com
To: users@tomee.apache.org
Cc:
Sent: Thursday, January 31, 2013 2:14 PM
Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
on me, nothing in server logs
Interesting, I ran tomcat7w.exe from d:\tomcat7.0.35\bin folder, and I
am
accessing the 'tomee
:
Sent: Thursday, January 31, 2013 2:14 PM
Subject: Re: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just
died on me, nothing in server logs
Interesting, I ran tomcat7w.exe from d:\tomcat7.0.35\bin folder, and I
am
accessing the 'tomee' windows service config. So, I can use
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
On Wed, Jan 30, 2013 at 12:44 PM, Howard W. Smith, Jr.
smithh032...@gmail.com wrote:
On Wed, Jan 30, 2013 at 1:14 AM, Romain Manni-Bucau rmannibu...@gmail.com
wrote:
Add -Dtomee.keep-server-info=true ... but that's an atmosphere issue. It
shouldn't rely on this to get the tomcat version.
Since these issues started when I started using Atmosphere 1.0.8 and 1.0.9
with TomEE 1.5.2-SNAPSHOT (2013-01-28), I assuming that this is either a
tomcat7.0.35 or Atmosphere issue.
Please let me know if I should create a tomcat issue/jira or atmosphere
issue on atmosphere github.
Again/FYI,
: Latest-version TomEE 1.5.2-SNAPSHOT (Tomcat 7.0.34?) just died
on me, nothing in server logs
Sending this to tomee/openejb and tomcat user mailing lists.
Cross-posting is really frowned upon.
Jan 29, 2013 10:27:25 AM org.apache.catalina.core.StandardWrapperValve
event
SEVERE
