[ 
https://issues.apache.org/jira/browse/QPID-7275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297511#comment-15297511
 ] 

Steven commented on QPID-7275:
------------------------------

Hello,Robbie

I use the forward slashes in the transport.trustStoreLocation

I have modified the connection 
URL:amqps://192.168.82.57:5673?transport.trustStoreLocation=F:/AMQP/QpidSSL/clientts.jks&transport.trustStorePassword=123456,but
 still reporting error,
2016-05-24 09:23:56,042 [main           ] - ERROR JmsConnectionFactory          
 - Failed to create JMS Provider instance for: amqps
Caught exception, exiting.
javax.jms.JMSException: Failed to create connection to: 
amqps://192.168.82.57:5673?transport.trustStoreLocation=F%253A%252F%252FAMQP%252F%252FQpidSSL%252F%252Fclientts.jks&transport.trustStorePassword=123456
        at 
org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:66)
        at 
org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:172)
        at 
org.apache.qpid.jms.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:161)
        at org.apache.qpid.jms.example.HelloWorld.test(HelloWorld.java:91)
        at org.apache.qpid.jms.example.HelloWorld.main(HelloWorld.java:73)
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        at sun.security.ssl.Handshaker.checkThrown(Unknown Source)
        at sun.security.ssl.SSLEngineImpl.checkTaskThrown(Unknown Source)
        at sun.security.ssl.SSLEngineImpl.readNetRecord(Unknown Source)
        at sun.security.ssl.SSLEngineImpl.unwrap(Unknown Source)
        at javax.net.ssl.SSLEngine.unwrap(Unknown Source)
        at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:927)
        at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:871)
        at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:827)
        at 
io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:228)
        at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:141)
        at 
io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:340)
        at 
io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:326)
        at 
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785)
        at 
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:116)
        at 
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:494)
        at 
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:461)
        at 
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350)
        at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101)
        at java.lang.Thread.run(Unknown Source)
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        at sun.security.ssl.Alerts.getSSLException(Unknown Source)
        at sun.security.ssl.SSLEngineImpl.fatal(Unknown Source)
        at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
        at sun.security.ssl.Handshaker.fatalSE(Unknown Source)
        at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source)
        at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source)
        at sun.security.ssl.Handshaker.processLoop(Unknown Source)
        at sun.security.ssl.Handshaker$1.run(Unknown Source)
        at sun.security.ssl.Handshaker$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.security.ssl.Handshaker$DelegatedTask.run(Unknown Source)
        at 
io.netty.handler.ssl.SslHandler.runDelegatedTasks(SslHandler.java:960)
        at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:891)
        ... 13 more
Caused by: java.security.cert.CertificateException: No subject alternative 
names present
        at sun.security.util.HostnameChecker.matchIP(Unknown Source)
        at sun.security.util.HostnameChecker.match(Unknown Source)
        at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source)
        at sun.security.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source)
        at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source)
        at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown 
Source)
        ... 22 more

By the way,I don't know much about that how to use "jms.transport.<foo>" 
options,Could you explain it,Thanks in advance



> connection.setExceptionListener() method cannot be invoked for Qpid
> -------------------------------------------------------------------
>
>                 Key: QPID-7275
>                 URL: https://issues.apache.org/jira/browse/QPID-7275
>             Project: Qpid
>          Issue Type: Bug
>          Components: JMS AMQP 1.0 Client
>    Affects Versions: 0.32
>         Environment: Window7,jdk7
>            Reporter: Steven
>
> I want to implement Re-connection functionality for AMQP 1.0,as We all know 
> that AMQP 1.0 protocol 's connection URL didn't support "broker-list",Hence,I 
> want to register the method "connection.setExceptionListener"  to monitor the 
> connection between client socket and server socket before invoking the method 
> "connection.start" ,I try to mock the connection closed through the three 
> following way:
> 1.stop the Qid server broker
> 2.pull out the cable
> 3.use the TCPViewer to close the connection manually.
> none of the above method didn't invoke the method 
> "connection.setExceptionListener"
> by the way,for the client API qpid-amqp-1-0-client-0.32,If  the connection 
> URL support brokerlist feature,That would be nice,I can implement 
> Re-connection functionality in a nice way,Thanks in advance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to