Guillaume (and others),

Thanks for the reply.

I've stepped through the http provider and I'm not sure exactly what the
best practice is.

I am sending the message to the http provider from a lw pojo SE.  The
message type is InOptionalOut, and it is being transferred via seda
(sendsync).

In the http provider, the code calls the provider web service and it returns
with a response.  Since there is an actual response, the system sends the
responseBodyAsStream back to the sender.  Then, the code explicitly states
to not close the connection (as I am not in a transaction)

Then, the control returns back to the original SE and the process continues. 
However, the connection is not closed.

Currently, I am not doing anything after the message returns - just
returning out of the lw se.


My questions:

What causes the connection to close in this scenario?  Do I need to do
something with the returned message that will result in the connection
closing?

Any other suggestions?

Thanks,
James
-- 
View this message in context: 
http://www.nabble.com/http-lock-up-tf3488493s12049.html#a10160639
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to