Windows 2008 x86_64 EC2 build

Build: #352 was successful Changes by Gary Russell

Build result summary

Details

Completed
Duration
96 minutes
Labels
None
Agent
(elastic) Elastic Agent on i-529047e3
Revision
6923ee8705bd9c2c58ad73120724b8b87c5ba37d 6923ee8705bd9c2c58ad73120724b8b87c5ba37d
Total tests
1546
Successful since
#348 ()

Tests

Code commits

Author Commit Message Commit date
Gary Russell Gary Russell 6923ee8705bd9c2c58ad73120724b8b87c5ba37d 6923ee8705bd9c2c58ad73120724b8b87c5ba37d XD-3709: Unique Domain Name for Module MBeans
JIRA: XD-3709">https://jira.spring.io/browse/XD-3709

Spring Integration has a (regression) bug that causes router MBeans to be
registered by the context `MBeanExporter`. Usually, Spring Integration components
are registered by the `IntegrationMBeanExporter`, if present.

This problem means that if more than one `router` sink is deployed with JMX enabled, deployment
fails with `InstanceAlreadyExistsException`.

This has been corrected in Spring Integration and will be available in 4.2.3.

However, the same issue would apply to user MBeans in custom modules.

The `mbean-exporters` XML currently adds a unique domain name to the integration exporter, but
leaves the context exporter with the default domain.

Tested with `time | router --expression='''queue:foo'''` (two streams) before and after.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeXD-3709Could not obtain issue details from Jira