[jira] [Commented] (AMQ-3728) Broker stops to accept messages

[ https://issues.apache.org/jira/browse/AMQ-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223824#comment-13223824 ] Timothy Bish commented on AMQ-3728: --- Since there is an offline durable subscriber the stor

[jira] [Closed] (AMQ-3741) Deadlock on Broker when JMX is enabled

[ https://issues.apache.org/jira/browse/AMQ-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3741. - Resolution: Fixed >From a code review of trunk this is already resolved by other fixes that have >changed

[jira] [Closed] (AMQ-3753) Exception on stopping the broker - Timer already cancelled

[ https://issues.apache.org/jira/browse/AMQ-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3753. - Resolution: Incomplete Not enough info provided here to go on. > Exception on stopping the

[jira] [Commented] (AMQ-3755) receiveNoWait blocked on same mutex as sending threads

[ https://issues.apache.org/jira/browse/AMQ-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223345#comment-13223345 ] Timothy Bish commented on AMQ-3755: --- VMTransport doesn't cause the locking issue, that exi

[jira] [Issue Comment Edited] (AMQ-3755) receiveNoWait blocked on same mutex as sending threads

[ https://issues.apache.org/jira/browse/AMQ-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223149#comment-13223149 ] Claudio Tagliola edited comment on AMQ-3755 at 3/6/12 2:56 PM: ---

[jira] [Created] (AMQ-3758) Recover scheduler database option

Recover scheduler database option - Key: AMQ-3758 URL: https://issues.apache.org/jira/browse/AMQ-3758 Project: ActiveMQ Issue Type: Improvement Components: Message Store Affects Versions: 5.5.0

[jira] [Resolved] (AMQ-2287) ActiveMQMessage.setXXXProperty() method needs to check if property name is a valid Java identifier.

[ https://issues.apache.org/jira/browse/AMQ-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke resolved AMQ-2287. - Resolution: Won't Fix Assignee: Torsten Mielke > ActiveMQMessage.setXXXProperty() method

[jira] [Commented] (AMQ-2287) ActiveMQMessage.setXXXProperty() method needs to check if property name is a valid Java identifier.

[ https://issues.apache.org/jira/browse/AMQ-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223161#comment-13223161 ] Torsten Mielke commented on AMQ-2287: - I am going to close this bug. If we decide to fi

[jira] [Updated] (AMQ-2287) ActiveMQMessage.setXXXProperty() method needs to check if property name is a valid Java identifier.

[ https://issues.apache.org/jira/browse/AMQ-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Torsten Mielke updated AMQ-2287: Description: currently the AMQ implementation of javax.jms.Message.setXXXProperty() does not check i

[jira] [Commented] (AMQ-3755) receiveNoWait blocked on same mutex as sending threads

[ https://issues.apache.org/jira/browse/AMQ-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223149#comment-13223149 ] Claudio Tagliola commented on AMQ-3755: --- We had a hunch we had to move to a multiple V

Jenkins build is still unstable: ActiveMQ #899

See