You appear to be specifying the trust store location twice, and no
password, in your URI, which may or may not be related. The rest of
the failure might give more details. It could simply be an issue with
your certificates. Turning on the full Java SSL debug logging
(-Djavax.net.debug=all) could also be help you to diagnose your issue:
http://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html

On 15 February 2017 at 15:37, pqvchen1 <[email protected]> wrote:
> I tried to use org.apache.qpid.jms.jndi.JmsInitialContextFactory for SSL
> connection and use the keystore in connection string in jndi.properties as
> indicated:
>
> connectionfactory.SBCF =
> amqps://127.0.0.1:5271?transport.keyStoreLocation=keystoreLocation&transport.keyStorePassword=test&transport.trustStoreLocation=truststoreLoc&transport.trustStoreLocation=truststore
>
> And here is the code:
>
> Hashtable<String, String> env = new Hashtable<String, String>();
> env.put(Context.INITIAL_CONTEXT_FACTORY,
> "org.apache.qpid.jms.jndi.JmsInitialContextFactory");
> env.put(Context.PROVIDER_URL, "jndi.properties");
>
> Context context = new InitialContext(env);
>
> ConnectionFactory factory = (ConnectionFactory) context.lookup("SBCF");
>
> Connnection connection = factory.createConnection("test", "test");
>
>
> and it keep return the following error:
> Rethrowing javax.net.ssl.SSLHandshakeException: General SSLEngine problem
> Rethrowing javax.net.ssl.SSLException: Inbound closed before receiving
> peer's close_notify: possible truncation attack?
>
> Can anyone give any suggestion? Thanks
>
>
>
>
>
> --
> View this message in context: 
> http://qpid.2158936.n2.nabble.com/JMS-can-I-include-ssl-keystore-truststore-in-connectionfactory-string-tp7659151p7659203.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to