The fix for Zimbra bug 22311, which we've been experiencing daily, is to upgrade java to 1.6.0_04. Currently, we're using 1.6.0_02 on a 4.5.10 installation.
I've downloaded 1.6.0_04 and placed the directory in /opt/zimbra/. I'd hoped that simply repointing the /opt/zimbra/java soft link from jdk1.6.0_02/ jdk1.6.0_04/ and restarting tomcat would swap in the new java. Alas, tomcat continues to use the older version. I've Googled and searched the Zimbra wiki and forums for instructions on how to do this, but all I've been able to find is how to upgrade from 1.5 to 1.6. I don't think it should be this complex to simply move to a newer build of java 6, though.
The fix for this -- i.e., the newer version of java -- is included with 4.5.11 when it's released, but we'd really like to squash this bug now if we can. Can anyone tell me how to switch in the newer java version?