Loading ...
Sorry, an error occurred while loading the content.

6642RE: [soaplite] Figuring out SOAP::Lite dependencies

Expand Messages
  • Joe Tseng
    Sep 27, 2013
    • 0 Attachment
      Looks like upping the value might have did the trick!  I just got a feed with an object of size 13178.  Thank you for the tip!

      (I say might because I'm still sporadically getting the "200 OK" errors, but if I manually trigger my job a minute later, it runs normally.  I suspect this time it's my feed provider; I'll be keeping an eye out on this for a while.)

       - Joe


      If you type "Google" into Google, you can break the Internet.  -- Jen Barber



      Date: Fri, 6 Sep 2013 08:20:25 -0700
      From: qglex@...
      Subject: Re: [soaplite] Figuring out SOAP::Lite dependencies
      To: joe_tseng@...

      If the length of the envelope/xml is truncating to 10000, take a look at

      $SOAP::Constants::MAX_CONTENT_SIZE

      By default it's set to 10,000.


       
      -Jeff


      From: Joe Tseng <joe_tseng@...>
      To: "soaplite@yahoogroups.com" <soaplite@yahoogroups.com>
      Sent: Wednesday, September 4, 2013 6:41 AM
      Subject: RE: [soaplite] Figuring out SOAP::Lite dependencies

       
      Some additional details:

      The first symptom of this issue was when I saw an email that was sent from my SOAP object's on_fault handler; the error said "200 OK".  When I looked further into it, it turns out I was still indeed pulling down XML content from the feed, but for whatever reason was being truncated.  So yes, the remote system was still up and working properly, but the problem was with one of my modules.

      Regarding symptoms, the only issue I've seen that *might* be a/the cause (and is definitely repeatable) is the amount of data is too large to be handled completely in one pass.  I get a msg saying there's an issue regarding my XML data at position 8192 - that's where the data is truncated.
      [...]


    • Show all 6 messages in this topic