Issue

• Should an invalid ActiveMQ connector option be reported as an error or warning ? Or does it require some additional configuration so that when an incorrect connector option is used then the broker should throw a Warning or error message ?
• ActiveMQ connectors can get options in activemq.xml. When an invalid option is given, ActiveMQ should loudly complain about it. It does not.
• For instance, I added a spurious X in the aaa option and, when staring, ActiveMQ reports:

2015-06-02 08:44:09,577 [TestMain] INFO TransportServerThreadSupport - Listening for connections at: stomp+nio://localhost:61616?transport.closeAsync=false&transport.aaa=3600000,0&transport.keepAlive=true&transport.soLinger=1

• No further waning so I guess the bogus option has been silently ignored. An unknown option (like transport.aaa above) should really be reported, at least as a warning, maybe even as an error. Or does it require an additional broker configuration?