[VOTE] Release Apache Apollo 1.0

Hi Everyone, I think Apollo has reached that point where it's ready to go out into the world as a 1.0 release. I've been pounding it the last few weeks and finally the last of the bugs that I know about have been shaken out. It's been a long road! First beta release happened in Apr 2011 and 5 be

[jira] [Updated] (AMQ-3680) Cleanup of temporary destinations by PooledConnection and ConnectionPool either leaks temp dests or deletes too many

[ https://issues.apache.org/jira/browse/AMQ-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-3680: --- Attachment: TestConnectionPoolTempCleanup.java JUnit that quickly demonstrates the issue. Includes cod

[jira] [Commented] (AMQ-3457) temp destinations should only be deleted once all users of a pooled connection call close

[ https://issues.apache.org/jira/browse/AMQ-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192728#comment-13192728 ] Arthur Naseef commented on AMQ-3457: Created AMQ-3680 to follow up. It turns out I can'

[jira] [Updated] (AMQ-3680) Cleanup of temporary destinations by PooledConnection and ConnectionPool either leaks temp dests or deletes too many

[ https://issues.apache.org/jira/browse/AMQ-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arthur Naseef updated AMQ-3680: --- Attachment: pooledConnCleanupOwnTemps.patch Patch which adds the correct cleanup on close() of PooledCo

[jira] [Closed] (AMQ-3053) misplaced semicolon in bin/activemq l

[ https://issues.apache.org/jira/browse/AMQ-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3053. - Resolution: Fixed The revamped scripts should have resolved this issue. > misplaced semico

[jira] [Created] (AMQ-3680) Cleanup of temporary destinations by PooledConnection and ConnectionPool either leaks temp dests or deletes too many

Cleanup of temporary destinations by PooledConnection and ConnectionPool either leaks temp dests or deletes too many Key: AMQ-3680 URL: https://is

[jira] [Updated] (AMQ-3679) Bad osgi metadata for activeio-core introduced with fix for AMQ-3461

[ https://issues.apache.org/jira/browse/AMQ-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McKibben updated AMQ-3679: -- Patch Info: Patch Available > Bad osgi metadata for activeio-core introduced with fix for AMQ

[jira] [Updated] (AMQ-3679) Bad osgi metadata for activeio-core introduced with fix for AMQ-3461

[ https://issues.apache.org/jira/browse/AMQ-3679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McKibben updated AMQ-3679: -- Attachment: patch Patch for bnd OSGI metadata generation in pom.xml > Bad osgi m

[jira] [Commented] (AMQ-3635) JmsTopicConnector checks for presence of localClientId then uses outboundClientId

[ https://issues.apache.org/jira/browse/AMQ-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192706#comment-13192706 ] Timothy Bish commented on AMQ-3635: --- Looks like you might be right. A good way forward is

[jira] [Created] (AMQ-3679) Bad osgi metadata for activeio-core introduced with fix for AMQ-3461

Bad osgi metadata for activeio-core introduced with fix for AMQ-3461 Key: AMQ-3679 URL: https://issues.apache.org/jira/browse/AMQ-3679 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (AMQ-3457) temp destinations should only be deleted once all users of a pooled connection call close

[ https://issues.apache.org/jira/browse/AMQ-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192700#comment-13192700 ] Timothy Bish commented on AMQ-3457: --- You are welcome to reopen or create a new issue with

[jira] [Commented] (AMQ-3461) ActiveIO fix osgi metadata

[ https://issues.apache.org/jira/browse/AMQ-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192693#comment-13192693 ] Michael McKibben commented on AMQ-3461: --- Dejan, there is a bug with this commit that c

[jira] [Commented] (AMQ-3457) temp destinations should only be deleted once all users of a pooled connection call close

[ https://issues.apache.org/jira/browse/AMQ-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192684#comment-13192684 ] Arthur Naseef commented on AMQ-3457: Is there more I can do to facilitate this? I know

[jira] [Commented] (AMQ-3674) TopicRegion removes durableScriber from durableSubscriptions when it is active; but leaves subscription on Topic

[ https://issues.apache.org/jira/browse/AMQ-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192615#comment-13192615 ] Timothy Bish commented on AMQ-3674: --- Good catch, fixed it. > TopicRegion

[jira] [Commented] (AMQ-3674) TopicRegion removes durableScriber from durableSubscriptions when it is active; but leaves subscription on Topic

[ https://issues.apache.org/jira/browse/AMQ-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192594#comment-13192594 ] Dominic Tootell commented on AMQ-3674: -- Hi Tim, Thanks for the feedback. Just wonderi

[jira] [Resolved] (AMQ-3603) STOMP 1.1 introduced the heartBeat header implemented by the inactivity monitor, would be nice to have this option for stomp 1.0

[ https://issues.apache.org/jira/browse/AMQ-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-3603. - Resolution: Fixed > STOMP 1.1 introduced the heartBeat header implemented by the inactivity > monitor,

[jira] [Commented] (AMQ-3630) NetworkBridgeFilterFactory should be assigned to Queue not NetworkBridge

[ https://issues.apache.org/jira/browse/AMQ-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192498#comment-13192498 ] Timothy Bish commented on AMQ-3630: --- Do you have a test case for this? Care to submit a t

[jira] [Commented] (AMQ-3603) STOMP 1.1 introduced the heartBeat header implemented by the inactivity monitor, would be nice to have this option for stomp 1.0

[ https://issues.apache.org/jira/browse/AMQ-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192492#comment-13192492 ] Timothy Bish commented on AMQ-3603: --- @gtully can we close this one now? it looks complete

[jira] [Resolved] (AMQ-3675) Removing a DurableTopicSubscription leaves subscription in active subscriptions map

[ https://issues.apache.org/jira/browse/AMQ-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-3675. --- Resolution: Fixed Fix Version/s: 5.6.0 Assignee: Timothy Bish Cleaned up the test to re

why nobody pay attention to this bug https://issues.apache.org/jira/browse/AMQ-3281

There are numerous reports of similar issues, and it is a credible and critical bug that prevents any serious usages of ActiveMQ in production. We should vote to push the resolution of this bug ASAP

Re: {VOTE] Release Apache.NMS.ActiveMQ 1.5.3

+1 There's a minor typo on the release page. The link text to the source zip still shows 1.5.2. The rest looks good. On Mon, Jan 23, 2012 at 5:29 PM, Timothy Bish wrote: > Hello > > This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.5.3. > > New in this release: > > * This rel

[jira] [Resolved] (AMQ-3674) TopicRegion removes durableScriber from durableSubscriptions when it is active; but leaves subscription on Topic

[ https://issues.apache.org/jira/browse/AMQ-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-3674. --- Resolution: Fixed Fix Version/s: 5.6.0 Assignee: Timothy Bish Simplified the test case

[jira] [Resolved] (AMQ-3573) Hardcoded defaults for systemUsage not suitable for out of the box

[ https://issues.apache.org/jira/browse/AMQ-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-3573. --- Resolution: Fixed Applied fix to fix failing tests in Eclipse > Hardcoded defaults for

[jira] [Reopened] (AMQ-3573) Hardcoded defaults for systemUsage not suitable for out of the box

[ https://issues.apache.org/jira/browse/AMQ-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened AMQ-3573: --- The fix breaks the unit tests in Eclipse and other tools where the temp dir value is not set as an Absolut

[jira] [Resolved] (AMQ-3573) Hardcoded defaults for systemUsage not suitable for out of the box

[ https://issues.apache.org/jira/browse/AMQ-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-3573. - Resolution: Fixed Fix Version/s: 5.6.0 Added warning and error messages is SystemUsage values cannot

[jira] [Assigned] (AMQ-3573) Hardcoded defaults for systemUsage not suitable for out of the box

[ https://issues.apache.org/jira/browse/AMQ-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-3573: --- Assignee: Rob Davies > Hardcoded defaults for systemUsage not suitable for out of the box > --

Re: {VOTE] Release Apache.NMS.ActiveMQ 1.5.3

+1 ** *Hiram Chirino* *Software Fellow | FuseSource Corp.* *chir...@fusesource.com | fusesource.com* *skype: hiramchirino | twitter: @hiramchirino * *blog: Hiram Chirino's Bit Mojo * * * On Mon, Jan 23, 2012 at 8:29 PM, Timo

[jira] [Created] (AMQ-3678) Active Durable Topic Consumer is not re-assigned to Topic after it is deleted and recreated

Active Durable Topic Consumer is not re-assigned to Topic after it is deleted and recreated --- Key: AMQ-3678 URL: https://issues.apache.org/jira/browse/AMQ-3678

[jira] [Updated] (AMQ-3678) Active Durable Topic Consumer is not re-assigned to Topic after it is deleted and recreated

[ https://issues.apache.org/jira/browse/AMQ-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Tootell updated AMQ-3678: - Attachment: Topic.patch.txt CountMessagesRecievedOnDurableTopicAfterTopicDeletion.ja

[jira] [Commented] (AMQNET-356) Inactivity monitor (or another background task) cause a NullPointerException in ActiveMQ

[ https://issues.apache.org/jira/browse/AMQNET-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192075#comment-13192075 ] Mikael Finstad commented on AMQNET-356: --- We are having the same symptoms. Last sunda

Re: {VOTE] Release Apache.NMS.ActiveMQ 1.5.3

+1 On 24 January 2012 01:29, Timothy Bish wrote: > Hello > > This is a call for a vote on the release of Apache.NMS.ActiveMQ v1.5.3. > > New in this release: > > * This release focuses on stability fixes for the NMS > ActiveMQ client, no new features were added in this release. > > The binaries a

Jenkins build is still unstable: ActiveMQ #863

See