MTA and Mailbox dies because of tomcat

[meikka]

Hi

I hope that someone could advise where find the cause of the tomcat dead.

I have build several systems and in most of them the MTA and Mailbox stop after a while. My assumption is that this happens, because the autentication fails because there is no respose from tomcat soap.

Here is the tail of the catalina.out

"Timer-0" daemon prio=1 tid=0x08e0e3f0 nid=0xe28 in Object.wait() [0x9ce69000..0x9ce69fc0]
at java.lang.Object.wait(Native Method)
- waiting on <0xa3b58098> (a java.util.TaskQueue)
at java.util.TimerThread.mainLoop(Timer.java:509)
- locked <0xa3b58098> (a java.util.TaskQueue)
at java.util.TimerThread.run(Timer.java:462)

"Low Memory Detector" daemon prio=1 tid=0x08750e28 nid=0xdb3 runnable [0x00000000..0x00000000]

"CompilerThread0" daemon prio=1 tid=0x0874f890 nid=0xdb0 waiting on condition [0x00000000..0x9dccb828]

"Signal Dispatcher" daemon prio=1 tid=0x0874ea48 nid=0xdaf runnable [0x00000000..0x00000000]

"Finalizer" daemon prio=1 tid=0x08744610 nid=0xda5 in Object.wait() [0x9ddcd000..0x9ddce140]
at java.lang.Object.wait(Native Method)
- waiting on <0xa37f0768> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue .java:116)
- locked <0xa37f0768> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue .java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finali zer.java:159)

"Reference Handler" daemon prio=1 tid=0x08743928 nid=0xda4 in Object.wait() [0x9de4e000..0x9de4f0c0]
at java.lang.Object.wait(Native Method)
- waiting on <0xa37f0690> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Refer ence.java:116)
- locked <0xa37f0690> (a java.lang.ref.Reference$Lock)

"main" prio=1 tid=0x086e6ee0 nid=0xd8b runnable [0xbf82e000..0xbf82f6e8]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.ja va:384)
- locked <0xa3d6aee8> (a java.net.SocksSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java :450)
at java.net.ServerSocket.accept(ServerSocket.java:421 )
at org.apache.catalina.core.StandardServer.await(Stan dardServer.java:362)
at org.apache.catalina.startup.Catalina.await(Catalin a.java:600)
at org.apache.catalina.startup.Catalina.start(Catalin a.java:560)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootst rap.java:271)
at org.apache.catalina.startup.Bootstrap.main(Bootstr ap.java:409)

"VM Thread" prio=1 tid=0x08740cc0 nid=0xda3 runnable

"VM Periodic Task Thread" prio=1 tid=0x08752300 nid=0xdb8 waiting on condition

Feb 26, 2006 7:25:46 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-80
Feb 26, 2006 7:25:46 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-7071
Feb 26, 2006 7:25:47 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Feb 26, 2006 7:25:48 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-80
Feb 26, 2006 7:25:48 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-7071


-- Timo

[KevinH]

What are the specs of you server? Is it a virtual machine? How much CPU RAM? What's the number of users and load on the system? How frequently does this happen? Web UI users? Imap? POP?

[meikka]

Hi

The machine in XEN vm in FC4 2.6.11 xenU-kernel. Memory have been tested with 512/738/1024 MB. Only 4 users.

-- Timo

[meikka]

Few answers more.

Only web ui. Currently it happens in 4-8 h.

-- Timo

[KevinH]

Problem is XEN. It's not a good idea to run anything other than a demo/test system on a VM. They just don't give you the same horse power and no where near the stability. I can assure you this problem doesn't happen on a well configured standard install.

Or in the words of Marc...

'The fix for that is on the Red Hat install CD'.

[meikka]

Hi

I can agree that Zimbra cannot run in XEN, but the Virtual machines will be the future.

We are running most of our company services in VM environment, because it gives so much freedom in administration. It is easy to test updates, easy to take system backups, easy to size the services, easy ...

I really hope that we can run Zimbra in Xen, because VM will be our platform.

-- Timo

[marcmac]

Runs fine in vmware - the problem is XEN, not virtual machines in general

[rodrigoccurvo]

We ran a lot of versions of Zimbra in XEN (both Zimbra binary and source) and with a lot of different uses, and it works quite well. We had some few misc problems, but nothing too bad.

[]'s

Rodrigo