Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 19 Sep 2011 06:36:09 +0000 (UTC)
From: "Hariharan (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1506571925.41182.1316414169202.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <179784946.34460.1316176209328.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3502) Subscribers lost from AMQ broker
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hariharan commented on AMQ-3502:
--------------------------------

Hi,
Can someone please help me out with this. We were forced to restart our production broker instance with a lot of hesitation and so we would like to put any kind of fix around it to avoid this from happening again in the future.

Thanks
Hari

> Subscribers lost from AMQ broker
> --------------------------------
>
>                 Key: AMQ-3502
>                 URL: https://issues.apache.org/jira/browse/AMQ-3502
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Hariharan
>              Labels: activemq, broker
>
> Hello,
> We are using AMQ 5.5.
> It has been working perfectly since we upgraded from 5.3 to 5.5. But, this morning out of nowhere the broker started reporting a bunch of durable subscribers as inactive i.e. placed them under 'false' folder in 'Subscription' folder. And the 'Durable' and 'Non-Durable' folders under 'Subscription' went missing. Upon further investigation, we found that the subscribers marked as false (inactive) were actually subscribed to the resp. topics and were active.
> Some publishers were also not able to publish messages.
> We tried looking through activemq.log and kahadb.log files but nothing could be found. In the end we had to restart the broker to get it back to normal state.
> Have you ever come across a situation like this before? Any thoughts on what could have caused this to happen?
> Thank you in Advance.
> Hari

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira