- well the first problem was that the original message associated
with the mediator's original "ctx" got overwritten by the new message
(because they shared the same context). I solved this by storing the
original envelope, action, to endpoint etc. and writing them back
into "ctx" when I'd sent the new message. So far so good, but then I
got the following exception:
Haven't you tried to clone the message? I think that will solve this problem
(but not that sure)
Unexpected HTTP protocol error : Transfer-encoding header already
present
org.apache.http.ProtocolException: Transfer-encoding header already
present
at org.apache.http.protocol.ResponseContent.process
(ResponseContent.java:66)
at org.apache.http.protocol.BasicHttpProcessor.process
(BasicHttpProcessor.java:221)
at org.apache.axis2.transport.nhttp.ServerHandler.commitResponse
(ServerHandler.java:221)
at org.apache.axis2.transport.nhttp.ServerWorker.handleException
(ServerWorker.java:430)
at org.apache.axis2.transport.nhttp.ServerWorker.processPost
(ServerWorker.java:214)
at org.apache.axis2.transport.nhttp.ServerWorker.run
(ServerWorker.java:171)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:613)
Under certain conditions I think I also got a broken pipe exception.
Hope this helps.
Yes, this helps a lot. We need to remove some transport headers when
creating the new Ctx from the old one.
All the best,
Nick
Thanks,
Ruwan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
