Hi Gregory
We are currently using the Synapse 1.0 release. Our Synapse Machine's OS is Windows Server 2003 R2 (Enterprise Edition) SP1 with a JDK 1.6.0_02-b06.
We haven't tested NIO code with JDK 1.6.x but only with 1.5.x.. from testing carried out by me on Windows environments, the NIO implementation on Windows has some issues, and I would strongly suggest using Linux as an alternative. You could also perform some of the tuning suggested in http://wso2.org/library/1721 at the bottom.
Both Tomcat Servers run on a Windows 2000 (5.00.2195) OS with JDK 1.5.0_06-b05 and JDK 1.5.0_07-b03. The version of Axis2 is 1.1.1 and of Tomcat is 5.5.20. As you already could have guessed, these servers run on different physical machines, but they are directly connected to each other (our Synapse server machine has multiple network cards).
You do not state your client environment, I am specifically interested to see if it sends HTTP 1.0 or 1.1 requests to Synapse, and if Keepalives are used
We performed the new requested tests (simple message forwarding to one of our Tomcat machines). We noticed the same disturbing behaviour (even with a dropped load - our Tomcat server couldn't cope with the same throughput as with the other tests). The client made 607 invocations and only received 304 correct answers returned to the client.
So are you saying that a direct client to Tomcat test has issues?
We are going to test our Synapse broker on a Linux machine (I've read somewhere that there might be some concurrency related problems with Windows and Java's NIO). I let you know what the outcome is.
This is great and I will look forward to your results. Meanwhile, if you can help me reproduce this test with the Apache Bench Java clone (that supports chunking, SSL etc - check the link I gave earlier for this) and Synapse, I can help you find the issue. You may send any confidential information privately to me if you please

asankha

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to