Hello all,

I have a http provider endpoint set up to a specific url.  

As I was testing the configuration, I had the receiving web server turned
off.

I watched the debug messages inside of service mix and saw the following
error

18:07:51,997 DEBUG [DeliveryChannelImpl] Processing inbound exchange:
InOptionalOut[
  id: ID:LT478-3062-1168643152156-55:4
  status: Error
  role: consumer
  service: {urn:servicemix:status-test}status-httpProvider-service
  endpoint: status-httpProvider-endpoint
  in: <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:urn="urn:ic">
<soapenv:Header/>
<soapenv:Body>
<UVLoad><Size>1</Size></UVLoad></soapenv:Body>
</soapenv:Envelope>
  error: java.net.ConnectException: Connection timed out: connect
]
2007-01-12 18:07:51,997 [Thread-47      ] DEBUG DeliveryChannelImpl           
- Notifying exchange ID:LT478-3062-1168643152156-55:4(197a82f) in
DeliveryChannel{MgmtEsb} from processInboundSynchronousExchange
18:07:51,997 DEBUG [DeliveryChannelImpl] Notifying exchange
ID:LT478-3062-1168643152156-55:4(197a82f) in DeliveryChannel{MgmtEsb} from
processInboundSynchronousExchange
2007-01-12 18:07:51,997 [Thread-30      ] DEBUG DeliveryChannelImpl           
- Notified: ID:LT478-3062-1168643152156-55:4(197a82f) in
DeliveryChannel{MgmtEsb} from sendSync
18:07:51,997 DEBUG [DeliveryChannelImpl] Notified:
ID:LT478-3062-1168643152156-55:4(197a82f) in
DeliveryChannel{KraftMaidSheetMgmtEsb} from sendSync


However, I check the exchange for a fault message and it is null and no
exception was thrown back to my code.

The exchangeStatus for the exchange is set to ERROR.

My question:  How do I retrieve the root cause for this error.  I can use
the exchangeStatus to know that an error occurred, but I don't know where to
look for the details (basically, the ConnectException)

Thanks,
James

-- 
View this message in context: 
http://www.nabble.com/Http-bc-fault-question-tf2969168s12049.html#a8308787
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to