3985e7225f
https://issues.apache.org/jira/browse/AMQ-5853 - fix cacheEnabled case - additional test and fix for both jdbc and kahadb stores
2015-07-09 10:30:54 +01:00
785b16bf9e
https://issues.apache.org/jira/browse/AMQ-5748
...
Added a getMessageSize method to MessageStore to support retrieving the
total message size of all stored messages for a destination. Added a
new storeMessageSize statistic to DestinationStatistics.
2015-07-07 18:03:27 +00:00
a2697b844e
https://issues.apache.org/jira/browse/AMQ-5853 - track per priority sequence on load from the store. Allow db to select from entire prority 0-9 range. fix and additonal test
2015-07-06 15:32:23 +01:00
eece28ac75
https://issues.apache.org/jira/browse/AMQ-5853 - rework fix, have store reset tracked recovered priority when higer priority messages are stored. Additional perf fix that removes unnecessary 2x multiplier on db fetch size; seems periodic message expiry was throwing some tests when the cache was enabled
2015-07-03 10:30:16 +01:00
12b26b641b
https://issues.apache.org/jira/browse/AMQ-5745
...
This commit is based off a patch submitted by admin@int3solutions.com .
It fixes several locations in the code where there are potential resource leaks.
2015-06-30 13:41:48 -04:00
f2a335c27d
https://issues.apache.org/jira/browse/AMQ-5853 - fix and test, statement was not configurable from xml also so there is no workaround.
2015-06-19 16:08:54 +01:00
38f7857533
bring some more consistency to derby usage and log nested exceptions on create failure
2015-06-17 14:30:25 +01:00
f45ce09655
fix incorrect warn message about lease duration and keep alive
2015-06-12 12:26:06 +01:00
baa10ed33e
more derby shutdown woes resolved
2015-05-20 09:57:05 +01:00
17f4f349f3
more tidy up of derby usage in tests to ensure proper cleanup; ci failures
2015-05-20 09:57:05 +01:00
977deb42c8
check for null in case where deleteAllMessages is called w/o broker ref, prevelant in tests resulting in bogus errors
2015-04-29 11:54:28 +01:00
9ef4259297
https://issues.apache.org/jira/browse/AMQ-5616
...
Use ConcurrentMap in declarations
2015-04-28 11:15:08 -04:00
bcdf770c10
ensure embedded jdbc is shutdown
2015-04-28 12:42:21 +01:00
165959e250
tidy up a bunch of jdbc test cases to ensure embedded derby is shutdown
2015-04-23 13:12:49 +01:00
3155c625c6
https://issues.apache.org/jira/browse/AMQ-5567 - fix and test - issue was eager dispatch with concurrent sends, recovery and outcome delivery now assign a new sequence id to message additions which sorts sequence order in the xa case
2015-02-06 12:56:29 +00:00
ae595c95b1
[maven-release-plugin] prepare for next development iteration
2015-01-30 12:46:19 +00:00
4ba1a1689f
[maven-release-plugin] prepare release activemq-5.11.0
2015-01-30 12:46:08 +00:00
bf5a2997c7
[maven-release-plugin] prepare for next development iteration
2015-01-26 16:48:46 +00:00
eec2955bde
[maven-release-plugin] prepare release activemq-5.11.0
2015-01-26 16:48:37 +00:00
64fa706d54
Revert "[maven-release-plugin] prepare release activemq-5.11.0"
...
This reverts commit f47fbe4b89
2015-01-26 16:39:35 +00:00
f47fbe4b89
[maven-release-plugin] prepare release activemq-5.11.0
2015-01-26 16:17:43 +00:00
aedcae139b
Revert "[maven-release-plugin] prepare release activemq-5.11.0"
...
This reverts commit 48b0cf396c
2015-01-05 12:25:58 -05:00
89995f4723
Revert "[maven-release-plugin] prepare for next development iteration"
...
This reverts commit 7b285c6f52
2015-01-05 12:25:47 -05:00
7b285c6f52
[maven-release-plugin] prepare for next development iteration
2014-12-29 12:44:32 +01:00
48b0cf396c
[maven-release-plugin] prepare release activemq-5.11.0
2014-12-29 12:44:20 +01:00
e16815ad3b
https://issues.apache.org/jira/browse/AMQ-5174 - apply patch from paulGale with thanks replace jdbc specific lease io handler with generic lease io handler - closesThis closes #53
2014-12-22 12:37:43 +00:00
f57fd7daad
fix intermittent failure of LeaseDatabaseLockerTest and fix log messge with lease expiry time
2014-12-16 13:38:05 +00:00
bc3587cfc9
fix failing RecoverExpiredMessagesTest - remove duplicate ref to secedualler task in jdbc pa inheritance and fix persistence adapter ref in test
2014-12-08 14:00:43 +00:00
51566104ab
https://issues.apache.org/jira/browse/AMQ-5447
...
shutdown the scheduled executer so that any scheduled tasks are canceled
and removed on stop.
2014-11-25 14:56:30 -05:00
3042797b41
https://issues.apache.org/jira/browse/AMQ-5266 tidy up leveldb impl with additional scenario tests
2014-10-23 16:29:57 +01:00
ad770ea79d
https://issues.apache.org/jira/browse/AMQ-5384 - apply variant of patch from Tomasz Skorka with thanks
2014-10-07 15:54:21 +01:00
e8f8155141
reflect need for store to set messageId.setFutureOrSequenceLong for journaled jdbc
2014-08-30 23:51:59 +01:00
54e2e3bef2
rework cursor store sync w.r.t to index order. resolve issues with skipped dispatch and duplicate dispatch. https://issues.apache.org/jira/browse/AMQ-4485 https://issues.apache.org/jira/browse/AMQ-5266
2014-08-30 00:51:21 +01:00
8b64e139f8
https://issues.apache.org/jira/browse/AMQ-5318
...
Check for auto-commit and don't call commit if enabled.
This closes #43
2014-08-11 11:15:17 -04:00
3b5d89a78b
https://issues.apache.org/jira/browse/AMQ-5277 - jdbc store make use of entryLocator on ack
2014-07-14 17:02:19 +01:00
6348d11976
https://issues.apache.org/jira/browse/AMQ-5266 - fix ordering of concurrent transaction completion in jdbc store, avoid skipped message dispatch. additional test
2014-07-10 12:33:29 +01:00
74846bb2b4
https://issues.apache.org/jira/browse/AMQ-3758
...
Refactor the scheduler store into a more KahaDB style store that can
recover from various problems like missing journal files or corruption
as well as rebuild its index when needed. Move the scheduler store into
a more configurable style that allows for users to plug in their own
implementations. Store update from legacy versions is automatic.
2014-07-07 12:28:11 -04:00
27b3a7c344
https://issues.apache.org/jira/browse/AMQ-5212 - ensure uncontented access to concurrent destination map avoides deadlock, rerework https://issues.apache.org/jira/browse/AMQ-4952 to differenciate duplicates from send and recovered messages from the store. https://issues.apache.org/jira/browse/AMQ-3454 benefits from getDestinationMap(destination) to get direct access to the map to determine existance. Additional test
2014-06-09 12:32:33 +01:00
fa086396a7
[maven-release-plugin] prepare for next development iteration
2014-06-05 11:59:29 +02:00
58dd93e42e
[maven-release-plugin] prepare release activemq-5.10.0
2014-06-05 11:59:17 +02:00
c2cf78542f
[maven-release-plugin] prepare for next development iteration
2014-06-04 11:33:17 +02:00
5bc741f227
[maven-release-plugin] prepare release activemq-5.10.0
2014-06-04 11:33:03 +02:00
b5c6c1eaeb
https://issues.apache.org/jira/browse/AMQ-5162 - introduce handleStartException configuration parameter, to make stopping of the slave broker optional
2014-05-27 15:20:27 +02:00
3f32507f78
Use autocrlf consistently for line endings
2014-04-29 14:18:37 -04:00
d60022ec65
https://issues.apache.org/jira/browse/AMQ-5162 - handle io exception in lease database locker start
2014-04-25 15:08:05 +02:00
d77014aa5d
AMQ-4399: Allow to configure checkpoint interval on jdbc persistence adapter.
2014-03-30 09:23:14 +02:00
7a0168a4f5
https://issues.apache.org/jira/browse/AMQ-4636 - tidy up commit failure case to redirect via IOExceptionHandler - failover still suppressed the commit on recovery - resulting in rollback exception the client due to indoubt commit
2014-03-26 16:19:46 +00:00
266d23ef79
revisit https://issues.apache.org/jira/browse/AMQ-3519 with more durable solution https://issues.apache.org/jira/browse/AMQ-5068 - JMSRedelivered header now persisted before dispatch so that it is a reliable indication of a possible duplicate delivery. The option is enabled via destination policy persistJMSRedelivered
2014-03-26 11:16:42 +00:00
ff409b6f2c
Applying https://github.com/apache/activemq/pull/18.patch to fix AMQ-5116: batchStatment is misspelled for JDBC adaptors.
...
This closes #18 @github.
2014-03-21 13:52:41 -04:00
cfe099d1cc
rework https://issues.apache.org/jira/browse/AMQ-3305 in the context of https://issues.apache.org/jira/browse/AMQ-4952 dlq processing of duplicates, also possible missed dispatch with interleaved xa completion and new messages - recovered transactions are now individually tracked by the store and replayed in the next batch, which negates the need to flush the cursor and avoids duplicates
2014-03-05 14:51:05 +00:00
gtully
Christopher L. Shannon (cshannon)
Timothy Bish
Hadrian Zbarcea
Dejan Bosanac
Claus Ibsen
Hiram Chirino