Hi,
I'm trying to impl a use case where a non-persistent msg producer can
send msgs until no more disk space. We want to flow the msgs to disk with a
limit - and to detect when the space is full (instead of being throttled).
The attempt is to set tempUsage limit with sendFailIfNoSpace on the
x27;t know enough about the code to pin it down.
Thanks, again.
From: Gary Tully
To: users@activemq.apache.org; Joe Smith
Sent: Friday, September 16, 2011 11:38 AM
Subject: Re: Could not start connection when using jms.prefetchPolicy on
failover protocol url
th
o the other brokers - even if the consumers on
the other brokers were busy/processing as well.
Really appreciate you and all the folks who are helping. Hope some of this
feedback will help.
Thanks
From: Gary Tully
To: users@activemq.apache.org; Joe Smith
Hi Johan,
Thanks for the info - placing the prefetch on the failover worked. I put the
prefetch on the tcp: based on the page at
http://activemq.apache.org/what-is-the-prefetch-limit-for.html.
The failover page dose not reference prefetch option:
http://activemq.apache.org/failover-transp
Could not start connection when using the following URL pattern:
failover:(tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1,tcp://localhost:62616?jms.prefetchPolicy.queuePrefetch=1)
When prefetchPolicy is removed, connection started normally.
Broker version: 5.4.2
Java client library
JVM
Hi,
Just another note on our test run w/5.4.2 version which was done earlier. The
broker does not exhibit the "pausing" behavior. In fact, it actually achieve
speed of 40k msg/sec on some occasions.
However, on a close examination of log and system stats. We notice the
following:
We were u
Hi Dejan,
Thanks for the reply. We use the vmQueueCursor - for based on our benchmark -
it give us better throughput than store and file cursors. We've tried the
systemUsage configs, giving spaces to memory, store, and temp space. Seem to
get the save results. Do you have any recommendation
Another follow-up. We let the job ran over the weekend. We kill the
consumers. The messages eventually filled up the buffer. The systemUsage is
the default (commented out). Assuming the msg will flow to disk until
limit. After we stopped the consumer for 24 hrs, we tried to connect the
Sorry. Could not see the attachment. Pasting it below. Sorry for the long
trace.
ActiveMQ - 5.5.0
JVM - 1.6
OS - Linux
Hi,
We are testing 5.5.0 for an upgrade from 5.4 - hoping for a performance boost.
In our testing, we notice brokers stop delivering messages on a regular
interval. The cpu graph clearly showing a slowing down of the broker at
regular interval. With some investigation by changing the
kahaDb'
Apologize if this is a re-post...
From: Joe Smith
Subject: Broker forwards msg only once or twice then msg stuck in queue.
To: users@activemq.apache.org
Date: Friday, June 24, 2011, 2:53 AM
Hi,
We have a cluster of 4 brokers (A, B, C, D). The test scenario is for one
produce connected to
Hi,
We have a cluster of 4 brokers (A, B, C, D). The test scenario is for one
produce connected to broker A.
1. producer sends msgs to broker A's queue.
2. stop producer. we see pending messages in queue on broker A.
3. consumer connect to broker D. consumer recv msgs.
4. stop consumer. we see
Hi Martin,
We use springframework for the listener and the listener container - we did not
set the listener/container to be exclusive - not sure if you can do so in
spring. However, I don't know if that is a default setting in spring - will
look into it.
We don't use message group either - so
Hi Edan,
Yes. with the springframework's PrefetchPolicy bean, I've used both values.
Unfortunately, the msgs were still queued within a listener container bounded a
single broker. The msgs were not re-distributed to the other 2 listen
containers (which were idle) bounded to the other 2 broke
Hi,
We are using 5.4.2 running on Linux w/Java 1.6. The cluster has 3 primary
brokers
and corresponding slaves (residing on separate hosts). We have 3 msg consumer
processes (using Springframework w/3 concurrent
threads each), connected to each broker.
Occasionally a consumer process
would be the right approach to
report/fix this issue?
Thanks.
From: Joe Smith
To: users@activemq.apache.org
Sent: Tue, March 22, 2011 3:03:46 PM
Subject: virtual topic with queue consumer on a broker cluster
Hi,
I'm encountering a problem in using Vir
Hi,
I'm encountering a problem in using VirtualTopics in a cluster of 3 brokers.
Hope ActiveMQ experts can help. I attached the configuration at the end. I
used most of the networkconnector and transportconnector option, hoping I got
it
right - please help. Thank you.
OS redhad linux
java
Billy,
You might want to try with just the failover: protocol and leave out the static
failover:(tcp://host1:port1,tcp://host2:port2...)
--- On Tue, 3/8/11, billy wrote:
From: billy
Subject: ActiveMQ-5.4.2 failover not working correctly
To: users@activemq.apache.org
Date: Tuesday, March 8, 20
removeBrokerInClusterUpdate
[1]
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/RegionBroker.java?view=markup
On 25 February 2011 22:14, Joe Smith wrote:
> Hi,
>
> I'm using the 5.4.x transport's updateClusterClients
try attachment again
From: Joe Smith
To: users@activemq.apache.org
Sent: Fri, February 25, 2011 5:22:04 PM
Subject: Re: Connection Re-balance Question
Attachment.
From: Joe Smith
To: users@activemq.apache.org
Sent
Attachment.
From: Joe Smith
To: users@activemq.apache.org
Sent: Fri, February 25, 2011 5:14:51 PM
Subject: Connection Re-balance Question
Hi,
I'm using the 5.4.x transport's updateClusterClients="true"
rebalanceClusterClients="tr
Hi,
I'm using the 5.4.x transport's updateClusterClients="true"
rebalanceClusterClients="true" options.
It works fine as a broker is added to the cluster - the existing connections
are
rebalanced.
When a broker that's already in the cluster when down, the connections failed
over succes
Hi, sorry if this is a re-post.
I'm using amq 5.4. adium 1.3.10 on macbook runing java 1.5 jvm.
Trying to connect to default xmpp port 61222 but getting error back. Not sure
where the problem is. Error msg on broker said "borken pipe." So I dump the tcp
trace - see below.
Thanks for the help
23 matches
Mail list logo
