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. >> 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. :) > > > Okay, I was wondering if TomEE 1.5.2-SNAPSHOT was now using (and when TomEE 1.5.2-SNAPSHOT started using) Tomcat 7.0.35, and I see that TOMEE-740[1] was when TomEE 1.5.2-SNAPSHOT upgraded to Tomcat 7.0.35. Since I listen in on tomcat user list, I do remember the announcement of tomcat 7.0.35, and I do remember a known issue with 7.0.35, and I heard that it was best to wait for 7.0.36, which was coming soon/ASAP. I wonder if the upgrade to 7.0.35 is the cause of the issue that I'm reporting here and in the OP. I see that Tomcat 7.0.35 dependency was added to TomEE 1.5.2-SNAPSHOT on 2013-01-17. As mentioned earlier, I had no issues when TomEE 1.5.2-SNAPSHOT was using Tomcat 7.0.34 dependency. Now, I'm reviewing TomEE 1.5.2-SNAPSHOT issue list (and/or change log) [2] and Tomcat 7.0.35 change log[3]. [1] https://issues.apache.org/jira/browse/TOMEE-740 [2] https://issues.apache.org/jira/issues/?jql=project%20%3D%20TOMEE [3] http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
