Hi Gregory
You might have pinpointed the problem. One run of the DummyService
takes about 900 ms. But since we really calculate something it will
keep the processor busy when there are simultaneous runs of the
DummyService. We notice that the service time grows semi-linear.
With our new tests in our Linux environment, we noticed dropped
message from 35 simultaneous users. So your 30 s might also be pretty
accurate, when our Tomcat servers receive 35 simultaneous requests,
the DummyService will run approximately 31 s.
Can you please help us fine tuning our Linux environment, but I have
to mention one more thing: I'm a Linux novice.
So this seems like a problem we can solve with proper tuning. From what
I understand, it seems like your client times out the connection from
its end, and I will need to know your exact OS and its version and the
Client software that you use (i.e. is it Axis2, .Net etc..). If you are
going to host Synapse on a Linux machine, the basic tuning I would
recommend is the following. You will need to edit these as "root" and
then reboot the system.
Edit /etc/sysctl.conf and add the following:
net.ipv4.ip_local_port_range = 1024 65535
net.ipv4.tcp_fin_timeout = 30
fs.file-max = 2097152
net.ipv4.tcp_tw_recycle = 1
net.ipv4.tcp_tw_reuse = 1
Edit /etc/security/limits.conf and add the following:
* soft nofile 4096
* hard nofile 65535
Although I am not specialized in tuning Windows etc. I will try to find
the relevant information for you once I know exactly what you use on
your client side.
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
