4e63ee7cc7
https://issues.apache.org/jira/browse/AMQ-6100 - Virtual topic message destination should be the target queue
2015-12-21 15:19:22 +01:00
370b181099
https://issues.apache.org/jira/browse/AMQ-6097
...
remove un-needed import statements
2015-12-18 19:47:46 +00:00
246ccb8e04
https://issues.apache.org/jira/browse/AMQ-6097
...
Fixing KahaDB so that the correct marshaller is used for the message
keys inside of the message order index. This will ensure that message
size metrics are accurate.
2015-12-18 19:26:24 +00:00
b7787bf6fb
https://issues.apache.org/jira/browse/AMQ-6086 - test cannot validate all start failures scenarios at this time, suffice that start and stop complete ok
2015-12-14 16:46:22 +00:00
455a628305
https://issues.apache.org/jira/browse/AMQ-6086 - avoid logging npe on attempted start of persistence adapter post stop
2015-12-14 16:32:10 +00:00
35df815fb8
https://issues.apache.org/jira/browse/AMQ-6086 - start exception can prevent stop from exiting fully, need to be more selective in creation on stop.
2015-12-14 15:40:05 +00:00
da076f4a63
https://issues.apache.org/jira/browse/AMQ-6086 - add some determinism to interleaved stop and start calls on broker service
2015-12-11 16:22:31 +00:00
8609f74db3
https://issues.apache.org/jira/browse/AMQ-6083 - ignore test scenario on leveldb store
2015-12-11 11:21:06 +00:00
768fa17085
https://issues.apache.org/jira/browse/AMQ-6005 - have plist whack it existing state on start. Start the temp store after the primary persistence adapter which does the locking
2015-12-10 14:24:03 +00:00
d7febddb67
https://issues.apache.org/jira/browse/AMQ-6084 - add broker.adjustUsageLimits to disable the adjustment of limits to what is available. In this way, a broker will fail to start if constrained, ensuring it won't accept connections and block pending resources if it has earlier exited for that reason
2015-12-10 11:23:56 +00:00
5db5f3e39a
https://issues.apache.org/jira/browse/AMQ-6083 - ignoreMissingJournalfiles false - check for missing acks and corruption anywhere and error out so that corruption does not go unnoticed - fix and test
2015-12-09 12:30:29 +00:00
179dc3acb2
https://issues.apache.org/jira/browse/AMQ-6070 - rework for virtual topic case, use the destination from the transient region destination rather than the message, such that consumer queue advisories work for delivered etc
2015-12-08 11:05:25 +00:00
315147c5ef
https://issues.apache.org/jira/browse/AMQ-6074
...
Make the transportConnector configs consistent across all four variants
by removing the enableCipherSuites option on openwire NIO+SSL. RC4 was
enabled on the broker side but in later JDK releases that suite is
disbaled as it is insecure so the client side couldn't find a supported
suite.
2015-12-07 12:27:34 -05:00
75ff17af41
https://issues.apache.org/jira/browse/AMQ-6070 - set correct originalDestination property value in advisories
2015-12-03 12:14:18 +00:00
8363c99b51
https://issues.apache.org/jira/browse/AMQ-6069
...
Fixed contains method in PrioritizedPendinList which was not returning
correctly. This was causing messages to not be removed from the
dispatchPendingList when purge was called inside a Queue leading to an
eventual OOM error if enough messages were purged. This fix also
improves performance of the contains method.
2015-12-02 13:24:32 +00:00
144b711a9a
add some additional trace debug to investigate linear store usage, this test has been failing in ci for the past 7 builds but work ok locally. This additional trace will help diagnose
2015-11-30 14:04:27 +00:00
cfb4ca9f54
[maven-release-plugin] prepare for next development iteration
2015-11-30 13:48:58 +00:00
abfe038ddf
[maven-release-plugin] prepare release activemq-5.13.0
2015-11-30 13:48:11 +00:00
f09000d1e6
https://issues.apache.org/jira/browse/AMQ-6065 - ensure no call to exit. fix mock test to account for extra call
2015-11-30 13:24:19 +00:00
0a12bcb928
https://issues.apache.org/jira/browse/AMQ-2191 https://issues.apache.org/jira/browse/AMQ-3529 - rework fixes to remove uncertanty from dealing with intettuptedexception. Sync requests will trap interrupts that ocurr while waiting for responses and fail the connection with an interruptedioexception. Interrupts pending before requests will be suppressed, allowing possible clean shutdown. It is not safe to replay openwire ops b/c they are not idempotent, the only safe option is to have a teardown of the broker side state from a close
2015-11-27 12:21:56 +00:00
95f58fa7c4
https://issues.apache.org/jira/browse/AMQ-6027
...
Adding back in test case now that AMQ-5898 is resolved
2015-11-25 19:13:24 +00:00
35b7ac250b
https://issues.apache.org/jira/browse/AMQ-5898
...
Removing assertion in VirtualDestinationInterceptor to allow
multiple composite destinations to forward to a physical destination
2015-11-25 13:33:32 +00:00
9acee62877
https://issues.apache.org/jira/browse/AMQ-5963
...
Making unit test more robust
2015-11-24 20:40:10 +00:00
ef129c21cd
NO-JIRA ensure each test has a store with its own directory.
2015-11-24 11:17:25 -05:00
dca6e4506e
AMQ-6058 added a check to make sure the destination starts with the virtual topic prefix.
2015-11-23 20:10:26 +00:00
8be1486508
NO-JIRA: Add a delay to fail in case an async operation has not fully
...
created the DLQ yet.
2015-11-23 14:24:06 -05:00
de5d0d9430
https://issues.apache.org/jira/browse/AMQ-5854
...
Fix intermittent test failure caused by the test reconnecting before
the failure assertion had a chance to assert the expected failure
2015-11-22 18:36:38 +00:00
4a27b72377
https://issues.apache.org/jira/browse/AMQ-6042
...
Apply fix and test from Martin Lichtin to preserve the rollback cause in
all ack modes.
2015-11-20 16:18:27 -05:00
cc6213ebf2
https://issues.apache.org/jira/browse/AMQ-5712
...
Switching addMessageLast to tryAddMessageLast when messages are added
to a Queue pending cursor to allow a potential deadlock to be
avoided. There is more work to be done here but this will at least
prevent a deadlock from occurring.
Fix and test based off of a patch created by Timothy Bish.
2015-11-20 20:58:27 +00:00
64aac4ce73
org.apache.activemq.network.VirtualConsumerDemandTest can take more than 10mins - increasing the fork limit
2015-11-18 16:08:29 +00:00
15412bae64
AMQ4221Test - remove system exit as it breaks surefire fork, https://issues.apache.org/jira/browse/AMQ-6004 interrupt causes errors on shutdown. Two are sorted but the check for errors in the logs may still cause intermittent failures
2015-11-18 16:08:29 +00:00
09054fc4a8
https://issues.apache.org/jira/browse/AMQ-6050
...
Clearing the subscription from the local map in
DemandForwardingBridgeSupport to make sure that demand can be properly
recreated again.
2015-11-18 15:06:33 +00:00
86ead7e9d2
fixing unit test to dynamically use a free port
2015-11-12 15:55:29 +00:00
d328864410
tweaking PeriodicDiskUsageLimitTest
...
Increasing the size of the files written during testing to try
and reduce the change of a test failure
2015-11-11 13:12:02 +00:00
078a101cf7
https://issues.apache.org/jira/browse/AMQ-6000
...
Fix and test, wakeup queue dispatch when resume is called.
2015-11-10 15:39:51 -05:00
3ef6a9f769
https://issues.apache.org/jira/browse/AMQ-6027
...
Fixing unit test to pass assertion
2015-11-10 18:42:03 +00:00
0c846cf8f6
https://issues.apache.org/jira/browse/AMQ-6027
...
Tweaking test case to apply virtual destination updates immediately
2015-11-10 14:45:37 +00:00
cc81680e10
https://issues.apache.org/jira/browse/AMQ-6027
...
Adding support for consumers on virtual destinations to create network
demand. This behavior is turned off by default but can be enabled.
For example, if a consumer comes online for a queue that is part of a
VirtualTopic, this will cause a network of brokers to forward messages
because a demand subscription will be created. Same for if a consumer
comes online for a forwarded destination from a composite
destination.
There is also an option to enable flow based on the existence of a
virtual destination if the virtual destination is forwarding to a
Queue.
Full configuration instructions for this feature will be on the wiki page.
2015-11-09 20:07:43 +00:00
fd0f71a4c8
https://issues.apache.org/jira/browse/AMQ-6033 - fix shadowing error, additional test
2015-11-02 15:08:22 +00:00
014d5594d6
AMQ-6032 Repack message prior to scheduler dispatch to store updated
...
properties in marshaled form.
2015-10-30 14:11:06 -04:00
f09b9203a0
https://issues.apache.org/jira/browse/AMQ-6021 - mqtt+nio+ssl certificate authentication
2015-10-23 15:25:33 +02:00
92d5efc32c
https://issues.apache.org/jira/browse/AMQ-6014 - test needs more time in ci. need to figure why it is sooo slow
2015-10-21 13:06:13 +01:00
a01578ad4c
fix stop/stop or stop no start NPE on sharedfilelocker
2015-10-20 13:02:57 +01:00
1ad0117932
https://issues.apache.org/jira/browse/AMQ-6014 - fix up reference counting for durable subs such that ack on one sub does not decrement usage for offline subs. Fix and test
2015-10-19 16:22:57 +01:00
dc06c8dc75
https://issues.apache.org/jira/browse/AMQ-5994 https://issues.apache.org/jira/browse/AMQ-4000 - proper fix for duplicate sub info from the store on recovery failure from AMQ2149Test. Additional test from Christopher L
2015-10-06 12:01:24 +01:00
81b4b9ae3d
https://issues.apache.org/jira/browse/AMQ-5996
...
When possible check for noLocl changes on durable subscription
reactivation and recreate the durable sub if it changes. For both
selector change and noLocal change also update the AbstractSubscription
selectorExpression so it matches with what was requested.
2015-10-01 19:23:58 -04:00
fc25535748
https://issues.apache.org/jira/browse/AMQ-5854 - fix intermittent test failure
2015-09-30 11:41:08 +01:00
8514e38135
https://issues.apache.org/jira/browse/AMQ-5951 - scenario wheere transaction command can block, additional test and further fix
2015-09-30 11:41:08 +01:00
92e1f60d98
https://issues.apache.org/jira/browse/AMQ-5854 - tidy up test
2015-09-29 13:11:29 +01:00
8d982479e9
https://issues.apache.org/jira/browse/AMQ-5854 - fix and test. Ensure transaction rollback if there are pending acks during a failover reconnect. Reliably tracking pending acks to eusure possible redelivery is too complex in the context of acks getting dropped by failover or ignored by the subscription, in addition to being sent async. Couple that with multiple consumers on the same connection and the locking of message delivery; only safe course is to ensure rollback outcome.
2015-09-28 14:29:57 +01:00
Dejan Bosanac
Christopher L. Shannon (cshannon)
gtully
Timothy Bish
Chad Zobrisky