Re: Securing JMS queque

2014-08-22 Thread artnaseef
a "plain-text" connection was attempted. Check the webconsole or via JMX to confirm the only connector is the nio+ssl connector. On the client side, make sure all clients use ssl:// for the URL. -- View this message in context: http://activemq.2283324.n4.nabble.com/Securing-JMS-que

Re: Securing JMS queque

2014-08-14 Thread Matt Pavlovich
is started sucessfully and started publishing on > Publishing: nio+ssl://127.0.0.1:61617 for broker transport URI: > nio+ssl://127.0.0.1:61617?trace=true&needClientAuth=true&maximumConnections=1000&wireFormat.maxFrameSize=104857600 > > but somehow connections are created on tcp >

Securing JMS queque

2014-08-14 Thread akshattandon
ze=104857600 but somehow connections are created on tcp and being displayed like following tcp://127.0.0.1:49881 can someone guide us how to make the connection as ssl as well -- View this message in context: http://activemq.2283324.n4.nabble.com/Securing-JMS-queque-tp4684509.ht