Hi,
Is there a way to increase kahadb read/write threads and ActiveMQ task
threads? If there is a pool, can we configure the thread pool size ?
ActiveMQ Journal Checkpoint Worker, ActiveMQ Data File Writer, KahaDB
Scheduler
and
ActiveMQ BrokerService[mqbrokerprod] Task-24650
Thanks,
Anuj
--
No one??
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Log4j2-ActiveMQ-JMS-Appender-Empty-body-received-in-Stomp-Client-tp4695855p4696078.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
What you describe matches what I've always understood based on answers from
people on here (and I've never heard anyone say that the behavior is
different for any of the data store types), but I can't claim any firsthand
knowledge so if that's not right hopefully someone else will say so.
Tim
On
Let’s say you have a queue with 1M items.. they are all low priority. Then
you add a high priority entry.
I believe, due to message cursors, that it won’t be executed until it’s
read into the “maxPageSize window”.
Is this correct or does it depend on the underlying store?
KahaDB and LevelDB coul
Thanks, Tim. Actually, it has nothing to do with activemq broker running in
Windows or linux. It is the missing of commit() call after
MessageProducer.send(TextMessage) in client code that caused the problem
when the transactional session is set up to create the producer.
Regards.
--
View t
I'm glad you found a fix.
If I understand correctly, the broker accepts those messages with an open
transaction when run under Windows but not under Linux. That sounds very
unexpected given that the broker is a Java process that should run
identically on any O/S, and it would indicate a bug in Ac
On 05/01/2015 06:55 AM, MarcoM wrote:
> Hi,
>
> We want to use the JMSActiveMQBrokerInTime/OutTime to do performance
> testing.
> The NMS .NET API (C#) doesn't provide these on the IMessage Interface.
> However, the Message classes implement them (BrokerIntime/OutTime).
>
> We now use reflection, b
Thanks for the reply, Tim. Days and weekend hours were spent in the
investigation of many possible causes of this issue. Eventually, I found
that the transaction was turned on for the session while the commit() was
never called. That is the root cause of the issue, very simple.
However, I just co
Hi,
We want to use the JMSActiveMQBrokerInTime/OutTime to do performance
testing.
The NMS .NET API (C#) doesn't provide these on the IMessage Interface.
However, the Message classes implement them (BrokerIntime/OutTime).
We now use reflection, but I think these properties should be exposed on the