Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 5 Apr 2013 15:15:16 +0000 (UTC)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: <JIRA.12628016.1358417987422.116842.1365174916888@arcas>
In-Reply-To: <JIRA.12628016.1358417987422@arcas>
References: <JIRA.12628016.1358417987422@arcas>
Subject: [jira] [Commented] (APLO-287) Weird errors with SSL + Java 7
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hiram Chirino commented on APLO-287:
------------------------------------

Ok, lets try something else.  Luckily the crypto implementations in the JVM are pluggable, and the bouncycastle folks have a very excellent implementation. I've just deployed a new version of Apollo [1] which will install the bouncycastle security provider if it finds it in the classpath.  You just need to install the bcprov-jdk15on-148.jar [2] in Apollo's lib directory.  You'll know it got loaded if on startup, you see the 'Loaded the Bouncy Castle security provider.' message logged to the console.

[1]: https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-apollo/99-trunk-SNAPSHOT/apache-apollo-99-trunk-20130405.150934-220-unix-distro.tar.gz
[2]: http://www.bouncycastle.org/download/bcprov-jdk15on-148.jar

Lionel, could you check to see if bouncycastle impl behaves better than the default JVM impl.
                
> Weird errors with SSL + Java 7
> ------------------------------
>
>                 Key: APLO-287
>                 URL: https://issues.apache.org/jira/browse/APLO-287
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: apollo-99-trunk-20130115.031918-158
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>
> When running simple functionality tests (that use STOMP+SSL) against apollo-99-trunk-20130115.031918-158, everything works fine when the broker runs on top of a Java 6 JVM.
> However, the exact same tests again the exact same version of Apollo fail randomly when the broker runs on top of a Java 7 JVM. For the record, we use: Java HotSpot(TM) 64-Bit Server VM 1.7.0_10 (Oracle Corporation).
> Here is what the broker logs:
> 2013-01-17 11:09:09,663 Shutting connection 'null'  down due to: java.io.EOFException: Peer disconnected
> 2013-01-17 11:09:09,764 Shutting connection 'null'  down due to: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
> 2013-01-17 11:11:16,110 Shutting connection 'null'  down due to: javax.net.ssl.SSLHandshakeException: Invalid padding
> 2013-01-17 11:13:54,671 Shutting connection 'null'  down due to: javax.net.ssl.SSLHandshakeException: Invalid padding
> [...]
> First of all, is Apollo supported on Java 7?
> If yes, any idea what could cause these failures on Java 7?

--
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