Results 1 to 10 of 10

Thread: Zimbra User Interface Goes Un-Responsive when Calendar Is Enabled

  1. #1
    Himanshu is offline Advanced Member
    Join Date
    Jan 2008
    Posts
    223
    Rep Power
    7

    Default Zimbra User Interface Goes Un-Responsive when Calendar Is Enabled

    As I enable Calendar feature The Web Interface Screen Goes Un-Responsive after Login. Can Some One Guide ?

  2. #2
    jjohnson is offline Zimbra Employee
    Join Date
    Feb 2011
    Location
    San Mateo, CA
    Posts
    75
    Rep Power
    4

    Default

    Quote Originally Posted by Himanshu View Post
    As I enable Calendar feature The Web Interface Screen Goes Un-Responsive after Login. Can Some One Guide ?
    Please provide more information, such as "version of Zimbra", "open source or network edition", "platform and browser being used", etc. as this will help immensely in narrowing issues like this.

  3. #3
    Himanshu is offline Advanced Member
    Join Date
    Jan 2008
    Posts
    223
    Rep Power
    7

    Default

    Release 8.0.7_GA_6021.RHEL6_64_20140408123911 RHEL6_64 FOSS edition
    Chrome Version 35.0.1916.114-->Does not respond.
    Mozilla Firefox 25.0.1--> Script Taking Time , Stop/Continue message and On stop can take operations . But as we Take cursor to Date Field
    of Mail it again Stucks and gets non-responsive.

  4. #4
    jjohnson is offline Zimbra Employee
    Join Date
    Feb 2011
    Location
    San Mateo, CA
    Posts
    75
    Rep Power
    4

    Default

    Quote Originally Posted by Himanshu View Post
    Release 8.0.7_GA_6021.RHEL6_64_20140408123911 RHEL6_64 FOSS edition
    Chrome Version 35.0.1916.114-->Does not respond.
    In Chrome, open Developer Tools and reload the login page so everything is clear, then login and watch the console display. There should be an error of some sort, at which point you can copy/paste the information here.

  5. #5
    Himanshu is offline Advanced Member
    Join Date
    Jan 2008
    Posts
    223
    Rep Power
    7

    Default

    The Error Looked Like following.

    GET https://mailserver.domainname.com/zi...v=140408125659 404 (Not Found) mail?adminPreAuth=1:50
    GET https://mailserver.Domainname.com/zi...v=140408125659 404 (Not Found) mail?adminPreAuth=1:50
    ------------------------------------- Loading package: MailCore mail?adminPreAuth=1:1553
    ------------------------------------- Loading package: Share mail?adminPreAuth=1:1553
    ------------------------------------- Loading package: Startup2 mail?adminPreAuth=1:1553
    ------------------------------------- Loading package: CalendarCore, Calendar mail?adminPreAuth=1:1553
    ------------------------------------- Loading package: Zimlet mail?adminPreAuth=1:1553
    ------------------------------------- Loading package: ContactsCore mail?adminPreAuth=1:1553
    ------------------------------------- Loading package: Contacts

    But Even when It loads after Disabling Calender Feature the Error is Displayed. On FireFx following gets Displayed.
    __________________________________________________ ___________________________________________
    "------------------------------------- Loading package: MailCore" mail:1552
    "------------------------------------- Loading package: Share" mail:1552
    "------------------------------------- Loading package: Startup2" mail:1552
    "------------------------------------- Loading package: CalendarCore, Calendar" mail:1552
    "------------------------------------- Loading package: Zimlet" mail:1552
    "------------------------------------- Loading package: ContactsCore" mail:1552
    "------------------------------------- Loading package: Contacts" mail:1552
    Error: Script terminated by timeout at:
    AjxUtil.createProxy@https://mailserv...1_1_all.js.zgz?v=140408125659:379:1
    ZmAppt.quickClone@https://mailserver.domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:4321:1
    ZmApptList._fanout@https://mailserver.domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5405:1
    ZmApptList.toVector@https://mailserver.domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5378:1
    ZmApptCache.prototype.processSearchR...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:6056:1
    ZmApptCache.prototype._getApptSummar...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5946:1
    AjxCallback.prototype.run@https://ma...domainname.com/zimbra/mail?adminPreAuth=1:855:1
    ZmRequestMgr.prototype._handleRespon...1_2_all.js.zgz?v=140408125659:22127:1
    AjxCallback.prototype.run@https://ma...domainname.com/zimbra/mail?adminPreAuth=1:855:1
    ZmCsfeCommand.prototype._runCallback...1_1_all.js.zgz?v=140408125659:21880:1
    AjxCallback.prototype.run@https://ma...domainname.com/zimbra/mail?adminPreAuth=1:855:1
    AjxRpcRequest.__handleResponse@https...1_1_all.js.zgz?v=140408125659:1232:1
    AjxRpcRequest.prototype.invoke/this.__httpReq.onreadystatechange@https://mailserver.domainname.com/zimbra/js/Startup1_1_all.js.zgz?v=140408125659:1175:1
    AjxRpcRequest.prototype.invoke@https...1_1_all.js.zgz?v=140408125659:1186:1
    AjxRpc.invoke@https://mailserver.dom...1_1_all.js.zgz?v=140408125659:1277:1
    ZmMailMsgView.prototype._displayCont...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:6034:1
    ZmMailMsgView.prototype._renderMessa...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:6456:39
    Function.prototype.run@https://mails...domainname.com/zimbra/mail?adminPreAuth=1:820:1
    ZmMailMsg.prototype.getBodyPart@http...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:1136:1
    ZmMailMsgView.prototype._renderMessa...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:6402:1
    Function.prototype.run@https://mails...domainname.com/zimbra/mail?adminPreAuth=1:820:1
    ZmMailMsg.prototype.load@https://mai...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:1050:1
    ZmMailMsgCapsuleView.prototype._rend...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:9531:1
    ZmMailMsgCapsuleView.prototype._hand...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:9459:1
    ZmMailMsgCapsuleView.prototype._rend...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:9450:1
    ZmMailMsgCapsuleView.prototype._rend...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:9430:1
    ZmMailMsgView.prototype.set@https://...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5472:1
    ZmMailMsgCapsuleView.prototype.set@h...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:9376:1
    ZmConvView2.prototype._renderMessage...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:8690:1
    ZmConvView2.prototype._renderMessage...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:8675:1
    ZmConvView2.prototype._renderConv@ht...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:8622:1
    ZmConvView2.prototype.set@https://ma...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:8571:1
    ZmDoublePaneView.prototype.setItem@h...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:4591:1
    ZmConvDoublePaneView.prototype.setIt...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:7623:1
    ZmConvListController.prototype._disp...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:13438:1
    ZmConvListController.prototype._hand...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:13367:1
    Function.prototype.run@https://mails...domainname.com/zimbra/mail?adminPreAuth=1:820:1
    ZmConv.prototype._handleResponseLoad...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:197:1
    AjxCallback.prototype.run@https://ma...domainname.com/zimbra/mail?adminPreAuth=1:855:1
    ZmSearch.prototype._handleResponseGe...1_2_all.js.zgz?v=140408125659:5627:1
    ZmRequestMgr.prototype._handleRespon...1_2_all.js.zgz?v=140408125659:22127:1
    AjxCallback.prototype.run@https://ma...domainname.com/zimbra/mail?adminPreAuth=1:855:1
    ZmCsfeCommand.prototype._runCallback...1_1_all.js.zgz?v=140408125659:21880:1
    AjxCallback.prototype.run@https://ma...domainname.com/zimbra/mail?adminPreAuth=1:855:1
    AjxRpcRequest.__handleResponse@https...1_1_all.js.zgz?v=140408125659:1232:1
    AjxRpcRequest.prototype.invoke/this.__httpReq.onreadystatechange@https://mailserver.domainname.com/zimbra/js/Startup1_1_all.js.zgz?v=140408125659:1175:1
    Startup1_1_all.js.zgz:379
    "------------------------------------- Loading package: PreferencesCore, Preferences" mail:1552
    "------------------------------------- Loading package: Mail" mail:1552
    Error: Script terminated by timeout at:
    AjxUtil.createProxy@https://mailserv...1_1_all.js.zgz?v=140408125659:379:1
    ZmAppt.quickClone@https://mailserver.domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:4323:1
    ZmApptList._fanout@https://mailserver.domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5405:1
    ZmApptList.toVector@https://mailserver.domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5378:1
    ZmApptCache.prototype.processSearchR...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:6056:1
    ZmApptCache.prototype.processBatchRe...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5803:1
    ZmApptCache.prototype.handleBatchRes...domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5903:1
    AjxCallback.prototype.run@https://ma...domainname.com/zimbra/mail?adminPreAuth=1:855:1
    ZmRequestMgr.prototype._handleRespon...1_2_all.js.zgz?v=140408125659:22127:1
    AjxCallback.prototype.run@https://ma...domainname.com/zimbra/mail?adminPreAuth=1:855:1
    ZmCsfeCommand.prototype._runCallback...1_1_all.js.zgz?v=140408125659:21880:1
    AjxCallback.prototype.run@https://ma...domainname.com/zimbra/mail?adminPreAuth=1:855:1
    AjxRpcRequest.__handleResponse@https...1_1_all.js.zgz?v=140408125659:1232:1
    AjxRpcRequest.prototype.invoke/this.__httpReq.onreadystatechange@https://mailserver.domainname.com/zimbra/js/Startup1_1_all.js.zgz?v=140408125659:1175:1
    Startup1_1_all.js.zgz:379
    Last edited by Himanshu; 06-18-2014 at 11:48 AM.

  6. #6
    jjohnson is offline Zimbra Employee
    Join Date
    Feb 2011
    Location
    San Mateo, CA
    Posts
    75
    Rep Power
    4

    Default

    I passed this along to one of our developers. Here's his feedback:

    From what I can see of the partial function names in the trace where its timing out, it looks like the display of the first message (invite?) triggers a GetApptSummary. The only way I've seen something like that wedge the UI is when the user has specified a recurring appt (say daily) that they set the duration of the daily appt to be the date range where it applies, instead of the duration during the day.

    To clarify, they may have created a daily recurring appt, and set the duration from something like June 1 2014 - December 31 2014, instead of setting the duration to be 2PM-3PM daily. The last couple of lines of the trace are:

    AjxUtil.createProxy@https://mailserv...1_1_all.js.zgz?v=140408125659:379:1
    ZmAppt.quickClone@https://mailserver.domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:4323:1
    ZmApptList._fanout@https://mailserver.domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5405:1
    ZmApptList.toVector@https://mailserver.domainname.com/zimbra/mail?adminPreAuth=1 line 1061 > eval:5378:1

    And fanout is where the UI will try break apart the (for example) June1-Dec31 appt into 200 some odd daily instances, and do so for every actual daily recurrence returned by the server - so we may get something like several thousand instances (200 per real daily recurrence), which kills the UI.

    Maybe use the HTML client to view the Calendar entries? If its something like is described above, deleting the appt should fix the problem. Like I mentioned, that's the only case in 8.0 where I know of something that wedges the Calendar UI.
    So I'd suggest logging into the account with the HTML client and checking the calendar to see if there's anything weird looking there.

  7. #7
    Himanshu is offline Advanced Member
    Join Date
    Jan 2008
    Posts
    223
    Rep Power
    7

    Default

    Checked , and Found working Ok with HTML Client.

  8. #8
    jjohnson is offline Zimbra Employee
    Join Date
    Feb 2011
    Location
    San Mateo, CA
    Posts
    75
    Rep Power
    4

    Default

    Quote Originally Posted by Himanshu View Post
    Checked , and Found working Ok with HTML Client.
    Does that mean you found a problematic calendar entry while logged into the HTML client and all is working, or just that the HTML client was working?

  9. #9
    Himanshu is offline Advanced Member
    Join Date
    Jan 2008
    Posts
    223
    Rep Power
    7

    Default

    in Ajax Issue there . But in HTML no issue.

  10. #10
    jjohnson is offline Zimbra Employee
    Join Date
    Feb 2011
    Location
    San Mateo, CA
    Posts
    75
    Rep Power
    4

    Default

    Quote Originally Posted by Himanshu View Post
    in Ajax Issue there . But in HTML no issue.
    And you didn't see any calendar items in HTML that could be problematic? Ex. A calendar appointment with a duration longer than the occurrence period, like a week long appointment occurring daily for a year.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 3
    Last Post: 01-18-2012, 10:20 PM
  2. Replies: 0
    Last Post: 01-09-2012, 08:52 PM
  3. LMTP server closing connection - system non-responsive
    By karol@uri.edu in forum Administrators
    Replies: 13
    Last Post: 10-11-2011, 06:19 AM
  4. how to login zimbra user interface
    By chandu in forum Administrators
    Replies: 3
    Last Post: 12-31-2007, 07:30 AM
  5. [SOLVED] Using Zimbra User Interface
    By RidwanNizam in forum Developers
    Replies: 1
    Last Post: 08-21-2007, 03:19 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •