[jira] Updated: (AMQ-2928) new 5.4.0 activemq sysv init script tries to open the JDWP debug port when run with "stop"

[ https://issues.apache.org/activemq/browse/AMQ-2928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mats Henrikson updated AMQ-2928: Description: With the new ActiveMQ 5.4.0 if you have /etc/default/activemq configured with the f

[jira] Created: (AMQ-2928) new 5.4.0 activemq sysv init script tries to open the JDWP debug port when run with "stop"

new 5.4.0 activemq sysv init script tries to open the JDWP debug port when run with "stop" -- Key: AMQ-2928 URL: https://issues.apache.org/activemq/browse/AMQ-2928

[jira] Created: (AMQ-2920) new ActiveMQ 5.4.0 sysv start script redirects process stdout and stderr to /dev/null

new ActiveMQ 5.4.0 sysv start script redirects process stdout and stderr to /dev/null - Key: AMQ-2920 URL: https://issues.apache.org/activemq/browse/AMQ-2920 Project:

[jira] Commented: (AMQ-2583) Implement stomp+nio+ssl transport

[ https://issues.apache.org/activemq/browse/AMQ-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61858#action_61858 ] Mats Henrikson commented on AMQ-2583: - I am interested in the same thing as Martin, SSL+NIO

[jira] Commented: (AMQ-2332) it's possible to cause a deadlock in ActiveMQ 5.2 using the client

[ https://issues.apache.org/activemq/browse/AMQ-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60594#action_60594 ] Mats Henrikson commented on AMQ-2332: - This has been resolved as Fixed, was it really? Beca

[jira] Updated: (AMQ-2618) systemUsage tempUsage limit causes broker to lock up when using permanent queue with persistent messages

[ https://issues.apache.org/activemq/browse/AMQ-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mats Henrikson updated AMQ-2618: Attachment: UnlimitedEnqueueTest.java > systemUsage tempUsage limit causes broker to lock up when

[jira] Created: (AMQ-2618) systemUsage tempUsage limit causes broker to lock up when using permanent queue with persistent messages

systemUsage tempUsage limit causes broker to lock up when using permanent queue with persistent messages Key: AMQ-2618 URL: https://issues.apache.org/activemq

[jira] Commented: (AMQ-2616) filling a temporary queue and disconnecting does not free the queues Usage Manager memory limit

[ https://issues.apache.org/activemq/browse/AMQ-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57649#action_57649 ] Mats Henrikson commented on AMQ-2616: - A more realistic sequence of events is this: # Consu

[jira] Updated: (AMQ-2616) filling a temporary queue and disconnecting does not free the queues Usage Manager memory limit

[ https://issues.apache.org/activemq/browse/AMQ-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mats Henrikson updated AMQ-2616: Attachment: activemq.xml > filling a temporary queue and disconnecting does not free the queues U

[jira] Created: (AMQ-2616) filling a temporary queue and disconnecting does not free the queues Usage Manager memory limit

filling a temporary queue and disconnecting does not free the queues Usage Manager memory limit --- Key: AMQ-2616 URL: https://issues.apache.org/activemq/browse/AMQ-2616

[jira] Reopened: (AMQ-2352) it should be possible to specify userName and password in the webconsole-properties.xml

[ https://issues.apache.org/activemq/browse/AMQ-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mats Henrikson reopened AMQ-2352: - Please note that JNDIConfiguration.java has had the user/password methods mixed around as well, an

[jira] Updated: (AMQ-2368) it makes no sense for activemq-admin to load SUNJMX env var from /etc/activemq.conf

[ https://issues.apache.org/activemq/browse/AMQ-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mats Henrikson updated AMQ-2368: Attachment: activemq-admin_reset_SUNJMX.patch > it makes no sense for activemq-admin to load SUNJ

[jira] Created: (AMQ-2368) it makes no sense for activemq-admin to load SUNJMX env var from /etc/activemq.conf

it makes no sense for activemq-admin to load SUNJMX env var from /etc/activemq.conf --- Key: AMQ-2368 URL: https://issues.apache.org/activemq/browse/AMQ-2368 Project: Act

[jira] Commented: (AMQ-2356) optimizeDispatch=true and UseDedicatedTaskRunner=false lead to deadlocked queues

[ https://issues.apache.org/activemq/browse/AMQ-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53759#action_53759 ] Mats Henrikson commented on AMQ-2356: - Yes, but only in 5.2. Unfortunately I can't get the

[jira] Commented: (AMQ-2356) optimizeDispatch=true and UseDedicatedTaskRunner=false lead to deadlocked queues

[ https://issues.apache.org/activemq/browse/AMQ-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53669#action_53669 ] Mats Henrikson commented on AMQ-2356: - I just downloaded the latest 5.3-SNAPSHOT dated Mon

[jira] Created: (AMQ-2356) optimizeDispatch=true and UseDedicatedTaskRunner=false lead to deadlocked queues

optimizeDispatch=true and UseDedicatedTaskRunner=false lead to deadlocked queues Key: AMQ-2356 URL: https://issues.apache.org/activemq/browse/AMQ-2356 Project: ActiveMQ

[jira] Commented: (AMQ-2332) it's possible to cause a deadlock in ActiveMQ 5.2 using the client

[ https://issues.apache.org/activemq/browse/AMQ-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53444#action_53444 ] Mats Henrikson commented on AMQ-2332: - I believe that the most likely cause was a non-optim

[jira] Commented: (AMQ-2332) it's possible to cause a deadlock in ActiveMQ 5.2 using the client

[ https://issues.apache.org/activemq/browse/AMQ-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52981#action_52981 ] Mats Henrikson commented on AMQ-2332: - Versions for the broker: ActiveMQ 5.2 release java

[jira] Created: (AMQ-2332) it's possible to cause a deadlock in ActiveMQ 5.2 using the client

it's possible to cause a deadlock in ActiveMQ 5.2 using the client -- Key: AMQ-2332 URL: https://issues.apache.org/activemq/browse/AMQ-2332 Project: ActiveMQ Issue Type: Bug