Reading FailoverTransportFactory.java, I see the code that causes the
exception to occur, but I don't understand the logic. It seems like this
check is added later. I don't see the same check in 4.1.2
public Transport createTransport(CompositeData compositData) throws
IOException {
Map options = compositData.getParameters();
FailoverTransport transport = createTransport(options);
if (!options.isEmpty()) { <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
throw new IllegalArgumentException("Invalid connect parameters:
" + options);
}
transport.add(compositData.getComponents());
return transport;
}
public FailoverTransport createTransport(Map parameters) throws
IOException {
FailoverTransport transport = new FailoverTransport();
IntrospectionSupport.setProperties(transport, parameters);
return transport;
}
I don't see how the options can possibly be empty if it is specified in the
URL. Am I missing something? Is there new ways to specifying the options?
--
View this message in context: http://www.nabble.com/connection-failover-using-ActiveMQ-5.2-tp23374917p23375575.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.