42327a490a
ARTEMIS-2480 - Reloading configuration can kill broker
...
https://issues.apache.org/jira/browse/ARTEMIS-2480
2019-09-11 17:37:11 +02:00
02d3384b87
This closes #2828
2019-09-11 09:41:38 -04:00
793a45f35a
NO-JIRA Speeding up JMSNonDestructiveTest
2019-09-11 09:37:03 -04:00
e43c5390cf
ARTEMIS-2478 Expired message not removed in non destructive queue
2019-09-11 09:37:03 -04:00
a8d68d9dd7
This closes #2833
2019-09-10 20:10:20 -04:00
a2dd5ae590
ARTEMIS-2483 Sync calculation should use the block size
2019-09-10 20:10:19 -04:00
485043cf0b
This closes #2829
2019-09-10 20:05:26 -04:00
c5376789b0
ARTEMIS-2475 log metrics plugin init details
2019-09-10 20:05:25 -04:00
9002bc533f
This closes #2818
2019-09-10 15:04:19 -04:00
1928180a7c
ARTEMIS-2467 Allowing create of static clusters through CLI
2019-09-10 15:04:18 -04:00
2a2b6bc260
This closes #2826
2019-09-10 15:03:02 -04:00
5373c60891
ARTEMIS-2474 Retry interval ignored on Backup Connectors
2019-09-10 15:03:01 -04:00
b583ba7a47
This closes #2830
2019-09-10 15:02:27 -04:00
60b62940b9
ARTEMIS-2479 Initial connection will not work with infinite retry and multiple nodes
2019-09-10 15:02:27 -04:00
54de31e813
NO-JIRA Fixing intermittent failures
2019-09-10 15:00:45 -04:00
7fd7558ed8
NO-JIRA Fixing intermittent failures
2019-09-10 14:53:49 -04:00
d888e91cf2
This closes #2827
2019-09-09 17:43:03 -04:00
9a1a2b1369
ARTEMIS-2477 - create a less verbose and more descriptive warning when the native Netty jars are not present on the classpath
...
https://issues.apache.org/jira/browse/ARTEMIS-2477
2019-09-09 17:42:52 -04:00
298ad01b4f
This closes #2814
2019-09-06 14:27:01 -04:00
fb01bc5644
ARTEMIS-2465 [JDBC-STORE] Adding index on txId
2019-09-06 14:27:00 -04:00
0a0b0fcb23
This closes #2823
2019-09-06 14:26:30 -04:00
da6fedf6ae
ARTEMIS-2472 Persistent and delivering size not right in replacement of lvq message
2019-09-06 14:26:30 -04:00
85170ace50
This closes #2825
2019-09-06 14:26:04 -04:00
9413925957
ARTEMIS-2473 RemoteQueueBindingImpl should check for empty filters
2019-09-06 14:26:03 -04:00
48027bdee2
This closes #2824
2019-09-06 14:24:59 -04:00
93dcd27b39
NO-JIRA Fixing intermittent failure on BasicXaTest
...
It would fail on cannot destroy queue
as the failure could be asynchronous, introducing a quick race, which is acceptable
you just need to make sure the async operation will finish before removing the queue.
Fix is to introduce a Wait.assertEquals call.
2019-09-06 10:28:14 -04:00
07276ee09c
This closes #2822
2019-09-05 15:41:34 -04:00
7263e820f3
NO-JIRA Fixing intermittent failure on CreditsSemaphoreTest
2019-09-05 15:41:33 -04:00
cfd84f3994
This closes #2821
2019-09-05 09:21:36 -05:00
a9ce90f97a
ARTEMIS-2471 JdbcNodeManager doesn't use jdbc-user and jdbc-password tags
2019-09-05 09:21:35 -05:00
0106329816
This closes #2820
2019-09-04 12:09:54 +02:00
39fe4fd9ef
Updated Apache BeanUtils to address CVE
...
1.9.4 is a minor update do address CVE-2014-0114:
http://commons.apache.org/proper/commons-beanutils/javadocs/v1.9.4/RELEASE-NOTES.txt
2019-09-04 12:09:54 +02:00
9c1cbf3dc9
This closes #2703
2019-09-04 11:02:19 +08:00
4a61d2dc76
ARTEMIS-2380 Fix delivering message in the case of consume close
2019-09-04 11:02:16 +08:00
8dd1501971
This closes #2819
2019-09-03 09:28:57 -05:00
a3a5a48d2e
ARTEMIS-2468 console.war doesn't need checker-compat-qual lib
2019-09-03 09:28:57 -05:00
289e5b8d44
This closes #2817
2019-08-29 18:42:29 -04:00
60a15f3b50
ARTEMIS-2424 Testing functionality where we disable isReacheable if a ping custom command is used
2019-08-29 18:41:34 -04:00
90e4384a41
ARTEMIS-2424 Add option to override isReachable()
...
Added check for non default ping command(s)
Bypass InetAddress.isReachable() to allow exclusive use of user defined
ping command(S).
2019-08-29 18:25:31 -04:00
84c4c2a754
This closes #2813
2019-08-29 09:38:00 -04:00
397cef699a
ARTEMIS-2462 Allow store-forward queue to be deleted afte scaledown
...
After a node is scaled down to a target node, the sf queue in the
target node is not deleted.
Normally this is fine because may be reused when the scaled down
node is back up.
However in cloud environment many drainer pods can be created and
then shutdown in order to drain the messages to a live node (pod).
Each drainer pod will have a different node-id. Over time the sf
queues in the target broker node grows and those sf queues are
no longer reused.
Although use can use management API/console to manually delete
them, it would be nice to have an option to automatically delete
those sf queue/address resources after scale down.
In this PR it added a boolean configuration parameter called
cleanup-sf-queue to scale down policy so that if the parameter
is "true" the broker will send a message to the
target broker signalling that the SF queue is no longer
needed and should be deleted.
If the parameter is not defined (default) or is "false"
the scale down won't remove the sf queue.
2019-08-28 21:16:38 +08:00
3a58387bd3
NO-JIRA Fixing ScaleDownDirectTest and ReconnectTest
2019-08-27 16:52:02 -04:00
3293aba119
NO-JIRA Fixing SharedNothingReplicationFlowControlTest::testSendPages
2019-08-27 14:52:16 -04:00
321a0c2ea4
This closes #2812
2019-08-27 11:33:53 -04:00
b7906399f5
ARTEMIS-2423 doc auto-create/delete for core API
2019-08-27 11:33:52 -04:00
5d9395ddb9
NO-JIRA Fixing intermittent failure on QuorumFailOverLiveVotesTest
2019-08-27 11:28:01 -04:00
b52dec085a
NO-JIRA Bumping extra-tests pom
2019-08-26 10:44:23 -04:00
5016f69daa
[maven-release-plugin] prepare for next development iteration
2019-08-26 10:42:13 -04:00
f092d5396a
[maven-release-plugin] prepare release 2.10.0
2019-08-26 10:42:01 -04:00
52c38fbf7d
This closes #2810
2019-08-26 10:06:53 -04:00
Andy Taylor
Clebert Suconic
Wei Yang
Justin Bertram
Francesco Nigro
Jan Boehm
Tom
Howard Gao