04b60cb188
AMQ-6664 - Adding missing header tag to JSP files
...
Also fixing JSP comments. This fix is a follow on to
AMQ-6620
2017-05-24 16:22:23 -04:00
7cae60eae0
[AMQ-6684] exclude json cat-x transitive dep
2017-05-24 16:19:09 +01:00
e69367fbc3
https://issues.apache.org/jira/browse/AMQ-6680
...
Fix handling of incoming MQTT binary data over WS. The handler should
use the MQTTCodec to ensure that partial or packed frames are fully
processed
2017-05-22 12:27:16 -04:00
acab282d9c
[AMQ-6678] sync destructive queue view mbean (jmx) operations such that concurrent calls see consistent state
2017-05-18 12:37:54 +01:00
02353226c9
https://issues.apache.org/jira/browse/AMQ-6630
...
Update Qpid JMS to v0.23.0
2017-05-16 15:35:23 -04:00
0eb11bf0a1
https://issues.apache.org/jira/browse/AMQ-6676
...
Handle continuation frames on the test client WS transport.
2017-05-16 10:53:23 -04:00
88efa01e11
AMQ-6675 AMQP Test client can't accept bigger frames on WS
...
Need to configure the WS Handshaker in the test client's netty transport
with the same value given to the proton connection via setMaxFrameSize
so that incoming frames larger than the default 65535 over WS don't
trigger netty to fail the connection.
2017-05-11 18:33:38 -04:00
4f7c9ec811
AMQ-6674 Ensure timely shutdown of the connection executor
...
Don't wait for next idle check or other scheduled tasks to run before
shutdown can proceed.
2017-05-11 15:59:08 -04:00
154ff81eee
AMQ-6673 Add some fixes and improvements to the AMQP test client
...
Adds some thread safety fixes and Netty usage fixes to the transport as
well as adding a traceBytes option to trace the bytes sent / received
during testing.
2017-05-11 15:01:16 -04:00
fddbac2b8a
AMQ-6672 Use a dynamic proxy to create unmodifiable types
...
Use a dynamic proxy instead of hand-crafted wrappers around proton
types to prevent access to mutating methods in tests that could
inadvertantly change the state outside the connection thread.
2017-05-11 13:14:39 -04:00
eb1a3eb77b
[AMQ-6670] - harden the test to avoid ci failure
2017-05-10 11:30:30 +01:00
73e70299e6
AMQ-6623: update to proton-j 0.19.0
2017-05-08 12:42:51 +01:00
053c38f99f
[AMQ-6670] - disable expiry processing that may page in and change the test
2017-05-08 11:53:55 +01:00
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
ae97fbd52e
fix cn to match jdk8 cert
2017-05-05 11:01:33 +01:00
b30ae4e846
[AMQ-6665] - remove extranious import from test
2017-05-05 10:48:13 +01:00
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
07b0d913af
conform to jdk8 algorithm constraints with keystores
2017-05-04 13:14:31 +01:00
dcd9b9e186
use jdk8 allowed cypher in the restricted set
2017-05-04 12:58:25 +01:00
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
2b3f0e5958
add some logging to diagnose ci failure
2017-05-04 10:23:13 +01:00
18d05ba5e0
modify test to validate setting isDLQ flag via startup destination query options
2017-05-03 16:17:29 +01:00
35f30102a6
[AMQ-2100] fix for intermittent ci failure
2017-05-03 12:31:09 +01:00
c4a1346875
[AMQ-6465] fix up test interplay - clean on start and consume what is produced
2017-05-03 12:22:24 +01:00
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
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
0e74c52e8a
[NO JIRA] tidy up MbeanInfo text in DestinationView
2017-04-26 12:10:24 +01:00
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
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
Christopher L. Shannon (cshannon)
gtully
Timothy Bish
Robert Gemmell
Hiram Chirino
Christian Schneider