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

Timothy Bish commented on AMQ-4340:
-----------------------------------

There were some recent NIO transport fixes which would ripple into the NIO+SLL 
case as well, have you tested using the most recent 5.9-SNAPSHOT?
                
> When client uses the latest Java release, (eg. jdk1.7.0_13, jdk 1.7.0_9), 
> client ssl connection fails when broker is set to use nio+ssl, and 
> simpleAuthenticationPlugin
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4340
>                 URL: https://issues.apache.org/jira/browse/AMQ-4340
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.6.0, 5.7.0
>         Environment: broker is running on Linux 2.6.18-308.1.el5. Client is 
> running in window7 (64bit)
>            Reporter: Yelu huang
>
> When client uses jdk1.7.0_13 or 1.7.0_9 and tries to make a ssl connection to 
> a broker which has a transportConnector set as:
>    <transportConnector name="nio+ssl" uri="nio+ssl://0.0.0.0:7021" />
> and a simple plugin like:
>  <plugins>
>           <simpleAuthenticationPlugin>
>              <users>
>                 <authenticationUser username="system"
>                    password="manager" groups="users,admins"/>
>                 <authenticationUser username="yelu"
>                    password="rabbit" groups="users"/>
>                 <authenticationUser username="guest"
>                    password="password" groups="guests"/>
>             </users>
>          </simpleAuthenticationPlugin>
>  </plugins>
> The connection got javax.jms.JMSException: java.io.EOFException. You can 
> reproduce it by simply running an example ProducerTool provided by Activemq.
> It is noted if client uses java 1.6, we have no problem to run the same 
> program. Or if client still uses jdk1.7.0_13, 1.7.0_9, but broker remove nio, 
> ie, just use ssl for transportConnector, we have no problem too. So the 
> problem is nio+ssl is not working properly with the recent Java release. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to