Last saturday we upgraded our Zimbra NE from 5.0.22 to 5.0.23
Everything OK, as usually.

However, yesterdate (monday) we suffered two unexpected hangs of zmmaiboxd. No response from http/https/imap/imaps/pop server. So we had to restart zmmailboxd. Twice yesterday (on morning and afternoon) and twice this morning in a 30 minutes period.

We have opened a support ticket, but since we are at Europe, I'm posting here in order to check if somebody has experienced same problems and there is an easy fix for this.

JVM dump shows all threads are OK but one:
Exception in thread "btpool0-76" java.lang.IllegalStateException: Internal error
at com.sun.net.ssl.internal.ssl.SSLEngineImpl.initHan dshaker(SSLEngineImpl.java:397)
at com.sun.net.ssl.internal.ssl.SSLEngineImpl.readRec ord(SSLEngineImpl.java:909)
at com.sun.net.ssl.internal.ssl.SSLEngineImpl.readNet Record(SSLEngineImpl.java:787)
at com.sun.net.ssl.internal.ssl.SSLEngineImpl.unwrap( SSLEngineImpl.java:663)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:566)
at org.mortbay.jetty.security.SslHttpChannelEndPoint. unwrap(SslHttpChannelEndPoint.java:601)
at org.mortbay.jetty.security.SslHttpChannelEndPoint. close(SslHttpChannelEndPoint.java:193)
at org.mortbay.io.nio.SelectChannelEndPoint.idleExpir ed(SelectChannelEndPoint.java:174)
at org.mortbay.jetty.security.SslHttpChannelEndPoint. doIdleExpired(SslHttpChannelEndPoint.java:144)
at org.mortbay.jetty.security.SslHttpChannelEndPoint$ 1.run(SslHttpChannelEndPoint.java:131)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
CompilerOracle: exclude com/zimbra/cs/session/SessionMap putAndPrune