Today we had new crash on zimbra server after backup procedure. I didn't found the same error on
/opt/zimbra/db/data/hostname.err
Code:
100219 1:00:16 InnoDB: Starting shutdown...
100219 1:00:20 InnoDB: Shutdown completed; log sequence number 1 488376754
100219 1:00:20 [Note] /opt/zimbra/mysql/libexec/mysqld: Shutdown complete
100219 01:00:20 mysqld ended
100219 02:10:35 mysqld started
100219 2:10:40 InnoDB: Started; log sequence number 1 488376754
100219 2:10:40 [Note] /opt/zimbra/mysql/libexec/mysqld: ready for connections.
Version: '5.0.51a-log' socket: '/opt/zimbra/db/mysql.sock' port: 7306 Source distribution
But i see this on /opt/zimbra/log/zmmailboxd.out
Code:
2010-02-18 01:00:09
Full thread dump Java HotSpot(TM) 64-Bit Server VM (10.0-b19 mixed mode):
"Pop3Server-3884" prio=10 tid=0x00002aabdad99000 nid=0x6e76 runnable [0x0000000042c7c000..0x0000000042c7ce20]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
- locked <0x00002aab9dd18b60> (a com.zimbra.cs.tcpserver.TcpServerInputStream)
at com.zimbra.cs.tcpserver.TcpServerInputStream.readLine(TcpServerInputStream.java:73)
at com.zimbra.cs.pop3.TcpPop3Handler.processCommand(TcpPop3Handler.java:48)
at com.zimbra.cs.tcpserver.ProtocolHandler.processConnection(ProtocolHandler.java:160)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:128)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)
"btpool0-462" prio=10 tid=0x00002aabd7be5400 nid=0x6e6e in Object.wait() [0x0000000043190000..0x0000000043190aa0]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00002aab9db9b640> (a org.mortbay.thread.BoundedThreadPool$PoolThread)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:482)
- locked <0x00002aab9db9b640> (a org.mortbay.thread.BoundedThreadPool$PoolThread)
"ImapServer-5312" prio=10 tid=0x00002aabd834ec00 nid=0x455d runnable [0x0000000041d81000..0x0000000041d81ba0]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293)
at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:789)
- locked <0x00002aab86f99c28> (a java.lang.Object)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:746)
at com.sun.net.ssl.internal.ssl.AppInputStream.read(AppInputStream.java:75)
- locked <0x00002aab86f99cf0> (a com.sun.net.ssl.internal.ssl.AppInputStream)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
- locked <0x00002aab86fc1490> (a com.zimbra.cs.tcpserver.TcpServerInputStream)
at com.zimbra.cs.tcpserver.TcpServerInputStream.readLine(TcpServerInputStream.java:73)
at com.zimbra.cs.imap.TcpImapRequest.continuation(TcpImapRequest.java:54)
at com.zimbra.cs.imap.TcpImapHandler.processCommand(TcpImapHandler.java:107)
at com.zimbra.cs.tcpserver.ProtocolHandler.processConnection(ProtocolHandler.java:160)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:128)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)
........................
"Reference Handler" daemon prio=10 tid=0x00002aabd75e7400 nid=0x2dfb in Object.wait() [0x0000000040089000..0x0000000040089da0]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00002aaab65400e0> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:485)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0x00002aaab65400e0> (a java.lang.ref.Reference$Lock)
"VM Thread" prio=10 tid=0x00002aabd75e5000 nid=0x2dfa runnable
"GC task thread#0 (ParallelGC)" prio=10 tid=0x000000004011d400 nid=0x2df6 runnable
"GC task thread#1 (ParallelGC)" prio=10 tid=0x000000004011e800 nid=0x2df7 runnable
"GC task thread#2 (ParallelGC)" prio=10 tid=0x000000004011fc00 nid=0x2df8 runnable
"GC task thread#3 (ParallelGC)" prio=10 tid=0x0000000040121000 nid=0x2df9 runnable
"VM Periodic Task Thread" prio=10 tid=0x00002aabd77cc000 nid=0x2e0d waiting on condition
JNI global references: 1217
Heap
PSYoungGen total 1336000K, used 691191K [0x00002aab76540000, 0x00002aabcd590000, 0x00002aabd6540000)
eden space 1292544K, 50% used [0x00002aab76540000,0x00002aab9ddd7658,0x00002aabc5380000)
from space 43456K, 99% used [0x00002aabc5380000,0x00002aabc7de66c8,0x00002aabc7df0000)
to space 69312K, 0% used [0x00002aabc91e0000,0x00002aabc91e0000,0x00002aabcd590000)
PSOldGen total 2851520K, used 700923K [0x00002aaab6540000, 0x00002aab645f0000, 0x00002aab76540000)
object space 2851520K, 24% used [0x00002aaab6540000,0x00002aaae11becf0,0x00002aab645f0000)
PSPermGen total 49856K, used 49765K [0x00002aaaae540000, 0x00002aaab15f0000, 0x00002aaab6540000)
object space 49856K, 99% used [0x00002aaaae540000,0x00002aaab15d95a8,0x00002aaab15f0000)
What does it mean??Some advice?
Thanks!
LinkBack URL
About LinkBacks
Server connection failure during transaction
Is it a specific issue??
Originally Posted by samesisa 
