Hello,
I would like to get some details on how can work the flow control through
JMS.
For example I see there is thow methods in the BasicDestination class which
are theorically called by the broker to slow down the producer
(fastProducer) or speed up the consumer (slowConsumer). The problem
Hi Dejan,
Thanks for your help! I'll try this out as soon as I have time for this and
will notify this thread about the result.
Dejan Bosanac wrote:
Hi Yury,
note that you have to configure XStream properly so it can use your class'
annotations, like
bean
Hi all,I am testing the activemq to learn how to use it. I write a simple
single thread jms client to send 1 messages, but it is blocked at the
5083rd message. I use:
activemq 5.2
jvm 1.5
ubuntu 8.10
and the program is simple :
public class Sender {
public static void main(String[]
you are seeing producer flow control in
actionhttp://activemq.apache.org/producer-flow-control.html.
The objective of producer flow control is to ensure that an entire
connection is not blocked when the memory limit of a destination is reached.
The broker and producer communicate to push back on
Just came across this useful blog entry on flow
controlhttp://blog.kovyrin.net/2009/01/23/activemq-tips-flow-control-and-stalled-producers-problem/from
Homo-Adminus http://blog.kovyrin.net/ who had a similar experience. It is
worth a read.
2009/4/2 Gary Tully gary.tu...@gmail.com
you are seeing
Thanks!
On Thu, Apr 2, 2009 at 6:14 PM, Gary Tully gary.tu...@gmail.com wrote:
Just came across this useful blog entry on flow
control
http://blog.kovyrin.net/2009/01/23/activemq-tips-flow-control-and-stalled-producers-problem/
from
Homo-Adminus http://blog.kovyrin.net/ who had a similar
See this issue at JBoss Jira
https://jira.jboss.org/jira/browse/JBMESSAGING-1384 JBMESSAGING-1384 for a
solution that allows running StompConnect as JBoss Service. It allows
running StompConnect as JBoss Service in the same JVM. It worked for me with
JBoss 5.0.1 - not sure if other versions
Hi
There appears to be an issue with expired messages on ActiveMQ version
5.2.0. Expired messages are not immediately moved to the DLQ when they
expire. Instead they remain in the queue until they have exceeded their
expiry date by several minutes AND another message is delivered to the
queue.
Hi,
We are using AMQ 5.1.0 on some of our servers. We noticed that (on few
servers) after a while the AMQ failover transport stops working thus making
messages to be not delivered. (from a producer AMQ server box to a central
consumer AMQ server box through camel)
I am running ActiveMQ embedded in another application and it seems like it is
running correctly but broker.start() never returns which is hanging the
startup of my program. In 4.x I didn't have this problem.
Here is a code snippet of how I am starting ActiveMQ :
broker = new
On Thu, Apr 2, 2009 at 10:48 AM, virtualshock nab...@virtualshock.net wrote:
I am running ActiveMQ embedded in another application and it seems like it is
running correctly but broker.start() never returns which is hanging the
startup of my program. In 4.x I didn't have this problem.
Here is
Is there any progress on message prioritization? This could be a deal-breaker
for using ActiveMQ..
Hiram Chirino wrote:
HI Attila,
Your right on all counts. Something like the PriorityQueue should do
the trick but it would need to be done on the PrefetchSubscription's
pending list.
We are using ActiveMQ quite extensively at Last.fm and are experiencing a
number of issues related to the huge load we are putting on it (at peak
times up to thousands of messages per second). We are using it in a number
of different scenarios but our general use case is that we would much rather
Hey There-
I'm not gonna be of much help off the bat but can certainly commiserate with
you. I'm trying to achieve the same goal with similar message loads and am
getting frustrated too.
Are you guys running multiple brokers using the network-of-brokers
configuration? What I'm seeing right
Thanks Bruce. You got me in the right direction. My connectionFactory had
already locked the data directory causing my custom startup code to hang. I
used create=false in my brokerURL on the connectionFactory and now it is
starting up correctly.
bsnyder wrote:
On Thu, Apr 2, 2009 at 10:48
Hi there,
as for the first question. AFAIK the methods you mention just send
advisory messages
that you could monitor for the moment. I could imagine you could use
the method hooks for implementing
a broker plugin that automatically disconnects slow consumers for
example.
As for the
please post as much information as you can w.r.t number of topics, queues
and xml configuration. If you can produce a junit test case that
demonstrates the behaviour you are experiencing that would be fantastic.
Using systemUsage it should be possible to ensure memory is never exhausted
and
I am trying to determine the ideal hardware to run my ActiveMQ 5.2
Pure Master/Slave brokers on. I am currently deciding between
hardware with 2 NICs versus 4 NICs. I am curious if ActiveMQ features
currently support multiple replication connections between Master and
Slave or alternatively
Thanks for the quick response. We are running 2 instances of ActiveMQ - one
is running 5.1.0 and the other is running 5.2.0. The one running 5.1.0 runs
out of memory every now and then and all connected senders go nuts and we
see a *big* increase in CPU on the sender machines (possibly due to
19 matches
Mail list logo
