[jira] [Comment Edited] (AMQ-5573) Configurable messages size for Stomp producer

[ https://issues.apache.org/jira/browse/AMQ-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518848#comment-14518848 ] Abhi edited comment on AMQ-5573 at 4/29/15 6:52 AM: Can you please docum

[jira] [Created] (AMQ-5751) Configuration to limit the number of Topics/Queues that can be created on broker

Abhi created AMQ-5751: - Summary: Configuration to limit the number of Topics/Queues that can be created on broker Key: AMQ-5751 URL: https://issues.apache.org/jira/browse/AMQ-5751 Project: ActiveMQ Issu

[jira] [Commented] (AMQ-5573) Configurable messages size for Stomp producer

[ https://issues.apache.org/jira/browse/AMQ-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518848#comment-14518848 ] Abhi commented on AMQ-5573: --- Can you please document this option on http://activemq.apache.org/tc

[jira] [Created] (AMQ-5720) Provide per adapter store usage limit in multi-KahaDB case

Abhi created AMQ-5720: - Summary: Provide per adapter store usage limit in multi-KahaDB case Key: AMQ-5720 URL: https://issues.apache.org/jira/browse/AMQ-5720 Project: ActiveMQ Issue Type: Improvement

[jira] [Commented] (AMQ-5705) originBrokerURL incorrectly set in advisory messages

[ https://issues.apache.org/jira/browse/AMQ-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392549#comment-14392549 ] Abhi commented on AMQ-5705: --- What kind of issues can be triggered by this? > originBrokerURL inco

[jira] [Commented] (AMQ-5585) Messages not reachable after moving

[ https://issues.apache.org/jira/browse/AMQ-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322695#comment-14322695 ] Abhi commented on AMQ-5585: --- Hi, Which memory limit are we talking about here - temp usage store o

[jira] [Commented] (AMQ-5510) Listener is not able to connect again once maxReconnectAttempts are exhausted by the ActiveMQ layers.

[ https://issues.apache.org/jira/browse/AMQ-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303312#comment-14303312 ] Abhi commented on AMQ-5510: --- Did anyone got a chance to look at this bug? > Listener is not able

[jira] [Issue Comment Deleted] (AMQ-5510) Listener is not able to connect again once maxReconnectAttempts are exhausted by the ActiveMQ layers.

[ https://issues.apache.org/jira/browse/AMQ-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhi updated AMQ-5510: -- Comment: was deleted (was: Did anyone got a chance to look at this bug?) > Listener is not able to connect again once max

[jira] [Updated] (AMQ-5510) Listener is not able to connect again once maxReconnectAttempts are exhausted by the ActiveMQ layers.

[ https://issues.apache.org/jira/browse/AMQ-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhi updated AMQ-5510: -- Description: I have multiple listeners sharing same connection and the broker url has maxReconnectAttempts property set t

[jira] [Created] (AMQ-5510) Listener is not able to connect again once maxReconnectAttempts are exhausted by the ActiveMQ layers.

Abhi created AMQ-5510: - Summary: Listener is not able to connect again once maxReconnectAttempts are exhausted by the ActiveMQ layers. Key: AMQ-5510 URL: https://issues.apache.org/jira/browse/AMQ-5510 Project: Ac

[jira] [Created] (AMQ-4965) Dequeue count for Topics increase for non-durable subscribers but not for durable subscribers

Abhi created AMQ-4965: - Summary: Dequeue count for Topics increase for non-durable subscribers but not for durable subscribers Key: AMQ-4965 URL: https://issues.apache.org/jira/browse/AMQ-4965 Project: ActiveMQ