Yes, I have a subscriber per advisory topic on the server. I am not using the
scheduler (not knowingly anyways).
I thought the log output might be related because we see messages sent to
the topic occasionally never hit some subscribers; at the same time the
MBean for the subscriber queue shows a s
We only use non-persistent messages and there should not be any messages
expiring on my development server (the stats on the MBean confirm this). To
be on the save side I changed my destination policies to what is posted
below, but it did not change the behavior of the server once tmp space usage
h
no errors in the logs, but we see message flow resume after a server
restart...I'm starting to question our connection/server configuration a bit
now given this thread dump...
our application uses camel-activemq (2.10.1) and runs embedded in an AMQ
broker (5.7)use the same connection factory/p
Hi Christian,
Thank you for the clarification. What are the factors in activemq that
could effect this, other than time to live that is set in the publisher ? I
have a time to live of 2 minutes currently, how can i ensure that most
messages are delivered before expiry ?
On 15 July 2013 20:04, Chr
Hello all,
Using ActiveMQ 5.8.0 we are seeing a message hoarding issue that only crops
up when we use a Master/Slave configuration.
A single producer sends persistent, never expiring messages to two discrete
Queues in the Broker in spurts. Each queue has a single polling consumer (so
we when we l
Your best bet is to take a look at the test case Gary recommended. Will
probably be easiest.
On Mon, Jul 22, 2013 at 4:50 AM, Tushar Nagar wrote:
> Hey, thanks for the reply
>
> but the thing is, I am not able to see the DLQ in my ActiveMQ web console
> i.e. http://localhost:8161/admin/queue
So you'll need to give some more clues here... The log message you're
showing is most likely not directly from the virtual topics... do you have
other non-virtual topic consumers/subscribers? And/Or using the scheduler?
What kind of producers, consumers, etc and how many messages, message sizes?
can you take a stack trace of the broker when it gets into that state?
On Fri, Jul 19, 2013 at 12:26 PM, Oleg Dulin wrote:
> I have two brokers set up on two servers. One is 10.194.2.1, the other is
> 10.194.2.2 .
>
> One of them has this in its config file:
>
>
>
Did you see any exceptions in the broker logs?
Seems like the server-side VMTransport stopped draining its message queue
and processing consumer acks... causing the client VMTransport to block on
a put...and all other consumers using that connection to block...
On Mon, Jul 22, 2013 at 3:46 PM, bo
Did you create that script using '$ACTIVEMQ_BASE/bin/activemq create'
command?
Looks like it will work properly if you change the last statement to
${ACTIVEMQ_HOME}/bin/activemq "$*@*"
On Mon, Jul 22, 2013 at 6:47 PM, Christian Posta
wrote:
> what happens when you use the activemq script direc
what happens when you use the activemq script directly?
On Mon, Jul 22, 2013 at 5:09 PM, Chirag Pujara wrote:
> sorry msg got sent in middle of typing:
>
> Hello,
>
> I have created 3 instance for activemq. activemq_8100, activemq_8200,
> activemq_8300.
>
> when I execute follwoing command:
>
>
sorry msg got sent in middle of typing:
Hello,
I have created 3 instance for activemq. activemq_8100, activemq_8200,
activemq_8300.
when I execute follwoing command:
/opt/gwx/apache-activemq-5.8.0/activemq_8100/bin/activemq_8100 start
-Dactivemq.data=/opt/gwx/activemqdata -DopenwirePort=61616 -
Hello,
I have created 3 instance for activemq. activemq_8100, activemq_8200,
activemq_8300.
when I execute follwoing command:
/opt/gwx/apache-activemq-5.8.0/activemq_8100/bin/activemq_8100 start
-Dactivemq.data=/opt/gwx/activemqdata -DopenwirePort=61616 -DamqpPort=5600
-DrmiPort=8100
it starts
seeing some thread blocking in our ActiveMQ 5.7 production application (using
VM transport and AMQ connection pool)...anyone know of any
configuration/known bugs that could be contributing to this?
seeing 20 thread like this one, WAITING for a single thread to release a
lock on 659ec0a4
"Camel (c
When messages are expired, they end up on the dead-letter queue.
If you don't have any consumers on that queue it fills up.
Take a look at this :
http://activemq.apache.org/message-redelivery-and-dlq-handling.html
That may very well be what is filling up your storage.
Regards,
Oleg
On 2013
Hello,
It seems I am missing yet another setting to completely disable producer
flow control. I am using virtual topics and despite plenty of temp space
being availble, it seems the dispatch from the topic to the consumer queue
is being blocked:
2013-07-22 14:13:00,601 | INFO | TopicSubscription
Hello all,
I am having trouble getting the resource configuration right... My local
development server (ActiveMQ 5.8.0) stops to accept new messages
indefinitely once the "temp percent used" counter reaches >= 100%. From this
point onwards the server does not accept any new messages. Consumers are
Assuming there is a message in the queue, I was expecting the following code
to output: 0123456789 but I get 0123412345.
for ( i=1; i<=5; i++ )
{
msg = consumer->receive(TIMEOUT);
cout << msg->getIntProperty("JMSXDeliveryCount");
sess
On 07/22/2013 02:37 AM, cineva wrote:
I know about the "JMSXDeliveryCount" property but it seems it doesn't work
between consumers. Everytime a message is redelivered for the same consumer
the property is increased by one which is correct but if a second consumer
gets the same message, the proper
Hey, thanks for the reply
but the thing is, I am not able to see the DLQ in my ActiveMQ web console
i.e. http://localhost:8161/admin/queues.jsp
and so I am not able to detect whether my messages hv been enqueued in the
DLQ or not. when I am running the consumer, the DLQ is session is getting
r
20 matches
Mail list logo
