Quote:
Originally Posted by ekaftan  Interesting... I am having the same problem with one machine...
I'll try to get more info and report. In this case, machine runs out of network ports and fill up with CLOSE_WAIT on pop3 port. |
A hangup just happened before my eyes.
First, a los of there starting to appear:
2007-06-25 18:52:59,496 WARN [LmtpServer-32] [name=losangeles@recaudadora.cl;]
sqltrace - Connection pool is 75% utilized. 10 connections out of a maximum of
10 in use. Turn on debug logging for zimbra.sqltrace to see stack traces of con
nections not returned to the pool.
First with 8, then 9, then 10 connections.
Then two or three of these:
2007-06-25 18:51:02,288 INFO [Pop3Server-13] [] ProtocolHandler - Exception occ
urred while handling connection
java.net.SocketException: Connection reset
at java.net.SocketOutputStream.socketWrite(SocketOutp utStream.java:96)
at java.net.SocketOutputStream.write(SocketOutputStre am.java:136)
at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65
)
at java.io.BufferedOutputStream.write(BufferedOutputS tream.java:78)
at com.zimbra.cs.pop3.Pop3Handler.sendMessage(Pop3Han dler.java:429)
at com.zimbra.cs.pop3.Pop3Handler.doRETR(Pop3Handler. java:625)
at com.zimbra.cs.pop3.Pop3Handler.processCommandInter nal(Pop3Handler.jav
a:257)
at com.zimbra.cs.pop3.Pop3Handler.processCommand(Pop3 Handler.java:141)
at com.zimbra.cs.tcpserver.ProtocolHandler.processCon nection(ProtocolHan
dler.java:231)
at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:198)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown So
urce)
at java.lang.Thread.run(Thread.java:595)
After that, only this messages:
2007-06-25 18:53:03,654 INFO [Pop3Server-1669] [] pop - connected
2007-06-25 18:53:08,016 INFO [Pop3Server-1670] [] pop - connected
2007-06-25 18:53:10,027 INFO [Pop3Server-1671] [] pop - connected
Then, huge amounts of pop3 ports in CLOSE_WAIT state and no more service until
a tomcat reboot...
Any ideas?