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. > Le 30 janv. 2013 04:26, "Howard W. Smith, Jr." <smithh032...@gmail.com> a > écrit : > > > > Okay, i need to add that -D-tomee.keep-server-info=true, but the latest version of TomEE 1.5.2-SNAPSHOT (2013-01-28) that I downloaded/installed on Windows Server 2008 R2 (32GB RAM) was stopping too much on my endusers, so I had to revert to the 2013-01-14 version of TomEE 1.5.2-SNAPSHOT. :) Honestly, I have no way of debugging/troubleshooting this issue. Reverting to earlier/stable version is all I know for now. Of course, I'm quite sure I cannot build or assemble a test case that can duplicate this issue. I've noticed that Windows Server 2008 had a Software Protection Service running and it seemed as though that was the possible cause of TomEE 1.5.2-SNAPSHOT (2013-01-28) windows service 'stopping'... The windows Event Viewer was the only reliable logging method to track this. When Atmosphere 1.0.10 is available/released, I will try to reinstall 2013-01-28 (or later) version of TomEE 1.5.2-SNAPSHOT on production server, and hopefully, TomEE windows service will continue to run. Again, I wish I knew what changed (if anything) between 2013-01-14 and 2013-01-28 that might be causing TomEE windows service to 'stop' running so much now. The 2013-01-14 version of TomEE 1.5.2-SNAPSHOT was running very well and stable between 01-18-2013 and 01-28-2013 (prior to installing 2013-01-28 version).
