c4d460bf60
[maven-release-plugin] prepare for next development iteration
2017-10-17 10:16:08 -04:00
9e595d8674
[maven-release-plugin] prepare release activemq-5.15.2
2017-10-17 10:09:04 -04:00
a218119e6b
[maven-release-plugin] prepare for next development iteration
2017-09-28 10:45:21 -04:00
d17a8740fc
[maven-release-plugin] prepare release activemq-5.15.1
2017-09-28 10:28:20 -04:00
1d0121ccd4
Revert "[maven-release-plugin] prepare release activemq-5.15.1"
...
This reverts commit 756b858fa4
2017-09-28 10:05:01 -04:00
756b858fa4
[maven-release-plugin] prepare release activemq-5.15.1
2017-09-28 09:59:18 -04:00
76474fbc67
Revert "[maven-release-plugin] prepare release activemq-5.15.1"
...
This reverts commit 37227fbf8b
2017-09-27 08:54:44 -04:00
ade1a87e09
Revert "[maven-release-plugin] prepare for next development iteration"
...
This reverts commit e2eabeb1c2
2017-09-27 08:54:36 -04:00
eccbd75bcf
AMQ-6823 Ensure that MessagePull is works across HTTP transport
...
The MessagePull command needs to have the transients initialized such
that the pull operation works across transports that use XStream or
other marshaling that doesn't performs custom serialization.
(cherry picked from commit a21dd40527
2017-09-25 13:26:59 -04:00
e2eabeb1c2
[maven-release-plugin] prepare for next development iteration
2017-09-25 09:23:32 -04:00
37227fbf8b
[maven-release-plugin] prepare release activemq-5.15.1
2017-09-25 09:17:38 -04:00
7a2c4eecb2
AMQ-6765 Add trace logging of start failure exception
...
Log the exception at trace level when start fails.
(cherry picked from commit 56bed30c64
2017-09-07 12:10:08 -04:00
ca86e2fbe6
AMQ-6801: ensure transport listener is set before tripping latch to indicate startup is occuring
...
(cherry picked from commit 2e492569db
2017-09-01 13:02:39 +01:00
e7956b527d
NO-JIRA: Incrementing version to 5.15.1-SNAPSHOT
2017-06-27 13:52:45 -04:00
5f0d6943cb
[maven-release-plugin] prepare release activemq-5.15.0
2017-06-27 13:41:01 -04:00
2490c85fc5
AMQ-6699 Fix STOMP over WS not encoding header values
...
When sending STOMP frames out over WS the marshal isn't doing a proper
encode based on the STOMP version in use and so header values can be
transmitted without proper escaping.
2017-06-14 15:15:09 -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
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
4f6c55ad67
[AMQ-6571] use browsercompatspec cookie matcher - apply patch from Andrew Flegg with thanks
2017-01-20 14:54:37 +00:00
29b4db5c34
https://issues.apache.org/jira/browse/AMQ-6521
...
Fixing support for Jetty 9.3 and Jetty 9.2. The previous attempt at a
fix had the wrong class instance.
2016-12-09 09:47:16 -05:00
80f46a8056
https://issues.apache.org/jira/browse/AMQ-6521
...
Adding support for Jetty 9.3 by re-adding in the logic to dynamically
load the correct GzipHandler depending on the version
2016-11-29 11:38:36 -05:00
f40532a23d
https://issues.apache.org/jira/browse/AMQ-6491
...
Changing the WebSocket servlet to return a succesful empty response
instead of an error when a GET request is made
2016-11-22 07:27:29 -05:00
937b2acd46
https://issues.apache.org/jira/browse/AMQ-6482
...
Adding websocket send timeout to AMQP over websockets
2016-11-04 14:09:26 -04:00
450cabe4ea
https://issues.apache.org/jira/browse/AMQ-6482
...
Adding a timeout for websocket sends to prevent the transport thread
from getting stuck and blocking. The default is 30 seconds.
2016-11-04 12:56:20 -04:00
946c9454d5
proposed websocket fix
2016-11-04 12:56:20 -04:00
be24a133ef
This closes #88 (merged as a65ac586). More file permissions fixes.
2016-11-03 14:26:34 -04:00
d5a929c0d2
This closes #205 . Won't fix. (fix even more file permissions)
2016-11-03 14:11:40 -04:00
d54d046b8a
This closes #185 . Won't fix. (fix more file permissions)
2016-11-03 11:54:33 -04:00
06e929f101
https://issues.apache.org/jira/browse/AMQ-6397
...
Setting the HTTP timeout for all HttpClients instead of just on send
2016-08-17 09:35:18 -04:00
06a21dbbb3
[maven-release-plugin] prepare for next development iteration
2016-08-02 09:03:37 -04:00
71cbc65283
[maven-release-plugin] prepare release activemq-5.14.0
2016-08-02 09:02:54 -04:00
bd442a3388
https://issues.apache.org/jira/browse/AMQ-6343
...
On MQTT Websocket close, a LWT message will be properly sent if
configured and a disconnect packet was not received
2016-07-05 18:13:45 +00:00
96494f74c7
https://issues.apache.org/jira/browse/AMQ-6346
...
Prevent concurrent access to the MQTT protocol handlers which can lead
to a tansport level deadlock
2016-07-05 17:50:03 +00:00
31c55f7510
https://issues.apache.org/jira/browse/AMQ-6339
...
Add support for AMQP client to connect using WebSockets.
2016-06-30 14:52:40 -04:00
5ba8679083
Allow for the connection to close without getting the ERROR frame
2016-06-16 11:20:59 -04:00
71893f1434
Allow the HTTP test to have extra time to wait for all messages to
...
arrive as the transmission rate is much slower.
2016-05-10 10:59:12 -04:00
e47edd7a28
https://issues.apache.org/jira/browse/AMQ-6262
...
Ensure that the connection check task is stopped once commands pass
through the inactivity monitor to prevent the transport from being
closed for no reason.
2016-04-25 17:05:09 -04:00
34eb1ee959
https://issues.apache.org/jira/browse/AMQ-6259 - mqtt-over-ws configuration
2016-04-19 16:02:45 +02:00
30d6ad72fa
NO-JIRA Allow for the disconnect call in the test to fail as the short
...
keepAlive interval can trigger a shutdown of the socket before we have a
chance to write the disconnect depending on the timing.
2016-03-17 14:08:09 -04:00
e375af3810
https://issues.apache.org/jira/browse/AMQ-6182
...
Adding missing License header
2016-03-01 16:01:58 +00:00
473b3284d4
https://issues.apache.org/jira/browse/AMQ-6182
...
Reworking patch so that the http trace method is also turned off by
default for the HttpTransport, besides just for the Websocket transport.
Also added SSL tests for both transports.
2016-02-29 22:36:59 +00:00
7335f699f2
https://issues.apache.org/jira/browse/AMQ-6182
...
adding timeout to test method
2016-02-26 19:20:16 +00:00
4fb8083977
https://issues.apache.org/jira/browse/AMQ-6182
...
Disabling the HTTP trace method on the websocket port by default. It
can be enabled by setting the parameter "http.enableTrace=true" on the
connection uri if it is needed for debugging.
2016-02-26 18:54:25 +00:00
4ecff14030
NO-JIRA Update master version to 5.14.0-SNAPSHOT to match the eventual
...
release version.
2016-01-20 12:40:20 -05:00
b9dcb010f7
https://issues.apache.org/jira/browse/AMQ-6077
...
Making new values in ActiveMQObjectMessage transient which fixes HTTP
serialization
2015-12-15 19:37:05 +00:00
913f64476b
https://issues.apache.org/jira/browse/AMQ-6073
...
WSServlet for websockets will attempt to detect the subprotocol
requested and respond with the appropriate one. Currently the protocols
loaded are what stomp.js use for stomp (v11.stomp and v12.stomp).
If a protocol can't be found then a default will be returned, either
"stomp" or "mqtt", which is the same behavior before this patch.
This will make it a bit easier to use stomp over websockets out of the
box as stomp.js will work by default.
2015-12-07 15:29:13 +00:00
cfb4ca9f54
[maven-release-plugin] prepare for next development iteration
2015-11-30 13:48:58 +00:00
abfe038ddf
[maven-release-plugin] prepare release activemq-5.13.0
2015-11-30 13:48:11 +00:00
0a12bcb928
https://issues.apache.org/jira/browse/AMQ-2191 https://issues.apache.org/jira/browse/AMQ-3529 - rework fixes to remove uncertanty from dealing with intettuptedexception. Sync requests will trap interrupts that ocurr while waiting for responses and fail the connection with an interruptedioexception. Interrupts pending before requests will be suppressed, allowing possible clean shutdown. It is not safe to replay openwire ops b/c they are not idempotent, the only safe option is to have a teardown of the broker side state from a close
2015-11-27 12:21:56 +00:00
Christopher L. Shannon (cshannon)
Timothy Bish
Robbie Gemmell
gtully
Hadrian Zbarcea
Dejan Bosanac