Thanks a lot for the time you take Justin here.
Bellow information you requested
> Le 15 mars 2023 à 20:10, Justin Bertram a écrit :
>
> - How many clients will be using the edge broker, and how will they be
> using it (e.g. consumer, producer, protocol, multicast, anycast, etc.)?
On the centr
The business use-case isn't my primary concern. In order to make a
recommendation I need to know exactly how you want to use the broker. Some
questions to answer:
- How many clients will be using the edge broker, and how will they be
using it (e.g. consumer, producer, protocol, multicast, anycast
The message that will pass between instances are robots work orders in one way
and robots feedback in the other way
All of them are fixed robots (not automotive) and with on prem safety, not
dependent of any networks
Order are basic JSON document with list of instructions to pass once, and the
I'm not sure what exactly you're doing on your edge node so it's hard to
make a recommendation.
Justin
On Wed, Mar 15, 2023 at 1:07 PM Yoann Gini wrote:
> Thanks a lot for that feedback!
>
> Between the three option (bridges, federation, and broker connection) what
> would be the most suited f
Thanks a lot for that feedback!
Between the three option (bridges, federation, and broker connection) what
would be the most suited for a configuration only at the edge side?
All our edges have a certificate available published by a private CA, ideally I
would like my central instance to be wit
Thanks for following up!
Justin
On Wed, Mar 15, 2023 at 12:56 PM prateekjai...@gmail.com <
prateekjai...@gmail.com> wrote:
> Hi All,
>
> I am able to fix this issue. Posting my solution here, just in case anyone
> else faces a similar issue. I converted deployment to a statefulset (to get
> pr
Hi All,
I am able to fix this issue. Posting my solution here, just in case anyone
else faces a similar issue. I converted deployment to a statefulset (to get
predictable names). Then used headless services for each pod. This enabled
both master and slave pods to lookup each other just by pod nam
The WARN messages about ActiveMQShutdownException are likely a symptom and
not a cause of the broker shutdown. Those exceptions are being thrown
because a few threads are still trying to access the journal after it's
been shut down (as part of the overall broker shutdown process). You'd need
to pro
The edge use-case with substantial hardware is quite different from the
classic IoT use-case. Also, the fact that you want to use messaging between
clients on the edge device is also a significant difference. Therefore, my
answer certainly would change given that the underlying assumptions from my
ActiveMQ "Classic" moved to Log4j2 in 5.17.0 so you'll need to replace your
existing log4j.properties with an equivalent log4j2.properties file (e.g.
the one shipped with 5.17.4).
Justin
On Wed, Mar 15, 2023 at 11:04 AM ABURTO, BRUNO M CTR USAF ACC 99 RS/MPC
wrote:
> 5.16.5
>
> -Original M
5.16.6 would use the same log4j configuration file, its still using
reload4j (log4j 1.x fork) as before.
5.17.x uses Log4j 2, so you would need to use the newer log4j2 config
file to configure things.
On Wed, 15 Mar 2023 at 16:04, ABURTO, BRUNO M CTR USAF ACC 99 RS/MPC
wrote:
>
> 5.16.5
>
>
5.16.5
-Original Message-
From: Justin Bertram
Sent: Wednesday, March 15, 2023 8:55 AM
To: users@activemq.apache.org
Subject: Re: [URL Verdict: Neutral][Non-DoD Source] Re: Re: Query on OracleJava
alternative for ActiveMQ
Looking back through the email thread I don't see a clear indica
Looking back through the email thread I don't see a clear indication of
which version you're upgrading from. Can you clarify this for me?
Justin
On Wed, Mar 15, 2023 at 10:51 AM ABURTO, BRUNO M CTR USAF ACC 99 RS/MPC
wrote:
> Configuration file
>
> -Original Message-
> From: Justin Ber
Hi Justin,
Thanks for replying, I think artemis is failing to lookup POD by its name
because we cannot just get POD IP just by its name. Given below is the
error which is getting repeated in logs:
2023-03-15 10:04:06,611 INFO [org.apache.activemq.artemis] AMQ241002:
Artemis Jolokia REST API ava
We recently encountered a fatal error in which Artemis stopped. Can anyone
help explain how we might have got here? Does this indicate issues with
journal storage?
I don’t expect we’ll find a smoking gun, but perhaps you can suggest other log
entries to look for or other diagnostics to captur
Configuration file
-Original Message-
From: Justin Bertram
Sent: Wednesday, March 15, 2023 8:06 AM
To: users@activemq.apache.org
Subject: Re: [URL Verdict: Neutral][Non-DoD Source] Re: Re: Query on OracleJava
alternative for ActiveMQ
Are you asking about the logs themselves or the Log4
I just need a way to reproduce what you're seeing so once you get your
reproducer in order let me know. Thanks!
Justin
On Wed, Mar 15, 2023 at 9:36 AM Oliver Lins wrote:
> Hi Justin,
>
> thank you for your fast reply.
>
> > Would it be possible for you to work up a way to reproduce the
> beha
Are you asking about the logs themselves or the Log4j configuration file?
Justin
On Wed, Mar 15, 2023 at 9:59 AM ABURTO, BRUNO M CTR USAF ACC 99 RS/MPC
wrote:
> Do old Log4j files need to be deleted after updating to 5.16.6 or 5.17.4?
>
> -Original Message-
> From: Justin Bertram
> Se
Do old Log4j files need to be deleted after updating to 5.16.6 or 5.17.4?
-Original Message-
From: Justin Bertram
Sent: Tuesday, March 14, 2023 11:24 AM
To: users@activemq.apache.org
Subject: [URL Verdict: Neutral][Non-DoD Source] Re: Re: Query on OracleJava
alternative for ActiveMQ
N
Hi Justin,
thank you for your fast reply.
> Would it be possible for you to work up a way to reproduce the
behavior you're seeing?
Yes, I can reproduce the behavior. I have simplified producer and
consumer Java code to reproduce.
The code is not yet the bare minimum necessary to work, but I ca
ActiveMQ Artemis offers JGroups integration for cloud use-cases such as
yours, but, generally speaking, we don't really provide support for JGroups
in the ActiveMQ community since we don't maintain the JGroups code-base and
don't know its inner workings.
That said, I would suggest that the JGroups
Based on your description, attached configuration, and logs I don't see
anything wrong, per se. Would it be possible for you to work up a way to
reproduce the behavior you're seeing?
Do you ever have more than 1 producer? If so, is the order-of-creation only
essential per producer or is it essenti
Hi,
we are using Artemis with the following setup:
- 2 independent broker instances (on 2 hosts)
- a cluster configuration to create a Core bridge between both instances
(no failover, no HA)
- multiple JMS clients produce and consume AMQP messages using topics
- the clients do a failover themse
Hi All,
How are you? I am a bit confused about the errors reported by artemis slave
instance (running in clustered mode using jgroups). I might be missing
something here so please bear with me.
Deployment details: I am running 2 pods of artemis in master/slave
configuration in k8s. It supports NF
24 matches
Mail list logo
