[jira] Created: (AMQ-1672) Mirror Queues on Temp Queues is causing Memory leak

Mirror Queues on Temp Queues is causing Memory leak --- Key: AMQ-1672 URL: https://issues.apache.org/activemq/browse/AMQ-1672 Project: ActiveMQ Issue Type: Bug Components: Broker

[jira] Commented: (AMQ-1482) Channel was inactive for too long.

[ https://issues.apache.org/activemq/browse/AMQ-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42342#action_42342 ] Kevin Yaussy commented on AMQ-1482: --- Please see AMQ-1671, as it may be related? > Channel w

[jira] Commented: (AMQ-1582) If InactivityMonitor is inactive, exception notification are not reported

[ https://issues.apache.org/activemq/browse/AMQ-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42343#action_42343 ] Kevin Yaussy commented on AMQ-1582: --- Please see AMQ-1671, as it may be related. > If Inactiv

Re: [VOTE] Release ActiveMQ 5.1.0 (RC 3)

I attempted to build the RC3 snapshot today using a clean install. It gets most of the way through and then gives me an error that an artifact is missing. It failed to resolve artifact "org.apache.activemq:activemq-core:test-jar:tests:5.1.0". Looks like right before that error came up it was down

[jira] Created: (AMQ-1671) InactivityMonitor issue with regards to exceptions on a connection

InactivityMonitor issue with regards to exceptions on a connection -- Key: AMQ-1671 URL: https://issues.apache.org/activemq/browse/AMQ-1671 Project: ActiveMQ Issue Type: Bug

[jira] Resolved: (AMQ-1670) Element Order in the XSD do not match the order required by ActiveMQ

[ https://issues.apache.org/activemq/browse/AMQ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino resolved AMQ-1670. Fix Version/s: 5.1.0 (was: 5.2.0) Resolution: Fixed I have just com

[jira] Resolved: (AMQ-1664) Example illustrating trasactions

[ https://issues.apache.org/activemq/browse/AMQ-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1664. - Fix Version/s: 5.1.0 Resolution: Fixed Patch applied in SVN revision 649192 > Example illustra

[jira] Assigned: (AMQ-1664) Example illustrating trasactions

[ https://issues.apache.org/activemq/browse/AMQ-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1664: --- Assignee: Rob Davies > Example illustrating trasactions > > >

[jira] Assigned: (AMQ-1666) connection URI options not applied to both sides of VM transport

[ https://issues.apache.org/activemq/browse/AMQ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1666: --- Assignee: Rob Davies > connection URI options not applied to both sides of VM transport > -

[jira] Resolved: (AMQ-1666) connection URI options not applied to both sides of VM transport

[ https://issues.apache.org/activemq/browse/AMQ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1666. - Resolution: Fixed Patch applied by SVN revision 649191 > connection URI options not applied to both si

[jira] Resolved: (AMQ-1665) SslBrokerTest that verifies the programetic setting of truststore etc and negates the need to use javax.net.ssl. system props

[ https://issues.apache.org/activemq/browse/AMQ-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1665. - Resolution: Fixed Patch applied in SVN revision 649187 > SslBrokerTest that verifies the programetic s

Re: [VOTE] Release ActiveMQ 5.1.0 (RC 3)

Hi everyone seems these RC builds have really generated a surge in bug fixing activity. I'm going to change my vote to -1 for this RC so that we can try to include the bulk of those fixes into the next RC. Just goes to show we need to generate RCs more often and release more often too. Thanks and

[jira] Assigned: (AMQ-1665) SslBrokerTest that verifies the programetic setting of truststore etc and negates the need to use javax.net.ssl. system props

[ https://issues.apache.org/activemq/browse/AMQ-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1665: --- Assignee: Rob Davies (was: Hiram Chirino) > SslBrokerTest that verifies the programetic setting of

[jira] Work started: (AMQ-1670) Element Order in the XSD do not match the order required by ActiveMQ

[ https://issues.apache.org/activemq/browse/AMQ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AMQ-1670 started by Hiram Chirino. > Element Order in the XSD do not match the order required by ActiveMQ >

[jira] Created: (AMQ-1670) Element Order in the XSD do not match the order required by ActiveMQ

Element Order in the XSD do not match the order required by ActiveMQ Key: AMQ-1670 URL: https://issues.apache.org/activemq/browse/AMQ-1670 Project: ActiveMQ Issue Type: Bug

[jira] Commented: (AMQ-1638) XmlBeanDefinitionStoreException : activemq.xsd URL broken in spring.schemas

[ https://issues.apache.org/activemq/browse/AMQ-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42336#action_42336 ] Glen Mazza commented on AMQ-1638: - Our company has also stumbled upon this problem--it was rath

Re: Fix for AMQ-765

Hi Kai, we rarely go back and do fixes for older releases - we all tend to work from trunk cheers, Rob On 17 Apr 2008, at 12:36, khudalla wrote: Rob, good to hear that, I do have another issue with the RA pending for which I also have produced a fix. I will create an issue in JIRA and

Re: Fix for AMQ-765

Rob, good to hear that, I do have another issue with the RA pending for which I also have produced a fix. I will create an issue in JIRA and upload the patch once I figured it all out. However, is there a chance that the fix for 765 also makes it into the 4.x branch (since we are using a patche

Re: [VOTE] Release ActiveMQ 5.1.0 (RC 3)

+1 I think if we cancel the release each time we find a bug, we'll never be able to release anything. I'd rather do a minor bug fix release in a few weeks. I'll defer to Hiram if he thinks the bugs warrant delaying the release. My 2 cents. On Tue, Apr 15, 2008 at 6:06 PM, Hiram Chirino <[EMAIL P

Re: Fix for AMQ-765

Hi Kai, the patch looks great - appreciate it! What you say about the jira process makes sense - but we only check open issues - as it was marked as fixed - we didn't pay attention to it. The convention is to mark an issue as fixed only after its been committed to SVN. I've only update tr

Re: Fix for AMQ-765

Since I did not know the particular process of setting the status according to the progress in JIRA, I assumed that once someone had created a patch for the bug (thereby fixing it) he would (should?) set the status to fixed. Then someone (a committer?) could review the changes and then decide whet