You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hariharan (JIRA)" <ji...@apache.org> on 2011/09/16 14:30:09 UTC
[jira] [Created] (AMQ-3502) Subscribers lost from AMQ broker
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
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
[jira] [Commented] (AMQ-3502) Subscribers lost from AMQ broker
Posted by "Hariharan (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Closed] (AMQ-3502) Subscribers lost from AMQ broker
Posted by "Hariharan (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hariharan closed AMQ-3502.
--------------------------
Resolution: Not A Problem
This was caused due to memory space issue in the filer where the data dir was present.
> 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.
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
[jira] [Commented] (AMQ-3502) Subscribers lost from AMQ broker
Posted by "Hariharan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126543#comment-13126543 ]
Hariharan commented on AMQ-3502:
--------------------------------
The filer on which the data dir was present had run out of memory and that seems to have caused this.
> 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.
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