Hi Asankha,
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. 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).
Regarding your question about our extensions. We just implemented a new
mediator that sets the "To" attribute of the address via
"MessageContext.setTo()". When the new address is set, we just use the
default send-mediator to forward the entire message (with the changed
To-address of course) to the respective Tomcat Server. So we are not
using Synapse's load balancing mechanism (mediators seemed the fastest
way to implement our goal).
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. We also
noticed the same entries in our logs: 607 /[/157.193.215.56:9090]:
Content encoder [chunk-coded; completed: true]/ and /304
[/157.193.215.56:9090]: Content decoder [chunk-coded; completed: true]/.
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.
Thanks in advance,
Gregory
Asankha C. Perera wrote:
Hi Gregory
Could you let me know the version of HTTP (1.0 or 1.1) being used
between your client and Synapse, and between Synapse and Tomcat. Are
you using SSL by any means. Also let me know the OS version, and your
JDK version (including the minor version). Do you see anything in the
log files? Are the client, Synapse and Tomcat on different physical
hosts, virtual machines or same host? Also what do you mean by "we
have extended Synapse.." have you done any code changes? Also are you
using the Synapse 1.0 release or the 1.1 RC?
This works extremely well with a few messages (even if we use several
simultaneous clients). But when we stress test our setup, we notice
something peculiar. We have sent in a particular test run 1110
requests to synapse, but at the client we only got 878 responses back.
Are you using a load balanced endpoint? Do you think you loose
messages when load balancing is not used? Could you verify with a
simple test in this same environment?
The debug-logs on the org.apache.axis2.transport classes showed a
discrepancy between the content encoder (/[DEBUG] 06 nov 10:51:27.828
AM I/O reactor worker thread 2
[org.apache.axis2.transport.nhttp.ClientHandler]HTTP connection
[/157.193.215.56:9090]: Content encoder [chunk-coded; completed:
true]/) en content decoder (/BUG] 06 nov 10:51:28.718 AM I/O reactor
worker thread 2 [org.apache.axis2.transport.nhttp.ClientHandler]HTTP
connection [/157.193.215.56:9090]: Content decoder [chunk-coded;
completed: true]/) for both Tomcat-axis2 servers. We noticed 1110 of
the content encoder entries and only 878 entries for the content
decoder. These numbers fit to perfectly to be coincidence.
Again.. we just renamed our packaging of the NIO based http/s
transports to org.apache.synapse.transport.nhttp .. so either you are
using Synapse 1.0 or the 1.1 RC with a possibly older transport?
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
