#1 (permalink) 03-03-2008, 10:24 AM MySQL error, seems to be one specific mailbox Hi,
Windows 7 Keygen, I'm running 5.0.2 Open Source edition on Debian. Since last night, my mailbox keeps dying,
Office 2010 Update Key, and looking from the logs,
Office Standard 2007 Keygen, it's always due to some MySQL error, pertaining to one mailbox. How do I find out which account points to which mailbox number, and also,
Office Professional Plus 2007 Keygen, how do I fix something like this? Code: 2008-03-03 08:47:54,182 INFO [ImapServer-21] [] imap - [192.168.50.90] connected
2008-03-03 08:48:02,246 INFO [ImapServer-21] [ip=192.168.50.90;] MailboxIndex - Initialized Index for mailbox 18 directory: LuceneIndex at org.apa
che.lucene.store.FSDirectory@optzimbraindex018inde x0 Analyzer=com.zimbra.cs.index.ZimbraAnalyzer@21447f
2008-03-03 08:48:02,
Office Professional Plus 2010 Serial Key,246 INFO [ImapServer-21] [ip=192.168.50.90;] cache - Initializing folder and tag caches for mailbox 18
2008-03-03 08:48:02,548 FATAL [ImapServer-21] [ip=192.168.50.90;] mailbox - Unable to commit database transaction. Forcing server to abort.
com.zimbra.common.service.ServiceException: system failure: committing database transaction
Code:service.FAILURE at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:183) at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.j ava:144) at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailb ox.java:5734) at com.zimbra.cs.mailbox.Mailbox.getConfig(Mailbox.ja va:1125) at com.zimbra.cs.mailbox.Mailbox.finishInitialization (Mailbox.java:460) at com.zimbra.cs.mailbox.MailboxManager.getMailboxByI d(MailboxManager.java:406) at com.zimbra.cs.mailbox.MailboxManager.getMailboxByA ccountId(MailboxManager.java:265) at com.zimbra.cs.mailbox.MailboxManager.getMailboxByA ccountId(MailboxManager.java:218) at com.zimbra.cs.imap.ImapCredentials.getMailbox(Imap Credentials.java:99) at com.zimbra.cs.imap.ImapHandler.startSession(ImapHa ndler.java:1054) at com.zimbra.cs.imap.ImapHandler.authenticate(ImapHa ndler.java:1019) at com.zimbra.cs.imap.ImapAuthenticatorUser.authentic ate(ImapAuthenticatorUser.java:62) at com.zimbra.cs.security.sasl.Authenticator.authenti cate(Authenticator.java:104) at com.zimbra.cs.security.sasl.PlainAuthenticator.han dle(PlainAuthenticator.java:63) at com.zimbra.cs.imap.ImapHandler.continueAuthenticat ion(ImapHandler.java:204) at com.zimbra.cs.imap.ImapHandler.continueAuthenticat ion(ImapHandler.java:195) at com.zimbra.cs.imap.TcpImapHandler.processCommand(T cpImapHandler.java:149) at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHandler.java:160) at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:128) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source) at java.lang.Thread.run(Thread.java:619)
Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnect ionException: Communications link failure during commit(). Transaction resolution unkn
own. at com.mysql.jdbc.SQLError.createSQLException(SQLErro r.java:888) at com.mysql.jdbc.Connection.commit(Connection.java:2 246) at org.apache.commons.dbcp.DelegatingConnection.commi t(DelegatingConnection.java:248) at org.apache.commons.dbcp.PoolingDataSource$PoolGuar dConnectionWrapper.commit(PoolingDataSource.java:2 44) at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.j ava:142) ... 19 more