I have been working on the ESB solution at the place I am at and I came across the following error as I added more and more services:
The adapter failed to transmit message going to send port “ALL.Exceptions” with URL “SQL://(local)/EsbExceptionDb/”. It will be retransmitted after the retry interval specified for this Send Port. Details:”HRESULT=”0x80040e14″ Description=”XML parsing: line 32, troche character 203, unexpected end of input”
I will spare you the detail of how I came to the solution, but it appears that complex itineraries have never been written, or the bigger the itinerary, the less likely it is to fail (? !!!).
The ultimate cause of the problem is the ItineraryHeader context property.
By default the ContextProperties table in the EsbExceptionDb is defined as 4096 bytes
And the stored procedure that load the table:
This context property is much larger than even what is documented:
I changed it to:
Now it works like a charm…