Re: Artemis EmbeddedActiveMQ with jolokia

To run Jolokia you need an HTTP server. This is not provided by EmbeddedActiveMQ, but it is provided in the standalone distribution (i.e. via Jetty). If you're running embedded you still have the option to access management operations directly (e.g. if your app is in the same JVM), via JMX, or via

Re: Practical limit on #queues in Artemis

There is certainly a practical limit, but I doubt anybody has a clear view of what it is. I think you're more likely to hit pain points with management (e.g. the web console) before the queues themselves cause problems. Justin On Fri, Nov 4, 2022 at 2:16 PM John Lilley wrote: > Greetings, > >

Re: Artemis management API: getting message counts

Currently there's no way to differentiate between “queue does not exist” and other errors due to the way the broker handles the underlying exception when retrieving the attribute's value. However, you can use the createQueue method of ClientSession with some exception handling before you invoke the

RE: Artemis: How to make maximally resilient/retrying connection

Thanks! [rg] John Lilley Data Management Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761 | john.lil...@redpointglobal.com From: Roskvist Anton Sent: Tuesday,

Re: ActiveMQ 5.16.5 with TLS under FIPS

Hello, I've also tried an alternative approach. I have defined an SSL Context bean like this: [image: image.png] But when I try to point the SSLContext attribute to it like this: [image: image.png] It tells me: "Cannot convert value of type 'java.lang.String' to required type 'javax.net.ssl

ActiveMQ 5.16.5 with TLS under FIPS

Hello, I'm trying to configure TLS/SSL connectors using ActiveMQ 5.16.5 under FIPS.I'm using the following SSL Context configuration: [image: image.png] When I do that, an exception is thrown at startup which boils down to: "Transport Connector could not be registered in JMX: java.io.IOExce

Re: How to revoke write access to Acceptors folder in ActiveMQ Artemis Management Console(Jolokia)

The management.xml file controls RBAC for *all* MBeans, not just those for addresses. You can therefore take the name of the MBean and restrict method and attribute access to whatever roles you like, e.g.: With this configuration only users in the role "amq" will

Re: Slack Channel Request

Done. Justin On Tue, Nov 8, 2022 at 10:46 AM Ekta Awasthi wrote: > Hi, > > Please add me to the asf slack channel. Thank you! > > Ekta Awasthi, > Engineer, EAI Operations & Support | Office Depot, Inc. > 6600 North Military Trail | Boca Raton, FL 33496-2434 > Office: 561-438-3552 | Mobile: 206

Slack Channel Request

Hi, Please add me to the asf slack channel. Thank you! Ekta Awasthi, Engineer, EAI Operations & Support | Office Depot, Inc. 6600 North Military Trail | Boca Raton, FL 33496-2434 Office: 561-438-3552 | Mobile: 206-966-5577 | ekta.awas...@officedepot.com -- T

How to revoke write access to Acceptors folder in ActiveMQ Artemis Management Console(Jolokia)

Hello All, Seeking some guidance on how to revoke all the write access to Artemis Management Console(Jolokia). I understand we can control the rbac for the addresses by playing around in the management.xml but I am unable to determine on how to control the acceptors folder which includes the Ar

Hawtio/Jolokia CORS Requests

Hello, I'm trying to display queue status on an external webpage. Sadly, I can't seem to be able to get the unauthenticated CORS Preflight (OPTIONS) requests working, even though my broker is set up for guest access. Is there something I am missing? Thanks in advance Konstantin

Re: Artemis plug-in missing console when deployed in kubernetes

Hi Domenico, I was on holiday so that is why I didn't respond to your email sooner. The console service is deployed as: apiVersion: v1 kind: Service metadata: name: artemis-console labels: name: artemis spec: type: NodePort ports: - port: 80 targetPort: 8161 selector: nam

Re: Slack channel request

Done. Justin On Tue, Nov 8, 2022 at 4:33 AM Thomas Wahlberg wrote: > Hi, > please add me to the asf slack channel. Thank you ! > > -- > > Thomas Wahlberg > Chief Technology Officer > Quriiri / NextUp Oy > Puh. +358407031990 > thomas.wahlb...@quriiri.fi >

Re: Artemis: Artemis crashing and restarting randomly due to IO timeout

Thanks for your reply. We can indeed update to 2.20.0 and we're moving forward with this now. Newer versions seemed to have new possible issues so we'll try with 2.20.0 for starters. On Tue, Nov 8, 2022 at 12:52 PM Roskvist Anton wrote: > Hello Thomas, > > I might be mistaken but I believe this

RE: Artemis: Artemis crashing and restarting randomly due to IO timeout

Hello Thomas, I might be mistaken but I believe this has been fixed in broker version 2.20.0... it might be a good idea to update the broker version regardless since there has been quite a few bug fixes, added features and improvements made since 2.19.0. Be sure to follow the "Versions" documen

RE: Artemis: How to make maximally resilient/retrying connection

Hello John, I believe the parameter you are looking for is: "initialConnectAttempts=-1" in addition to what you have already configured. The default value is 0, meaning try once and throw an exception if that does not work (which is what you are seeing in your post). Br, Anton From: John Lill

Slack channel request

Hi, please add me to the asf slack channel. Thank you ! -- Thomas Wahlberg Chief Technology Officer Quriiri / NextUp Oy Puh. +358407031990 thomas.wahlb...@quriiri.fi

Artemis: Artemis crashing and restarting randomly due to IO timeout

Hi, we're using artemis 2.19.0 and we've noticed this is happening randomly. Sometimes it happens twice per day, sometimes once a month. It doesn't seem to be related to any cron jobs or any server load. Sometimes during the night, sometimes during the day. We're using Python with Artemis. The serv