On Wed, Jan 30, 2013 at 4:44 PM, Patrick Flaherty <pflah...@rampageinc.com>wrote:
> > I have an open question about 32 bit vs 64 bit. We are currently deploying > our app with 32 bit JVM and Tomcat. We are running into memory issues > as we add more functionality (some via tools in the open source > ecosystem). We are testing our complete app with 64 bit JVM and 64 bit > Tomcat and so far we have seen no issues. My question is how prevalent is > the deployment of 64 bit enterprise apps. (just to show my naiveté). > We use some open source tools and look to use more in the future. Is there > things I should be worried about in moving to 64 bit in terms of open source > tools? > > > I recently became a user of Tomcat 7.0.33+ when I started using TomEE 1.5.1-SNAPSHOT and 1.5.2-SNAPSHOT. I migrated my web app from Glassfish 3.1.2.2, running very stable on Windows 2003 Server 32bit 4GB RAM (32bit client JVM), to Tomcat 7.0.34 on the same Windows Server 2003 server. My web app contains many open source libraries (PrimeFaces 3.5-SNAPSHOT, PrimeFaces Push which is Atmosphere 1.0.6+, and many others enabling silent printing, generating PDF files in memory, Google Calendar API, etc...). With 4GB RAM, honestly, the web app really did not have any memory issues. the user base is not that large (at all). Within the last 2 weeks, we finally migrated from Windows 2003 Server 32bit to Windows Server 2008 R2 64bit 32GB RAM. Running Tomcat 7.0.34 (TomEE 1.5.2-SNAPSHOT 2013-01-14 JAR), the web app was running very very stable on 64bit 'server' JVM with no memory issues. Honestly, it's only been recently, when tomEE 1.5.2-SNAPSHOT added Tomcat 7.0.35 dependency, have I started seeing unstability, server just stopping and only Windows event log tells me when this happens. This all started happening (2 days ago), when I migrated to TomEE 1.5.2-SNAPSHOT that has Tomcat 7.0.35 as a dependency. Honestly, I don't know if there is some issue between Tomcat 7.0.35 and Atmosphere 1.0.6+ plus, but tomcat/tomee logs is not telling me anything. So, i reverted to earlier version of tomEE 1.5.2-SNAPSHOT that has Tomcat 7.0.34 dependency. :) just sharing my personal experience.
