Hi Oleg,
I didn't have time to look into this and finally found that this is a
regression, which occurs even with the SUN JDK.
If you change the synapse-nhttp modules dependency of the httpcore to
4.1-alpha1 and build synapse nhttp transport test cases are failing and also
when you got the build
Hi Ruwan
I didn't have time to look into this and finally found that this is a
regression, which occurs even with the SUN JDK.
If you change the synapse-nhttp modules dependency of the httpcore to
4.1-alpha1 and build synapse nhttp transport test cases are failing and also
when you got the
Thanks Asankha.
Ruwan
On Mon, Oct 5, 2009 at 8:17 AM, Asankha C. Perera asan...@apache.orgwrote:
Hi Ruwan
I didn't have time to look into this and finally found that this is a
regression, which occurs even with the SUN JDK.
If you change the synapse-nhttp modules dependency of the
Hi Ruwan
Thanks Asankha.
.
I know the reason for this with 4.1-alpha1, the cause is in the Synapse
codebase.. I will fix it...
I've fixed this now.. Could you please check if your scenario is now
working correctly?
thanks
asankha
--
Asankha C. Perera
AdroitLogic,
Yeah, just tested and seems to work fine :-)
Thanks,
Ruwan
On Mon, Oct 5, 2009 at 8:43 AM, Asankha C. Perera asan...@apache.orgwrote:
Hi Ruwan
Thanks Asankha.
.
I know the reason for this with 4.1-alpha1, the cause is in the Synapse
codebase.. I will fix it...
I've fixed this
Has any one tried to run synapse on IBM JDK 1.5?? I have tried this but
having some issue with the HTTP NIO transport :-(
Oleg, I had a look at the issue [1] and tried synapse with the 4.1-alpha1
release of the httpcore, but still the issue persists. It seems it is taking
a long time to send the
On Fri, Sep 25, 2009 at 01:07:00PM +0530, Ruwan Linton wrote:
Has any one tried to run synapse on IBM JDK 1.5?? I have tried this but
having some issue with the HTTP NIO transport :-(
Oleg, I had a look at the issue [1] and tried synapse with the 4.1-alpha1
release of the httpcore, but still
Hi Oleg,
Thanks, Yes this does solve most part of the problem, may be we can make it
a configuration as well apart from the automatic tuning that you are planing
to do, so in case if the autodetection fails for enabling that users can do
it manually using the nhttp.properties file.
But, it still
Ruwan Linton wrote:
Hi Oleg,
Thanks, Yes this does solve most part of the problem, may be we can make
it a configuration as well apart from the automatic tuning that you are
planing to do, so in case if the autodetection fails for enabling that
users can do it manually using the