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
9c4ef26d5c
with failover the reported exception may be wrapped by the failover listener
2015-12-09 12:30:29 +00:00
7a7c70ad75
https://issues.apache.org/jira/browse/AMQ-6082
...
Propertly re-setting the storeOpenWireVersion from the BrokerService
on the KahaDB Metadata if a corrupted index is detected and the
Metadata has to be recreated.
2015-12-08 20:10:11 +00:00
5772e7bed8
https://issues.apache.org/jira/browse/AMQ-6080
...
fixing typos
2015-12-08 13:18:11 +00:00
88ec9dad9d
https://issues.apache.org/jira/browse/AMQ-5454 https://issues.apache.org/jira/browse/AMQ-6070 - in the case of duplicates from the store the regiondestination was not set
2015-12-08 11:25:50 +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
913f64476b
https://issues.apache.org/jira/browse/AMQ-6073
...
WSServlet for websockets will attempt to detect the subprotocol
requested and respond with the appropriate one. Currently the protocols
loaded are what stomp.js use for stomp (v11.stomp and v12.stomp).
If a protocol can't be found then a default will be returned, either
"stomp" or "mqtt", which is the same behavior before this patch.
This will make it a bit easier to use stomp over websockets out of the
box as stomp.js will work by default.
2015-12-07 15:29:13 +00:00
66c348b1b8
https://issues.apache.org/jira/browse/AMQ-6071 - Log info about corrupted journal records at WARN level
2015-12-04 11:29:55 +00: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
d346a765e3
https://issues.apache.org/jira/browse/AMQ-6062
...
Updated QueueBrowserSubscription to use a ConcurrentMap to avoid a
potential race condition when multiple queue browsers browse
multiple queues.
2015-12-02 15:51:55 +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
5a27bdf07e
https://issues.apache.org/jira/browse/AMQ-6068 - fix and test. Cleanup from ra managed connection needs to remove the connection info, leaving the tcp connection free for another identity. Possibly this could be conditional on having a user supplied clientId
2015-12-01 14:28:07 +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
1bef4de4dc
Revert " https://issues.apache.org/jira/browse/AMQ-6065 "
...
CPL dependency is not fully compatable with ASF and is not really necessary
This reverts commit 39a20bd788
2015-11-30 13:24:18 +00:00
1499f2eee0
Adding 5.13.0 to schemas file
2015-11-30 12:34:17 +00:00
39a20bd788
https://issues.apache.org/jira/browse/AMQ-6065
...
Fixed test case so that a System.exit call will not take down the
JVM and cause the test suite to abort in Jenkins early
2015-11-29 10:05:27 -05:00
673c2928a1
https://issues.apache.org/jira/browse/AMQ-6066
...
Improving performance of OrderedPendingList contains method
Thanks for David Sitsky for the patch
2015-11-28 13:25:53 -05:00
2aa172f905
https://issues.apache.org/jira/browse/AMQ-6065 - allow ioexception handler to flip the systemExitOnShutdown broker attribute before calling stop, i.e: exit on store io errors
2015-11-27 14:21:20 +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
29d943429c
https://issues.apache.org/jira/browse/AMQ-5393
...
Reverting commit because allowing 0 doesn't actually set the usage to
0 size. It ends up disabling the check all together which was the
opposite intention of the commit.
This reverts commit 3b658f8e1a
2015-11-25 17:59:41 +00:00
8f30866fdf
https://issues.apache.org/jira/browse/AMQ-6063
...
Fixing potential NullPointerException during KahaDB index recovery.
2015-11-25 16:02:52 +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
3b658f8e1a
https://issues.apache.org/jira/browse/AMQ-5393
...
Allowing disk limit percentages to be 0
2015-11-25 13:18:59 +00:00
9acee62877
https://issues.apache.org/jira/browse/AMQ-5963
...
Making unit test more robust
2015-11-24 20:40:10 +00:00
e07809dec6
NO JIRA - Clear journalSize counter
...
The journalSize counter should be set to 0 after KahaDB is shut down.
Usually, a store is not restarted again after stopping, but if it ever
was the value would be wrong since it wasn't reset back to 0.
2015-11-24 17:53:34 +00:00
ef129c21cd
NO-JIRA ensure each test has a store with its own directory.
2015-11-24 11:17:25 -05:00
9bc28214d5
https://issues.apache.org/jira/browse/AMQ-6060 - retain will message
2015-11-24 14:13:32 +01:00
d9e22a9368
https://issues.apache.org/jira/browse/AMQ-6044
...
Clean up some test client code.
2015-11-23 16:55:11 -05:00
bc9edf00d1
https://issues.apache.org/jira/browse/AMQ-6058
...
Updating patch to make sure SelectorAwareVirtualTopics are covered
and code cleanup
2015-11-23 20:35:32 +00:00
bf36c4cb88
This closes #159
2015-11-23 20:31:53 +00: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
4c1a6b4c2b
Add Martyn's key so we can keep the KEYS files in sync
2015-11-23 12:28:37 -05:00
4318eba4a3
https://issues.apache.org/jira/browse/AMQ-6014 - topic store prefetch should take ownership like in the non persistent case - DurableSubscriberNonPersistentMessageTest regression
2015-11-23 12:27:03 +00:00
48fbd3116d
test for transacted send and ack camel route with explicit set of connection factory necessary due to config clone across component endpoints
2015-11-23 12:27:03 +00:00
3a3dcac184
https://issues.apache.org/jira/browse/AMQ-5957
...
Updating several dependencies to the latest
2015-11-22 19:56:27 +00:00
bbde8473bd
https://issues.apache.org/jira/browse/AMQ-5980
...
Fixing an intermittent test failure in:
org.apache.activemq.transport.ws.StompWSSTransportTest.
testHeartbeatsKeepsConnectionOpen
Adding synchronization on sends for StompWSConnection. The protocol
doesn't allow multiple threads to call a blocking send at the same time
and the heartbeat keep alive thread was colliding with the main
thread on sends.
2015-11-22 19:01:31 +00: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
272fb2b973
https://issues.apache.org/jira/browse/AMQ-6044
...
Add support for transactions to the test client.
2015-11-20 17:48:14 -05: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
b5dd0a16f4
https://issues.apache.org/jira/browse/AMQ-6055
...
Account for Authzid in SASL PLAIN mechanism and provide a means to fail
the authorization if the challenge response is invalid. Update the
client to properly exclude sasl mechanism that don't apply to it's
configured credentials such as using only ANONYMOUS when no user or
password is set.
2015-11-20 14:39:03 -05:00
gtully
Christopher L. Shannon (cshannon)
Timothy Bish
Torsten Mielke
Dejan Bosanac
Chad Zobrisky
Daniel Kulp