Results 1 to 6 of 6

Thread: An invalid request was made

  1. #1
    deepblue is offline Partner (VAR/HSP)
    Join Date
    Jul 2006
    Location
    Stuttgart / Germany
    Posts
    223
    Rep Power
    9

    Default An invalid request was made

    Hello,

    after upgrading from 4.0.3 NE to 4.5.0 I noticed a Problem using the new basic client.
    After login I see the error: "An invalid request was made." on top of the page.

    The HTML Source of the page reveales an java error:

    <!-- com.zimbra.soap.SoapFaultException: invalid request: empty/missing item ID
    at com.zimbra.soap.Soap12Protocol.soapFault(Soap12Pro tocol.java:102)
    at com.zimbra.soap.SoapTransport.extractBodyElement(S oapTransport.java:215)
    at com.zimbra.soap.SoapTransport.parseSoapResponse(So apTransport.java:191)
    at com.zimbra.soap.SoapHttpTransport.invoke(SoapHttpT ransport.java:214)
    at com.zimbra.soap.SoapTransport.invoke(SoapTransport .java:231)
    at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:346)
    at com.zimbra.cs.zclient.ZMailbox.getMessage(ZMailbox .java:1367)
    at com.zimbra.cs.taglib.tag.msg.GetMessageTag.doTag(G etMessageTag.java:77)
    at org.apache.jsp.tag.web.message.messageListView_tag $messageListView_tagHelper.invoke0(org.apache.jsp. tag.web.message.messageListView_tag:808)
    at org.apache.jsp.tag.web.message.messageListView_tag $messageListView_tagHelper.invoke(org.apache.jsp.t ag.web.message.messageListView_tag:1306)
    at org.apache.jsp.tag.web.infra.handleError_tag._jspx _meth_c_catch_0(org.apache.jsp.tag.web.infra.handl eError_tag:146)
    at org.apache.jsp.tag.web.infra.handleError_tag.doTag (org.apache.jsp.tag.web.infra.handleError_tag:83)
    at org.apache.jsp.tag.web.message.messageListView_tag .doTag(org.apache.jsp.tag.web.message.messageListV iew_tag:151)
    at org.apache.jsp.h.search._jspx_meth_app_messageList View_0(org.apache.jsp.h.search:675)
    at org.apache.jsp.h.search._jspx_meth_c_when_7(org.ap ache.jsp.h.search:651)
    at org.apache.jsp.h.search._jspx_meth_c_choose_1(org. apache.jsp.h.search:458)
    at org.apache.jsp.h.search._jspService(org.apache.jsp .h.search:133)
    at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:97)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:332)
    at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:314)
    at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:264)
    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 com.zimbra.webClient.filters.CharEncodingFilter.do Filter(CharEncodingFilter.java:45)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:323)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202)
    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)
    -->
    Regards
    Thomas

  2. #2
    schemers is offline Zimbra Employee
    Join Date
    Aug 2005
    Posts
    228
    Rep Power
    9

    Default

    Looks like you have "Group mail by: message" turned on (judging by messageListView_tag in the stack trace), the bug could also be related to reading-pane handling. Can you go into Options/Mail and turn off:

    Always show the reading pane : [x]

    And see if that fixes it?

    It would also help if you could file a bug, with the stack trace from view source and the server logfile if possible.

    thanks.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  3. #3
    moniker is offline Loyal Member
    Join Date
    Mar 2006
    Posts
    80
    Rep Power
    9

    Default

    I am also receiving this error message when logging into the basic client.

  4. #4
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,470
    Rep Power
    56

    Default

    Quote Originally Posted by moniker View Post
    I am also receiving this error message when logging into the basic client.
    Did you try the suggestion above? If that didn't help, have you filed it as a bug?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #5
    deepblue is offline Partner (VAR/HSP)
    Join Date
    Jul 2006
    Location
    Stuttgart / Germany
    Posts
    223
    Rep Power
    9

    Default

    Quote Originally Posted by schemers View Post
    Looks like you have "Group mail by: message" turned on (judging by messageListView_tag in the stack trace), the bug could also be related to reading-pane handling. Can you go into Options/Mail and turn off:

    Always show the reading pane : [x]

    And see if that fixes it?

    It would also help if you could file a bug, with the stack trace from view source and the server logfile if possible.

    thanks.
    Sorry for answering so late...

    Both of your suggestions help. When I turn of "Always show the reading pane" or when I Group mail by conversation both fix the problem. I have filed a bug: http://bugzilla.zimbra.com/show_bug.cgi?id=14094.
    What Server log should I append to that bug? I can not find any logentries which seem to be related to the problem...

    Regards
    Thomas

  6. #6
    schemers is offline Zimbra Employee
    Join Date
    Aug 2005
    Posts
    228
    Rep Power
    9

    Default

    thanks, due to other issues (lack of scroll bar, mainly), we decide to not enable the reading pane in message list view, so this issue will be resolved in 4.5.1.
    Bugzilla - Wiki - Downloads - Before posting... Search!

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. I give up
    By rainynight65 in forum Installation
    Replies: 6
    Last Post: 11-23-2011, 08:45 AM
  2. zmprov mc default zimbraFeatureNotebookEnabled TRUE
    By nbhanji in forum Installation
    Replies: 11
    Last Post: 04-29-2008, 10:39 AM
  3. Postfix problem
    By jimbo in forum Administrators
    Replies: 46
    Last Post: 07-23-2007, 05:24 AM
  4. Can not reach https://example.com:7017/zimbraAdmin
    By Max Ma in forum Installation
    Replies: 14
    Last Post: 03-31-2007, 09:14 AM
  5. Replies: 26
    Last Post: 02-12-2007, 07:23 PM

Posting Permissions

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