f4149c0a46
Implements https://issues.apache.org/jira/browse/AMQ-5458 - Also needed to update the slave since it does writes slightly differently.
2014-11-26 08:36:43 -05:00
ebafd5c193
Implements https://issues.apache.org/jira/browse/AMQ-5458
2014-11-25 11:41:00 -05:00
350889c1eb
https://issues.apache.org/jira/browse/AMQ-5266 - fix regression in levedlb xa recovery and durable sub scan - org.apache.activemq.broker.mLevelDBXARecoveryBrokerTest and org.apache.activemq.bugs.AMQ2149LevelDBTest
2014-10-24 14:28:00 +01: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
1a0bd45a4e
https://issues.apache.org/jira/browse/AMQ-4485 - leveldb version - shows the need to flag async adds so they can get suppressed as duplicates \(and not go to the dlq\) when the cursor order is out of sync on cache full
2014-10-17 13:35:31 +01:00
51a2596c52
run leveldb tests on osx
2014-10-16 23:53:44 +01:00
8a37f97315
AMQ4677Test.testSendAndReceiveAllMessages - demoed the lack of reference increment for transacted send and the non completion of transacted futures in leveldb
2014-08-30 23:36:05 +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
b76d8318d7
Support configuring a connectUrl on the leveldb store in case your running in a system like OpenShift where clients connect to a different ip:port from the one that the sever binds.
2014-08-27 13:08:01 -04:00
66a689df0e
fix up karaf-itests , related commits https://issues.apache.org/jira/browse/AMQ-5224 https://issues.apache.org/jira/browse/AMQ-5105 Update poms to fully load into M2E - 06bb7a2716
2014-07-28 15:30:12 +01:00
3c69127524
https://issues.apache.org/jira/browse/AMQ-4349 - stopping leveldb throws NPE
2014-07-18 15:12:02 +02:00
4da588d4fc
https://issues.apache.org/jira/browse/AMQ-5105 - problem starting broker with leveldb store
2014-07-17 17:12:52 +02:00
06bb7a2716
Update poms to fully load into M2E
2014-07-10 13:47:55 -04:00
13581c9aac
Exclude leveldb tests on AIX, Solaris, HP-UX, and Windows as they cause problems with CI
2014-07-10 11:10:11 +02:00
e62e90abaf
https://issues.apache.org/jira/browse/AMQ-5125
...
Fix for potential deadlock when external classes synchronize on the
LevelDBStore instance which can deadlock the hawtDispatch runner thread
if a task also attempts to take the lock to protect some mutable state
values.
2014-07-07 17:53:46 -04: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
bbd61084e0
Change logging from TRACE to WARN to save space on CI nodes
2014-06-24 11:21:34 +02: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
bdb24ee7c7
Fixes AMQ-5176: Support building ActiveMQ using Java 8 JDK
2014-05-07 10:53:51 -04:00
ad1f751a41
https://issues.apache.org/jira/browse/AMQ-5077 - reduce reader thread work when client uses async send; async store updates can now queue up to the destination memory limit b/c they don't block the send thread. Pending store writes are now tracked in memory usage. This allows a client to quickly provide a burst of messages to fill the destination cache bounded only by network bandwidth
2014-04-30 16:13:18 +01: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
db321727c9
Fixes AMQ-5115: LevelDB sync=true is not being honored.
2014-03-21 12:54:55 -04:00
cb6941ee0b
https://issues.apache.org/jira/browse/AMQ-4886 - think the sync on shutdown issue is resolved and the test will no longer hang
2014-03-20 14:14:31 +00:00
4ca5519e9b
Reduced timeouts from 60 to 10 minutes to avoid long CI hangs
2014-02-20 14:21:02 +01:00
43a88a9367
Get mvn eclipse:eclipse work for the leveldb stuff
2014-02-05 11:41:22 -05:00
d36e3c0e95
AMQ-5005. Fix for scala plugin
2014-01-30 15:43:45 -05:00
c027552035
Upgraded surefire plugin to 2.16. AMQ-5006
2014-01-30 14:22:44 +01:00
0f0c0d676a
fix leveldb version of org.apache.activemq.bugs.AMQ2870Test#testSize
2014-01-07 16:54:18 +00:00
30f3a9b7f3
Default flushDelay on the replicated leveldb store did not have the correct default.
2013-12-05 13:38:52 -05:00
ed8e4eae8f
Fixes https://issues.apache.org/jira/browse/AMQ-4923 : Replicated LevelDB: Loss of broker Quorum fails to fully stop the master
2013-12-05 13:38:52 -05:00
3b5fa4bf89
Implementing a dirty stop method for the leveldb store that might come in handy for testing.
2013-12-05 09:24:10 -05:00
8378cb1ffc
Fixing https://issues.apache.org/jira/browse/AMQ-4917 : LevelDB store can fail when using durable subs.
...
We were browsing durable sub entries which had been concurrently GCed causing leveldb store failures which then caused the broker to restart.
2013-12-04 12:09:47 -05:00
5fa462a08a
Adding assertions to make sure that we only append to the log from the write thread. Found a code path that was appending to the log from a different thread. This might have been affecting https://issues.apache.org/jira/browse/AMQ-4882
2013-12-03 12:05:16 -05:00
61e13fa6ce
Fixing regression caused by changes to SuppressRelyException in commit b0e91d47f5.
2013-12-02 12:29:21 -05:00
b0e91d47f5
Have the leveldb store thorw SuppressReplyExceptions instead of IOExceptions so that the clients retry try the operations instead of giving up. Also retry the problemantic getMessage() call which seems to fail at times.
2013-11-25 13:17:58 -05:00
00cb9a5668
AMQ-4858: Moved scala source file from java to scala dir. Thanks to Jaromir Hamala for patch.
2013-11-22 11:25:08 +01:00
c0090f6f0c
AMQ-4885: Renamed some API methods in MessageStore due typos.
2013-11-22 11:21:42 +01:00
38ab4b10a4
https://issues.apache.org/jira/browse/AMQ-4855
...
Deprecate the misspelled subcription named getters and use the correctly
spelled versions where the older ones are in use.
2013-11-11 11:40:07 -05:00
42e1c463d4
Replicated leveldb slaves index snapshots were being labeled with higher journal positions than what they really contained.
2013-11-08 10:34:21 -05:00
4367ec1b82
If a replicated leveldb slave's connection gets slow, lets merge together journal write events to avoid them queuing up on the master side.
2013-11-05 11:53:37 -05:00
a907fc9e94
leveldb store: Add more log traces for when we need to get more details on what's going on.
2013-11-04 09:26:01 -05:00
b1d8cbe4cd
Fixes for leveldb replication: make sure we only apply index updates when we encounter a UOW_END_RECORD so that we don't end up with an inconsistent index if a partial UOW is replicated.
2013-11-04 09:26:01 -05:00
dea38e62f8
leveldb replication: Lets always download the current append log just to be safe
2013-11-04 09:26:01 -05:00
2824a94af4
Continue to append to the last leveldb log file on a store restart.
2013-11-04 09:26:01 -05:00
190da29691
Fix for: https://issues.apache.org/jira/browse/AMQ-4837 : LevelDB corrupted in AMQ cluster.
...
- The tracked flushed offset was not getting initialized to match the initial size of the log file. This invalid flushed offset was being used to do the initial sync /w the slave and then things went downhill.
2013-11-01 12:13:33 -04:00
24d5490e57
Fix for: https://issues.apache.org/jira/browse/AMQ-4837 : LevelDB corrupted in AMQ cluster.
...
- Log rotation was causing a pre-mature index snapshot to be taken on the slave (snapshot while the slave was still synchronizing).
- Also fix issue with the append position displayed in JMX for the master not being correct.
2013-10-31 12:52:50 -04:00
3ed52ef8a2
Working on a test case for https://issues.apache.org/jira/browse/AMQ-4837 : LevelDB corrupted in AMQ cluster.
2013-10-30 15:44:06 -04:00
Hiram Chirino
gtully
Dejan Bosanac
Daniel Kulp
Kevin Earls
Timothy Bish
Hadrian Zbarcea
Claus Ibsen
Timothy Bish