Bruce,
Here is the error we are getting
ERROR - TransportConnector - Could not accept connection : No
available certificate or key corresponds to the SSL cipher suites which are
enabled.
ERROR - TransportConnector - Could not accept connection : No
available certificate or key corresponds to the SSL cipher suites which are
enabled.
ERROR - TransportConnector - Could not accept connection : No
available certificate or key corresponds to the SSL cipher suites which are
enabled.
bsnyder wrote:
>
> On Wed, May 14, 2008 at 12:35 PM, javadevel <[EMAIL PROTECTED]> wrote:
>>
>> I have statically configured ServiceMix cluster that is working
>> flawlessly.
>> However, when I change the protocol from tcp to ssl I run into broker
>> connection issues. I made sure the certificates that are found in the
>> keystores are identical on both servers. Is there anything more I have
>> to do
>> to make sure the communication occurs over SSL?
>>
>> Configuration
>> <amq:networkConnector
>> uri="static://(ssl://serverAt:61616,ssl://serverB:61616)"/>
>>
>>
>> Exception
>> Could not start network bridge between: vm://localhost and:
>> ssl://172.28.1.204:61616 due to: javax.net.ssl.SSLException
>> : Unrecognized SSL message, plaintext connection?
>
> Please post a larger hunk of the log file including a stack trace if
> you have one. There is not enough context in the error above to
> understand what is happening.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
> Apache Geronimo - http://geronimo.apache.org/
>
> Blog: http://bruceblog.org/
>
>
--
View this message in context:
http://www.nabble.com/Using-SSL-in-cluster-configuration-tp17238081p17427575.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
