Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Add appointment failure

  1. #1
    yrosenbach Guest

    Question Add appointment failure

    Hello,

    I'm new to Zimbra.
    While adding an appointment on Zimbra 4.0.3 on RHEL 4, i get a network service error with the following report:

    msg - system failure: java.lang.IllegalArgumentException: Illegal end time 86400000
    com.zimbra.cs.service.ServiceException: system failure: java.lang.IllegalArgumentException: Illegal end time 86400000
    at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:272)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:162)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:173)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
    at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
    at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
    at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: java.lang.IllegalArgumentException: Illegal end time 86400000
    at java.util.SimpleTimeZone.decodeEndRule(SimpleTimeZ one.java:1406)
    at java.util.SimpleTimeZone.setEndRule(SimpleTimeZone .java:456)
    at com.zimbra.cs.mailbox.calendar.ICalTimeZone.(ICalTimeZone.java:477)
    at com.zimbra.cs.service.mail.CalendarUtils.parseTime Zones(CalendarUtils.java:574)
    at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teElementCommon(CalendarUtils.java:622)
    at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teForCreate(CalendarUtils.java:117)
    at com.zimbra.cs.service.mail.CreateAppointment$Creat eAppointmentInviteParser.parseInviteElement(Create Appointment.java:62)
    at com.zimbra.cs.service.mail.ParseMimeMessage$Invite Parser.parse(ParseMimeMessage.java:136)
    at com.zimbra.cs.service.mail.ParseMimeMessage.parseM imeMsgSoap(ParseMimeMessage.java:249)
    at com.zimbra.cs.service.mail.CalendarRequest.handleM sgElement(CalendarRequest.java:87)
    at com.zimbra.cs.service.mail.CreateAppointment.handl e(CreateAppointment.java:80)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:261)
    ... 21 more

    code - service.FAILURE
    method - ZmCsfeCommand.prototype.invoke
    detail - soap:Receiver


    An help will be highly appreciated.

    Thanks,
    Yariv

  2. #2
    jhahm is offline Zimbra Employee
    Join Date
    Sep 2005
    Posts
    57
    Rep Power
    9

    Default

    Hi, can you try again with the debug window up and cut/paste the CreateAppointmentRequest? You can bring up the debug window by going to this URL:

    http:///?mjsf=true&gzip=false&debug=1

    What is the timezone being used by the client machine?
    Bugzilla - Wiki - Downloads - Before posting... Search!

  3. #3
    yrosenbach Guest

    Default

    Hi,

    I have opened the debug window and tried to add an appointment.
    The debug window was kept empty.

    Additional information is that i could add an appointment from a web client executed on a linux box.

    The time zone of my windows box is: (GMT+2:00) Jerusalem

    Thanks,
    Yariv

  4. #4
    jhahm is offline Zimbra Employee
    Join Date
    Sep 2005
    Posts
    57
    Rep Power
    9

    Default

    Sorry, my previous post didn't show the correct URL because of HTML badness with angle brackets. The URL should be:

    http://HOSTNAME/?mjsf=true&gzip=false&debug=1

    The "?mjsf=true&gzip=false&debug=1" part is important. Without it the debug window won't work even if you bring it up.

    And did you change any timezone config in LDAP?

    I tried Jerusalem TZ on Windows client with 4.0.4 server and it worked for me.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  5. #5
    andyc is offline Zimbra Employee
    Join Date
    Oct 2005
    Location
    California
    Posts
    79
    Rep Power
    9

    Default

    Quote Originally Posted by jhahm View Post
    http://HOSTNAME/?mjsf=true&gzip=false&debug=1
    Actually, it's the following:

    http://HOSTNAME/?mode=mjsf&gzip=false&debug=1
    And you may need to even add the query string (i.e. the stuff after the question mark in the URL) to the /zimbra/mail URL and reload after you've authenticated. This is required because the the login page doesn't forward the query string to the mail URL.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  6. #6
    andyc is offline Zimbra Employee
    Join Date
    Oct 2005
    Location
    California
    Posts
    79
    Rep Power
    9

    Default Jerusalem Timezone

    From your message, I see that you are using the Jerusalem timezone. So I should probably say a few words about our current timezone support...

    On Windows, the timezone labeled "Jerusalem" doesn't use daylight savings time (DST). But from the information I've seen on the internet, Jerusalem really does obey DST. So there's a discrepancy already.

    Besides that, though, there's a reason why people whose machine's timezone is set to Jerusalem in Windows is seeing some other timezone name. The timezone information is equivalent, just the display name is different. And the reason why this happens is because of the browser run-time environment.

    Our client application is written in JavaScript running in the browser. And within that context, the program has no way of asking the browser for the user's timezone. So we have to guess. And we guess by having a list of known timezone information (which was taken from Windows) and then run a series of calculations to find the first entry in that list that matches the browser information that we do have. In this particular case, there is another entry in the list that matches the Jerusalem timezone information but appears before Jerusalem.

    So what can we do to fix this?

    Well, we could move Jerusalem in the list before the other equivalent entry. But then people in that timezone would complain that it auto-detects their timezone as "Jerusalem". Basically, you can't please everyone with this solution.

    The real solution is to allow the user to specify their default timezone in the user preferences. I have opened a request for enhancement to track this feature which can be viewed at the following URL.

    http://bugzilla.zimbra.com/show_bug.cgi?id=12580
    Bugzilla - Wiki - Downloads - Before posting... Search!

  7. #7
    yrosenbach Guest

    Default

    Hi,

    Thanks for the explanation.
    The following is the requested debug information:
    HTML Code:
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    <soap:Header>
    <context xmlns="urn:zimbra">
    <sessionId id="9"/>
    <change token="99" type="new"/>
    <authToken>
    0_9eab7ddadf7a5d82eda33b9cc2798e23c8115f53_69643d33363a34356536656132312d653961652d346531632d623332382d3838356662313132316162353b6578703d31333a313136343931393538323232303b61646d696e3d313a313b
    </authToken>
    <format type="js"/>
    </context>
    </soap:Header>
    <soap:Body>
    <CreateAppointmentRequest xmlns="urn:zimbraMail">
    <m d="1164876549790">
    <tz id="(GMT+02.00) Auto-Detected" stdoff="120" dayoff="180">
    <standard mon="10" mday="5" hour="24" min="0" sec="0"/>
    <daylight mon="4" mday="5" hour="1" min="0" sec="0"/>
    </tz>
    <inv method="REQUEST" type="event" fb="B" transp="O" status="CONF" allDay="0" name="test" loc="office">
    <s tz="(GMT+02.00) Auto-Detected" d="20061201T110000"/>
    <e tz="(GMT+02.00) Auto-Detected" d="20061201T120000"/>
    <or a="admin@leo21.devsphera.com"/>
    </inv>
    <mp ct="multipart/alternative">
    <mp ct="text/plain">
    <content>
    The following is a new meeting request: Subject: test Organizer: [email]admin@leo21.devsphera.com[/email] Location: office Time: Friday, December 1, 2006, 11:00:00 AM - 12:00:00 PM *~*~*~*~*~*~*~*~*~*
    </content>
    </mp>
    <mp ct="text/html">
    <content>
    <html><body><h3>The following is a new meeting request:</h3> <p> <table border='0'> <tr><th align=left>Subject:</th><td>test </td></tr> <tr><th align=left>Organizer:</th><td>admin@leo21.devsphera.com </td></tr> </table> <p> <table border='0'> <tr><th align=left>Location:</th><td>office </td></tr> <tr><th align=left>Time:</th><td>Friday, December 1, 2006, 11:00:00 AM - 12:00:00 PM </td></tr></table> <div>*~*~*~*~*~*~*~*~*~*</div></body></html>
    </content>
    </mp>
    </mp>
    <su>
    test
    </su>
    </m>
    </CreateAppointmentRequest>
    </soap:Body>
    </soap:Envelope>
    Thanks,
    Yariv
    Last edited by yrosenbach; 11-30-2006 at 02:11 AM.

  8. #8
    jhahm is offline Zimbra Employee
    Join Date
    Sep 2005
    Posts
    57
    Rep Power
    9

    Default

    It looks like the problem is the client's timezone detection code. In the < CreateAppointmentRequest >, the timezone block was specified like this:

    < tz id="(GMT+02.00) Auto-Detected" stdoff="120" dayoff="180" >
    < standard mon="10" mday="5" hour="24" min="0" sec="0"/ >
    < daylight mon="4" mday="5" hour="1" min="0" sec="0"/ >
    < /tz >
    Notice hour="24". That should have been hour="0", as there is no such time of day as 24:00:00. Can you file a bug? (http://bugzilla.zimbra.com/)
    Bugzilla - Wiki - Downloads - Before posting... Search!

  9. #9
    yrosenbach Guest

    Default bug 12623 was submitted

    Hi,

    I have submited a bug with all the details.

    Yariv

  10. #10
    jarbelix is offline Member
    Join Date
    Oct 2006
    Location
    Campo Grande - MS - Brasil
    Posts
    11
    Rep Power
    8

    Thumbs down I have the same error

    Quote Originally Posted by andyc View Post
    Actually, it's the following:
    And you may need to even add the query string (i.e. the stuff after the question mark in the URL) to the /zimbra/mail URL and reload after you've authenticated. This is required because the the login page doesn't forward the query string to the mail URL.
    My debug with append "?mode=mjsf&gzip=false&debug=1" in URL is:
    HTML Code:
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    <soap:Header>
    <context xmlns="urn:zimbra">
    <sessionId id="4"/>
    <change token="501" type="new"/>
    <authToken>
    0_3d9e751f1a115d74d81ca222f35e0d17a2a3dbeb_69643d33363a35353836666166322d616663642d346638302d613537632d3165353761343362383232313b6578703d31333a313136343934363332353036313b61646d696e3d313a313b
    </authToken>
    <format type="js"/>
    </context>
    </soap:Header>
    <soap:Body>
    <CreateAppointmentRequest xmlns="urn:zimbraMail">
    <m d="1164902922747">
    <tz id="(GMT-03.00) Auto-Detected" stdoff="-180" dayoff="-240">
    <standard mon="10" mday="14" hour="24" min="0" sec="0"/>
    <daylight mon="2" mday="18" hour="22" min="0" sec="0"/>
    </tz>
    <inv method="REQUEST" type="event" fb="B" transp="O" status="CONF" allDay="0" name="Almocar">
    <s tz="(GMT-03.00) Auto-Detected" d="20061201T113000"/>
    <e tz="(GMT-03.00) Auto-Detected" d="20061201T123000"/>
    <or a="admin@ubuntu.prevnet"/>
    </inv>
    <mp ct="multipart/alternative">
    <mp ct="text/plain">
    <content/>
    </mp>
    <mp ct="text/html">
    <content>
    <html><body></body></html>
    </content>
    </mp>
    </mp>
    <su>
    Almocar
    </su>
    </m>
    </CreateAppointmentRequest>
    </soap:Body>
    </soap:Envelope>
    Body: {
    Fault: {
    Code: {
    Value: "soap:Receiver"
    },
    Detail: {
    Error: {
    Code: "service.FAILURE",
    Trace: "com.zimbra.cs.service.ServiceException: system failure: java.lang.IllegalArgumentException: Illegal end time 86400000
    at com.zimbra.cs.service.ServiceException.FAILURE(Ser viceException.java:174)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:272)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:162)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:173)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
    at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
    at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
    at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: java.lang.IllegalArgumentException: Illegal end time 86400000
    at java.util.SimpleTimeZone.decodeEndRule(SimpleTimeZ one.java:1406)
    at java.util.SimpleTimeZone.setEndRule(SimpleTimeZone .java:456)
    at com.zimbra.cs.mailbox.calendar.ICalTimeZone.(ICalTimeZone.java:477)
    at com.zimbra.cs.service.mail.CalendarUtils.parseTime Zones(CalendarUtils.java:574)
    at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teElementCommon(CalendarUtils.java:622)
    at com.zimbra.cs.service.mail.CalendarUtils.parseInvi teForCreate(CalendarUtils.java:117)
    at com.zimbra.cs.service.mail.CreateAppointment$Creat eAppointmentInviteParser.parseInviteElement(Create Appointment.java:62)
    at com.zimbra.cs.service.mail.ParseMimeMessage$Invite Parser.parse(ParseMimeMessage.java:136)
    at com.zimbra.cs.service.mail.ParseMimeMessage.parseM imeMsgSoap(ParseMimeMessage.java:249)
    at com.zimbra.cs.service.mail.CalendarRequest.handleM sgElement(CalendarRequest.java:87)
    at com.zimbra.cs.service.mail.CreateAppointment.handl e(CreateAppointment.java:80)
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:261)
    ... 21 more
    ",
    _jsns: "urn:zimbra"
    }
    },
    Reason: {
    Text: "system failure: java.lang.IllegalArgumentException: Illegal end time 86400000"
    }
    }
    },
    Header: {
    context: {
    _jsns: "urn:zimbra",
    change: {
    token: 501
    },
    sessionId: [
    0: {
    _content: "4",
    id: "4"
    }
    ]
    }
    },
    _jsns: "urn:zimbraSoap"
    I related this "bug" in other forum and no have solution yet. Zimbra Calendar in Ubuntu Dapper

    NB.: My system locale and timezone:

    root@ubuntu:~# cat /etc/timezone
    America/Campo_Grande

    root@ubuntu:~# locale
    LANG=pt_BR.UTF-8
    LANGUAGE=pt_BRtt_PT
    LC_CTYPE="pt_BR.UTF-8"
    LC_NUMERIC="pt_BR.UTF-8"
    LC_TIME="pt_BR.UTF-8"
    LC_COLLATE="pt_BR.UTF-8"
    LC_MONETARY="pt_BR.UTF-8"
    LC_MESSAGES="pt_BR.UTF-8"
    LC_PAPER="pt_BR.UTF-8"
    LC_NAME="pt_BR.UTF-8"
    LC_ADDRESS="pt_BR.UTF-8"
    LC_TELEPHONE="pt_BR.UTF-8"
    LC_MEASUREMENT="pt_BR.UTF-8"
    LC_IDENTIFICATION="pt_BR.UTF-8"
    LC_ALL=
    Last edited by jarbelix; 11-30-2006 at 09:22 AM.

Page 1 of 2 12 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Zimbra + Samba LDAP, cannot add winxp
    By fajarpri in forum Installation
    Replies: 4
    Last Post: 07-08-2007, 11:45 AM
  2. 3.0 to 4.5.3 Upgrade failed (mysql error)
    By dealt in forum Installation
    Replies: 35
    Last Post: 03-19-2007, 10:30 PM
  3. Cannot determine services - exiting
    By tawas in forum Installation
    Replies: 7
    Last Post: 04-25-2006, 02:47 AM
  4. Yet another get.DirectContext issue
    By dccpark in forum Installation
    Replies: 5
    Last Post: 03-08-2006, 01:25 PM
  5. system failure: getDirectContext
    By avisser in forum Installation
    Replies: 3
    Last Post: 10-12-2005, 05:32 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
  •