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]
