Confused about Jolokia and Artemis

I have a few servers (Ubuntu VMs) running Artemis 2.14. When I check the version of Jolokia through the console it shows Jolokia 1.6.2 However, I can also see that Jolokia is available through the same port as the Artemis console -- https://[host]:8443/jolokia -- and that it's version 1.3.5 (Which

Re: Optimizing for many short connections

22 at 5:07 PM Clebert Suconic wrote: > @Ben Warrick: BTW When I said "you are likely" hitting the bug, I was > just using polite words... > > > I am 100% sure you are hitting that condition by creating one session > per message. You should definitely look to upgrade or

Re: Optimizing for many short connections

ttps://netty.io/wiki/tcp-fast-open.html > > > > > > Given that Netty can makes use of it and Artemis can as well: if it's > not > > > present in the doc it means we need to expose it in the acceptor > > > configuration (for epoll) and...we love

Re: Optimizing for many short connections

figuration) or...submit a PR to let Artemis separate (multiple) > threads > > to accept connections but, as you said, this is just an anti-pattern and > in > > order to reduce the client code you can think about using a transparent > > connection pooling mechanism, instead. &g

Optimizing for many short connections

I'm running Artemis 2.14, and one of the systems publishing to it creates a lot of separate tasks -- from its perspective. I can see on Artemis that the Total connection count vs Total messages acknowledged is pretty close, so it's apparent that the client system is making use of the anti-pattern o

Dynamic queues with filters, question

I have an integration layer that I'm using to receive data. I'd like to publish this data to Artemis to make it available to multiple applications. The data comes from multiple sources, and the data has different classifications. So, a simple example would be banks and currency. I'm listening to m

Stability issue

I have a new instance of Artemis now two weeks in a production scenario. I'm using it as part of an integration layer between a website, inventory manager, and an ERP. The website published to an address where I have an interface pulling the messages from a queue and processing them through an API

Re: Artemis failed but HA secondary did not take over

roker(s) and explicitly setting max-size-bytes > and/or global-max-size for your use-case. > > > Justin > > [1] https://issues.apache.org/jira/browse/ARTEMIS-3021 > [2] https://issues.apache.org/jira/browse/ARTEMIS-3061 > > On Wed, Jan 20, 2021 at 12:15 PM Ben Warrick

Re: Artemis failed but HA secondary did not take over

ouldn't connect to the slave. > > I recommend you take a look at your global-max-size as well as your > max-size-bytes configuration as these are designed to help prevent OOME > when receiving lots of messages. > > > Justin > > On Wed, Jan 20, 2021 at 9:12 AM Ben Warri

Artemis failed but HA secondary did not take over

I had an incident last night. I can share the actual log files with anyone interested in seeing the full picture. Below is a summary. I also have OS resource tracking data. I have a pair of Artemis servers using a shared store -- an NFS mounted folder. My use case is enterprise integration. I use

Good monitoring practices, JMX

Hello, I'm trying to put together a good monitoring strategy to keep Artemis healthy. I set up Zabbix, which is working pretty well, and I'm using jconsole to explore the JMX MBeans and troubleshoot. Right now I only have two alerts. One that watech for the secondary cluster to come up, and sends