gtully
053c38f99f
[AMQ-6670] - disable expiry processing that may page in and change the test
2017-05-08 11:53:55 +01:00
gtully
2518bded67
[AMQ-6670] - trap classcast and marshall errors on load message from journal such that errors are consistently propagated to the ioExceptionHandler
2017-05-05 15:43:09 +01:00
gtully
ae97fbd52e
fix cn to match jdk8 cert
2017-05-05 11:01:33 +01:00
gtully
b30ae4e846
[AMQ-6665] - remove extranious import from test
2017-05-05 10:48:13 +01:00
Timothy Bish
2e2d5ddd3d
https://issues.apache.org/jira/browse/AMQ-6669
...
Respect the wireFormat.maxFrameSize option on WS and WSS transports
allowing binary content larger than 65535
2017-05-04 16:37:53 -04:00
gtully
07b0d913af
conform to jdk8 algorithm constraints with keystores
2017-05-04 13:14:31 +01:00
gtully
dcd9b9e186
use jdk8 allowed cypher in the restricted set
2017-05-04 12:58:25 +01:00
gtully
2bd3379932
[AMQ-6068] make full cleanup of the rar managed connection conditional on a user specified client id being present
2017-05-04 11:08:32 +01:00
gtully
2b3f0e5958
add some logging to diagnose ci failure
2017-05-04 10:23:13 +01:00
gtully
18d05ba5e0
modify test to validate setting isDLQ flag via startup destination query options
2017-05-03 16:17:29 +01:00
gtully
35f30102a6
[AMQ-2100] fix for intermittent ci failure
2017-05-03 12:31:09 +01:00
gtully
c4a1346875
[AMQ-6465] fix up test interplay - clean on start and consume what is produced
2017-05-03 12:22:24 +01:00
gtully
a0ba0bf4c6
[AMQ-6667] gate cursor cache enablement on a single pending send and tidy up setbatch to always check outstanding async future list. Fix and test
2017-05-03 11:36:06 +01:00
gtully
57795bafce
[AMQ-6665] - check for peercerts is now on tcp transport such that the bridge connection info can have the correct context
2017-04-27 12:07:12 +01:00
gtully
0e74c52e8a
[NO JIRA] tidy up MbeanInfo text in DestinationView
2017-04-26 12:10:24 +01:00
Christopher L. Shannon (cshannon)
808a4c5c17
AMQ-6661 - Fix Auto MQTT protocol detection
...
Protocol detection now takes into account the variable length header in
the CONNECT packet.
2017-04-25 08:47:08 -04:00
Timothy Bish
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
Timothy Bish
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
Timothy Bish
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
gtully
af03ad4679
[AMQ-6652] add final modifier to test
2017-04-11 11:39:22 +01:00
gtully
ca5e41bb7a
[AMQ-6652] ensure checkpoint pagefile flush includeds the checkpoint transaction
2017-04-10 17:15:07 +01:00
Hiram Chirino
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
Christopher L. Shannon (cshannon)
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
gtully
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
gtully
63b2e5c4ea
[AMQ-6494] fix check order of close state for onException handler
2017-04-06 10:23:16 +01:00
Timothy Bish
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
Christian Schneider
548403ad99
Removing two tests as they do not actually test anything
2017-04-05 15:27:04 +02:00
gtully
b64ac1dd77
[AMQ-6646] improve error reporting to include url
2017-04-04 17:30:29 +01:00
gtully
09acc504f1
[AMQ-5558] don't log password
2017-04-04 16:36:34 +01:00
gtully
4a3d117d96
[AMQ-6645] add originalDestination to the mapped properties
2017-04-04 15:03:54 +01:00
gtully
729766e492
[AMQ-6494] ensure vm transport propagates onCommand exceptions to peer
2017-04-04 14:17:27 +01:00
gtully
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
gtully
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
gtully
8b064889c6
[AMQ-6643] final modifier for test in the right place
2017-04-04 10:57:57 +01:00
gtully
2a2cb3997f
[AMQ-6643] final modifier for test
2017-04-04 10:52:38 +01:00
gtully
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
Christopher L. Shannon (cshannon)
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
gtully
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
gtully
5ac9657c12
[AMQ-6640] shrink test duration for ci boxes
2017-03-30 10:16:18 +01:00
gtully
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
gtully
770a73e9ba
[no jira] add identity option to consumer bean to aid logging/debugging
2017-03-29 22:19:15 +01:00
gtully
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
Timothy Bish
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
Timothy Bish
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
gtully
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
gtully
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
Robert Gemmell
0707031334
AMQ-6623: update to proton-j 0.18.0
2017-03-10 15:31:17 +00:00
Christian Schneider
f651aa361f
[AMQ-6620] Workaround until the actual issue is fixed in karaf
2017-03-10 16:19:05 +01:00
Timothy Bish
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
gtully
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