Re: How to get connections programmatically in Artemis

2025-07-31 Thread ski n
Note that you can also get a list of connections as JSON: ActiveMQServer activeBroker = broker.getActiveMQServer(); ActiveMQServerControlImpl manageBroker = activeBroker.getActiveMQServerControl(); String connectionsList = manageBroker.listConnectionsAsJSON(); Raymond On Thu, Jul 31, 2025 at 3:2

Re: ArtemisMQ branding

2025-04-25 Thread ski n
tbh ArtemisMQ sound pretty neat. Raymond On Fri, Apr 25, 2025 at 8:35 PM Justin Bertram wrote: > > However there's still 2 distinct broker versions, right? > > That's correct. There's ActiveMQ Classic and ActiveMQ Artemis. > > > How about just putting artemis on the bottom, or something of the

Better understanding performance tuning

2025-04-05 Thread ski n
Hi ActiveMQ community, I have an environment where I communicate a lot between Apache Camel and Apache ActiveMQ. Currently, I use Classic as broker, but I used Artemis in other environments before. Mostly I just take the default settings (with a few small tweaks) and let it run. Currently, I try

Re: ActiveMQ Artemis Release Schedule

2024-12-04 Thread ski n
You can also track upcoming features on the Jira of Apache (Just need an Apache account): https://issues.apache.org/jira/projects/ARTEMIS?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased Raymond On Wed, Dec 4, 2024 at 10:51 PM Justin Bertram wrote: > There'

Re: Question related to JDK

2024-11-28 Thread ski n
We have been running ActiveMQ 5 Classic a while with JDK 11 (Temurin). Now we are upgrading to ActiveMQ Classic 6.1.x and Artemis 2.38.0 while running it with JDK 21 (tested with OpenJDK, Temurin, Azul Zulu, and GraalVM). So far it's running fine. Raymond On Thu, Nov 28, 2024 at 7:37 AM wrote:

Re: Need help in upgrading activemq

2024-05-13 Thread ski n
Probably an issue with the version of SLFJ. See: https://stackoverflow.com/questions/20537459/java-lang-nosuchmethoderror-org-slf4j-spi-locationawarelogger-log Maybe you need to update other versions of your application (spring or the JDK itself), but it's recommended to take the newest version a

Re: feasibility of connecting ActiveMQ Artemis with IBM MQ

2024-03-29 Thread ski n
I once did a connection between Artemis and IBM MQ. The work I did is based on ActiveMQ & Camel and open source: https://github.com/assimbly/gateway https://github.com/assimbly/gateway/wiki/component-amqps https://github.com/assimbly/gateway/wiki/component-ibmmq It may help you. Raymond On Fr

Re: Xbean with ActiveMQ Classic 6

2023-12-05 Thread ski n
Short update on the upgrade to AMQ 6. After checking the dependency tree with Gradle I found out that ActiveMQ was downgraded to 5.18.3. I changed that and now it works fine.Thnx Raymond On Tue, Dec 5, 2023 at 10:04 AM ski n wrote: > And does there is also a new version of the activemq.

Re: Xbean with ActiveMQ Classic 6

2023-12-05 Thread ski n
o the Jakarta project as managed by the Eclipse foundation. Raymond On Tue, Dec 5, 2023 at 9:50 AM ski n wrote: > I think you are right. I for example, thought I updated all dependencies > to Jakarta, but still got: > > jakarta.servlet.ServletException: Handle

Re: Xbean with ActiveMQ Classic 6

2023-12-05 Thread ski n
gt; I suspect a classpath issue. > > If you can share a simplified code project via GitHub, I’d be happy to > look at it this week. > > Thanks, > Matt Pavlovich > > > On Dec 4, 2023, at 4:16 PM, ski n wrote: > > > > I'm currently upgrading to the new

Xbean with ActiveMQ Classic 6

2023-12-04 Thread ski n
I'm currently upgrading to the new ActiveMQ 6 (from 5.18.3 to 6.0.1). I'm starting an embedded with the help of xbean: https://activemq.apache.org/broker-xbean-uri Using the " xbean:file:filePathResource ". My code is like this: //get the path of activemq.xml file String brokerPath = brokerFil

Re: Jakarta dependencies

2023-11-04 Thread ski n
t; If you add in the Jakarta-based broker it can expand depending on if you > are using JDBC or other things (web console uses Jakarta Servlet, etc). > > -Matt Pavlovich > > > > On Nov 3, 2023, at 3:21 AM, ski n wrote: > > > > I'm planning to move to Jakart

Jakarta dependencies

2023-11-03 Thread ski n
I'm planning to move to Jakarta namespace (JEE10). What I understand is: 1. ActiveMQ Classic Server: Jakarta is not supported (but will be soon from version 6). 2. ActiveMQ Classic Client: Jakarta is supported. 3. ActiveMQ Artemis Server: Jakarta is supported. 4. ActiveMQ Artemis Client: Jakarta i

Re: Native Oauth/OIDC integration in ActiveMQ

2023-11-01 Thread ski n
What I know from my time as a consultant is that it often goes like this. The company: 1. Requirement 1: We need secure authentication. 2. Requirement 2: We need to comply with standards. 3. Requirement 3: We need a technology-neutral way to authenticate. The architects: The conclusion is that

Re: Jakarta namespace on the broker

2023-06-19 Thread ski n
ively 5.19.0). > > ActiveMQ 5.18.x LTS >+ JDK 11 >+ javax.jms >+ JMS 2.0 >+ Spring 5.x > > ActiveMQ 5.19.x >+ JDK 17 >+ jakarta.jms >+ Jakarta Messaging 3.x >+ Spring 6.x > > Thanks, > Matt Pavlovich > > > On Jun 19, 20

Jakarta namespace on the broker

2023-06-19 Thread ski n
For both the Classic (Since 5.18.0) and Artemis (Since 2.17.0) there is support for the Jakarta namespace in the client: 1. Classic: https://mvnrepository.com/artifact/org.apache.activemq/activemq-client-jakarta 2. Artemis: https://mvnrepository.com/artifact/org.apache.activemq/artemis-jakarta-cli