View Single Post
  #14 (permalink)  
Old 12-10-2005, 03:36 PM
adobrin adobrin is offline
Special Member
 
Posts: 135
Default anything?

well. this user stopped complaining a few days ago, and then we tried the Outlook Connector for him; everything seems to be working smoothly on his machine.

In an unfortuante turn of events, it appears that I am having a similar problem now. I recently switched from Blackberry to Treo, and tried using ChatterMail (as i read in another post); and shortly after doing that got the same symptoms as he was having.

Chattermail became unable to login to the server; and after getting home, my web client hangs on login like his did.

If i had to guess, it seems like this is related to persistent IMAP connections; as Chatter and (i'm guessing) Outlook IMAP keep the connection open for extended periods of time. (of course, just a guess.)

Anyway.. reading in the logs (/opt/zimbra/zimbra.log) it appears that the problem is related to :

Code:
2005-12-10 12:24:18,227 INFO  [Convertd-369] [] ProtocolHandler - Exception occurred while handling connection
java.nio.channels.AsynchronousCloseException
        at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:185)
        at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236)
        at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:171)
        at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:86)
        at java.io.InputStream.read(InputStream.java:89)
        at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:64)
        at java.io.FilterInputStream.read(FilterInputStream.java:66)
        at com.zimbra.cs.convertd.TransformationHandler.processCommand(TransformationHandler.java:95)
        at com.zimbra.cs.tcpserver.ProtocolHandler.processConnection(ProtocolHandler.java:230)
        at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:197)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:595)
restarting tomcat has fixed the problem for now.
Reply With Quote