4bf3152fa9
https://issues.apache.org/jira/browse/AMQ-6630
...
Update to QpidJMS 0.22.0 and Netty 4.1.9.Final
2017-04-21 11:44:06 -04:00
381a1ae206
https://issues.apache.org/jira/browse/AMQ-6659
...
Honor the sender settle mode from the client and ensure we always set
receiver mode to FIRST to reflect we don't support SECOND. Adds tests
coverage and needed test client changes for this.
2017-04-21 10:51:35 -04:00
1fd2450544
NO-JIRA Make the version string indicate that the value is unknown
...
The default version string is out of date and doesn't indicate that a
proper value couldn't be found, return something that makes that a bit
more clear.
2017-04-11 13:13:30 -04:00
af03ad4679
[AMQ-6652] add final modifier to test
2017-04-11 11:39:22 +01:00
ca5e41bb7a
[AMQ-6652] ensure checkpoint pagefile flush includeds the checkpoint transaction
2017-04-10 17:15:07 +01:00
172c29091e
AMQ-6651: Add new implementations of the writeUTF8 and readUTF8 methods that are based on Apache Harmony code. This also avoid some code duplication that was occurring.
2017-04-10 10:49:17 -04:00
58046194d0
https://issues.apache.org/jira/browse/AMQ-6649
...
Adding MS SQL jdbc driver 6.1 support
2017-04-10 08:52:05 -04:00
d42b51a78e
[AMQ-6630][AMQ-6493] fix feature and add explicit 2.0 jms dep to karaf for the amqp client test
2017-04-07 11:01:51 +01:00
63b2e5c4ea
[AMQ-6494] fix check order of close state for onException handler
2017-04-06 10:23:16 +01:00
0752d840b9
https://issues.apache.org/jira/browse/AMQ-6638
...
Adds some additional logging to the connection validation code, adds
some additional tests as well.
2017-04-05 16:20:28 -04:00
548403ad99
Removing two tests as they do not actually test anything
2017-04-05 15:27:04 +02:00
b64ac1dd77
[AMQ-6646] improve error reporting to include url
2017-04-04 17:30:29 +01:00
09acc504f1
[AMQ-5558] don't log password
2017-04-04 16:36:34 +01:00
4a3d117d96
[AMQ-6645] add originalDestination to the mapped properties
2017-04-04 15:03:54 +01:00
729766e492
[AMQ-6494] ensure vm transport propagates onCommand exceptions to peer
2017-04-04 14:17:27 +01:00
0f7561e85a
Revert "AMQ-6494 Return ExceptionResponse during broker service shutdown"
...
the root cause seems to be in the vm transport iterator
This reverts commit dce2b61f87
2017-04-04 14:15:00 +01:00
c1cbf509da
[AMQ-6644] - ensure journal files past last update are not included in the logged gc set in error
2017-04-04 12:21:31 +01:00
8b064889c6
[AMQ-6643] final modifier for test in the right place
2017-04-04 10:57:57 +01:00
2a2cb3997f
[AMQ-6643] final modifier for test
2017-04-04 10:52:38 +01:00
679db08db3
[AMQ-6643] ensure a wildcard virtual topic subscriber is restricted to the wildcard destination - avoid duplicate and spurious dispatch. fix and test
2017-04-04 10:16:48 +01:00
2731f04f1c
AMQ-6642: Fix potential NPE on updateMessage
...
Fixing potential NPE when calling updateMessage on a Queue store in
KahaDB if subscription statistics are enabled. Also reduced the
visibily from public to protected to subscription statistic related
methods that shouldn't be public and added null pointer checks there as
well.
https://issues.apache.org/jira/browse/AMQ-6642
2017-03-31 09:06:01 -04:00
4ef1fc74cf
[AMQ-6640] either broker dispatch to bridge or bridge dispatch to broker needs to be async - dispatchAsync network option is the trigger for the vm transport to be sync in line with the current defaults. original BacklogNetworkCrossTalkTest scenario exposed this. upshot is dispatchAsync=false is not compatible with duplicate subscription suppression which is fair.
2017-03-30 12:12:13 +01:00
5ac9657c12
[AMQ-6640] shrink test duration for ci boxes
2017-03-30 10:16:18 +01:00
d84a58656c
[AMQ-6640] allign use of sync vm transport usage on duplex end of networkconnector with initiator end. only duplexinbound for forwarding is async to allow thread for responses. vm transport options applied in one place and test more deterministic w.r.t the hang scenario
2017-03-29 23:50:47 +01:00
770a73e9ba
[no jira] add identity option to consumer bean to aid logging/debugging
2017-03-29 22:19:15 +01:00
8e00c6c2bc
[AMQ-6640] fix duplicate suppression sync request on responder end of duplex network connector only b/c that has the async local transport. Additional test. Ensure broker sync is conditional on the need for duplicate suppression which should only be necessary in ring topologies when properly configured
2017-03-28 14:49:23 +01:00
0196be1d27
https://issues.apache.org/jira/browse/AMQ-6630
...
Update to latest Qpid JMS release 0.21.0 and match the netty 4.1.8.Final
dependency up with it.
2017-03-15 12:41:25 -04:00
44a318bd3f
https://issues.apache.org/jira/browse/AMQ-6629
...
Allow for broker stats to be viewed in tests by enabling JMX but
disabling the creation of a management connector.
2017-03-15 09:59:57 -04:00
36689beff7
[AMQ-6561] fix up unit test that expects socket to remain open after InvalidClientIDException, dubious expectation in the test that wants to verify broker is ok
2017-03-14 11:59:13 +00:00
c5a8b2c8b1
[AMQ-6625] ensure kahadb stops operation on the first IOException to facilitate auto recovery from partial writes
2017-03-13 13:49:41 +00:00
0707031334
AMQ-6623: update to proton-j 0.18.0
2017-03-10 15:31:17 +00:00
f651aa361f
[AMQ-6620] Workaround until the actual issue is fixed in karaf
2017-03-10 16:19:05 +01:00
ef064953b4
https://issues.apache.org/jira/browse/AMQ-6621
...
Fix year values and remove an outdated attribution.
2017-03-08 14:12:04 -05:00
21ae1ef2e6
[AMQ-6606] - reset next batch so it does not get reused after error and refine fix to sync write batches b/c async locations will already be in the index
2017-03-07 12:28:58 +00:00
0d824a8e68
AMQ-6377: Storing JournalSyncStrategy as an enum
...
Switching MessageDatabase to store JournalSyncStrategy as its enum value
instead of String to avoid the performance penalty of comparing Strings
everytime isEnableJournalDiskSyncs() is called which currently happens
on every write.
2017-03-06 07:54:39 -05:00
01b1f7f694
[AMQ-3233] respect policy entry blockedProducerWarningInterval for flow control warning, 0 disables and Xmillis makes it periodic, default period of 30s is not unlike the existing once behaviour. fix and tests
2017-03-03 11:23:23 +00:00
2809befff5
[AMQ-6610] - fix up brittle jmock test
2017-03-03 10:14:30 +00:00
e67d48680f
[AMQ-6614] fix up jmx blockedSendsCount and producer view blocking flag for async send case. fix and test
2017-03-02 17:00:16 +00:00
eab9a0d057
[AMQ-6603] pull unnecessary guava dep from the new test
2017-03-01 15:25:57 +00:00
90b808ab98
AMQ-6603 Stop tracking producer if creation failed
...
Track the message producer create and ensure it is not recreated on
failover if the creation resulted in an error response. Add failover
level tests to cover consumer and producer failed create tracking.
2017-02-28 16:17:32 -05:00
8641928553
[AMQ-6603] ensure failover does not track consumer creation that fails with an exception, fix and test. Thanks for the test Tadayoshi Sato
2017-02-28 17:17:18 +00:00
b6521e292b
[AMQ-6414] additional logging that helped identify root cause
2017-02-27 17:01:16 +00:00
a1f6261fb2
[AMQ-6414] additional test that reproduces and validates
2017-02-27 16:35:54 +00:00
67ad35d342
NO-JIRA: Adding 5.14.4 schemas
2017-02-27 07:56:14 -05:00
ef84db5e64
AMQ-6610: Fixing JDBC test
...
Durable destinations need to always be loaded on connector start
2017-02-27 07:34:22 -05:00
bab0887ed6
AMQ-6610 - Network connector mbean not registered on reload
...
On network connector add or update after broker start (such as the
runtime plugins) the mbean was not created. There was also a couple of
other properties not set. Fixed the network connector start to be the
same for normal broker start and runtime reload.
2017-02-24 14:05:27 -05:00
0cf64783d2
AMQ-6602 - fix java 7 incompatibility
2017-02-24 06:36:57 -05:00
1f53b124bc
AMQ-6602 - Removing lambdas for java 7 compatibility
2017-02-23 10:56:57 -05:00
79069598b1
AMQ-6606 - fix typo
2017-02-23 10:21:54 -05:00
fe5164a404
AMQ-6602: Fix race condition in TaskRunnerFactory
...
Fixing a race condition in TaskRunnerFactory where if multiple threads
call createTaskRunner() at the same time some threads might see the
executor as null (if it hasn't finished initializing) leading to the
creation of extra DedicatedTaskRunner objects instead of sharing a
PooledTaskRunner.
2017-02-23 10:20:13 -05:00
Timothy Bish
gtully
Hiram Chirino
Christopher L. Shannon (cshannon)
Christian Schneider
Robert Gemmell