Implement comprehensive JMS ConnectionFactory configuration for Service Bus #47950

Copilot · 2026-02-10T02:11:08Z

Plan: Change sender's default JmsConnectionFactory to CachingConnectionFactory

Understanding:

Currently, when spring.jms.servicebus.pool.enabled and spring.jms.cache.enabled are not set, both sender and receiver use ServiceBusJmsConnectionFactory
This is inefficient for senders using JmsTemplate as each send creates and closes a connection
The fix: Use CachingConnectionFactory by default for the sender side

Implementation Strategy:

Modify ServiceBusJmsConnectionFactoryConfiguration.java to implement complete configuration matrix
Modify ServiceBusJmsContainerConfiguration.java to match all scenarios
Add comprehensive test coverage for all 9 scenarios
Add JavaDoc tables to sender and receiver configurations
Update CHANGELOG.md with detailed configuration table and rules
Implement proper fallback logic when required classes not in classpath
All tests passing (77 JMS tests)
Fix checkstyle linting errors (operator wrapping)
Address code review feedback:
- Improved fallback logic to immediately return when requested classes missing
- Memoized ALL dedicated receiver ConnectionFactory types to avoid duplicate instances
- Enhanced fallback tests to validate real scenarios
- Implemented lifecycle management with DisposableBean
- Fixed CHANGELOG typo
- Added comprehensive receiver ConnectionFactory tests that verify actual types and instances

Original prompt

This section details on the original issue you should resolve

<issue_title>[FEATURE REQ] Change sender's default JmsConnectionFactory from ServiceBusJmsConnectionFactory to CachingConnectionFactory</issue_title>
<issue_description>## Current behavior

	Property (spring.jms.servicebus.pool.enabled and spring.jms.cache.enabled) not set or set to false	Property (spring.jms.servicebus.pool.enabled or spring.jms.cache.enabled) set to true
sender side	ServiceBusJmsConnectionFactory	CachingConnectionFactory or JmsPoolConnectionFactory
receiver side	ServiceBusJmsConnectionFactory	CachingConnectionFactory or JmsPoolConnectionFactory

Expected behavior

Comment from @vinaysurya

If we don't use a CachingConnectionFactory on Sender side, I'm afraid when using JMSTemplate every send from Spring SDK will create and close a connection which will be very inefficient.

	Property (spring.jms.servicebus.pool.enabled and spring.jms.cache.enabled) not set or set to false	Property (spring.jms.servicebus.pool.enabled or spring.jms.cache.enabled) set to true
sender side	CachingConnectionFactory	CachingConnectionFactory or JmsPoolConnectionFactory
receiver side	ServiceBusJmsConnectionFactory	CachingConnectionFactory or JmsPoolConnectionFactory

Relate codes

azure-sdk-for-java/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java

Lines 29 to 48 in d9d47b6

    
           JmsListenerContainerFactory<?> jmsListenerContainerFactory( 
        
               DefaultJmsListenerContainerFactoryConfigurer configurer, ConnectionFactory connectionFactory) { 
        
               DefaultJmsListenerContainerFactory jmsListenerContainerFactory = new DefaultJmsListenerContainerFactory(); 
        
               configurer.configure(jmsListenerContainerFactory, connectionFactory); 
        
               jmsListenerContainerFactory.setPubSubDomain(Boolean.FALSE); 
        
               configureCommonListenerContainerFactory(jmsListenerContainerFactory); 
        
               return jmsListenerContainerFactory; 
        
           } 
        
           @Bean 
        
           @ConditionalOnMissingBean(name = "topicJmsListenerContainerFactory") 
        
           JmsListenerContainerFactory<?> topicJmsListenerContainerFactory( 
        
               DefaultJmsListenerContainerFactoryConfigurer configurer, ConnectionFactory connectionFactory) { 
        
               DefaultJmsListenerContainerFactory jmsListenerContainerFactory = new DefaultJmsListenerContainerFactory(); 
        
               configurer.configure(jmsListenerContainerFactory, connectionFactory); 
        
               jmsListenerContainerFactory.setPubSubDomain(Boolean.TRUE); 
        
               configureCommonListenerContainerFactory(jmsListenerContainerFactory); 
        
               configureTopicListenerContainerFactory(jmsListenerContainerFactory); 
        
               return jmsListenerContainerFactory; 
        
           }

azure-sdk-for-java/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsConnectionFactoryConfiguration.java

Lines 59 to 72 in 1ab5874

    
           public void registerBeanDefinitions(AnnotationMetadata importingClassMetadata, 
        
                                               BeanDefinitionRegistry registry) { 
        
               BindResult<Boolean> poolEnabledResult = Binder.get(environment).bind("spring.jms.servicebus.pool.enabled", Boolean.class); 
        
               BindResult<Boolean> cacheEnabledResult = Binder.get(environment).bind("spring.jms.cache.enabled", Boolean.class); 
        
               if (isPoolConnectionFactoryClassPresent() && poolEnabledResult.orElseGet(() -> false)) { 
        
                   registerJmsPoolConnectionFactory(registry); 
        
                   return; 
        
               } 
        
               if (isCacheConnectionFactoryClassPresent() && cacheEnabledResult.orElseGet(() -> false)) { 
        
                   registerJmsCachingConnectionFactory(registry); 
        
                   return; 
        
               }

</issue_description>

Comments on the Issue (you are @copilot in this section)

@rujche ## Current status

From azure-spring-boot-samples, the sender is JmsTemplate bean.
The sender side, related code is in spring-boot/../JmsClientConfigurations.java, the JmsTemplate bean will only be configured when there is only one bean with type ConnectionFactory. @ConditionalOnSingleCandidate(ConnectionFactory.class).
The receiver side, related code is in azure-sdk-for-java/.../ServiceBusJmsContainerConfiguration, it also uses the bean ConnectionFactory, it's the same one used in spring-boot/../JmsClientConfigurations.java

Implementation suggestion

Keep the configuration with only one bean with type ConnectionFactory, to make the spring-boot/../JmsClientConfigurations.java can still work.
On the sender side, in [azure-sdk-for-java/.../ServiceBusJmsConnectionFactoryConfiguration](https://github.com/Azure/azure-sdk-for-java/blob/be5923f94284df7f971c59785322a596fde1b37e/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/...

Fixes [FEATURE REQ] Change sender's default JmsConnectionFactory from ServiceBusJmsConnectionFactory to CachingConnectionFactory #47923

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

…iver ConnectionFactory Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

...azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java

The receiver now conditionally uses the ConnectionFactory bean when it's JmsPoolConnectionFactory or CachingConnectionFactory, otherwise creates a dedicated ServiceBusJmsConnectionFactory. This matches the expected behavior where the receiver should use the same pooled/cached connection factory as the sender when those features are enabled. Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

...azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java

The receiver now only uses the shared ConnectionFactory bean when pooling or caching is EXPLICITLY enabled. When properties are not set, the receiver creates a dedicated ServiceBusJmsConnectionFactory instance, even though the sender defaults to CachingConnectionFactory. This matches the expected behavior table from the issue. Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

rujche · 2026-02-10T08:42:32Z

Table

`spring.jms.servicebus.pool.enabled` value	`spring.jms.cache.enabled` value	sender	receiver	case number
not set	not set	CachingConnectionFactory	ServiceBusJmsConnectionFactory	4
not set	true	CachingConnectionFactory	CachingConnectionFactory	1
not set	false	ServiceBusJmsConnectionFactory	ServiceBusJmsConnectionFactory	3
true	not set	JmsPoolConnectionFactory	JmsPoolConnectionFactory	1
true	true	CachingConnectionFactory	CachingConnectionFactory	2
true	false	JmsPoolConnectionFactory	JmsPoolConnectionFactory	1
false	not set	CachingConnectionFactory	ServiceBusJmsConnectionFactory	4
false	true	CachingConnectionFactory	CachingConnectionFactory	1
false	false	ServiceBusJmsConnectionFactory	ServiceBusJmsConnectionFactory	3

Explanation

If only one of the properties (spring.jms.servicebus.pool.enabled and spring.jms.cache.enabled) set to true, set both sender and receiver to that factory. (4 cases)
If both properties set to true, set both sender and receiver to CachingConnectionFactory. (1 case)
Otherwise, if spring.jms.cache.enabled set to false, set both sender and receiver to ServiceBusJmsConnectionFactory . (2 case)
Otherwise, use default value: set sender to CachingConnectionFactory, set receiver to ServiceBusJmsConnectionFactory. (2 cases)
When use CachingConnectionFactory or JmsPoolConnectionFactory, confirm related class in the classpath. If it's not in the classpath, fallback to ServiceBusJmsConnectionFactory.

@copilot , According to this table and explanation:

Update related code.
Update test code, enrich test case.
Update change log, add the table to change log to make it more clear.
Add the table into related java doc to make it clear. In sender's java doc, only add sender in the table, in the receiver's java doc, only add receiver in the doc.

- Updated logic to follow the complete configuration table with all 9 scenarios - Added JavaDoc tables to both sender and receiver configurations - Added comprehensive test coverage for all scenarios - Updated CHANGELOG with detailed configuration table and rules - Both properties set to true now uses CachingConnectionFactory (cache takes precedence) - Added proper fallback logic when required classes are not in classpath Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

Copilot · 2026-02-10T08:53:17Z

Table

| spring.jms.servicebus.pool.enabled value | spring.jms.cache.enabled value | sender | receiver | case number |
...

Done in commit 29cb8b3:

✅ Updated related code - Implemented the complete logic table with all 9 scenarios for both sender and receiver
✅ Enriched test cases - Added 7 new test cases covering all property combinations
✅ Updated CHANGELOG - Added the complete table with all scenarios and 5 rules explaining the behavior
✅ Added JavaDoc tables - Both ServiceBusJmsConnectionFactoryConfiguration (sender) and ServiceBusJmsContainerConfiguration (receiver) now have JavaDoc tables showing only their respective ConnectionFactory types

Key changes:

When both properties are true → CachingConnectionFactory (cache takes precedence)
When cache.enabled=false → checks pool.enabled for JmsPoolConnectionFactory vs ServiceBusJmsConnectionFactory
Proper fallback when required classes not in classpath
All 68 JMS tests passing

rujche · 2026-02-10T09:18:32Z

@copilot Fix the lint error:

2026-02-10T08:59:38.1667963Z ##[section]Starting: Generate Linting Reports
2026-02-10T08:59:38.1673984Z ==============================================================================
2026-02-10T08:59:38.1674245Z Task         : PowerShell
2026-02-10T08:59:38.1674382Z Description  : Run a PowerShell script on Linux, macOS, or Windows
2026-02-10T08:59:38.1674517Z Version      : 2.268.1
2026-02-10T08:59:38.1674645Z Author       : Microsoft Corporation
2026-02-10T08:59:38.1674758Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2026-02-10T08:59:38.1674900Z ==============================================================================
2026-02-10T08:59:38.2973795Z Generating script.
2026-02-10T08:59:38.2987577Z ========================== Starting Command Output ===========================
2026-02-10T08:59:38.3000052Z [command]/usr/bin/pwsh -NoLogo -NoProfile -NonInteractive -Command . '/mnt/vss/_work/_temp/83345fb9-d951-4514-b781-8c89e93550e7.ps1'
2026-02-10T08:59:43.5087035Z 
2026-02-10T08:59:43.5148381Z File Name,Line Number,Column Number,Message,Type
2026-02-10T08:59:43.5149175Z "/mnt/vss/_work/1/s/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java",101,72,"'&&' should be on a new line.","com.puppycrawl.tools.checkstyle.checks.whitespace.OperatorWrapCheck"
2026-02-10T08:59:43.5150228Z "/mnt/vss/_work/1/s/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java",110,70,"'&&' should be on a new line.","com.puppycrawl.tools.checkstyle.checks.whitespace.OperatorWrapCheck"
2026-02-10T08:59:43.5151038Z "/mnt/vss/_work/1/s/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java",116,68,"'&&' should be on a new line.","com.puppycrawl.tools.checkstyle.checks.whitespace.OperatorWrapCheck"
2026-02-10T08:59:43.5151816Z "/mnt/vss/_work/1/s/sdk/spring/spring-cloud-azure-autoconfigure/src/main/java/com/azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java",117,43,"'&&' should be on a new line.","com.puppycrawl.tools.checkstyle.checks.whitespace.OperatorWrapCheck"
2026-02-10T08:59:43.5152171Z 
2026-02-10T08:59:43.8298576Z Linting errors have been found. Navigate to https://dev.azure.com/azure-sdk/public/_build/results?buildId=5859617&view=artifacts&pathAsName=false&type=publishedArtifacts and download the 'linting-report.zip' artifact to see what was found.
2026-02-10T08:59:43.8316634Z �[32;1mCapacity�[0m�[32;1m MaxCapacity�[0m�[32;1m Length�[0m
2026-02-10T08:59:43.8317460Z �[32;1m--------�[0m �[32;1m-----------�[0m �[32;1m------�[0m
2026-02-10T08:59:43.8317947Z      568  2147483647    285
2026-02-10T08:59:43.8318350Z     1136  2147483647    570
2026-02-10T08:59:43.8318688Z     1136  2147483647    855
2026-02-10T08:59:43.8319051Z     2272  2147483647   1140
2026-02-10T08:59:43.8319377Z     2321  2147483647   1189
2026-02-10T08:59:43.8320027Z 
2026-02-10T08:59:43.8837982Z 
2026-02-10T08:59:43.8871651Z ##[error]PowerShell exited with code '1'.
2026-02-10T08:59:43.8920855Z ##[section]Finishing: Generate Linting Reports

Fixed OperatorWrapCheck violations by moving && operators from end of line to the beginning of the next line, following the project's code style rules. Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

Copilot · 2026-02-10T09:25:30Z

@copilot Fix the lint error:

...

Fixed in commit 42d8270. Moved all && operators from the end of lines to the beginning of the next line to comply with OperatorWrapCheck. Checkstyle now passes with 0 violations.

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

...azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java

sdk/spring/CHANGELOG.md

...azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java

rujche · 2026-02-11T06:37:25Z

@copilot apply changes based on the comments in this thread

1. Fixed CHANGELOG typo: Removed extra comma after "Note:" 2. Added lifecycle management: Implemented DisposableBean to properly close dedicated ConnectionFactory instances on shutdown 3. Memoized all dedicated factory types: Added volatile fields and synchronized getter methods for CachingConnectionFactory, JmsPoolConnectionFactory, and ServiceBusJmsConnectionFactory to prevent duplicate instances 4. Added receiver tests: Added 4 comprehensive tests verifying receiver uses correct ConnectionFactory type in different configuration scenarios This ensures proper resource cleanup and validates receiver behavior. Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

Copilot · 2026-02-11T06:47:05Z

@copilot apply changes based on the comments in this thread

Applied all changes in commit 93ee8fa:

Test coverage (2791618663): Added 4 new tests verifying receiver ConnectionFactory logic for different configurations
Duplicate instances (2791618679): Memoized all 3 dedicated factory types using volatile fields with synchronized getters - both listener containers now share the same instance
CHANGELOG typo (2791618687): Fixed extra comma after "Note:"
Lifecycle management (2791618704): Implemented DisposableBean.destroy() to properly close dedicated ConnectionFactory instances on shutdown

All 77 JMS tests passing, checkstyle 0 violations.

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

...azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsAutoConfigurationTests.java

rujche · 2026-02-11T07:26:06Z

@copilot apply changes based on the comments in this thread

1. Fixed CHANGELOG typo: Removed extra comma after "Note:" 2. Enhanced receiver tests to verify actual ConnectionFactory instances: - Create DefaultMessageListenerContainer from factories - Assert ConnectionFactory type using getConnectionFactory() - Verify dedicated instances are NOT same as sender bean - Verify shared beans ARE same as sender bean - Verify both listener containers share same dedicated instance (memoization) Tests now properly validate that receiver uses correct ConnectionFactory type and that memoization prevents duplicate instances. Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

Copilot · 2026-02-11T07:36:00Z

@copilot apply changes based on the comments in this thread

Applied in commit 0b12dc2. Enhanced all 4 receiver tests to:

Create DefaultMessageListenerContainer from each factory
Assert actual ConnectionFactory type using getConnectionFactory()
Verify dedicated instances are NOT same as sender bean (using isNotSameAs())
Verify shared beans ARE same as sender bean (using isSameAs())
Verify both queue and topic containers share same dedicated instance (validates memoization)

Tests now properly validate receiver ConnectionFactory behavior and instance sharing.

Copilot

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.

rujche · 2026-02-11T13:36:04Z

/azp run java - spring - tests

azure-pipelines · 2026-02-11T13:36:37Z

Azure Pipelines successfully started running 1 pipeline(s).

Initial plan

a76d7f4

Copilot AI assigned Copilot and rujche Feb 10, 2026

Copilot started work on behalf of rujche February 10, 2026 02:11 View session

Copilot AI and others added 3 commits February 10, 2026 02:14

Change sender's default to CachingConnectionFactory and separate rece…

e4cd102

…iver ConnectionFactory Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

Update tests to reflect CachingConnectionFactory as default

9167051

Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

Add CHANGELOG entry for breaking change to default ConnectionFactory

26ce42c

Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Change sender's default JmsConnectionFactory to CachingConnectionFactory~~ Use CachingConnectionFactory by default for Service Bus JMS sender operations Feb 10, 2026

Copilot AI requested a review from rujche February 10, 2026 02:22

Copilot finished work on behalf of rujche February 10, 2026 02:22

rujche reviewed Feb 10, 2026

View reviewed changes

...azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java Show resolved Hide resolved

Copilot started work on behalf of rujche February 10, 2026 02:27 View session

Copilot AI requested a review from rujche February 10, 2026 02:39

Copilot finished work on behalf of rujche February 10, 2026 02:39

rujche reviewed Feb 10, 2026

View reviewed changes

...azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsContainerConfiguration.java Outdated Show resolved Hide resolved

Copilot started work on behalf of rujche February 10, 2026 02:44 View session

Copilot AI requested a review from rujche February 10, 2026 02:51

Copilot finished work on behalf of rujche February 10, 2026 02:51

Copilot started work on behalf of rujche February 10, 2026 08:43 View session

Copilot AI changed the title ~~Use CachingConnectionFactory by default for Service Bus JMS sender operations~~ Implement comprehensive JMS ConnectionFactory configuration for Service Bus Feb 10, 2026

Copilot finished work on behalf of rujche February 10, 2026 08:54

Copilot started work on behalf of rujche February 10, 2026 09:19 View session

Fix checkstyle violations - move && operators to new lines

42d8270

Fixed OperatorWrapCheck violations by moving && operators from end of line to the beginning of the next line, following the project's code style rules. Co-authored-by: rujche <171773178+rujche@users.noreply.github.com>

rujche added 2 commits February 11, 2026 14:10

Update CHANGELOG

b622cdf

Fix compile error

546526a

rujche requested a review from Copilot February 11, 2026 06:15

Copilot started reviewing on behalf of rujche February 11, 2026 06:16 View session

Copilot AI reviewed Feb 11, 2026

View reviewed changes

Fix lint error

336442f

Copilot started work on behalf of rujche February 11, 2026 06:37 View session

Copilot finished work on behalf of rujche February 11, 2026 06:48

rujche requested a review from Copilot February 11, 2026 07:06

Copilot started reviewing on behalf of rujche February 11, 2026 07:07 View session

Copilot AI reviewed Feb 11, 2026

View reviewed changes

...azure/spring/cloud/autoconfigure/implementation/jms/ServiceBusJmsAutoConfigurationTests.java Show resolved Hide resolved

rujche moved this from Todo to In Progress in Spring Cloud Azure Feb 11, 2026

Copilot started work on behalf of rujche February 11, 2026 07:26 View session

Copilot finished work on behalf of rujche February 11, 2026 07:36

rujche requested a review from Copilot February 11, 2026 07:46

Copilot started reviewing on behalf of rujche February 11, 2026 07:47 View session

Copilot AI reviewed Feb 11, 2026

View reviewed changes

rujche marked this pull request as ready for review February 11, 2026 08:36

rujche requested review from a team, Netyyyy, moarychan and saragluna as code owners February 11, 2026 08:36

	JmsListenerContainerFactory<?> jmsListenerContainerFactory(
	DefaultJmsListenerContainerFactoryConfigurer configurer, ConnectionFactory connectionFactory) {
	DefaultJmsListenerContainerFactory jmsListenerContainerFactory = new DefaultJmsListenerContainerFactory();
	configurer.configure(jmsListenerContainerFactory, connectionFactory);
	jmsListenerContainerFactory.setPubSubDomain(Boolean.FALSE);
	configureCommonListenerContainerFactory(jmsListenerContainerFactory);
	return jmsListenerContainerFactory;
	}

	@Bean
	@ConditionalOnMissingBean(name = "topicJmsListenerContainerFactory")
	JmsListenerContainerFactory<?> topicJmsListenerContainerFactory(
	DefaultJmsListenerContainerFactoryConfigurer configurer, ConnectionFactory connectionFactory) {
	DefaultJmsListenerContainerFactory jmsListenerContainerFactory = new DefaultJmsListenerContainerFactory();
	configurer.configure(jmsListenerContainerFactory, connectionFactory);
	jmsListenerContainerFactory.setPubSubDomain(Boolean.TRUE);
	configureCommonListenerContainerFactory(jmsListenerContainerFactory);
	configureTopicListenerContainerFactory(jmsListenerContainerFactory);
	return jmsListenerContainerFactory;
	}

	public void registerBeanDefinitions(AnnotationMetadata importingClassMetadata,
	BeanDefinitionRegistry registry) {
	BindResult<Boolean> poolEnabledResult = Binder.get(environment).bind("spring.jms.servicebus.pool.enabled", Boolean.class);
	BindResult<Boolean> cacheEnabledResult = Binder.get(environment).bind("spring.jms.cache.enabled", Boolean.class);

	if (isPoolConnectionFactoryClassPresent() && poolEnabledResult.orElseGet(() -> false)) {
	registerJmsPoolConnectionFactory(registry);
	return;
	}

	if (isCacheConnectionFactoryClassPresent() && cacheEnabledResult.orElseGet(() -> false)) {
	registerJmsCachingConnectionFactory(registry);
	return;
	}

Implement comprehensive JMS ConnectionFactory configuration for Service Bus #47950

Are you sure you want to change the base?

Implement comprehensive JMS ConnectionFactory configuration for Service Bus #47950

Uh oh!

Conversation

Copilot AI commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Plan: Change sender's default JmsConnectionFactory to CachingConnectionFactory

Understanding:

Implementation Strategy:

Expected behavior

Relate codes

Comments on the Issue (you are @copilot in this section)

Implementation suggestion

Uh oh!

Uh oh!

Uh oh!

rujche commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Table

Explanation

Uh oh!

Copilot AI commented Feb 10, 2026

Table

Uh oh!

rujche commented Feb 10, 2026

Uh oh!

Copilot AI commented Feb 10, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

rujche commented Feb 11, 2026

Uh oh!

Copilot AI commented Feb 11, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

rujche commented Feb 11, 2026

Uh oh!

Copilot AI commented Feb 11, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

rujche commented Feb 11, 2026

Uh oh!

azure-pipelines bot commented Feb 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Copilot AI commented Feb 10, 2026 •

edited

Loading

rujche commented Feb 10, 2026 •

edited

Loading