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 10-03-2011, 06:12 AM
Advanced Member
 
Posts: 214
Default java.lang.OutOfMemoryError: Java heap space

Hello again,


Im getting frequently the usual out of memory
java.lang.OutOfMemoryError: Java heap space
at java.lang.StringCoding$StringEncoder.encode(String Coding.java:232)
<------>at java.lang.StringCoding.encode(StringCoding.java:27 2)
<------>at java.lang.StringCoding.encode(StringCoding.java:28 4)
<------>at java.lang.String.getBytes(String.java:986)
<------>at com.zimbra.common.mime.shim.JavaMailInternetHeader s.setHeader(JavaMailInternetHeaders.java:138)
<------>at com.zimbra.common.mime.shim.JavaMailMimeBodyPart.s etHeader(JavaMailMimeBodyPart.java:671)
<------>at com.zimbra.cs.service.mail.ParseMimeMessage.attach Part(ParseMimeMessage.java:835)
<------>at com.zimbra.cs.service.mail.ParseMimeMessage.handle Attachments(ParseMimeMessage.java:476)
<------>at com.zimbra.cs.service.mail.ParseMimeMessage.parseM imeMsgSoap(ParseMimeMessage.java:369)
<------>at com.zimbra.cs.service.mail.ParseMimeMessage.parseM imeMsgSoap(ParseMimeMessage.java:205)
<------>at com.zimbra.cs.service.mail.SaveDraft.handle(SaveDr aft.java:96)
<------>at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:412)
<------>at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:287)
<------>at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158)
<------>at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:294)
<------>at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:215)
<------>at javax.servlet.http.HttpServlet.service(HttpServlet .java:725)
<------>at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208)
<------>at javax.servlet.http.HttpServlet.service(HttpServlet .java:814)
<------>at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
<------>at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
<------>at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79)
<------>at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
<------>at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
<------>at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
<------>at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157)
<------>at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
<------>at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218)
<------>at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
<------>at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
<------>at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422)
<------>at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230)


Obiviously its a scrambled message
ANd in the draft of the user im getting a 172mb message which is supposed to be 150k
Only a few PDF Attachments


So heres my question: is it possible that kida weird PDF can produce this error?

This is the only the user who can create this problem but it shutdown the hole server which is getting kinda problem - real problem.


So the real question is - anyway to prevent this?
Why isnt the mailboxservice restarting - isnt it supposed to be to restart if it fails?
Anyone else having similar issues ?


This zimbra server is the OSS 7.1.2
thanks in advance
Reply With Quote
  #2 (permalink)  
Old 10-03-2011, 08:12 AM
Special Member
 
Posts: 146
Default

Do you have swap space ?

Check your memory ussage in your OS.
__________________
# ZCS 7.1.3 SLES11 SP1
Reply With Quote
  #3 (permalink)  
Old 10-03-2011, 10:40 AM
Advanced Member
 
Posts: 214
Default

The Memmory is fine, swap is fine.
The Point is this user frequently scrambles his Mails.

A normal 50 Text line mail with 3 5k PDF attached grows up to 175MB - when you try to open this Mail server goes down.

I got a Messesage Limit of 50Meg so its not possible to make a 172meg Mail on purpose
Reply With Quote
  #4 (permalink)  
Old 10-03-2011, 10:56 AM
Special Member
 
Posts: 146
Default

I have several 7.x ZCS servers.

For example:
An environment with 4 core Intel (8 threads) - VMware (8CPU) and 32 GB RAM, and 3 k users have no problem - the size of the store up to 4TB. OS: UBUNTU LTS.
The amount of mail per hour - about 100-300

Use google: java.lang.OutOfMemoryError: Java heap space

check:> zmlocalconfig | grep zimbra_zmjava_options
__________________
# ZCS 7.1.3 SLES11 SP1

Last edited by soba@ukw.edu.pl; 10-03-2011 at 11:05 AM..
Reply With Quote
  #5 (permalink)  
Old 10-03-2011, 05:50 PM
Advanced Member
 
Posts: 214
Default

And again - its not really a memory Problem

The Problem is that somehow a Message get scrambled twice a week - always the same user.

The Scrambled Message result in a Memmory Leak - all thats left is that 172 Meg Mail but i got a good guess that once it opend it uses way more than this
Way way way more....


So the Solution cant be simply increase Memory - its More stopping Zimbra scrambling it.

Also the fakt that the zmmailbox Daemon simply stops and never get rehived is a very bad thing.

Maybe a Feature request - if a Message like this Occurs - Detain it or delete) and restart the Process and inform the User

But this wouldn be a Solution for the root of that Problem which is - why does a Message get scrambled and how can it be that even a Message without an Attachment get a size of 175 MB while there only a few lines Text

And is there someone else getting those Issues


Believe me i could make 128 Gig Ram and still no Solution - even worse he may be able to send it then which result in a 200 Meg Mail transfer to nowheres land
Reply With Quote
  #6 (permalink)  
Old 10-03-2011, 10:36 PM
Special Member
 
Posts: 146
Default

check:> zmlocalconfig | grep zimbra_zmjava_options

Please creeate a bug for it and put the affected message there.
__________________
# ZCS 7.1.3 SLES11 SP1
Reply With Quote
  #7 (permalink)  
Old 10-05-2011, 03:57 AM
Advanced Member
 
Posts: 214
Default

and again zmjava is fine i got xmx to 512 out of pure desperation
crahes there also with 256

and we dont know how big the scrambled message really gets - i have the suspiscion that it will grow endless as long memory is there

no other reason i can see that a 20kb message grows to 200megs

the real question are - so again -

1. Did anyone else have scrambled messages frequently
2. why doest the zmmailbox respawn after crash
3. anyway to prevent this
4. can it really a poor pdf creator bring down hole zimbra

BTW its not repoduceable - it jst happens from time to time but the exact same files uploaded later work fine
Reply With Quote
  #8 (permalink)  
Old 11-22-2011, 04:30 AM
Starter Member
 
Posts: 2
Default Face the same problem

Hello,
I'm a newbe user so ...forgive errors.
Zimbra in my company also faces the 'big emails - drafts problem'.
Open case in support and bugzilla. Some dumps are being analized. For now - no solution.
Reply With Quote
  #9 (permalink)  
Old 11-30-2011, 12:28 PM
Junior Member
 
Posts: 6
Default

Hi!

We saw this problem for the first time today.

Our mailboxd crashed 3 times today and everytime I got the:
"java.lang.OutOfMemoryError: Java heap space" in a fatal errormessage in regard to one user.

I found this thread and I looked in his draftsfolder and I found a message with a pdf atachment which it said was 10 kB but the message was reported by zimbra as 112 MB big.

I have removed the message and I hope we are in the clear for this time but I agree that it is a big problem since there is big consequences in the form that no emails are being delivered and noone can read or send email until we have restarted the mailboxd.
Reply With Quote
  #10 (permalink)  
Old 11-30-2011, 11:14 PM
Zimbra Consultant & Moderator
 
Posts: 20,315
Default

Quote:
Originally Posted by s00mar View Post
I found this thread and I looked in his draftsfolder and I found a message with a pdf atachment which it said was 10 kB but the message was reported by zimbra as 112 MB big.
I guess you've raised a support case for this (and supplied the original email, plus headers and attachment for evidence of the problem) or filed a bug report (after searching for this problem)?
__________________
Regards


Bill
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.