Re: ActiveMQ 5.4: Message transactions/history to be permanently stored

Hi Gary, Thanks alot for replying. Really appreciate it. I have some further questions below: 1) "you can listen to advisory messages and keep running counts or do the same via a broker plugin." -> what are advisory messages and how to listen to them. -> what broker plugins can i use for my purp

Re: ActiveMQ 5.4: Message transactions/history to be permanently stored

you can listen to advisory messages and keep running counts or do the same via a broker plugin. But if you want to ensure that the journal reflects the state, enable archiving with archiveDataLogs=true on the kahadb persistence adapter. You will then need to look at the kahaDB journal api to pars

Re: Fail over options when using JMS Bridge

If you set setMaximumRetries to 0, it should retry forever. On 26 April 2011 15:39, koevet wrote: > Hello, > I'm using Active MQ 5.5.0. > I have the following scenario: > I have created a JMS bridge between ActiveMQ and Weblogic 10.3. JMS Messages > sent to ActiveMQ get forwarded to Weblogic. No

Re: Large amounts of queues and topics

the selectors are run on the broker, but on only on the in-memory part of the queue. For this reason, if you have sparse selectors, you need to configure a large page size for the destination such that most of the pending messages can be in memory. The pageSize defaults to 200 and is configured vi

Re: Large amounts of queues and topics

Hi, I'm interested in similar scenario as well. Any advice would be appreciated. Could someone please confirm if I'm right or wrong on this. It seems to me that "selector" operation is done within MessageConsumer implementation. (i.e. ALL messages are still dispatched from Message Broker to Mes

Fail over options when using JMS Bridge

Hello, I'm using Active MQ 5.5.0. I have the following scenario: I have created a JMS bridge between ActiveMQ and Weblogic 10.3. JMS Messages sent to ActiveMQ get forwarded to Weblogic. No response needed. Everything works. Now, I would like to understand which kind of fail over options I do have

Failover issue in ActiveMQ

Hi , We have a cluster of two brokers with the below configuration. Broker A http://activemq.apache.org/schema/core"; brokerName="broker-A" dataDirectory="${activemq.base}/data"> Broker B http://activemq.apache.org/

RE: current thread's class loader is changed during onMessage of

Hi, something to add: The flow in AMQ: ThreadPoolExecutor: run PoolTaskRunner: run PoolTaskRunner: runTask ActiveMQSessionExecutor:iterate ActiveMQSessionExecutor:dispatch ActiveMQSessionConumer:dispatch ClientMessageListener: onMessage When I debug the PoolTaskRunner:run method when the onMessage

current thread's class loader is changed during onMessage of

Hi, I have a problem which will reproduce on AMQ 5.2.0 as well as 5.5.0 and I assume on every version. I am running a multi process environment, where the client and server processes communicate through ActiveMQ. Client is on top of tomcat 6.0.18, server is on top of Spring 2.5.6. I am using 2 w