Hi!
I am using AMQ_SCHEDULED_DELAY when sending a message to ActiveMQ and found
that scheduler stores it data at activemq-data/scheduler. In jdbc
master-slave topology this data will be lost when master node goes down.
What is the best way to implement scheduler failover?
Thx!
--
View this
The only way to do this currently is to use a SAN or GFS - see
http://activemq.apache.org/shared-file-system-master-slave.html
On 2 Nov 2010, at 08:42, werdex wrote:
Hi!
I am using AMQ_SCHEDULED_DELAY when sending a message to ActiveMQ and found
that scheduler stores it data at
Thx for reply!
Maybe is it possible to continue to keep the messages in database
(oracle,ms-sql) , but use shared file system only for scheduler data
directory?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Scheduler-failover-in-Master-Slave-tp3023340p3023396.html
Sent
Yes - that would be possible - you can set the directory used for the scheduler
database in the activemq XML configuration file
On 2 Nov 2010, at 09:25, werdex wrote:
Thx for reply!
Maybe is it possible to continue to keep the messages in database
(oracle,ms-sql) , but use shared file
Hello all.
I'm working into the migration from activemq 4.1 to activemq 5.4.1. One
of the things we have noticed is a sensible growth in both memory and
number of thread usage of our application.
I would like to know if this is the expected behaviour, and also gain
some insights in what threads
I've just installed version 5.4.1 on Windows and altered the ProducerTool
example source code to produce MapMessages instead of TextMessages (patch
for ProducerTool.java at end of this email). When I run the producer
consumer pair from Ant as per the usual instructions, I see the 'produced'
Ok, i do have a somewhat contrived workaround. Basically, I decided to
cache selector string of any queue subscription (well vtopic queue)
that I intercept (BrokerFilter). Then I have modified
org
.apache
.activemq.broker.region.virtual.SelectorAwareVirtualTopicInterceptor
so that if
hi maciej,
that sounds interesting. would you mind sharing the filter and changes
to SelectorAwareVirtualTopicInterceptor?
On 11/02/2010 03:48 PM, Maciej Rakowicz wrote:
Ok, i do have a somewhat contrived workaround. Basically, I decided to
cache selector string of any queue subscription
Hello,
We recently upgraded from ActiveMQ 5.1 to ActiveMQ 5.4.1 and have noticed
some odd behavior in the web interface. The two most persistent issues are:
1) When selecting a message in one queue to be copied into another queue, it
does not appear in the other queue, yet the 'number of
