[ http://jira.jboss.com/jira/browse/JBMESSAGING-487?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-487: --------------------------------------------- The "javax.net.ssl.SSLProtocolException: Illegal client handshake msg, 1" exception is caused by ServerConsumerEndpoint's attempt to push messages to the client. Pushing a message would make the ServerConsumerEndpoint use the the reverse (server->client) SSL connection to send invocations into the client-side callback server. The first attempt to write on that socket causes the SSLProtocolException. The same stress test did not fail with 1.0.1.CR3 because the server (ServerConsumerEndpoint) never sent asynchronously messages to the calback server. Pre-CR4 refactoring code did not do push, so the first (and only) message of the test was pulled by client, using the direct connection. The reverse connection was never tested. This is not a regression error, but a piece of functionality that was incorrectly implemented in the first place. The initial test was not good enough to catch the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-487?page=all ] Ovidiu Feodorov closed JBMESSAGING-487. --------------------------------------- Resolution: Done The latest Remoting snapshot (the future 2.0.0.CR2) fixed the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira