One warning about using the activemq scheduler is that it requires the use
of KahaDB. It doesn’t yet support LevelDB (or replication).
So if you go down the scheduler path, you’re stuck with KahaDB…
At least for the foreseeable future.
On Thu, May 21, 2015 at 1:14 AM, contezero74 wrote:
> Hi E
On May 25, 2015 2:51 AM, "contezero74" wrote:
>
> Hi Tim,
> your suggestion was one of the first tentative we perform: but the result
> doesn't change. The problem seems very related to the use of the ActiveMQ
> schedule-area with a great amount of messages.
My suggestion was that you subdivide y
Hi ActiveMQ gods,
Another ping!
Is there any suggestion on what is a good estimate for the number of
consumers/producers on a single connection?
Thanks,
Abhi
--
View this message in context:
http://activemq.2283324.n4.nabble.com/No-of-consumers-per-connection-in-ActiveMQ-tp4696635p4696903.ht
Hi Tim,
your suggestion was one of the first tentative we perform: but the result
doesn't change. The problem seems very related to the use of the ActiveMQ
schedule-area with a great amount of messages.
At the moment, we are implementing a work-around based on persistence-queues
and application ti