I do not doubt that you are using ssl but are you setting up the configuration 
using the sslContext element within the configuration file?

This allow you to set the key and trust store files and their required 
passwords.  

for instance,

<amq:broker useJmx="false" persistent="false"> <amq:sslContext> <amq:sslContext 
 keyStore="server.keystore" keyStorePassword="password" 
trustStore="client.keystore" trustStorePassword="password"/> </amq:sslContext> 
<amq:transportConnectors> <amq:transportConnector uri="ssl://localhost:61616" 
/>  </amq:transportConnectors> </amq:broker> 

You can also use the technique where you scramble the password and then pass 
the key using an environment variable.
I do not know how this is done off the top my head but can look for a reference.



>________________________________
> From: Geurt Schimmel <gschim...@schubergphilis.com>
>To: "users@activemq.apache.org" <users@activemq.apache.org>; 'Claudio Corsi' 
><clco...@yahoo.com> 
>Sent: Tuesday, December 11, 2012 11:23 AM
>Subject: RE: SSL: could not load resource
> 
>All brokers run SSL as the only communication-protocol and intercommunicate 
>over SSL.
>
>-----Original Message-----
>From: Claudio Corsi [mailto:clco...@yahoo.com] 
>Sent: Tuesday, December 11, 2012 5:17 PM
>To: users@activemq.apache.org
>Subject: Re: SSL: could not load resource
>
>Did you try to use the sslContext element to set your store information 
>withint he broker configuration file?
>
>Here is a link http://activemq.apache.org/how-do-i-use-ssl.html.
>
>
>
>>________________________________
>> From: Geurt Schimmel <gschim...@schubergphilis.com>
>>To: "users@activemq.apache.org" <users@activemq.apache.org>
>>Sent: Tuesday, December 11, 2012 9:54 AM
>>Subject: RE: SSL: could not load resource
>> 
>>Created key- and truststores for a number of brokers, so not using the 
>>packaged .ks and .ts files.
>>
>>Tried different truststores in different locations, tried a path to a 
>>truststore that didn't exist, just to see what happens. In all cases, the 
>>same error. Apparently, the point where the keystore is accessed is not 
>>reached. Setting the same variables/values in JAVA_OPTS works:
>>
>>java -Djavax.net.ssl.trustStore=/opt/activemq/conf/client.ts 
>>-Djavax.net.ssl.trustStorePassword=xxxxxxxx Producer
>>
>>-----Original Message-----
>>From: Christian Posta [mailto:christian.po...@gmail.com]
>>Sent: Tuesday, December 11, 2012 3:41 PM
>>To: users@activemq.apache.org
>>Subject: Re: SSL: could not load resource
>>
>>Is the client truststore in that location?  /opt/activemq/conf/client.ts I 
>>think there was some issues with packaging activemq 5.7 and some of the 
>>client keystores might have been missing.
>>
>>You'll have to copy from the 5.6.0 version
>>
>>
>>
>>
>>On Tue, Dec 11, 2012 at 7:05 AM, Geurt Schimmel < 
>>gschim...@schubergphilis.com> wrote:
>>
>>> Hi,
>>>
>>> My broker is running SSL only, with a 'simple' transportConnector:
>>>      <transportConnector name="openwire" uri="ssl://0.0.0.0:61616"/>
>>>
>>> When trying to run a java-client:
>>>
>>> Exception in thread "main" javax.jms.JMSException: Could not create  
>>>Transport. Reason: java.io.IOException: Could not load resource:
>>> /opt/activemq/conf/client.ts
>>>                 at
>>> 
>>>org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSuppor
>>>t.java:35)
>>>                 at
>>> 
>>>org.apache.activemq.ActiveMQSslConnectionFactory.createTransport(Activ
>>>eMQSslConnectionFactory.java:115)
>>>                 at
>>> 
>>>org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection
>>>(ActiveMQConnectionFactory.java:277)
>>>                 at
>>> 
>>>org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveM
>>>QConnectionFactory.java:202)
>>>                 at Producer.main(Producer.java:32) Caused by: 
>>> java.io.IOException: Could not load resource:
>>> /opt/activemq/conf/client.ts
>>>                 at
>>> 
>>>org.apache.activemq.ActiveMQSslConnectionFactory.getUrlOrResourceAsStr
>>>eam(ActiveMQSslConnectionFactory.java:188)
>>>                 at
>>> 
>>>org.apache.activemq.ActiveMQSslConnectionFactory.createTrustManager(Ac
>>>tiveMQSslConnectionFactory.java:126)
>>>                 at
>>> 
>>>org.apache.activemq.ActiveMQSslConnectionFactory.createTransport(Activ
>>>eMQSslConnectionFactory.java:108)
>>>                 ... 3 more
>>>
>>> Removed the java-code that deals with the truststore and moved the 
>>> functionality  to JAVA_OPTS, but this is not what I want/expected.
>>> Using  activemq-all-5.7-SNAPSHOT.jar.
>>>
>>> Thought this problem only occurs when using an SSL failover URI ?
>>>
>>> Thanks,
>>> Geurt
>>>
>>
>>
>>
>>--
>>*Christian Posta*
>>http://www.christianposta.com/blog
>>twitter: @christianposta
>>
>>
>>
>
>
>

Reply via email to