My developers had a nice little script that took Email over imap, populated a database, then moved it to a /processed folder. That's fine for them, but it became a nightmare for me when it got to around 55 gig. I got approval to flush the folder but ....
root@mail:~# su - zimbra
zimbra@mail:~$ zmmailbox -z -m cthulhu@madness.edu emptyFolder /processed
ERROR: remote.TIMEOUT (https://mail.madness.edu:7071/service/admin/soap/) (cause: java.net.SocketTimeoutException Read timed out)
omg halp?
zmmailbox java.net.SocketTimeoutException Read timed out
-
- Posts: 8
- Joined: Sat Sep 13, 2014 12:02 am
-
- Posts: 8
- Joined: Sat Sep 13, 2014 12:02 am
zmmailbox java.net.SocketTimeoutException Read timed out
Anyone? Help?
-
- Posts: 8
- Joined: Sat Sep 13, 2014 12:02 am
zmmailbox java.net.SocketTimeoutException Read timed out
2009-04-29 16:48:59,746 FATAL [ImapServer-4] [] system - Fatal error occurred while handling connection
java.lang.OutOfMemoryError: Java heap space
at java.util.ArrayList.ensureCapacity(ArrayList.java:169)
at java.util.ArrayList.add(ArrayList.java:351)
at com.zimbra.cs.db.DbMailItem.loadImapFolder(DbMailItem.java:2428)
at com.zimbra.cs.mailbox.Mailbox.openImapFolder(Mailbox.java:2455)
at com.zimbra.cs.imap.ImapFolder.loadFolder(ImapFolder.java:184)
at com.zimbra.cs.imap.ImapFolder.register(ImapFolder.java:131)
at com.zimbra.cs.imap.ImapHandler.setSelectedFolder(ImapHandler.java:772)
at com.zimbra.cs.imap.ImapHandler.selectFolder(ImapHandler.java:1169)
at com.zimbra.cs.imap.ImapHandler.doSELECT(ImapHandler.java:1125)
at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:607)
at com.zimbra.cs.imap.TcpImapHandler.processCommand(TcpImapHandler.java:124)
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:595)
Release 5.0.15_GA_2851.UBUNTU8_64 UBUNTU8_64
java.lang.OutOfMemoryError: Java heap space
at java.util.ArrayList.ensureCapacity(ArrayList.java:169)
at java.util.ArrayList.add(ArrayList.java:351)
at com.zimbra.cs.db.DbMailItem.loadImapFolder(DbMailItem.java:2428)
at com.zimbra.cs.mailbox.Mailbox.openImapFolder(Mailbox.java:2455)
at com.zimbra.cs.imap.ImapFolder.loadFolder(ImapFolder.java:184)
at com.zimbra.cs.imap.ImapFolder.register(ImapFolder.java:131)
at com.zimbra.cs.imap.ImapHandler.setSelectedFolder(ImapHandler.java:772)
at com.zimbra.cs.imap.ImapHandler.selectFolder(ImapHandler.java:1169)
at com.zimbra.cs.imap.ImapHandler.doSELECT(ImapHandler.java:1125)
at com.zimbra.cs.imap.ImapHandler.executeRequest(ImapHandler.java:607)
at com.zimbra.cs.imap.TcpImapHandler.processCommand(TcpImapHandler.java:124)
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:595)
Release 5.0.15_GA_2851.UBUNTU8_64 UBUNTU8_64
zmmailbox java.net.SocketTimeoutException Read timed out
Just a quick thought... is IO or proc being hit?
I've noticed that when purging messages from the WebUI, some times it will time-out while it works. After a while, the process will complete and everything goes back to normal.
Cheers,
Dusty
I've noticed that when purging messages from the WebUI, some times it will time-out while it works. After a while, the process will complete and everything goes back to normal.
Cheers,
Dusty
zmmailbox java.net.SocketTimeoutException Read timed out
How much memory is in the server ?su - zimbra
zmlocalconfig mailboxd_java_heap_memory_percent
zmlocalconfig mailboxd_java_heap_memory_percent
zmmailbox java.net.SocketTimeoutException Read timed out
I'm seeing the same thing with a couple of users, but without the out of memory error. When I do a select mailbox from zmprov, it eventually times out with the same message. The user is also unable to login to the web client.