I'm not an expert on the JMS client, but I'm not sure that the "verifyHost" option would make any sense on a non-TLS connection (since by definition you can only verify the host when you receive the TLS certificate).
I think the use of the Java Broker here is not important, as I assume this fails before it even tries to make a connection, -- Rob On 1 February 2017 at 11:31, Adel Boutros <[email protected]> wrote: > Hello, > > > I was playing around SSL/SASL with the Java Broker and noticed that some > of the options which I can pass to the JMS client do not work. > > > For example, if I set the following url for the JMS Connection Factory, I > will get the below exception. Is this expected behavior? > > > JmsConnectionFactory jmsConnectionFactory = new > JmsConnectionFactory("amqp://localhost:5672?transport.verifyHost=false"); > jmsConnectionFactory.createConnection(); > > > Caused by: java.lang.IllegalArgumentException: Not all transport options > could be set on the TCP Transport. Check the options are spelled correctly. > Unused parameters=[{verifyHost=false}]. This provider instance cannot be > started. > at org.apache.qpid.jms.transports.TransportFactory.createTransport( > TransportFactory.java:64) > at org.apache.qpid.jms.transports.TransportFactory. > create(TransportFactory.java:120) > at org.apache.qpid.jms.provider.amqp.AmqpProvider.connect( > AmqpProvider.java:160) > > > Regards, > > Adel >
