[
https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594634#action_12594634
]
Asankha C. Perera commented on SYNAPSE-287:
-------------------------------------------
Nicolas
Please attach all artifacts that will help us analyse and reproduce this
scenario. At a minimum, the synapse.xml you use and your JMeter test case.
> Setting up a proxy with sequences in and out empty.
What do you mean setting "sequences in and out empty" ? This doesn't seem like
a valid configuration at all to me.. ?
asankha
> Bad performances
> ----------------
>
> Key: SYNAPSE-287
> URL: https://issues.apache.org/jira/browse/SYNAPSE-287
> Project: Synapse
> Issue Type: Bug
> Components: Transports
> Affects Versions: 1.1.1
> Environment: Windows XP SP2, JDK SUN 1.5.0_15
> Ubuntu Server 6.10, JDK SUN 1.5.0_15
> Reporter: Nicolas KOHUT
> Priority: Critical
>
> Synapse has some networks problems.
> When it is stressed, is freeze synapse in transport http.
> This behavior is obtained by influencing 2 parameters:
> - the number of competitors access (number of thread).
> - the size of messages sent.
>
> More generally, the higher the speed is high (combination of 2 parameters
> above) synapse freezes more quickly.
> A simple test case (using JMeter):
> - Install distribution synapse-1.1.1 default.
> - Setting up a proxy with sequences in and out empty.
> - Launch a thread (1 single thread is sufficient ...) which calls the proxy
> with a message 6Ko infinite loop. The thread sits 100 ms between each call.
> Synapse must freeze (random) after about 2 000 calls (5 max 000).
> The freeze takes place at a rate of 7 messages (6Ko) per second ...
>
> The only configuration synapse that I could find is the file in the folder
> synapse.properties Conf of synapse.
> This file can affect a pool of thread used by synapse. Increase the various
> parameters of the pool has no impact and does not correct the problem.
> Listed JVM, jconsole indicates that there is no leakage and no memory thread
> in deadlock.
> Finally, the synapse approved http requests with nio-http (I do not know
> more).
> Conclusion:
> The simple test presented above is surprising. Synapse seems not to hold a
> charge very light.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
