[GitHub] activemq-artemis pull request #2405: ARTEMIS-2158 don't get pagedMessage if ...
GitHub user wy96f opened a pull request: https://github.com/apache/activemq-artemis/pull/2405 ARTEMIS-2158 don't get pagedMessage if it's nontransactional Transaction id of the non transactional paged message is -1. When we acknowledge the message, we judge transactionID < 0 and get paged message. The page where message resides maybe retrieved causing performance degradation. So we only need to get paged message if transactionID < -1 instead of 0. You can merge this pull request into a Git repository by running: $ git pull https://github.com/wy96f/activemq-artemis default_page_reference_transaction_id Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/2405.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2405 commit e024efcccde28ec6ad863cc4d1ad1df7e105905c Author: yang wei Date: 2018-10-31T02:02:11Z ARTEMIS-2158 don't get pagedMessage if it's nontransactional ---
[GitHub] activemq-artemis pull request #2387: ARTEMIS-2142 Support JMSXGroupSeq -1to ...
Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/2387 ---
[GitHub] activemq-artemis pull request #2390: NO-JIRA Move JMS_SESSION_CLIENT_ID_PROP...
Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/2390 ---
[GitHub] activemq-artemis pull request #2392: ARTEMIS-2100 address routing-type overr...
Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/2392 ---
[GitHub] activemq-artemis issue #2400: ARTEMIS-2151 JMS Selectors broken in some case...
Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/2400 The some cases you mention is just AMQGroupID? If that's the case can you rename the JIRA and commit here? something like AMQGroupID is ignored on filter? Or am I misunderstanding what you changed here? ---
[GitHub] activemq-artemis issue #2401: ARTEMIS-1710 Allow management msgs to pass the...
Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/2401 @franz1981 did you run a full testsuite on this? ---
[GitHub] activemq-artemis pull request #2402: NO-JIRA: Clarify journal-buffer-timeout...
Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/2402 ---
[GitHub] activemq-artemis pull request #2403: ARTEMIS-2155 disconnect on failure to h...
Github user asfgit closed the pull request at: https://github.com/apache/activemq-artemis/pull/2403 ---
[GitHub] activemq-artemis pull request #2404: ARTEMIS-2157 Extra information on Criti...
GitHub user clebertsuconic opened a pull request: https://github.com/apache/activemq-artemis/pull/2404 ARTEMIS-2157 Extra information on CriticalAnalyzer and its components You can merge this pull request into a Git repository by running: $ git pull https://github.com/clebertsuconic/activemq-artemis ARTEMIS-2157 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/2404.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2404 commit 692c30a701374f28dceeb491ffcf5e16077a04dd Author: Clebert Suconic Date: 2018-10-30T20:10:35Z ARTEMIS-2157 Extra information on CriticalAnalyzer and its components ---
[GitHub] activemq-artemis pull request #2403: ARTEMIS-2155 disconnect on failure to h...
GitHub user jbertram opened a pull request: https://github.com/apache/activemq-artemis/pull/2403 ARTEMIS-2155 disconnect on failure to handle packet You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-2155 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/2403.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2403 commit cb627379a05d47b45874c970a8113d6a68e047ae Author: Justin Bertram Date: 2018-10-23T18:06:22Z ARTEMIS-2155 disconnect on failure to handle packet ---
[GitHub] activemq-artemis issue #2402: NO-JIRA: Clarify journal-buffer-timeout docume...
Github user cshannon commented on the issue: https://github.com/apache/activemq-artemis/pull/2402 I know, either way, this is just to update the documentation to say that 0 will disable the timed buffer ---
[GitHub] activemq-artemis issue #2402: NO-JIRA: Clarify journal-buffer-timeout docume...
Github user franz1981 commented on the issue: https://github.com/apache/activemq-artemis/pull/2402 You need to disable data-sync too if you want to rely just on the sync provided by OS ie just application failure protection AFAIK. Without being too OT, provided you have enough RAM, the mapped journal is specifically built to address this use case :) ---
[GitHub] activemq-artemis pull request #2402: NO-JIRA: Clarify journal-buffer-timeout...
GitHub user cshannon opened a pull request: https://github.com/apache/activemq-artemis/pull/2402 NO-JIRA: Clarify journal-buffer-timeout documentation Clarify how to disable the buffer timeout. On one of my test brokers I disabled journal-sync-transactional and journal-sync-non-transactional as data loss is not a big deal. In this scenario I just want to write directly to the file and not use a timed buffer and let the OS handle data syncing, however it was not clear on how to accomplish this. Looking at the code I discovered setting the timeout to 0 will disable the buffer so I'm adding a comment in case others want to do the same. You can merge this pull request into a Git repository by running: $ git pull https://github.com/cshannon/activemq-artemis persistenceDocUpdate Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/2402.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2402 ---
[ANNOUNCE] Apache ActiveMQ 5.15.7 Released
Hi everyone, The ActiveMQ team is pleased to announce that Apache ActiveMQ 5.15.7 has been released. A list of issues resolved in this release is available here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12344049 The Wiki page for the release is here: http://activemq.apache.org/activemq-5157-release.html A big thanks to everyone who contributed to this release.
[GitHub] activemq-artemis issue #2384: ARTEMIS-2141 Add Filter column to Consumers Vi...
Github user sebthom commented on the issue: https://github.com/apache/activemq-artemis/pull/2384 @michaelandrepearce Thanks for merging the PR! Is there any chance this gets backported/included into 2.6.4? ---
Re: Aggregate subscriptions from users
Hello Art, thanks for your help. Yes, it allready helped and confirmed that my first suggestion about this issue of decreasing the subscriptions from each client to a mininum will be the first step to go. But I'm not sure if removing all selectors would be a solution: What I've missed in my question was that we are talking about 2000 till 2 clients running in one network, each subscribing n-times to one JMS Server. So we are afraid that removing those selectors will cause a lot of unnecessary network traffic. To give you the whole example: Right now we are talking at that one customer about 2400 clients doing 28 individual subscriptions (that should make use of the "in" selector in my opinion) at least. Thanks in advance! Patrik -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html
