Re: Queue locks up , purging it allows it to work again.

Are you reaching your diskUsage threshold (see systemUsage)? On Sunday, April 19, 2015, Kevin Burton bur...@spinn3r.com wrote: Interesting. It’s already 1 in the connection configuration. I assume you mean queuePrefetch as it’s named differently in the destination policy. On Sun, Apr 19,

Changing message persistence on messages forwarded using composite queue?

Hello, We have a composite queue defined as follows: amq:virtualDestinations amq:compositeQueue name=DataQueue forwardOnly=false amq:forwardTo amq:queue physicalName=StatisticsQueue/

Re: Changing message persistence on messages forwarded using composite queue?

with (ForcePersistencyModeBrokerPlugin) and add some more logic to apply to only certain destinations. On Thu, May 9, 2013 at 9:04 AM, Geoffrey Arnold geoff...@geoffreyarnold.com wrote: Hello, We have a composite queue defined as follows: amq:virtualDestinations

Re: Pause/Resume MessageListener using DefaultMessageListenerContainer

To stop: DefaultMessageListenerContainer#stop DefaultMessageListenerContainer#shutdown To restart: DefaultMessageListenerContainer#initialize On Aug 28, 2012, at 4:18 PM, jpcook01 wrote: Hmmm, Thinking about this, if I shut the DefaultMessageListenerContainer down

Re: Problem with network-of-brokers configuration after upgrading to AMQ 5.6.0

org.springframework.beans.factory.config.PropertyPlaceholderConfigurer If is important that the clientId, the combination of brokerName and networkConnector name, is consistent across restarts. On 20 May 2012 21:45, Geoffrey Arnold geoffrey.arn...@gmail.com wrote: Hello again, We are from AMQ 5.4.0 to 5.6.0, and there appears

Problem with network-of-brokers configuration after upgrading to AMQ 5.6.0

Hello again, We are from AMQ 5.4.0 to 5.6.0, and there appears to be a new uniqueness constraint in network connector names in network-of-brokers configurations. Here's our setup: - N copies of a producer application; each copy of the producer application consists of an embedded broker with 2

Re: Questions on upgrading to 5.6.0

Many thanks Gary! Do you have recommendations for the storeUsage and tempUsage limits given that our max journal file size is 32mb? How did this work in 5.4.0? On May 18, 2012, at 9:19 AM, Gary Tully wrote: inline On 18 May 2012 05:24, Geoffrey Arnold geoff...@geoffreyarnold.com wrote

Questions on upgrading to 5.6.0

We are upgrading from AMQ 5.4.0 to 5.6.0, and noticed two issues right off the bat: - The activemq-all-5.6.0.jar library is now bundled with the SLF4J Log4J binding, trumping the JDK 1.4 binding already in our classpath. As a workaround we have switched to using the individual libraries

Re: Messages stuck in queue

FWIW we experienced the same issue when using a single queue with selectors. Simply moving to multiple queues without selectors resolved the issue. Most definitely related to the default page size setting others have mentioned, but we didn't have time to experiment with different settings.

Re: ConcurrentModificationException in embedded 5.5.0 broker

We're having the same issue with SLF4J 1.5.11 (the version distributed with ActiveMQ 5.5.0). On Apr 8, 2011, at 7:35 AM, dcheckoway dchecko...@gmail.com wrote: I suppose I should also mention that we're using slf4j 1.6.1. Not sure if that has anything to do with this, since the stack trace

Re: Messages stuck in queue

Quick follow-up: After another restart, JMX reported the queue size as 75 for over a day, but now the queue size is -17. How reliable is this metric? On Dec 1, 2010, at 2:04 PM, Geoffrey Arnold wrote: Hello us...@! We have a queue defined in an embedded broker that when viewed through

Messages stuck in queue

Hello us...@! We have a queue defined in an embedded broker that when viewed through the JMX console appears to have 17 messages stuck on the queue. The application that is consuming the messages contains the embedded broker. We have a constant flow of messages that are being processed from

Re: Programmatically stopping and restarting network connector

. Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Sat, May 8, 2010 at 4:05 PM, Geoffrey Arnold geoff...@geoffreyarnold.com wrote: Looks like

Re: Programmatically stopping and restarting network connector

://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Mon, May 10, 2010 at 2:07 PM, Geoffrey Arnold geoff...@geoffreyarnold.com wrote: Hi Dejan, If you run the test, the second assertion (right before the finally block) fails. Could you clarify

Re: Programmatically stopping and restarting network connector

(); } }); assertNotNull(consumerJmsOperations.receive()); } } On May 5, 2010, at 12:42 PM, Geoffrey Arnold wrote: Issued opened with failing test: https://issues.apache.org/activemq/browse/AMQ-2722 Attaching JUnit test here too: NetworkOfBrokersTest.java On Apr 6, 2010, at 5:10 AM, Dejan

Re: Programmatically stopping and restarting network connector

Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Fri, Apr 2, 2010 at 11:16 PM, Geoffrey Arnold geoff...@geoffreyarnold.com wrote: Hi All! During upgrades we

Programmatically stopping and restarting network connector

Hi All! During upgrades we would like to be able to stop and restart the network connector between embedded brokers running in separate VMs. In the embedded broker of the producer VM we have a network connector pointing to the transport connector of an embedded broker in the consumer VM. I

Re: OutOfMemoryError when reconnecting forwarding bridge

Ok, looking forward to 5.3.1. Thanks Swen! On Dec 5, 2009, at 1:01 PM, smoc wrote: Seems to be the same bug as: http://issues.apache.org/activemq/browse/AMQ-2448 http://issues.apache.org/activemq/browse/AMQ-2448 -- View this message in context:

OutOfMemoryError when reconnecting forwarding bridge

Hi all, We have a forwarding bridge between an embedded broker in one VM and a remote broker in another VM using the examples from the network-of-brokers documentation[1]. While testing failover, we left the embedded broker VM running overnight but did not start the remote broker VM. NOTE:

Re: Strategies for purging internal consumer queue

about. It can impact performance though. See http://activemq.apache.org/what-is-the-prefetch-limit-for.html Geoffrey Arnold-2 wrote: Thanks Gary. Our Cucumber tests are really integration tests, so it would require a restart of the VM running the embedded broker. Is there anyway to disable

Re: Transactions and redelivery

it seems the transactional mode would be sufficient. It just so happens our previous messaging framework retried messages by placing them at the end of the queue so this is more of legacy support than anything. Regards Geoffrey Arnold-2 wrote: Hey Mark, We ended up opting to put

Re: Strategies for purging internal consumer queue

it is the session behavior that is under test? 2009/10/15 Geoffrey Arnold geoff...@geoffreyarnold.com Hi All, We are successfully using JMX to purge our queues in between our Cucumber-based test scenarios, however this does not clear the session's internal consumer queue. This can cause messages

Re: Transactions and redelivery

Hey Mark, We ended up opting to put the message back on the end of the queue instead of rolling back, but this leads to repeated reprocessing of the message. My guess is that you have solved this with metadata: Our framework is sophisticated enough to manage redeliveries in this way by

JMS bridge v. network of brokers

Hi All, I'm trying to form a topology where queues hosted on independent brokers (separate machines) are consolidated into a single queue on a central broker. Messages will be consumed by listeners on that central broker. Independent brokers will come on and off the network. Originally

Re: JMS bridge v. network of brokers

is also referred to as a forwarding bridge. See the following http://activemq.apache.org/networks-of-brokers.html AMQ 5.3 comes with a couple of example cfg files to set up a simple 2 node NoB. Joe http://www.ttmsolutions.com Geoffrey Arnold wrote: Hi All, I'm trying to form a topology

Strategies for purging internal consumer queue

Hi All, We are successfully using JMX to purge our queues in between our Cucumber-based test scenarios, however this does not clear the session's internal consumer queue. This can cause messages which have been delivered to the consumer's session but not yet consumed by the listener

Transactions and redelivery

Hi All, When a message is rolled back on a session, it appears that no other messages will be delivered to the consumer's listener for that session until the original message is consumed (committed). I believe that this is due to the session attempting to maintain message order, however