Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 9 Nov 2011 12:38:51 +0000 (UTC)
From: "Pauli Kaila (Updated) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1150438481.14077.1320842331818.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <978248107.14071.1320842331544.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (AMQ-3583) Failures to page in queue messages and
 retrieving messages caused by NullPointerExceptions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQ-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pauli Kaila updated AMQ-3583:
-----------------------------

    Attachment: exceptions.log
    
> Failures to page in queue messages and retrieving messages caused by NullPointerExceptions
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3583
>                 URL: https://issues.apache.org/jira/browse/AMQ-3583
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>         Environment: Network of brokers running on Windows XP SP3 machines. Java version is Sun JRE 1.6.0_23 32 bit.
>            Reporter: Pauli Kaila
>         Attachments: exceptions.log
>
>
> Our product is composed of a server and multiple clients. The server and each of the clients have their own internal ActiveMQ broker which are then joined in to a network of brokers. 
> After having ran successfully for almost two months the server on one of our customer installations stopped communicating with the clients. Based on the logs available (see the attachment) the issue seems to stem from ActiveMQ, which is failing to page in messages and retrieving messages because of NullPointerExceptions. The situation was only resolved after we instructed the customer to restart the server process, which also restarted the ActiveMQ broker.
> Sadly we do not have remote access to that particular installation so we could not investigate the issue closer. The only diagnostics we have about the issue are the aforementioned log statements.
> The broker is using Apache DerbyDB 10.6.1.0 for storage instead of the KahaDB.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira