Commit Graph

8411 Commits

Author SHA1 Message Date
gtully 4648dbee41 resolve intermittent faiure - make deterministic intervetion and assertions 2015-01-22 14:13:32 +00:00
Dejan Bosanac b53d8ea295 https://issues.apache.org/jira/browse/AMQ-5534 - generic jms pool reconnection 2015-01-22 12:51:11 +01:00
gtully 189a75afdc fix AMQ4221Test failure on low disk space - use warn level when resetting to available. Test checked log for error messages 2015-01-22 11:41:06 +00:00
gtully bedb207883 reduce test duration, mem limits still reached as before and temp store utilised 2015-01-21 22:35:49 +00:00
gtully 7ce5be44d8 wait for bundle installation to complete - makes obr test more robust 2015-01-21 22:17:35 +00:00
Timothy Bish c93b6614b4 Adds a test case to validate that JMSXGroupID and Seq are retained over
time while messages are produced and consumed.  Older ActiveMQ releases
seemed to have an issue in this area due to the Proton-J library used.
Test should help to ensure this does not reappear.
2015-01-21 11:19:11 -05:00
gtully 25f18ad20d https://issues.apache.org/jira/browse/AMQ-5526 - tidy up karaf-itest, features amqp now work,still issue with camel and bundlecontext null 2015-01-21 15:10:09 +00:00
gtully 548aa1e415 https://issues.apache.org/jira/browse/AMQ-5525 - worked around the issue with blueprint converter - all. All of the activemq commands have the same single arg signature, so the conversion should be trivial, doing the conversion inline in the default case 2015-01-20 11:47:01 +00:00
Dejan Bosanac efe68aa032 upgrade derby 2015-01-16 13:01:38 +01:00
Claus Ibsen 5c7985c695 AMQ-5523: Average message size attribute on statistics plugin should not have decimals 2015-01-16 09:29:52 +01:00
Claus Ibsen dbf2c28b96 AMQ-5521: Average message size attribute on destination mbean should not have decimals 2015-01-16 09:22:28 +01:00
Daniel Kulp 3ec36818eb Get more tests passing with Jetty9 2015-01-15 12:16:17 -05:00
Daniel Kulp f4eade2bb3 [AMQ-5520] Use a network interface that actually supports multicast and is up 2015-01-14 13:43:10 -05:00
Daniel Kulp 0d815642c1 Add a jetty9 profile to help with testing 2015-01-14 13:21:01 -05:00
Robert Gemmell 6466ae2bcf AMQ-5519: use the NOT_FOUND error condition when failing to find a DurableSubscription
https://issues.apache.org/jira/browse/AMQ-5519
2015-01-14 16:47:41 +00:00
gtully 5b7213eb82 add jira ref - commit message had incorrect url 2015-01-14 12:25:40 +00:00
Daniel Kulp ffa396ca2d Fix several eclipse warnings of unused things, and other compiler warnings 2015-01-13 15:03:10 -05:00
Daniel Kulp 2128d4d246 Fix some itests due to the servlet import range being inadequate for the version of karaf we are testing with 2015-01-13 13:29:52 -05:00
Daniel Kulp d4aff4da64 Update to import stuff needed to run in karaf 2.4+ 2015-01-13 12:54:08 -05:00
Daniel Kulp 3f82625077 [AMQ-5517] Runtime support for Jetty 9. Build/compile with Jetty8, but tests pass with Jetty 9 for runtime level support. 2015-01-13 12:47:53 -05:00
Daniel Kulp bc2e2d9a41 [AMQ-5517] Start stubbing in some of the extra params and such that will be needed to support jetty 9 2015-01-13 09:24:50 -05:00
Daniel Kulp 2c68116158 Update to import into m2e without a plugin error 2015-01-13 09:00:50 -05:00
gtully 60f9b020cc https://issues.apache.org/jira/browse/AMQ-5515 - update to 8.1.15.v20140411 2015-01-13 12:06:54 +00:00
Arthur Naseef 2a9f8a3632 Added the key for Arthur Naseef. 2015-01-12 17:54:21 -07:00
gtully cf62d58ae7 https://issues.apache.org/jira/browse/AMQ-5515 - tidy up jetty deps - fix jetty maven coords 2015-01-12 22:58:07 +00:00
gtully 869c193d1f fix mvn warn on missing plugin ver 2015-01-12 15:04:13 +00:00
gtully 849987e5dd https://issues.apache.org/jira/browse/AMQ-5513 - remove inadvertent change of statement log level 2015-01-12 13:12:25 +00:00
gtully 8dbb48a23f https://issues.apache.org/jira/browse/AMQ-4107 - apply patch - resolved intermittent failure of TwoMulticastDiscoveryBrokerTopicSendReceiveTest 2015-01-12 12:00:42 +00:00
artnaseef 3e007d89a2 [AMQ-5514] Add the 5.10.1 release to the spring.schemas file. 2015-01-09 12:34:57 -07:00
gtully dbb1d8b83d https://issues.apache.org/jira/browse/AMQ-5513 - have lastDeliveredSequence -1 indicate nothing was received, respect this value in queue sub remove and durable sub deactivate. 0 still constitutes no info - so old clients see same behaviour as before 2015-01-09 13:30:59 +00:00
gtully 05f6cd6cfc ignore intermittent failures for 5.11 - leveldb can be a focus for 5.12 - https://issues.apache.org/jira/browse/AMQ-5512 2015-01-09 13:30:59 +00:00
gtully 383c27e245 add some more diagnostic logging to test 2015-01-09 13:30:59 +00:00
Dejan Bosanac 7948d69056 https://issues.apache.org/jira/browse/AMQ-5511 - retained message for zero-byte clientId client 2015-01-09 12:58:53 +01:00
gtully f303f85ce3 remove inadvertent test mods 2015-01-08 15:58:28 +00:00
Claus Ibsen 81d83718ae Upgrade slf4j 2015-01-08 16:30:59 +01:00
gtully 6588aea8e1 avoid npe causing hang on shutdown, sync shutdown of log 2015-01-08 15:21:31 +00:00
gtully 726bc97bae more logging for leveldb tests 2015-01-08 15:06:40 +00:00
gtully b54606b124 https://issues.apache.org/jira/browse/AMQ-5300 - fix and test that verifies recovery in the absense of an index 2015-01-07 17:11:09 +00:00
gtully f1df9f8b82 ignore errors on dir cleanup 2015-01-07 17:11:09 +00:00
Hadrian Zbarcea c5cebd5ec6 More test cleanup: use available port instead of hardcoded 2015-01-06 16:22:56 -05:00
gtully a52bfe62a4 track first missing message - to see if there is some consistency to the ubuntu ci failures 2015-01-06 15:57:50 +00:00
gtully 5616d39d82 see if a stronger sync will sort the ubuntu ci test failures of leveldb - i cannot reproduce 2015-01-06 15:40:45 +00:00
Timothy Bish 7ebc6ceef8 https://issues.apache.org/jira/browse/AMQ-5481
Add some additional logs to MQTT at the trace level.
2015-01-06 10:32:56 -05:00
Hadrian Zbarcea 4bf5d0fc13 Test cleanup: use available port instead of hardcoded 2015-01-06 01:23:13 -05:00
Timothy Bish 4b7131ff85 https://issues.apache.org/jira/browse/AMQ-5468
Add a connect check in the inactivity monitor to account for opened
connections that might drop but not be spotted, in the case where the
connect frame is lost this can lead to connections that aren't fully
opened and won't be cleaned up until the broker detects the socket has
failed.  

By default the connection timer is set to 30 seconds, if no connect
frame is read by then the connection is dropped.  The broker can be
configured via the 'transport.connectAttemptTimeout' URI option, a value
<= zero disable the check.
2015-01-05 18:53:34 -05:00
gtully 6c2e2f5446 using a more sensible session timeout sorts org.apache.activemq.leveldb.test.ElectingLevelDBStoreTest#testElection also 2015-01-05 21:05:34 +00:00
gtully 4d8489ba38 https://issues.apache.org/jira/browse/AMQ-5506 - fix typo in leveldb attribute ZkSessionTmeout - now with the i, store.setZkSessionTimeout 2015-01-05 21:00:45 +00:00
gtully 5ebe71cec9 improve reliability of leveldb replication test org.apache.activemq.leveldb.test.ReplicatedLevelDBBrokerTest - ZOOKEEPER-1751 fixed in 3.4.6 is releated, also the default 2s session expiry with a 500ms tick seems to be problematic with porpotional ping intervals. With 3.4.6 random client session expiry due to ping timeouts are avoided but unexpected server side expiry still ocurrs due to missing pings. Upping the session expiry to 15s avoids the client - server mismatch in session connection cleanup 2015-01-05 21:00:45 +00:00
Hadrian Zbarcea 9ee7bbb0af This closes #49. For some reason didn't register with commit 46bc26cea5 2015-01-05 15:46:14 -05:00
Hadrian Zbarcea 8e0865d5d1 [AMQ-5505]. Add getUptimeMillis to the BrokerView MBean. This closes #56 2015-01-05 13:23:19 -05:00