Thank you Tim,
After I changed the kubernetes services that expose 8161 from ClsusterIP to
NodePort, i setup port forward to the exposed port (8161) but i am not able
to reach the console, here is the config and the cmd i used:
apiVersion: v1
kind: Service
metadata:
creationTimestamp:
I don't know of any way to *automatically* tie a web application's
life-cycle to that of the broker. This should be possible manually, though.
You could create your own "middle-man" bean of sorts that registers itself
with the broker using a
org.apache.activemq.artemis.core.server.ActivateCallback
For what it's worth, this situation should be vastly improved since 2.16.0
where dbcp2 was incorporated for connection management. See ARTEMIS-2823
[1] for more details.
Justin
[1] https://issues.apache.org/jira/browse/ARTEMIS-2823
On Wed, Apr 22, 2020 at 9:45 AM ChrisSu wrote:
> I exactly
What exact configuration did you try in ActiveMQ Artemis'
logging.properties? Did you receive any kind of error message?
Justin
On Mon, Dec 16, 2019 at 9:15 AM vlk wrote:
> Hello,
> I would send logs from artemis instance to central Graylog. Other
> Jboss/wildfly instances can send server
Hello
A new queue is added in the master node. When the master and slave switch, the
queue will appear in the slave node; After deleting the queue at the master
node and after the master-slave switch, the queue still exists at the slave
node. Is there no data synchronization during deletion?
Well, I didnt create it so much as update the description to repurpose
it rather than simply close it hehe.
On Mon, 23 Aug 2021 at 09:34, Robbie Gemmell wrote:
>
> Technically I updated it in both, I created ARTEMIS-3421 and made the
> change against it so its in the next release notes, and also
The first bit is slightly more nuanced meaning there is another
possibility (which is what actually occurred in ARTEMIS-3421), so I
would state it a little differently:
Change the hostname value that is being connected to in the broker
config, so it can match against the existing certificate
Technically I updated it in both, I created ARTEMIS-3421 and made the
change against it so its in the next release notes, and also mentioned
ARTEMIS-3367 so it can also be seen by anyone happening across the
original change via there.
I tweaked the default doc and clarified what the setting does
Justin,
You just saved me a lot of time, thx!
FYI, I see that Robbie updated the documentation on 18-aug, but in ARTEMIS-3421.
e.
-Oorspronkelijk bericht-
Van: Justin Bertram
Verzonden: maandag 23 augustus 2021 03:51
Aan: users@activemq.apache.org
Onderwerp: Re: SSL error as of
