Looks like your network connectors are in one direction only, ie, node1 --
node2
What this means is messages will only flow across the network FROM node1 TO
node2 based on the demand (consumers) on node2. They will not flow the
other way unless you set up a bridge in the other direction (node2 --
Hi,
Using 5.7.0 I find that the problem exists in the following way:
2 brokers connected via network.
Broker A
has consumer connected to a /queue/foo.test
Broker B
has a producer connected to /queue/foo.test
the producer is producing message for /queue/foo.test and the
We tested with activemq version 5.4.2. The message stuck with this version
too. I think a jms provider in which the messages stuck is not useable. The
activemq team should stop to fix another problems and begin to analyse what
the reason for this problem is and deliver a patch as soon as possible.
Hi,
the problem we have too. Sometimes the messages stuck in queue and after a
restart it deliver to the consumer.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Stuck-messages-Dispatch-issues-tp2367852p3443852.html
Sent from the ActiveMQ - User mailing list archive at
We have been experiencing the same Issue and using 5.2.0.
Recently upgraded to 5.4.2 because of this, But I am Not Sure this has been
fixed.
Responding to Rob Davis Post..
I think nothing to suspect with Spring here, because when this is happening
I tried hitting the same queue with a new
Sounds scary to me, as system I'm working on uses activemq extensively, and
is not production-proven yet.
Do you have/can you build a junit test case that reproduces the issue under
5.3? If so, that looks like a good start for Jira defect.
Disclaimer - I'm not an AMQ committer.
Thanks,
Pavel
Do you still get problems if not using Spring ?
On 20 Feb 2010, at 07:12, Elliot Barlas wrote:
Was this issue ever resolved? I am seeing this as well with a large
number
of concurrent consumers. Same symptoms. Lost messages until broker
restart.
Thanks,
Elliot
chrajanirao wrote:
Yes. I am using spring 3.0, but not for JMS. I manage my own connections,
sessions, producers, and consumers. I have tried reproducing the issue in a
test case, but I cannot. It only occurs in my application, when I have
roughly 20 or more concurrent consumers, each associated with a
Was this issue ever resolved? I am seeing this as well with a large number
of concurrent consumers. Same symptoms. Lost messages until broker
restart.
Thanks,
Elliot
chrajanirao wrote:
We are seeing issues with ActiveMQ 5.1 and 5.2 RC2 with message
dispatching from queues. It is easily
Unfortunately I am seeing it in 5.3. I just posted on this more current
thread as well:
http://old.nabble.com/50k-%2B-messages-stuck-in-queue-with-all-consumers-blocking-on-receive-td27162095.html
Thanks,
Elliot
rajdavies wrote:
This should be resolved in 5.3
On 20 Feb 2010, at 07:12,
can you share the details of the compilation issues so we can help diagnose?
2009/7/30 couzteau couzt...@bitfaeule.net
Thanks for the info!
I integrated 5.3-snapshot but ran into compile issues with the latest jar -
So I abandoned that.
Gary Tully wrote:
in the absence of a test
Has this been solved yet? I'm seeing it with 5.2.0.
I'm seeing an issue that occurs on some machines (where machines are
identical regarding OS, Java version and hardware).
Consumers that are on the same machine as the producer usually work fine.
It's a major blocker for us - any comments
queues, and they will then not
deliver or accept any more messages until the broker is restarted.
Regards,
Mats
-Original Message-
From: couzteau [mailto:couzt...@bitfaeule.net]
Sent: Thursday, July 30, 2009 2:57 AM
To: users@activemq.apache.org
Subject: Re: Stuck messages
Thanks for the info!
I integrated 5.3-snapshot but ran into compile issues with the latest jar -
So I abandoned that.
Gary Tully wrote:
in the absence of a test case, the best approach is to try out a
5.3-SNAPSHOT
2009/7/30 couzteau couzt...@bitfaeule.net
Has this been solved yet?
A test case would be great because it would be good to get this issue
fully understood. This is a potential blocker for the 5.2.0 release
IMHO. Can you raise a jira issue to track this?
thanks.
2008/11/14 chrajanirao [EMAIL PROTECTED]:
I tried 5.2 RC3 and it seem to have new bugs. It
Once such problem[1] was resolved for 5.2.0 RC3, would it be possible
to validate RC3[2]?
What would really help here is a JUnit test case that demonstrates the problem.
[1] https://issues.apache.org/activemq/browse/AMQ-1984
[2]
I tried 5.2 RC3 and it seem to have new bugs. It dispatching duplicates. One
of my test run resulted below:
Messages sent: 1000 (using 50 threads 20 times)
Consumers: 2 trasacted
Queue Attributes in JConsole:
DequeCount: 1000
DipatchCount: 4849
EnqueueCount:1000
InFlightCount: 3849
QueueSize:
What are the queue's DequeueCount and InFlightCount attributes
registering on the jconsole?
Joe
Get a free ActiveMQ user guide @ http://www.ttmsolutions.com
chrajanirao wrote:
We are seeing issues with ActiveMQ 5.1 and 5.2 RC2 with message
dispatching from queues. It is easily
18 matches
Mail list logo
