The proton transport isn't used for SSL in the JMS client, but the thing I'm thinking of is more likely to happen when SSL is being used. In this case it would most likely be a bug in the client and the server, but a server could do it deliberately, and it would be something the client should cope with in any case.
On 31 October 2016 at 06:38, Artem <[email protected]> wrote: > Robbie, > > i think in that case transport had been used for ssl handshake, and after > this client trying to initialize transport frame size again. > > Also i test my ssl server with other client > <https://mvnrepository.com/artifact/org.apache.qpid/qpid-amqp-1-0-client> > and it works. > > In conclusion it can be concluded that there is an error in JMS client which > used for ssl connection. > > Thanks, > Artem > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/SSL-server-tp7652063p7652646.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]
