Never mind this is a bug. Come to find out that even though you set the
SslContext with in the activemq-broker.xml it is never used when creating
the SslSocketConnector for the Broker, so you see the behavior I am seeing.
On Tue, 24 Apr 2012 10:48:57 -0500, Chris Odom
chris.o...@mediadriver.com
Furthering debugging of the issue has revealed that the create
SslSocketConnector's sslContextFactory does not have the keyStore created
as in, its null. I have also noticed that when using either configuration
below the keyStorePassword is mucked up as well:
!-- SSL context used for both http(s)
Further debugging reveals that the SpringSSLContext is parsed correctly
from the activemq-broker.xml but during the binding process I found this:
org.apache.activemq.transport.TransportFactory
public static TransportServer bind(BrokerService brokerService, URI
location) throws IOException {
I am currently trying to setup both a https and ssl transport connector
for the default broker. I am using servicemix deploying a blueprint version
of the activemq-broker.xml and have followed all how-to with no success.
below is an excerpt of my broker.xml file for sslcontext configuration:
