Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-12-2007, 09:10 AM
Senior Member
 
Posts: 72
Default Outlook crashing tomcat

Yesterday I experienced an issue with our mailbox (tomcat) being stopped. I'd restart it and a few minutes later it would stop again. I had to do this about 8-10 times over the next hour while simultaneously looking through the logs. It stopped crashing just after 5 pm or so. I was able to find that there were repeated entries in the mailbox.log saying "java.lang.OutOfMemoryError: Java heap space". It was always for the same user and always during a message send. Turns out the user turned off their PC at 5pm and went home - right when the crashing stopped.

Today I was able to confirm that they have an email stuck in their outbox and every attempt to deliver results in this heap error and usually every 3rd or 4th attempt results in tomcat crashing completely.

As for the message, it doesn't appear to be too unusual. It is a reply to a mass email of about 30 people. He's attempting to reply to all 30 of them and then CC 2 other. I sent myself a test message from his account which does leave the inbox, but the stuck message stays stuck.

Obviously, deleting this email will stop this instance of the problem - but I want to prevent it from happening again with him or anyone else.

Specifics:
server is a VMWARE VM running with 2G of RAM and 2 cores assigned. There are about 75 total mailboxes on this server. Zimbra version is Network Edition 4.5.5. User is on XP Pro with Outlook 2003 and Zimbra ZCS 4.5.230.0.

What I find most disturbing is that outlook can bring down the Web Client and Web admin client.

I appreciate any help or troubleshooting/prevention advice.
Reply With Quote
  #2 (permalink)  
Old 09-12-2007, 11:27 AM
Former Zimbran
 
Posts: 5,606
Default

Quote:
Originally Posted by shankwc View Post
Yesterday I experienced an issue with our mailbox (tomcat) being stopped. I'd restart it and a few minutes later it would stop again. I had to do this about 8-10 times over the next hour while simultaneously looking through the logs. It stopped crashing just after 5 pm or so. I was able to find that there were repeated entries in the mailbox.log saying "java.lang.OutOfMemoryError: Java heap space". It was always for the same user and always during a message send. Turns out the user turned off their PC at 5pm and went home - right when the crashing stopped.

Today I was able to confirm that they have an email stuck in their outbox and every attempt to deliver results in this heap error and usually every 3rd or 4th attempt results in tomcat crashing completely.

As for the message, it doesn't appear to be too unusual. It is a reply to a mass email of about 30 people. He's attempting to reply to all 30 of them and then CC 2 other. I sent myself a test message from his account which does leave the inbox, but the stuck message stays stuck.

Obviously, deleting this email will stop this instance of the problem - but I want to prevent it from happening again with him or anyone else.

Specifics:
server is a VMWARE VM running with 2G of RAM and 2 cores assigned. There are about 75 total mailboxes on this server. Zimbra version is Network Edition 4.5.5. User is on XP Pro with Outlook 2003 and Zimbra ZCS 4.5.230.0.

What I find most disturbing is that outlook can bring down the Web Client and Web admin client.

I appreciate any help or troubleshooting/prevention advice.
Bug 19221 - Do not hold whole message in memory ?
Reply With Quote
  #3 (permalink)  
Old 09-12-2007, 12:22 PM
Senior Member
 
Posts: 72
Default So what could I do help make this a rare occurance??

Should I increase ram so it's harder to break java? Increase the heap-size?
Reply With Quote
  #4 (permalink)  
Old 09-12-2007, 12:37 PM
Moderator
 
Posts: 872
Default

Are you by chance using another server, besides your Zimbra server, as your SMTP server? We ran into a similar problem as you have described a while back, but we are using the Zimbra Web Client with the MTA pointed to another server. It turned out that there was a problem on this other server, and every time sometime tried to send a message Tomcat would crash, and I would see the same error messages that you are seeing.
Reply With Quote
  #5 (permalink)  
Old 09-12-2007, 02:34 PM
Senior Member
 
Posts: 72
Default

No. we are not setup like that.
Reply With Quote
  #6 (permalink)  
Old 09-12-2007, 02:41 PM
Former Zimbran
 
Posts: 5,606
Default

Quote:
Originally Posted by shankwc View Post
Should I increase ram so it's harder to break java? Increase the heap-size?
Is it still crashing? If not, I think we've done a lot of memory improvements in 4.5.7, you're best bet is to wait.

This also can happen if someone tries to send HUGE file. If it's still crashing, then can you remove the large file from the queue?
Reply With Quote
  #7 (permalink)  
Old 09-12-2007, 09:38 PM
Senior Member
 
Posts: 72
Default

I removed the file from the offending outlook outbox and the server has stablized. i'd like to try to prevent this from happening in the future. Shouldn't my 10M attachment limit prevent this?
Reply With Quote
  #8 (permalink)  
Old 09-12-2007, 09:45 PM
Former Zimbran
 
Posts: 5,606
Default

Quote:
Originally Posted by shankwc View Post
I removed the file from the offending outlook outbox and the server has stablized. i'd like to try to prevent this from happening in the future. Shouldn't my 10M attachment limit prevent this?
Totally depends on how much ram, and what the tomcat heap is. You can increase the heap size to prevent this from happening.

However, in 4.5.7 we've fixed this issue. So, it's up to you
Reply With Quote
  #9 (permalink)  
Old 09-13-2007, 09:44 AM
Moderator
 
Posts: 6,236
Default

Personally I would wait for all the other improvements-but if you we're curious:
zmlocalconfig | grep mem
Should spit out your tomcat_java_heap_memory_percent

if you wanted to change it - something like:
zmlocalconfig -e tomcat_java_heap_memory_percent=x
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.