[jira] [Commented] (ACTIVEMQ6-94) HornetQ Bridge does not handle large messages

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508554#comment-14508554 ] ASF GitHub Bot commented on ACTIVEMQ6-94: - Github user gaohoward commented on th

[GitHub] activemq-6 pull request: ACTIVEMQ6-94 Large Message over Bridge an...

Github user gaohoward commented on the pull request: https://github.com/apache/activemq-6/pull/211#issuecomment-95464278 give me some time to test it. I remember this producer window probably won't fix it. --- If your project is set up for it, you can reply to this email and have yo

[jira] [Commented] (AMQ-5733) kill -9 always results in failure signal

[ https://issues.apache.org/jira/browse/AMQ-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508523#comment-14508523 ] Marc Schöchlin commented on AMQ-5733: - Attempting a shutdown by JMX and and SIGTERM (8)

Re: [DISCUSS] dev mailing list is cluttered

Thanks for that Bruce ! Regards JB On 04/23/2015 06:16 AM, Bruce Snyder wrote: I just submitted a request to create the mailing list, so it should be created very soon. After that, the only thing left to do is the redirect the email notifications from the various ActiveMQ JIRA spaces to the new

Re: [DISCUSS] dev mailing list is cluttered

I just submitted a request to create the mailing list, so it should be created very soon. After that, the only thing left to do is the redirect the email notifications from the various ActiveMQ JIRA spaces to the new list. Bruce On Wed, Apr 22, 2015 at 12:30 PM, artnaseef wrote: > What are the

[jira] [Commented] (ACTIVEMQ6-94) HornetQ Bridge does not handle large messages

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508352#comment-14508352 ] ASF GitHub Bot commented on ACTIVEMQ6-94: - Github user clebertsuconic commented

[GitHub] activemq-6 pull request: ACTIVEMQ6-94 Large Message over Bridge an...

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-6/pull/211#issuecomment-95404561 @gaohoward can you take a look on my changes please? This will close your PR.. maybe you should close #197 already... I would appreciate

[GitHub] activemq-6 pull request: ACTIVEMQ6-94 Large Message over Bridge an...

GitHub user clebertsuconic opened a pull request: https://github.com/apache/activemq-6/pull/211 ACTIVEMQ6-94 Large Message over Bridge and server's transfer You can merge this pull request into a Git repository by running: $ git pull https://github.com/clebertsuconic/activemq-

[jira] [Commented] (ACTIVEMQ6-94) HornetQ Bridge does not handle large messages

[ https://issues.apache.org/jira/browse/ACTIVEMQ6-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508351#comment-14508351 ] ASF GitHub Bot commented on ACTIVEMQ6-94: - GitHub user clebertsuconic opened a p

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

Any plans for a 5.11.2 release between now and the targeted 5.12.0 May release? Thanks for putting the effort into a more aggressive release schedule. Brian On Wed, Apr 22, 2015 at 4:35 PM, artnaseef wrote: > Thanks JB. I hope we can target a 5.12.0 release for May. > > If you change your min

[GitHub] activemq-6 pull request: Management Methods for first message time...

Github user clebertsuconic commented on the pull request: https://github.com/apache/activemq-6/pull/97#issuecomment-95353338 @dpocock sorry it took us this long to merge this... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] activemq-6 pull request: Management Methods for first message time...

Github user asfgit closed the pull request at: https://github.com/apache/activemq-6/pull/97 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is e

[GitHub] activemq-6 pull request: Avoiding possible deadlock after Proton d...

Github user asfgit closed the pull request at: https://github.com/apache/activemq-6/pull/210 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (AMQ-5735) increment redeliverCounter in the absence of client supplied information

[ https://issues.apache.org/jira/browse/AMQ-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-5735. - Resolution: Fixed resolved in http://git-wip-us.apache.org/repos/asf/activemq/commit/eb6c0826 the removeInf

[jira] [Commented] (AMQ-5709) Logging of "Database ... is locked" should be done on level DEBUG

[ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507935#comment-14507935 ] Arthur Naseef commented on AMQ-5709: Great - thank you Gary. > Logging of "Database ...

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

Thanks JB. I hope we can target a 5.12.0 release for May. If you change your mind and decide some commits are important, please let me know and I'll work with you to either get them in, or decide the best alternate course of action. -- View this message in context: http://activemq.2283324.n4.

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

I can do that - no problem. But it will have to wait until the cherry harvest is complete. -- View this message in context: http://activemq.2283324.n4.nabble.com/HEADSUP-ActiveMQ-5-10-3-release-preparation-tp4695445p4695465.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

To come up with the commit list, I used "git log" to find all commits from the time of the last release until now, on the master branch. Then, I literally reviewed each, looking at the following: * commit comments * Jira tickets, if any was identified in the commit comment * actual code changes

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

There is probably more than one way to do this. But lets say you start at local branch based off origin/activemq-5.10.x, cherry pick all your commits. Then run 'git log --oneline origin/activemq-5.10.x..HEAD' On Wed, Apr 22, 2015 at 2:58 PM, artnaseef wrote: > Hiram - if you provide the specifi

[GitHub] activemq-6 pull request: Avoiding possible deadlock after Proton d...

GitHub user clebertsuconic opened a pull request: https://github.com/apache/activemq-6/pull/210 Avoiding possible deadlock after Proton deliveries You can merge this pull request into a Git repository by running: $ git pull https://github.com/clebertsuconic/activemq-6 proton-f

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

+1 I planned to do some fixes on OSGi, but nothing release blocker. Regards JB On 04/22/2015 07:57 PM, artnaseef wrote: I have started working on the 5.10.3 release. Here is the list of commits that I plan to include in the release. Please advise of others which are important. Note that I h

[jira] [Commented] (AMQ-5709) Logging of "Database ... is locked" should be done on level DEBUG

[ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507811#comment-14507811 ] Gary Tully commented on AMQ-5709: - logging once as warn and every time as debug works fine.

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

to me that fix is a no-brainer really. an obvious fix the lock between live and backup was repeating the log message in an infinite mode. it was supposed to log only once before getting on a waiting forever until the live is dead. Anyways, it seems you are going to cherry-pick fixes towards 5.10

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

We can apply that fix it you feel strongly about it. The only reason I'm holding off that specific fix right now is the discussion I started on the ticket regarding the desired new state of operation. I saw your response there - thank you. If we could get Gary to comment, that would address or e

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

NOTE: commit 72837960cffc58b559ced6c243a459c62cb153cf is not an actual commit from the AMQ repo; the commit be6617507914532188530a605e476cb8ae59cdce covers it. Apologies for any confusion. -- View this message in context: http://activemq.2283324.n4.nabble.com/HEADSUP-ActiveMQ-5-10-3-release-pr

[jira] [Commented] (AMQ-5709) Logging of "Database ... is locked" should be done on level DEBUG

[ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507708#comment-14507708 ] Arthur Naseef commented on AMQ-5709: It would be good to hear from Gary since it was his

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

Hiram - if you provide the specific commands that will get me the exact output you want from the list of commits, then I'll gladly run them. Getting a log of the precise commit list is not trivial in my experience. You're assistance is greatly anticipated. -- View this message in context: htt

Re: [DISCUSS] dev mailing list is cluttered

What are the next steps here? -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-dev-mailing-list-is-cluttered-tp4694420p4695448.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

+1 a suggestion: one thing you could do push a branch to your fork also on github.. it's easier to verify that way. no plans to include https://issues.apache.org/jira/browse/AMQ-5709? It's a very simple fix. Also: what commit is this from your list? (72837960cffc58b559ced6c243a459c62cb153cf) i

Re: [HEADSUP] ActiveMQ 5.10.3 release preparation

Could you post a 'git log --oneline' of the changes? It will make it easier to review. On Wed, Apr 22, 2015 at 1:57 PM, artnaseef wrote: > I have started working on the 5.10.3 release. Here is the list of commits > that I plan to include in the release. > > Please advise of others which are imp

[HEADSUP] ActiveMQ 5.10.3 release preparation

I have started working on the 5.10.3 release. Here is the list of commits that I plan to include in the release. Please advise of others which are important. Note that I haven't yet reviewed open patch submissions and will do so shortly. Also note that I haven't yet confirmed that all of these

[jira] [Commented] (AMQ-5709) Logging of "Database ... is locked" should be done on level DEBUG

[ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507507#comment-14507507 ] clebert suconic commented on AMQ-5709: -- this wasn't a bug.. the lock was held by the ot

[jira] [Commented] (AMQ-5709) Logging of "Database ... is locked" should be done on level DEBUG

[ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507491#comment-14507491 ] Arthur Naseef commented on AMQ-5709: If I'm reading the commits correctly, the fix was t

[jira] [Commented] (AMQ-5552) introduce a smoke-test profile that is enabled by default and during release:prepare

[ https://issues.apache.org/jira/browse/AMQ-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507206#comment-14507206 ] Gary Tully commented on AMQ-5552: - the existing sure-fire profiles using the property active

Re: Slow Consumer Detection

have you looked at: http://activemq.apache.org/slow-consumer-handling.html ? On Wed, Apr 22, 2015 at 8:10 AM, salma ali wrote: > what is the best way to detect Slow consumer in ActiveMQ 5.11 to end their > connection , please help ? > > > > -- > View this message in context: > http://activemq.2

Slow Consumer Detection

what is the best way to detect Slow consumer in ActiveMQ 5.11 to end their connection , please help ? -- View this message in context: http://activemq.2283324.n4.nabble.com/Slow-Consumer-Detection-tp4695426.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Created] (AMQ-5741) Automate the generation of the table of MBeans and their properties on the webpage

Tim Bain created AMQ-5741: - Summary: Automate the generation of the table of MBeans and their properties on the webpage Key: AMQ-5741 URL: https://issues.apache.org/jira/browse/AMQ-5741 Project: ActiveMQ

[jira] [Commented] (AMQ-5712) Broker can deadlock when using queues while producers wait on disk space

[ https://issues.apache.org/jira/browse/AMQ-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507000#comment-14507000 ] Christopher L. Shannon commented on AMQ-5712: - Thanks Timothy. I have tested ou

[jira] [Created] (AMQ-5740) Support --resetStatistics option for 'purge' command

Martin Lichtin created AMQ-5740: --- Summary: Support --resetStatistics option for 'purge' command Key: AMQ-5740 URL: https://issues.apache.org/jira/browse/AMQ-5740 Project: ActiveMQ Issue Type: W

[jira] [Created] (AMQ-5739) Document 'dstat' command

Martin Lichtin created AMQ-5739: --- Summary: Document 'dstat' command Key: AMQ-5739 URL: https://issues.apache.org/jira/browse/AMQ-5739 Project: ActiveMQ Issue Type: Improvement Repor

[GitHub] activemq-6 pull request: Queue Auto-create fixes on OpenWire

Github user asfgit closed the pull request at: https://github.com/apache/activemq-6/pull/209 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: Special Board Report

Tracy, We are getting commits and contributions from those outside the HornetQ team. It is natural that the majority of work at this point would be done by those familiar with the code base. The ActiveMQ Artemis project has only been around for 6 month or so. Therefore every commit on the

[jira] [Commented] (AMQ-5738) AMQP memory leak of sender links while closing non-durable consumers

[ https://issues.apache.org/jira/browse/AMQ-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506721#comment-14506721 ] Robbie Gemmell commented on AMQ-5738: - I noticed this while investigating memory leaks w

[jira] [Resolved] (AMQ-5738) AMQP memory leak of sender links while closing non-durable consumers

[ https://issues.apache.org/jira/browse/AMQ-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved AMQ-5738. - Resolution: Fixed > AMQP memory leak of sender links while closing non-durable consumers > -

[jira] [Commented] (AMQ-5738) AMQP memory leak of sender links while closing non-durable consumers

[ https://issues.apache.org/jira/browse/AMQ-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506720#comment-14506720 ] Robbie Gemmell commented on AMQ-5738: - Fixed in https://git-wip-us.apache.org/repos/asf

[jira] [Created] (AMQ-5738) AMQP memory leak of sender links while closing non-durable consumers

Robbie Gemmell created AMQ-5738: --- Summary: AMQP memory leak of sender links while closing non-durable consumers Key: AMQ-5738 URL: https://issues.apache.org/jira/browse/AMQ-5738 Project: ActiveMQ