Thanks Tim. I use CMS as ActiveMQ client and I use ""ssl://localhost:61614?wireFormat=stomp" as broker URI on the client side. I can see the STOMP meessage sent successfully through ssl connection. On the java server side, I can see the ssl handshake and the STOMP frame after that.
The CMS version is "activemq-cpp-library-3.8.3". Your suggestion is good and that is what we decided to go. But I do believe if "stomp+ssl" is used, we will have a problem and the problem is on the server side because of the "wireFormat.host" option added for Openwire. -- View this message in context: http://activemq.2283324.n4.nabble.com/wireFormat-host-option-for-StompSslTransportFactory-tp4685162p4685250.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
