[
https://issues.apache.org/jira/browse/QPID-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Jones updated QPID-5135:
------------------------------
Attachment: tx-test.pl
rx-test.pl
> System stalling
> ---------------
>
> Key: QPID-5135
> URL: https://issues.apache.org/jira/browse/QPID-5135
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.22
> Environment: RHEL5
> Reporter: Jimmy Jones
> Attachments: rx-test.pl, tx-test.pl
>
>
> See threads on qpid-user:
> http://qpid.2158936.n2.nabble.com/System-stalling-tp7597317.html and
> http://qpid.2158936.n2.nabble.com/Re-System-stalling-td7597940.html
> See attached scripts which reproduce the issue. Running rx-test.pl followed
> by tx-test.pl results in a system where the receiver can keep up with the
> producer (gets a message every <1s) (tx-test 118% CPU, qpidd 97% CPU, rx-test
> 60% CPU). However, if you stop rx-test and restart it (even after only a
> second or so), it starts to take 2s+ to receive messages, going up to about
> 6s on my system, so the ring quickly fills and overflows. Even if the
> producer is then stopped, messages are still only received every 3s - with
> qpidd on 100% CPU and the receiver on 5%. Also the resident size of qpidd
> reaches 5GB, yet the queue is only 2GB.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
