Spring Boot 3 is about to reach its “end of non-commercial support”. What does that mean for MQ’s support of the Spring Boot environment?
Continue reading “EoL: MQ with Spring Boot 3”This post was last updated on June 16th, 2026 at 10:51 am
Messaging, Music and Moving Around
Spring Boot 3 is about to reach its “end of non-commercial support”. What does that mean for MQ’s support of the Spring Boot environment?
Continue reading “EoL: MQ with Spring Boot 3”This post was last updated on June 16th, 2026 at 10:51 am
Previous articles in this series have shown OpenTelemetry (OTel) Context propagation for MQ applications in different languages.
This article is rather different. It shows the results of experiments I made with adding OTel tracing to the IBM MQ Kafka Connectors.
Continue reading “OTel Context Propagation: part 6 – MQ Kafka Connectors”This post was last updated on May 11th, 2026 at 03:55 pm
The first pre-release version of Spring Boot 4 (milestone 1) has just been published. What does it mean for MQ’s support of the Spring Boot environment?
Continue reading “MQ with Spring Boot 4”This post was last updated on August 27th, 2025 at 09:05 am
A previous article described some new sample programs showing the use of the MQ Spring Boot starter with transactions. There is a further similar sample now available, using a different transaction manager: Narayana.
Continue reading “MQ Spring Boot Starter: More on global transactions”This post was last updated on March 9th, 2025 at 12:20 pm
Previous articles in this series have shown OpenTelemetry (OTel) Context propagation for Node.js, Go and C/C++ MQ applications. You should read the first article for an introduction and explanation of the scenarios and problems that need solutions.
This (final?) entry discusses JMS applications.
Continue reading “OTel Context Propagation for MQ Applications: part 3 – JMS”This post was last updated on November 21st, 2024 at 07:15 am
The MQ JMS packages have options to permit configuration of internal tracing and related logging features. While debugging a recent project, I wanted to look at traces of both the MQ library, and some of the surrounding Spring behaviour. While possible, it was not as convenient as I would have liked. So I’ve added some new options that simplify tracing MQ JMS apps in Spring.
Continue reading “Tracing MQ JMS apps in Spring”This post was last updated on February 21st, 2025 at 07:25 am
Spring Boot 2 has now reached its “end of non-commercial support“. The lifecycle for that project is set by Spring’s owners; a major release typically has 2 years of open support before moving into a longer-term paid-for regime.
Continue reading “MQ JMS and Spring: Spring Boot 2 now at end of regular support”This post was last updated on January 15th, 2024 at 02:15 pm
A recent Idea opened against MQ asked for the ability to store JMS resources using a secure connection to LDAP servers. All the current LDAP support for JMSAdmin and Explorer is documented using the plaintext protocol, but could we use a TLS-protected connection? My first thought was that this was likely to be impossible without changing something – albeit likely small – in the product code. But as I needed to get an LDAP server running locally for other reasons, I thought I’d give it a go to see if my guess was right. It wasn’t; and so here’s how you can do it yourself.
Continue reading “JMS, JNDI and LDAPS”This post was last updated on February 3rd, 2023 at 08:31 am
I wrote recently about the support for Jakarta Messaging that is part of IBM MQ 9.3 and work to integrate it with Spring. At that point, I gave the mq-jms-spring-boot-starter a pre-release version number as there was not a formal version of the Spring Framework and Spring Boot packages. But that changes this week, with the release of Spring Boot 3.0.0. And so there is now a corresponding MQ release of the starter package, also version 3.0.0 to match.
> Task :bootRun . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v3.0.0) 2022-11-25T12:06:23.591Z INFO 1091972 --- [ main] sample3.Requester : Starting Requester using Java 17.0.5 with PID 1091972 (mq-jms-spring/samples/s3.jms3/build/classes/java/main started by metaylor in mq-jms-spring/samples/s3.jms3) 2022-11-25T12:06:23.596Z INFO 1091972 --- [ main] sample3.Requester : No active profile set, falling back to 1 default profile: "default" ...
Aside to the aside: this latest version of the MQ Boot Starter has new optional configuration parameters providing the equivalent of the -D command-line options that you might use for defining location and credentials for TLS keystores. Look at the ibmmq.jks parameters.
This post was last updated on November 26th, 2022 at 02:48 pm
One of the features of the newly-released MQ 9.3 is support for JMS 3, also known as Jakarta Messaging. There will be more information elsewhere about what that means for standalone JMS programs. There continues to be a JMS 2 package, of course, for ongoing compatibility. But JMS 3 introduces incompatibilities that mean that we need updated versions of other components to match if you want to move up to newer standards. This post will talk about supporting MQ Jakarta JMS in Spring Boot.
I’ll also discuss the issues I had when developing the new version – the annoying incompatible tooling upgrades I had to work through.
Continue reading “Supporting MQ Jakarta JMS in Spring Boot”This post was last updated on June 30th, 2022 at 07:53 am