Results 1 to 10 of 10

Thread: Out of control Java with 5.0.6

  1. #1
    Join Date
    Aug 2007
    Location
    Stamford, CT USA
    Posts
    16
    Rep Power
    8

    Default Out of control Java with 5.0.6

    I'm currently running zcs-NETWORK-5.0.6_GA_2313.RHEL5_64.20080522105815 on a AMD64 platform.

    Every other day at different times, we have observed zmmailboxdmgr begin to consume memory and eventually starve the machine to such an extent that the swapping locks the machine with 45 load or until it becomes unresponsive. The only remedy at this point is a SysRq-E and reboot.

    The process that causes this looks like this:

    /opt/zimbra/libexec/zmmailboxdmgr start -Xms803m -Xmx803m -client -XX:NewRatio=2 -Djava.awt.headless=true -XX:MaxPermSize=128m -XX:SoftRefLRUPolicyMSPerMB=1 -Xss256k

    The Zimbra server has 2 GB of physical RAM and 1 GB of swap. Under normal running circumstances (with Zimbra running), there is just under 1 GB free (uncached).

    The last thing in mailbox.log is the following:
    2008-06-11 22:15:11,163 INFO [btpool0-771] [name=admin@domain.com;mid=1;ip=5.5.5.5;] soap - NoOpRequest
    2008-06-11 22:15:14,765 INFO [MailboxPurge] [name=wiki@domain.com;mid=30;] purge - Purging messages.
    2008-06-11 22:16:05,393 INFO [btpool0-771] [name=admin@domain.com;mid=1;ip=5.5.5.5;ua=Zimbra Desktop/0.84;] soap - SyncRequest
    2008-06-11 22:16:11,680 INFO [btpool0-771] [name=admin@domain.com;mid=1;ip=5.5.5.5;] soap - NoOpRequest
    2008-06-11 22:16:14,949 INFO [MailboxPurge] [name=admin@domain.com;mid=1;] purge - Purging messages.

    I am currently using sun-jdk-1.6.0.06. The Zimbra documentation mentions that it should run on jdk 1.6. However, I'm wondering if it is safer to downgrade to jdk-1.5.0.15 or another jdk in the 1.5 series.

    It's impossible to reproduce this issue manually (I've tried). However, it will inevitably happen again. The recovery isn't too disruptive, but we'd obviously like to fix it.

    Please let me know if you have any advice and if you need additional information to diagnose the problem.

    If the forums do not prove helpful, I plan to open a ticket with Zimbra support.

    Thank you!

  2. #2
    Join Date
    Mar 2007
    Location
    Austin
    Posts
    441
    Rep Power
    8

    Default

    5.0.6 is on jdk-1.5.0.15, as far as I know. Have you changed that?

    Bug 27890 - Downgrade to JDK 1.5.0_15

    My /opt/zimbra/java points to /opt/zimbra/jdk1.5.0_15

  3. #3
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Quote Originally Posted by Myrddin View Post
    I'm currently running zcs-NETWORK-5.0.6_GA_2313.RHEL5_64.20080522105815 on a AMD64 platform.

    Every other day at different times, we have observed zmmailboxdmgr begin to consume memory and eventually starve the machine to such an extent that the swapping locks the machine with 45 load or until it becomes unresponsive. The only remedy at this point is a SysRq-E and reboot.

    The process that causes this looks like this:

    /opt/zimbra/libexec/zmmailboxdmgr start -Xms803m -Xmx803m -client -XX:NewRatio=2 -Djava.awt.headless=true -XX:MaxPermSize=128m -XX:SoftRefLRUPolicyMSPerMB=1 -Xss256k

    The Zimbra server has 2 GB of physical RAM and 1 GB of swap. Under normal running circumstances (with Zimbra running), there is just under 1 GB free (uncached).

    The last thing in mailbox.log is the following:
    2008-06-11 22:15:11,163 INFO [btpool0-771] [name=admin@domain.com;mid=1;ip=5.5.5.5;] soap - NoOpRequest
    2008-06-11 22:15:14,765 INFO [MailboxPurge] [name=wiki@domain.com;mid=30;] purge - Purging messages.
    2008-06-11 22:16:05,393 INFO [btpool0-771] [name=admin@domain.com;mid=1;ip=5.5.5.5;ua=Zimbra Desktop/0.84;] soap - SyncRequest
    2008-06-11 22:16:11,680 INFO [btpool0-771] [name=admin@domain.com;mid=1;ip=5.5.5.5;] soap - NoOpRequest
    2008-06-11 22:16:14,949 INFO [MailboxPurge] [name=admin@domain.com;mid=1;] purge - Purging messages.

    I am currently using sun-jdk-1.6.0.06. The Zimbra documentation mentions that it should run on jdk 1.6. However, I'm wondering if it is safer to downgrade to jdk-1.5.0.15 or another jdk in the 1.5 series.

    It's impossible to reproduce this issue manually (I've tried). However, it will inevitably happen again. The recovery isn't too disruptive, but we'd obviously like to fix it.

    Please let me know if you have any advice and if you need additional information to diagnose the problem.

    If the forums do not prove helpful, I plan to open a ticket with Zimbra support.

    Thank you!
    Hi Myrddin,
    I'm sad to say you don't have enough RAM, and you're using Swap. Swap is not good for Zimbra, and results in delays during Garbage Collection (GC).

    That's probably your problem.

    There is a myth in the world about 2GB on 64 bit. 2Gb on 64 bit doesn't equal 2Gb on 32bit. Why? Well, it's easy: There are more bits. More bits=more memory usage. Thus Java needs more memory that it would on a 32 bit system.

    The min requirements for 64 bit is 4GB, no swap. Swap doesn't = RAM.

    So.. what are your options? Well, You can install a 32 bit OS. You won't get the benefit of 64 bit extensions...but since you only have 2 GB, then it doesn't matter anyway. The main benefit of 64 bit is the ability to have more than 4 GB of RAM.

    So, here are your options:

    Option 1- Install 32 bit OS

    Option 2 - Disable AV/AS/POP3/IMAP/Logger

    Option 3 - Get more RAM.

    Hope this helps!!

  4. #4
    Join Date
    Aug 2007
    Location
    Stamford, CT USA
    Posts
    16
    Rep Power
    8

    Default

    I am going downgrade to jdk 1.5.0_15 _and_ get more RAM.

    Thank you very much for your replies!

  5. #5
    Join Date
    Mar 2008
    Location
    Palma, Majorca, Balearic Islands, Spain
    Posts
    44
    Rep Power
    7

    Default

    What about using Java 1.6, jholder? Java 1.6 introduces lots of improvements, specially in performance and memory management? Is there any set date from which Zimbra will ship with Java 1.6? Is it safe to use it (the latest revision) with the current version of Zimbra?
    Jaume Sabater
    http://linuxsilo.net/

    "Ubi sapientas ibi libertas"

  6. #6
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Quote Originally Posted by jsabater View Post
    What about using Java 1.6, jholder? Java 1.6 introduces lots of improvements, specially in performance and memory management? Is there any set date from which Zimbra will ship with Java 1.6? Is it safe to use it (the latest revision) with the current version of Zimbra?
    Did you have a change to read the above bug on why we backed out of 1.6? Too many issues:
    JDK 1.6.0_04 and 1.6.0_05 are affected by:

    Bug ID: 6614100 EXCEPTION_ACCESS_VIOLATION while running Eclipse with 1.6.0_05-ea (Zimbra bug 24648).

    CorruptIndexException with some versions of java | Lucene | Java-User

    We can't downgrade to JDK 1.6.0_03 because that has:

    Bug ID: 6546278 Synchronization problem in the pseudo memory barrier code (Zimbra bug 22311)

    JDK 1.5.0_15 has a fix for 6546278, and hope is it doesn't have the code
    generator regressions in JDK 1.6.0_04_and_05.

    With JDK 1.5, can't use jmap to get a heap dump at any moment. Have to use
    HeapDumpOnCtrlBreak. See Alan Bateman : Weblog

    JDK 1.5 NIO does NOT use poll by default. Jetty uses NIO extensively (as does
    Zimbra IM.) According to
    Bug ID: 6330315 (se) Selectors should use epoll on Linux:

    The epoll SelectorProvider has also been added to 5.0 update 9. It is not
    enabled by default and requires that the system property
    java.nio.channels.spi.SelectorProvider be set to
    sun.nio.ch.EPollSelectorProvider to enable it.
    Posted Date : 2006-07-29 17:02:49.0

  7. #7
    Join Date
    Mar 2008
    Location
    Palma, Majorca, Balearic Islands, Spain
    Posts
    44
    Rep Power
    7

    Default

    Quote Originally Posted by jholder View Post
    Did you have a change to read the above bug on why we backed out of 1.6? Too many issues:
    Yes, I did. That is why I asked about the latest revision (1.6 update 6 and above). Do you have any plans on using it in version 5.0.7 or above?

    Thanks in advance for the heads up.
    Jaume Sabater
    http://linuxsilo.net/

    "Ubi sapientas ibi libertas"

  8. #8
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Quote Originally Posted by jsabater View Post
    Yes, I did. That is why I asked about the latest revision (1.6 update 6 and above). Do you have any plans on using it in version 5.0.7 or above?

    Thanks in advance for the heads up.
    We're probably gonna let the update simmer in the java community before we implement. If you wanna run it, it'll run (probably). There's no Zimbra requirement to run in 1.6.

    As far as memory management, Bug 28569 – sun bug 6578538 - com.sun.crypto.provider.SunJCE memory leak with kerberos is fixed in u6 as well. However, as I'm sure you know, because the update is relatively new, we need to review any new issues that come up in the sun bugzilla, and then do some QA.

    We wouldn't have made the downgrade to 1.5 had it not been a critical situation for us.

  9. #9
    Join Date
    Mar 2008
    Location
    Palma, Majorca, Balearic Islands, Spain
    Posts
    44
    Rep Power
    7

    Default

    Given the performance differences we've noted in our in-house developed Java applications, I understand. I guess we've been fortunate enough not to need affected components of the Java platform.

    Anyway, we'll wait and hope for, perhaps, Java 1.6 update 10 to mean the return to 1.6 for Zimbra in, maybe, a couple of months or three.

    Thanks for your time, jholder.
    Jaume Sabater
    http://linuxsilo.net/

    "Ubi sapientas ibi libertas"

  10. #10
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Quote Originally Posted by jsabater View Post
    Given the performance differences we've noted in our in-house developed Java applications, I understand. I guess we've been fortunate enough not to need affected components of the Java platform.

    Anyway, we'll wait and hope for, perhaps, Java 1.6 update 10 to mean the return to 1.6 for Zimbra in, maybe, a couple of months or three.

    Thanks for your time, jholder.
    Sure, and if you wanna experiment, go for it. This is a house built on developers and community.

Similar Threads

  1. Replies: 4
    Last Post: 10-22-2007, 02:42 PM
  2. Fedora 5: Could not create the Java virtual machine
    By mi2enno in forum Installation
    Replies: 6
    Last Post: 06-01-2007, 04:16 AM
  3. Tomcat, Java VM Problems - RAM related? Help
    By Mo_Hong in forum Administrators
    Replies: 3
    Last Post: 03-28-2007, 03:00 PM
  4. Java 1.5 crashing on PPC Mac 10.4.8
    By bradn in forum Installation
    Replies: 1
    Last Post: 12-08-2006, 06:27 PM
  5. Replies: 0
    Last Post: 12-04-2005, 02:34 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •