Use Azure Service Bus with JMS

Artikkeli
11/15/2024

This article applies to: ✅ Version 4.19.0 ✅ Version 5.19.0

This article describes how to use Azure Service Bus with the JMS API integrated into the Spring JMS framework.

Core features

Passwordless connection

Passwordless connection uses Microsoft Entra authentication for connecting to Azure services without storing any credentials in the application, its configuration files, or in environment variables. Microsoft Entra authentication is a mechanism for connecting to Azure Service Bus using identities defined in Microsoft Entra ID. With Microsoft Entra authentication, you can manage Service Bus and other Microsoft services in a central location, which simplifies permission management.

How it works

Spring Cloud Azure first builds one of the following types of credentials depending on the application authentication configuration:

ClientSecretCredential
ClientCertificateCredential
UsernamePasswordCredential
ManagedIdentityCredential

If none of these types of credentials are found, the credential chain via DefaultTokenCredential is used to obtain credentials from application properties, environment variables, managed identity, or IDEs. For more information, see Spring Cloud Azure authentication.

Dependency setup

Add the following dependencies if you want to migrate your Spring JMS application to use Azure Service Bus.

<dependency>
    <groupId>com.azure.spring</groupId>
    <artifactId>spring-cloud-azure-starter-servicebus-jms</artifactId>
</dependency>

Configuration

The following table describes the configurable properties when using the Spring JMS support:

Property	Description
spring.jms.servicebus.connection-string	The Azure Service Bus connection string, for when you want to provide the connection string directly.
spring.jms.servicebus.topic-client-id	The JMS client ID. Only works for the `topicJmsListenerContainerFactory` bean.
spring.jms.servicebus.enabled	A value that indicates whether to enable Service Bus JMS autoconfiguration. The default value is `true`.
spring.jms.servicebus.idle-timeout	The connection idle timeout duration that indicates how long the client expects Service Bus to keep a connection alive when no messages are delivered. The default value is `2m`.
spring.jms.servicebus.passwordless-enabled	Whether to enable passwordless for Azure Service Bus JMS. The default value is `false`.
spring.jms.servicebus.pricing-tier	The Azure Service Bus Price Tier. Supported values are premium and standard. Premium tier uses Java Message Service (JMS) 2.0, while standard tier use JMS 1.1 to interact with Azure Service Bus.
spring.jms.servicebus.listener.reply-pub-sub-domain	A value that indicates whether the reply destination type is a topic. Only works for the `topicJmsListenerContainerFactory` bean.
spring.jms.servicebus.listener.phase	The phase in which this container should be started and stopped.
spring.jms.servicebus.listener.reply-qos-settings	Configures the `QosSettings` to use when sending a reply.
spring.jms.servicebus.listener.subscription-durable	A value that indicates whether to make the subscription durable. Only works for the `topicJmsListenerContainerFactory` bean. The default value is `true`.
spring.jms.servicebus.listener.subscription-shared	A value that indicates whether to make the subscription shared. Only works for the `topicJmsListenerContainerFactory` bean.
spring.jms.servicebus.pool.block-if-full	A value that indicates whether to block when a connection is requested and the pool is full. Set it to false to throw a `JMSException` instead.
spring.jms.servicebus.pool.block-if-full-timeout	The blocking period before throwing an exception if the pool is still full.
spring.jms.servicebus.pool.enabled	A value that indicates whether a `JmsPoolConnectionFactory` should be created, instead of a regular `ConnectionFactory`.
spring.jms.servicebus.pool.idle-timeout	The connection pool idle timeout.
spring.jms.servicebus.pool.max-connections	The maximum number of pooled connections.
spring.jms.servicebus.pool.max-sessions-per-connection	The maximum number of pooled sessions per connection in the pool.
spring.jms.servicebus.pool.time-between-expiration-check	The time to sleep between runs of the idle connection eviction thread. When negative, no idle connection eviction thread runs.
spring.jms.servicebus.pool.use-anonymous-producers	A value that indicates whether to use only one anonymous `MessageProducer` instance. Set it to `false` to create one `MessageProducer` every time one is required.
spring.jms.servicebus.prefetch-policy.all	The fallback value for the prefetch option in this Service Bus namespace. The default value is `0`.
spring.jms.servicebus.prefetch-policy.durable-topic-prefetch	The number of prefetch for durable topic. The default value is `0`.
spring.jms.servicebus.prefetch-policy.queue-browser-prefetch	The number of prefetch for queue browser. The default value is `0`.
spring.jms.servicebus.prefetch-policy.queue-prefetch	The number of prefetch for queue. The default value is `0`.
spring.jms.servicebus.prefetch-policy.topic-prefetch	The number of prefetch for topic. The default value is `0`.

Note

Spring JMS general configuration is omitted for short.

For more information, see Spring JMS Document.

Basic usage

Connect to Azure Service Bus JMS using passwordless

Configure the following properties in your application.yml file:

spring:
  jms:
    servicebus:
      namespace: ${AZURE_SERVICEBUS_NAMESPACE}
      pricing-tier: ${PRICING_TIER}
      passwordless-enabled: true

Important

Azure Service Bus JMS supports using Microsoft Entra ID to authorize requests to Service Bus resources. With Microsoft Entra ID, ensure that you've assigned the Azure Service Bus Data Owner role to the Microsoft Entra account you're currently using. For more information, see Assign Azure roles using the Azure portal.

Connect to Azure Service Bus with JMS use Managed Identity

To use the managed identity, enable the managed identity for your service and assign the Azure Service Bus Data Owner role. For more information, see Authenticate a managed identity with Microsoft Entra ID to access Azure Service Bus resources.
Configure the following properties in your application.yml file:
```
spring:
  cloud:
    azure:
      credential:
        managed-identity-enabled: true
  jms:
    servicebus:
      namespace: ${AZURE_SERVICEBUS_NAMESPACE}
      pricing-tier: ${PRICING_TIER}
      passwordless-enabled: true
```
Important

If you're using user-assigned managed identity, also need to add the property spring.cloud.azure.credential.client-id with your user-assigned managed identity client ID.

Connect to Azure Service Bus JMS using connection string

Add the following properties and you're good to go.

spring:
  jms:
    servicebus:
      connection-string: ${AZURE_SERVICEBUS_CONNECTION_STRING}
      pricing-tier: ${PRICING_TIER}

Connections

Spring Cloud Azure provides the following three Connection Factory options for connecting to Azure Service Bus JMS:

JmsPoolConnectionFactory: Set spring.jms.servicebus.pool.enabled=true or leave both pool and cache settings unset to use the default value. This factory maintains a connection pool with customizable options like spring.jms.servicebus.pool.max-connections. Additional pool configuration settings - prefixed with spring.jms.servicebus.pool. - are detailed in the Configuration section. This setup enhances performance by leveraging Azure Service Bus's load-balancing capability, distributing traffic across multiple endpoints.
CachingConnectionFactory: Set spring.jms.cache.enabled=true and leave spring.jms.servicebus.pool.enabled unset. This factory reuses a single connection for all calls to JmsTemplate, reducing the overhead of connection creation, which is ideal for low-traffic scenarios. However, this mode does not leverage Azure Service Bus's load-balancing capability.
ServiceBusJmsConnectionFactory: Set spring.jms.servicebus.pool.enabled=false and spring.jms.cache.enabled=false to use ServiceBusJmsConnectionFactory directly, with no pooling or caching. In this mode, each call to JmsTemplate creates a new connection, which can be resource-intensive and less efficient.

For optimal performance and load distribution, we recommend using JmsPoolConnectionFactory by setting spring.jms.servicebus.pool.enabled=true. Avoid wrapping a JmsPoolConnectionFactory with a CachingConnectionFactory or ServiceBusJmsConnectionFactory because this can negate pooling benefits and might result in holding inactive connections after they're evicted from the pool.