Hi,
I have broker that runs with increasing journal logs file with mKahadb store
for each destination.
One of the queue - journal logs are keep increasing overtime.
The strange part is that - everytime I restart activemq, these journal log
files get deleted.
To me, it looks like the message
We seems to experience the same issue upgrading from 5.6.0 to 515.8, but in
our case we use SQL database as a message store. As it was mentioned and
confirmed by us KahaDB has a fallback capability when it encounter older
(Version 6) of OpenWire.
Unfortunately, it looks like for SQL databases there
I have used QPID JMS as an ActiveMQ client with no issues so would recommend
you persevere with it.
-Original Message-
From: cooshal
Sent: 17 April 2019 13:51
To: users@activemq.apache.org
Subject: RE: Invoking JMS API with JMS 2.0, ActiveMQ and osgi (karaf)
I just had a quick look at Q
I just had a quick look at QPID JMS example. Also, I tried out a simple
example to browse an ActiveMQ queue. I am not able to get the intended
result. I am getting an empty enumerator. Could be possible that I might
have misconfigured something.
Thank you for suggesting this alternative. I need to
A possible option is to use the QPID JMS driver - this is a v2.0 driver - with
Active MQ v5. It uses AMQP to communicate with Active MQ instead of Openwire.
-Original Message-
From: cooshal
Sent: 17 April 2019 08:32
To: users@activemq.apache.org
Subject: Invoking JMS API with JMS 2.0, Ac
I have a scenario where I cannot switch to Artemis right now. And following
up with several posts, I understood that it gets tricky for ActiveMQ to
communicate with JMS 2.0.
Because of some limitations in Jolokia api
(http://activemq.2283324.n4.nabble.com/Is-it-possible-to-retrieve-more-than-400-m
