one user unable to use zimbra
I know this defies logic.
I have a single user that gets unbelievably long hang times using zimbra. The web interface locks up probably once an hour, for a good half hour at a time. He is getting the "server unavailable" dialog after its fuzzy white for a few minutes.
He is normally an outlook user, but outlook also hangs, and eventually decides it just doesnt want to connnect to the server. One of the errors it returns is "cannot open IMAP folder (null)".
Lots of other users.. nobody having this problem. It doesn't look like there is anything odd happening in the log files. He connects, it issues GetMsgRequest and GetInfoRequest.. and thats it. Hung. If you reload the web client, it shows the "loading" screen with the status bar, for about 12 - 15 minutes. Each time.
Immediately after stopping and restarting tomcat, he can login fine.
This problem is unrelated to his machine, as the problem persists across the network.
Some background, he has lots of mail, but not more than other uses, and just imported about 1000 contacts; i thought it may have been something related to the contacts, so i just deleted them from the database... and still nothing.
Code:
2005-12-01 18:09:00,000 DEBUG [http-443-Processor96] [ip=71.0.0.444;name=ivan@somedomain.com;] SoapEngine - dispatch: doc NoOpRequest
2005-12-01 18:09:04,908 DEBUG [http-80-Processor92] [ip=71.0.0.444;name=ivan@somedomain.com;] SoapEngine - dispatch: doc GetInfoRequest
2005-12-01 18:09:29,030 INFO [IndexWritersSweeper] [] MailboxIndex - open index writers sweep: before=3, closed=0, after=3 (0ms)
modified original thread.
i get the same results (with his account) on my machine.
Req_2 and Req_3 are timing out
maybe i can set a post count record.
the web client just loaded.. here's the results in the debug window:
Code:
Branch: main
Async RPC request: ready state = 2
Async RPC request: ready state = 3
Async RPC request: ready state = 3
Async RPC request: ready state = 4
Async RPC request: HTTP status = 200
ROUND TRIP TIME: 321541
RESPONSE (asynchronous)
round trip time is *awful* high.. right? :)
then we get a getInfoRequest reply.. with what looks like info for each of his folders.. and preferences... then:
Code:
Handling REFRESH
overview layout needed (refresh)
tags: / 1
folders: / 1[2,3,4,5,6,262[263,276,417,420,613,865,868,892,904,911,987,1109,2502,2503,2513,2779,2783,2794,2819,2832,3077,3316,3632,3735,3833,3918,5263,5410,5661,6093,6870,7038],3961,5004,9519]
Creating app calendar
*** Unrecognized setting: zimbraPrefCalendarNotifyDelegatedChanges
*** Unrecognized setting: zimbraPrefImapSearchFoldersEnabled
*** Unrecognized setting: zimbraMailAlias
*** Unrecognized setting: zimbraMailAlias
*** Unrecognized setting: zimbraMailAlias
*** Unrecognized setting: zimbraMailAlias
Creating app contacts
***** sendRequest: GetContactsRequest
ZmZimbraMail.sendRequest: timeout for Req_2 is 60000
then
Code:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Header>
<context xmlns="urn:zimbra">
<sessionId id="2354"/>
<change token="14041" type="new"/>
<authToken>
0_7aa95c27e49619c9e6f6e08a3fd89ad044da9d14_69643d33363a61333430313564662d333633612d313164612d393361352d6566616133343566646461393b6578703d31333a313133343036303737353532353b
</authToken>
<format type="js"/>
</context>
</soap:Header>
<soap:Body>
<GetContactsRequest xmlns="urn:zimbraMail"/>
</soap:Body>
</soap:Envelope>
with response:
Code:
Created RPC _rpcCtxt_1
Async RPC request
Async RPC request: Add header Content-Type - application/soap+xml; charset=utf-8
Async RPC request: ready state = 1
poll interval = 18000000ms
laying out overview panel
fitting to container: SASH
fitting to container: USER INFO
fitting to container: CURRENT APP
fitting to container: STATUS
fitting to container: TREE
fitting to container: SEARCH
fitting to container: APP CHOOSER
Container bounds for SASH: 214, 76 | 3 x 642
Container bounds for BANNER: 4, 6 | 210 x 32
Container bounds for USER INFO: 736, 6 | 180 x 32
Container bounds for CURRENT APP: 14, 47 | 187 x 24
Container bounds for STATUS: 14, 682 | 187 x 30
Container bounds for TREE: 51, 87 | 160 x 575
Container bounds for SEARCH: 224, 9 | 482 x 25
Container bounds for APP CHOOSER: 4, 77 | 40 x 595
activateApp: mail, current app = null
Creating app mail
Launching app mail
***** sendRequest: SearchRequest
ZmZimbraMail.sendRequest: timeout for Req_3 is 60000