I've upgraded my JVM a number of times, had no problems, ever. As long as you stay in the 1.4.2 space, the _#s are just bugfixes mostly, and you can safely upgrade on CFMX 6 or 7 (just watch out for 1.5 if you like web services and XML). I won't say that upgrading my JVM solved every one of my problems with servers crashing, but it did help. Really, the way to go is to see about re-architecting your applications, upgrading your servers (Java can use almost 2GB of RAM on a 32bit server), or considering network load balancing.
-nathan strutz http://www.dopefly.com/ On 4/5/06, powell @ nauticom. net powell @ nauticom. net < [EMAIL PROTECTED]> wrote: > > We've been having a rash of JVM crashes (1 per day usually) for the past > 7-10 days. That's better than what it was before then (4-5 per day). We > opened a ticket with Adobe/MM and made some jvm.config changes they > suggested for heap memory handling (and also moved the client var database > from Access to SQL Server), and that changed the frequency and nature of the > crashes. The JVM crashes we're seeing now have the JVM apparently running > out of memory (NT memory, not heap memory) and stopping in it's tracks. The > latest suggestion from Adobe/MM is to upgrade to version 1.4.2_09 of the > JVM, since this could in fact be a JVM bug. > > Anyone out there done this and know of any gotchas before I do this? > > TIA, > Reed > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:237016 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
