activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (JIRA)" <>
Subject [jira] [Commented] (APLO-287) Weird errors with SSL + Java 7
Date Fri, 05 Apr 2013 06:54:17 GMT


Lionel Cons commented on APLO-287:

Hiram, I've enabled debugging but this is _very_ verbose: I logged >100MB in only a few
minutes. Also, the broker seemed slowed down because of this logging and the test results
were different.

Most sessions appeared as:

%% Initialized:  [Session-3, SSL_NULL_WITH_NULL_NULL]
%% Negotiating:  [Session-3, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA]
Compression Method: 0
Extension renegotiation_info, renegotiated_connection: <empty>

Regarding the client used, this is using Perl + Net::STOMP::Client.

You should be able to perform the same tests by fetching the same package (
and follow the instructions in README.howto.
> Weird errors with SSL + Java 7
> ------------------------------
>                 Key: APLO-287
>                 URL:
>             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:
Peer disconnected
> 2013-01-17 11:09:09,764 Shutting connection 'null'  down due to:
General SSLEngine problem
> 2013-01-17 11:11:16,110 Shutting connection 'null'  down due to:
Invalid padding
> 2013-01-17 11:13:54,671 Shutting connection 'null'  down due to:
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:

View raw message