Add -Dtomee.keep-server-info=true ... but that's an atmosphere issue. It shouldn't rely on this to get the tomcat version. Le 30 janv. 2013 04:26, "Howard W. Smith, Jr." <smithh032...@gmail.com> a écrit :
> I didn't experience this issue while running Atmosphere 1.0.9, so i > recompiled the project with Atmosphere 1.0.9, atmosphere-compat-tomcat.jar > (tomcat6 jar) is in tomee/lib (as this has been standard procedure for me), > and restarted tomee. > > also, i checked event log on the windows server, and wow, google update > service was triggered and started to run one hour prior to tomee service > stopping. i had to login to the server and restart tomee. i just disabled > google update service and a dns client service running on the windows 2008 > server. i'm quite sure that i have no need of either of those services from > running. > > i'm going to monitor logs in tomee/logs to see if atmosphere 1.0.9 is > running good/okay with latest TomEE 1.5.2-SNAPSHOT. >
