Hi,
I'm a new user of ActiveMQ and I've some questions about the scalability.
I've found some tests the show activeMQ throughput (many senders and many
consumers). But I didn't find test showing how can ActimeMQ manage a large
number of subscribers of a topic.
I would like to send a msg for a l
I'm running the fuse 4.2.0-fuse-02-00 release.
It includes activemq 5.3.1 along with Camel 2.2 all running in ServiceMix.
The two work great together, but now I'm trying to use the
statisticsBrokerPlugin to query the number of messages on a queue.
I've attempted this several different ways in Ca
Forgive me if this is the wrong place to ask this question. Not sure if
questions about ActiveMQ-cpp wrappers should be directed to the mailing
list, but I kept getting here through the website.
I have a simple producer/consumer setup with topics. Everyone connects up
and messages are sent/recei
Hi All,
I am facing a very strange problem with ActiveMQ.
I have a java class that attaches itself to a queue. This class holds a
threadExecutor and once it gets a message, it uses the threadexecutor to run
a task with just arrived message.
It keeps track of how many threads are currently perf
Hi,
first of thanks very much for the prompt suggestions. I have enabled
Atomikos, ActiveMQ, and Spring JMS logging.
The posts below show the logs both for a transaction that succeeds and one
that fails. In both cases there is nothing on the queues to consume.
In both cases the transaction is
The actual root cause exception is set on the exchange after that
warning is logged, so it will be available from there.
On 1 June 2011 22:00, Brendan Long wrote:
> I'm working on a Camel route and I keep having error messages that look
> like this:
>
> TransactionErrorHandler WARN Transa
@Suneel
no need for doubts, cleanup and expiry will occur as expected but by
default expired messages are sent to the dead letter queue so they
will use up space until they are consumed.
You need to modify the default SharedDeadLetterStrategy and set
processExpired=false so that they don't consum
@James, yes it would, what would follow would be normal recovery, same
as on a restart.
On 2 June 2011 09:49, James Green wrote:
> +1 for that.
>
> What would happen in a snapshot freeze then restore to the journal file at
> present? Would KahaDB roll back those transactions?
>
> James
>
> On 2 J
well not quite an atomic write, but as close as one can get with java
io. Batch writes are serialised and followed by an fsync, so the
fsfreeze will either block the next write or the next fsync. Either
way is fine from a consistency point of view. The index is
checkpointed to the journal periodica
+1 for that.
What would happen in a snapshot freeze then restore to the journal file at
present? Would KahaDB roll back those transactions?
James
On 2 June 2011 00:19, Steve Smith wrote:
>
> A user-space KahaDB snapshotting tool would certainly be useful regardless.
>
> Cheers,
> Steve
>
10 matches
Mail list logo
