Affects Version/s: 5.5.0-fuse-00-00
Fix Version/s: None
Similar Issues:Show 10 results
MB-1064 Configure duplicate warn message when using composite destinations MB-1235 Cannot use a virtual topic with a composite destination. MB-158 Wrong message removed from store when using composite destinations MB-1111 Composite destinations break simple authorisation through role aggregation MB-660 Messages to composite destinations don't get sent to all queues on the slave. MB-708 When sending to a composite destination the CursorMemoryUsage is not updated for all destinations MB-250 TransportDisposedIOException exception loop when adding NetworkConnector with invalid URL MB-164 Warning when using multicast discoveryUri MB-169 Unexpected IllegalStateException when using the VMPendingQueueMessageStoragePolicy MB-701 ConcurrentModificationException on broker when sending messages to composite destinations
The attached test case highlights a problem with the way detect SSL connections when composite URL's are used. In "ActiveMQSslConnectionFactory.java", we have the following section of code:
When using an SSL URL for failover, for example, brokerURL.getScheme="failover" and not "ssl" thus our special considerations for SSL are not picked up.
The attached test case uses a custom Trust Manager. We can see that it works just fine with a URL of ""ssl://localhost:61618", however, when failover is added, ("failover://(ssl://localhost:61618)", it's not picked up. I ran this through the debugger to track it down but essentially in the good case, you'll see my output from test case:
In the failing case, "My manager" line is not printed as its never invoked.
I dropped the attached test case into org.apache.activemq.