Page 3 of 3 FirstFirst 123
Results 21 to 25 of 25

Thread: API and JSON responses, How to read it in Java not JavaScript

  1. #21
    Join Date
    Nov 2006
    Posts
    19
    Rep Power
    9

    Default here is the full java dump from catalina.out

    Here is the dump from catalina.out trigred by kill -3 <tomcat pid> while the client is waiting for a response from Zimbra which finaly results in a connection time out on the client side:

    NOTE: On client side I did not put <format type="js"/> in the request, If I put that there, Zimbra responses with no problem.
    Attached Files Attached Files
    Last edited by seeker; 01-06-2007 at 04:08 PM.

  2. #22
    Join Date
    Aug 2005
    Posts
    1,433
    Rep Power
    12

    Default zipfile is invalid

    Not sure why, but your zipfile downloads as invalid here.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  3. #23
    Join Date
    Nov 2006
    Posts
    19
    Rep Power
    9

    Default

    I just edited my last post. I added the original text files. The forum does not allow me to upload text files larger than 39k, so I had to upload it in 3 parts.

  4. #24
    Join Date
    Aug 2005
    Posts
    1,433
    Rep Power
    12

    Default Never hits Zimbra's processing code...

    Here's what I believe to be the relevant worker thread stack trace:
    Code:
    "http-8080-Processor100" daemon prio=1 tid=0xa37112d8 nid=0x1041 runnable [0xa0aa6000..0xa0aa6fb0]
    	at java.net.SocketInputStream.socketRead0(Native Method)
    	at java.net.SocketInputStream.read(SocketInputStream.java:129)
    	at org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:737)
    	at org.apache.coyote.http11.InternalInputBuffer.parseRequestLine(InternalInputBuffer.java:398)
    	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:827)
    	at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
    	at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
    	at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
    	at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
    	at java.lang.Thread.run(Thread.java:595)
    Note that it's still in the tomcat-processing-the-HTTP-request phase; it hasn't even hit any Zimbra code. The most likely culprit that I can think of is that the Content-Length on your request is incorrect.

    Note that if you're using Zimbra 4.0 or later, I believe that zmprov without the -l switch does SOAP requests in XML getting back XML responses. If zmprov works and your stuff doesn't, it's almost certainly your request at fault...
    Last edited by dkarp; 01-06-2007 at 04:22 PM.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  5. #25
    Join Date
    Aug 2005
    Posts
    228
    Rep Power
    10

    Default

    zmprov does in fact use SOAP by default, as does zmailbox and the HTML-only client.
    Bugzilla - Wiki - Downloads - Before posting... Search!

Posting Permissions

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