On 3/5/07, naga007 <[EMAIL PROTECTED]> wrote:
Thanks, that Dramatically improved the througput, but i have one question,
if the client is not waiting for an ACK when sending persistent messages,
then don't we think we are at a risk of loosing messages?
Async send avoids blocking until each me
Thanks, that Dramatically improved the througput, but i have one question,
if the client is not waiting for an ACK when sending persistent messages,
then don't we think we are at a risk of loosing messages?
James.Strachan wrote:
>
> If you are using AUTO_ACK then you might wanna enable async s
If you are using AUTO_ACK then you might wanna enable async sending...
http://activemq.apache.org/async-sends.html
On 3/5/07, naga007 <[EMAIL PROTECTED]> wrote:
Let me explain in more detail.
As i said, this application is a Framework for SOA based Applications(Kind
of similar to ServiceMix
Let me explain in more detail.
As i said, this application is a Framework for SOA based Applications(Kind
of similar to ServiceMix). We are using JMETER to send HttpSOAP Requests
and these SOAP rquests gets staged in multiple queues before its gets
deliverd to a service. So For Example if we are
On 3/5/07, naga007 <[EMAIL PROTECTED]> wrote:
We are noticing significant performance degradation with persistence
turned on, when the no of concurrent users is more than 50.
What do you mean by users? Producers, consumers, sessions,
connections? Its a bit hard to offer advice on optimisat
We are noticing significant performance degradation with persistence
turned on, when the no of concurrent users is more than 50. Our
application(which is like is SOA Framework) is using active 4.1 running on
Linux Redhat with 2 Cores, 8GB Ram and using SAN for journal files storage.
Our curre
