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 071021026B for ; Thu, 30 Jan 2014 23:22:11 +0000 (UTC) Received: (qmail 10110 invoked by uid 500); 30 Jan 2014 23:22:09 -0000 Delivered-To: apmail-activemq-commits-archive@activemq.apache.org Received: (qmail 10024 invoked by uid 500); 30 Jan 2014 23:22:09 -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 10014 invoked by uid 99); 30 Jan 2014 23:22:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jan 2014 23:22:09 +0000 Date: Thu, 30 Jan 2014 23:22:09 +0000 (UTC) From: "Hiram Chirino (JIRA)" To: commits@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (APLO-329) Connection being shut due to java.io.IOException 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-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino resolved APLO-329. -------------------------------- Resolution: Incomplete Need more info to proceed. > Connection being shut due to java.io.IOException > ------------------------------------------------ > > Key: APLO-329 > URL: https://issues.apache.org/jira/browse/APLO-329 > Project: ActiveMQ Apollo > Issue Type: Question > Components: apollo-broker > Affects Versions: 1.1 > Environment: RedHat 4.1.2-51 Architechture: x86_64 > Reporter: Sumanshu Dwivedi > Priority: Trivial > > We are using Apollo 1.1 currently. Today our connection to Apollo running on productions server crashed. I found in connections log exception as java.io.ioexception. I was trying to investigate it further, but cannot find more information in the logs. > So if someone could help me with location of any other logs through which I can investigate it further. > Thanks for the help. -- This message was sent by Atlassian JIRA (v6.1.5#6160)