Hi,
We are using AMQ 5.7.0.1 and our broker memory is increasing slowly...
I noticed while monitoring with jconsole, that the TotalProducersCount is
increasing slowly.
queueProducers, tempQueueProducers, TopicProducers etc, are all with the
same number of producers...
Hence, I'm not sure where t
Unfortunately no (not yet).
Anyway, it's a clean Artemis installation of version 1.5.1, made by following
the user manual instructions at
https://activemq.apache.org/artemis/docs/1.5.1/using-server.html.
The installation was done by using a dedicated user and also the artemis java
process runs
Hello people
I started using ActiveMQ and the initialRedeliveryDelay and redeliveryDelay
properties of the policy did not work! Both assume 1 second
maximumRedeliveries is working! I searched the solution for many days and
did not find it. Can anybody help me?
Here's my settings:
pom:
Hi,
Yes these log messages appeared at the startup only. I had faced an issue
where activemq dumped 7gb file - tx-14693130-1483907222896.tmp in one of
the mkahadb directories when i tried to destroy a durable topic consumer
which was inactive for quite some time and had hit the memory threshold o
Yes if you have a ton of data on a durable subscription and delete the
durable it tends to write a large temp file because of the kahadb
index. Even though the temp file should be deleted automatically
after deletion this is certainly not ideal.
Right now there isn't really a good way to discard
the MQTT ProtocolManager does some playing with retaining, perhaps
there's something wrong with reloading from journal on retaining. I
was wondering if you could send us a test showing the issue with MQTT
so we could see if there's anything specific to your test while using
MQTT.
On Wed, Jan 11, 2
Hi Tim Bish ,
I read http://activemq.apache.org/how-do-i-use-ssl.html.My
configuration seems to be correct.I can connect java client to broker using
ssl certificate.I am trying with C client.Since it takes certificate in .pem
format I want to convert I followed the instruction given in
htt
Hi,
I created SSL certificates for C client and
activemq(apache-activemq-5.14.1)broker using the following link :
https://github.com/rethab/php-stomp-cert-example/blob/master/README.md
Then I used broker.ks and broker.ts as keystore and truststore for broker
and php-cliet-chain.pem as a clien
Hi,
I am currently developing an ActiveMQ broker plugin which is intercepted and
override the BrokerPluginSupport.preProcessDispatch() and
BrokerPluginSupport.send() methods to perform some operation on the messge
object. When I setup a scenario with an embedded broker with one producer on
the top
Thanks christopher for the explanation. This makes sense. What are the
timelines for ActiveMQ v5.15.0 release - mid year? I am asking because I
plan to upgrade to 5.14.3 and if this issue will be handled well in 5.15.0 i
would love to upgrade directly to 5.15.0.
Thanks,
Abhi
--
View this mess
It looks to me like the full message buffer (not just the body) is getting
returned to the client. Clebert I think you're right in that we do some
hackery to handle retained messages. I suspect this is where the error is.
Francesco could you create a JIRA with some reproducer steps and I'll aim
Bump. Any help appreciated :)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-question-on-JMS-clustered-topic-and-high-availability-tp4720803p4720983.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
when you have a topic subscription in cluster.. the message will be
copied to every subscription on the cluster connection (or network of
brokers)...
When you have the same subscription among different nodes.. (that
is... the same core-queue name on more than one node), then
load-balancing will h
Your reply is much appreciated. So crossing master/slave is only possible
in a colocated environment? If so I think that's doable in my situation.
"what you are looking is having a copy of the topic subscription on every
node, making it a single cluster among different nodes,"
Is there an example
You are using AWS. Do you have the storage disk? or is it transient?
What I have been suggesting to cloud user is to just monitor their
system, and have the system restarting itself in case of a failure.
That is the best scenario you can get since the infra-structure would
give you the needed HA.
It's hard to say an exact time frame. Finished new features would be
the driving force behind a 5.15.0 release as bug fixes are already
backported but right now there hasn't been much done to justify a
5.15.0 release. Most work has been focused on Artemis but I would say
that mid year sounds abou
Thanks for the response. The paired LiveA/BackupB + LiveB/BackupA is what I
was wondering out with the JMS clustered topic. I'd like to not rely on
infrastructure to restart because of the latency that involves - I'd like
to keep any hiccups to < 1 sec if possible.
On Wed, Jan 11, 2017 at 1:46 PM,
You are still bound to connect retries and TTLs. So I would say that a good
reaction time would be 30s. You can decrease that but I am not sure I
recommend it.
It's up to you thought. If I was implementing my own system I would prefer
the cloud infra since you are AWS. I believe that's what m
18 matches
Mail list logo
