Asankha,
I'm aware of the bit transport changes in 1.2, that's why I back-ported
the 1.2 transport. In actual fact, if I go back to the 1.1.1 transport,
this problem goes away (but, as I'm sure you're aware, I get a bunch of
other problems in exchange).
________________________________
From: Asankha C. Perera [mailto:[EMAIL PROTECTED]
Sent: Monday, August 25, 2008 1:48 PM
To: [email protected]
Subject: Re: Occasionally loosing response for hosted service
within Synapse?
Jason
We have done major changes to the nhttp transport for 1.2
release, and we are continuing with more scenarios with the help of some
of our users like Eric Hubert, to nail down some of the more difficult
to reproduce issues as we speak.
Ok, I realize this is a bit of a stretch, as my Synapse
code is not exactly an official release, but;
I'm running Synapse 1.1.1, with the NHTTP transport code
from Synapse 1.2 (didn't want to take Axis 1.4 for reasons I won't go
into here). I'm also hosting an Axis2 generated service within my
Synapse runtime. I have an Axis2 generated client which is calling into
my hosted service. The client is running over the blocking HttpClient
based transport, and obviously the service is running on the Synapse
NHTTP transport. I should also mention I'm running with the fix I
proposed for JIRA-415 (since without that fix, I run out of
HttpServerWorkers in less than a minute).
Every now and then (maybe once every 30 seconds under
heavy load?), I'll send a request from the client, the server will
receive it and process it, but then will fail to send a reply back to my
client. Every now and then I see this happen for my
I can say very clearly that you are going to run into a severe
problem if you remain on an older codebase.. so whatever your reasons
maybe, please consider running Synapse standalone on another machine or
VM image than your Axis2 service, and run the latest version of Synapse.
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
