zmlmtpinject not working

Whenever I tried to use zmlmtpinject to import some message into a mailbox, I get a failed message. Then zmcontrol status shows that mailbox service has been stopped.

Checking the zimbra.log file I see the following

tail -f zimbra.log
2005-10-15 06:06:48,529 FATAL [LmtpServer-1] [] system - Fatal error occurred while handling connection
java.lang.OutOfMemoryError: Java heap space

Right now the test machine I have zimbra installed on has 512 MB of RAM. I thought this meets the minimum requirement for zimbra. Please help.

tron

It just meets the minimum. So you can expect trouble on some operations. How big is the message your trying to inject? Do you have anything other than Zimbra running on the machine? Is the OS install a *minimal* install or are you running X and GUI apps locally?

Thanks for the response.
There is nothing else running other than Zimbra. Also, there is no X and GUI apps locally. It is a headless server set up just to test Zimbra.

Quote:

---

Originally Posted by KevinH

It just meets the minimum. So you can expect trouble on some operations. How big is the message your trying to inject? Do you have anything other than Zimbra running on the machine? Is the OS install a *minimal* install or are you running X and GUI apps locally?

---

what size is the message, and what is the -Xmx option for the VM (ps -ef | grep tomcat).

ps -ef | grep tomcat
zimbra 3879 1 0 14:40 ? 00:00:05 /opt/zimbra/java/bin/java -client -XX:NewRatio=2 -Xms148m -Xmx148m -Djava.library.path=/opt/zimbra/lib -Djava.endorsed.dirs=/opt/zimbra/tomcat/common/endorsed -classpath :/opt/zimbra/tomcat/bin/bootstrap.jar:/opt/zimbra/tomcat/bin/commons-logging-api.jar -Dcatalina.base=/opt/zimbra/tomcat -Dcatalina.home=/opt/zimbra/tomcat -Djava.io.tmpdir=/opt/zimbra/tomcat/temp org.apache.catalina.startup.Bootstrap start

The file contains 1500 messges. The total size of the file is 11 MB.

Quote:

---

Originally Posted by anand

what size is the message, and what is the -Xmx option for the VM (ps -ef | grep tomcat).

---

148M max heap size should be more than enough for small systems.

Note that zmlmtpinject will inject the whole file as one message. It does not understand mbox format - you will have to split into individual messages.

The default message size limit is also 10M, so even if it is treated as one big message, the message should be rejected by the LMTP code. I do not understand why an OOM manifested itself. Maybe message parsing code is going bananas?

Can you do this as the zimbra user:

Code:

---

$ tomcat stop
$ zmlocalconfig -e tomcat_java_options="-client -XX:NewRatio=2 -Xrunhprof:file=/tmp/hprof.txt"
$ tomcat start
$ zmlmtpinject ...

---

This will cause the JVM to run dog slow, but at the end of the run, the JVM should dump some heap info and we can see why the OOM was triggered.

Remeber to remove the -Xrunhprof:... option when you are done!

What else do the log files say? catalina.out, zimbra.log, etc? Anything interesting there?

I am attaching the three logs here for your viewing pleasure. Let me know if you need me to run any other tests. I tried just one message per file and it worked. Thank you.

Quote:

---

Originally Posted by anand

148M max heap size should be more than enough for small systems.

Note that zmlmtpinject will inject the whole file as one message. It does not understand mbox format - you will have to split into individual messages.

The default message size limit is also 10M, so even if it is treated as one big message, the message should be rejected by the LMTP code. I do not understand why an OOM manifested itself. Maybe message parsing code is going bananas?

Can you do this as the zimbra user:

Code:

---

$ tomcat stop
$ zmlocalconfig -e tomcat_java_options="-client -XX:NewRatio=2 -Xrunhprof:file=/tmp/hprof.txt"
$ tomcat start
$ zmlmtpinject ...

---

This will cause the JVM to run dog slow, but at the end of the run, the JVM should dump some heap info and we can see why the OOM was triggered.

Remeber to remove the -Xrunhprof:... option when you are done!

What else do the log files say? catalina.out, zimbra.log, etc? Anything interesting there?

---

:)