Return-Path: X-Original-To: apmail-activemq-commits-archive@www.apache.org Delivered-To: apmail-activemq-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 61652EE98 for ; Mon, 4 Feb 2013 14:36:40 +0000 (UTC) Received: (qmail 74818 invoked by uid 500); 4 Feb 2013 14:28:13 -0000 Delivered-To: apmail-activemq-commits-archive@activemq.apache.org Received: (qmail 74785 invoked by uid 500); 4 Feb 2013 14:28:13 -0000 Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list commits@activemq.apache.org Received: (qmail 74752 invoked by uid 99); 4 Feb 2013 14:28:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Feb 2013 14:28:13 +0000 Date: Mon, 4 Feb 2013 14:28:12 +0000 (UTC) From: "Hiram Chirino (JIRA)" To: commits@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (APLO-292) javax.net.ssl.SSLException in latest snapshot MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/APLO-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570287#comment-13570287 ] Hiram Chirino commented on APLO-292: ------------------------------------ Can you guys reliably reproduce it? > javax.net.ssl.SSLException in latest snapshot > --------------------------------------------- > > Key: APLO-292 > URL: https://issues.apache.org/jira/browse/APLO-292 > Project: ActiveMQ Apollo > Issue Type: Bug > Environment: apollo-99-trunk-20130202.135855-180 > Reporter: Lionel Cons > > On some brokers with the latest Apollo snapshot, we do see: > 2013-02-04 14:18:54,382 | WARN | javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack? | > Any idea on what is causing this? -- 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