function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Doug ADoug A 

Outbound Message Failure: org.xml.sax.SAXParseException

I've created an Outbound Message -- fairly simple, on a custom object, passing three object Id fields -- and in the process of testing it, the outbound message ends up as a failure in the queue as noted on the Outbound Messaging Delivery Status page.

The error is org.xml.sax.SAXParseException: White spaces are required between publicId and systemId.

It may be related to the fact that I've set the SOAP endpoint to localhost, which is obviously non-routable. (Duh...) Still, it may be related to something else entirely.

Any clues?
You typically get that if the response is HTML (typically from an unhandled exception in your listner) if you entered localhost as the endpoint in the OM setup, that's obviously not going to work.
Doug ADoug A
Indeed. What's interesting is that the listener was never reached, as "localhost" would refer (at best) to the SFDC server which attempted to send out the SOAP call in the first place.

Are there plans to make the response content available as part of the Outbound Messaging Delivery Status report? This would aid in troubleshooting when the call does reach the listener. No substitute for debugging, of course, but it would be useful.
Its something that's on our radar, but tools like YATT, tcpTrace and SOAPScope make this trivial for you to capture and examine yourself at the listener.
Doug ADoug A
Thanks. Good stuff, Simon.