You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Nicolas KOHUT (JIRA)" <ji...@apache.org> on 2008/05/06 14:34:57 UTC
[jira] Created: (SYNAPSE-287) Bad performances
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-287) Bad performances
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera updated SYNAPSE-287:
--------------------------------------
Assignee: Asankha C. Perera
I am not sure if this is the best option, but I have used the Bix console (http://www.bixdata.com/) to monitor TCP and other network/system issues during load testing. I see you have listed Windows as an environment but also Ubuntu.. Windows will have its own tools to monitor TCP stack.
Refer to http://wso2.org/library/1721 for OS/network level tuning to prepare Synapse for a load test
> 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
> Assignee: Asankha C. Perera
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-287) An Invalid configuration can lead to
lockup
Posted by "Nicolas KOHUT (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas KOHUT updated SYNAPSE-287:
----------------------------------
Attachment: full_Linux.JPG
When we test under Linux and Jmeter launching in Windows, even with the parameters-Xms512m-Xmx1024m
- XX: PermSize = 256m-XX: MaxPermSize = 512m, it freeze too and we have a Synapse exception (see attachement)
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, read_time_out.JPG, synapse.xml, test de perf.jmx
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) Bad performances
Posted by "Paul Fremantle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594575#action_12594575 ]
Paul Fremantle commented on SYNAPSE-287:
----------------------------------------
Can you check that you are using HTTP 1.1 with connection re-use from JMeter, and that you are not running out of sockets in your TCP/IP stack?
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Issue Comment Edited: (SYNAPSE-287) Bad performances
Posted by "Nicolas KOHUT (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594594#action_12594594 ]
nkohut edited comment on SYNAPSE-287 at 5/6/08 7:33 AM:
---------------------------------------------------------------
I don't use the directive "FORCE HTTP 1.0", I therefore infer that I am HTTP 1.1.
How to verify that I'm not running out of sockets in my TCP/IP stack please ?
was (Author: nkohut):
I don't use the directive "FORCE HTTP 1.0", I therefore infer that I am HTTP 1.1.
How to verify that I'm not running out of sockets in your TCP/IP stack please ?
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) An Invalid configuration can lead
to lockup
Posted by "Jake Lambert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598318#action_12598318 ]
Jake Lambert commented on SYNAPSE-287:
--------------------------------------
Actually, I can consistently reproduce this HTTP-NIO lockup by sending larger messages (> 300KB - both with and without attachments) *and* >50 threads of concurrency using SoapUI as a client. I'm directing the messages through a simple forwarding proxy service. This happens for me on both Windows and Linux (Red-Hat and Ubuntu) platforms, both tuned and not.
After a lot of investigation, here's what I've found:
- each of the transport receiver I/O dispatcher threads can block writing to the request pipe sink in ServerHandler's inputReady() method when there are no ServerWorker processing threads left
- the block occurs because the pipe's sink can only buffer a limited number of bytes until a ServerWorker thread is actively reading from the pipe's source
- a blocked I/O dispatcher thread stops all incoming reads from the client and writes back to the client for its associated connections
- as more requests come in with no free ServerWorker threads, more of the incoming I/O dispatcher threads are blocked until they are *all* permanently blocked
- the ServerWorker threads are all blocked either waiting for a free ClientWorker thread or blocked waiting for more input from the client (because the incoming mediation can be complete before a request has been fully read from the incoming socket - this is where I think the larger messages come into play)
- the ClientWorker threads are all busy waiting to send to their responses back to the client (as previously mentioned, the socket writes back to the client have been for all I/O dispatcher threads)
- there's no way out of the situation, so Synapse is effectively disabled. As you can see, increasing the number of I/O dispatchers and worker threads can only delay and not fix the problem.
Since ClientHandler's inputReady() can also block in this way, it probably should be fixed also.
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx, too_main_files.JPG
>
>
> 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).
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) Bad performances
Posted by "Oleg Kalnichevski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594705#action_12594705 ]
Oleg Kalnichevski commented on SYNAPSE-287:
-------------------------------------------
> you are not running out of sockets in your TCP/IP stack?
That would have caused tons of exceptions.
Nicolas,
Are you seeing any exceptions prior to Synapse locking up? What is the CPU utilization once Synapse becomes unresponsive?
Oleg
> 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
> Assignee: Asankha C. Perera
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) Bad performances
Posted by "Paul Fremantle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594639#action_12594639 ]
Paul Fremantle commented on SYNAPSE-287:
----------------------------------------
I use TCPView on Windows which gives me a graphical view of how many connections are open:
http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx
> 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
> Assignee: Asankha C. Perera
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-287) An Invalid configuration can lead to
lockup
Posted by "Nicolas KOHUT (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas KOHUT updated SYNAPSE-287:
----------------------------------
Attachment: GipMock.war
Mock to deploy under Tomcat
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) Bad performances
Posted by "Nicolas KOHUT (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594594#action_12594594 ]
Nicolas KOHUT commented on SYNAPSE-287:
---------------------------------------
I don't use the directive "FORCE HTTP 1.0", I therefore infer that I am HTTP 1.1.
How to verify that I'm not running out of sockets in your TCP/IP stack please ?
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-287) An Invalid configuration can lead to
lockup
Posted by "Nicolas KOHUT (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas KOHUT updated SYNAPSE-287:
----------------------------------
Attachment: too_main_files.JPG
Ok With Linux, no problem.
But now, testing with our own mediators, we have "too many open files" error.
We do not use files in our developments.
Do you have any idea / track the cause of this error?
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx, too_main_files.JPG
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) Bad performances
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) An Invalid configuration can lead
to lockup
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594896#action_12594896 ]
Asankha C. Perera commented on SYNAPSE-287:
-------------------------------------------
I was able to run the full 10,000 rounds without a single error or exception on my Linux desktop.. Heap and CPU usage was very low and fully consistent.. I see no issues at all, as I used JMeter with your script, Synapse 1.1.1 with your config and Tomcat with your WAR file
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Issue Comment Edited: (SYNAPSE-287) An Invalid configuration
can lead to lockup
Posted by "Nicolas KOHUT (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594855#action_12594855 ]
nkohut edited comment on SYNAPSE-287 at 5/7/08 4:18 AM:
---------------------------------------------------------------
Mock to deploy under Tomcat (GipMock is only a servlet that returns the contents of a file xml)
was (Author: nkohut):
Mock to deploy under Tomcat
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-287) An Invalid configuration can lead to
lockup
Posted by "Nicolas KOHUT (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas KOHUT updated SYNAPSE-287:
----------------------------------
Attachment: read_time_out.JPG
10000_gros_message_KO_CPU.JPG
Exception and CPU screenshots
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, read_time_out.JPG, synapse.xml, test de perf.jmx
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-287) An Invalid configuration can lead to
lockup
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera updated SYNAPSE-287:
--------------------------------------
Priority: Minor (was: Critical)
Summary: An Invalid configuration can lead to lockup (was: Bad performances)
Editing the headline as I am confident this is an invalid configuration and user error..
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-287) An Invalid configuration can lead to
lockup
Posted by "Nicolas KOHUT (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas KOHUT updated SYNAPSE-287:
----------------------------------
Attachment: test de perf.jmx
synapse.xml
Two files :
- synapse.xml
- Jmeter script (test de perf.jmx) : the test to use is "gros message"
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: synapse.xml, test de perf.jmx
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Resolved: (SYNAPSE-287) An Invalid configuration can lead to
lockup
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved SYNAPSE-287.
---------------------------------------
Resolution: Invalid
This is not a defect with Synapse. When load testing the tools and the environment must be prepared to make accurate measurements. Else the observations will be erroneous and misleading.
In this case, it was most probably the fact of running a JMeter script on a Windows host that pushed that machine to behave badly, reducing the TPS to the extent that looked like Synapse was locked when infact it was fine.
It has now been confirmed that with proper tuning, and better OS environments, this test passes without any errors
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx, too_main_files.JPG
>
>
> 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).
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) An Invalid configuration can lead
to lockup
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594835#action_12594835 ]
Asankha C. Perera commented on SYNAPSE-287:
-------------------------------------------
Thanks for the configuration, Can I also know how and where the "http://10.33.31.108:8180/GipMock/" service is created and hosted as well, so that I can reproduce this scenario.
However, a strong point to note is that it seems like you are running Synapse on a Windows box! On Windows, the non-blocking transport implementation falls back to using in-memory buffered streams to convert from NIO channels to streams. Thus I suspect that you may be running into a low memory issue - is this visible from your JMX monitoring as well? Whats the size of the heap memory specified through the "-Xms" and "-Xmx" parameters at startup?
I strongly suggest switching the Synapse instance to Linux for load testing, where the native Pipe's are used for the channel to stream bridging
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, read_time_out.JPG, synapse.xml, test de perf.jmx
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) An Invalid configuration can lead
to lockup
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594897#action_12594897 ]
Asankha C. Perera commented on SYNAPSE-287:
-------------------------------------------
If you are running JMeter on Windows, and if you haven't tuned its Heap, it may run out of memory or get really sluggish in performance as the garbage collection increases.. Why dont you run everything on Linux and check results? I ran all three on my laptop and everything was perfect!
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Updated: (SYNAPSE-287) An Invalid configuration can lead to
lockup
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera updated SYNAPSE-287:
--------------------------------------
Description:
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).
was:
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.
Removed the invalid and erroneous 'Conclusion' of the original defect.
Please refrain from making invalid conclusions in the 'Description' of a JIRA at the time of opening. The development team will add comments and follow up the JIRA, and that will be the real conclusion for the issue at the time of resolution.
Questions which needs clarification are more suited to the mailing lists.
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx, too_main_files.JPG
>
>
> 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).
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) An Invalid configuration can lead
to lockup
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598333#action_12598333 ]
Asankha C. Perera commented on SYNAPSE-287:
-------------------------------------------
Jake
Can you open a new JIRA and attach the sample request and any other resources you've used, along with the above description.. I will take a look at this ASAP
asankha
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx, too_main_files.JPG
>
>
> 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).
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) An Invalid configuration can lead
to lockup
Posted by "Nicolas KOHUT (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594828#action_12594828 ]
Nicolas KOHUT commented on SYNAPSE-287:
---------------------------------------
The exceptions sent by Synapse during a freeze are type ReadTimeOut
And the CPU is 0% (see screenshots)
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: synapse.xml, test de perf.jmx
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[jira] Commented: (SYNAPSE-287) An Invalid configuration can lead
to lockup
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594969#action_12594969 ]
Asankha C. Perera commented on SYNAPSE-287:
-------------------------------------------
For "too many open files" and many other load testing level requirements - refer to the previous link I gave (http://wso2.org/library/1721)
The default limit of files per process on an un-tuned Linux system is usually 1024.. and this runs out very fast, with many sockets being opened
> An Invalid configuration can lead to lockup
> -------------------------------------------
>
> 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
> Assignee: Asankha C. Perera
> Priority: Minor
> Attachments: 10000_gros_message_KO_CPU.JPG, full_Linux.JPG, GipMock.war, read_time_out.JPG, synapse.xml, test de perf.jmx, too_main_files.JPG
>
>
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org