a4cd137dab
https://issues.apache.org/jira/browse/AMQ-6187
...
Create a proper SSLContext for the MQTT client provider in the tests to
avoid failure on newer JDKs
(cherry picked from commit 6e2edf08c3
2016-02-26 13:44:27 -05:00
86e51d2461
[maven-release-plugin] prepare for next development iteration
2016-02-02 17:11:44 +00:00
d60b73402c
[maven-release-plugin] prepare release activemq-5.13.1
2016-02-02 17:11:03 +00:00
95fc593975
Update version for next patch release iteration.
2015-11-30 14:35:26 +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
9bc28214d5
https://issues.apache.org/jira/browse/AMQ-6060 - retain will message
2015-11-24 14:13:32 +01:00
f8bfff0bc8
https://issues.apache.org/jira/browse/AMQ-6029 - wss transport with certificate authentication
2015-10-30 11:42:36 +01:00
f09b9203a0
https://issues.apache.org/jira/browse/AMQ-6021 - mqtt+nio+ssl certificate authentication
2015-10-23 15:25:33 +02:00
816e8dfe54
https://issues.apache.org/jira/browse/AMQ-6002 - escape client id in virtual topic mqtt subscription; add test
2015-10-07 11:42:03 +02:00
aa743cbd7a
https://issues.apache.org/jira/browse/AMQ-6002 - escape client id in virtual topic mqtt subscription
2015-10-07 11:28:41 +02:00
b83c38b04c
https://issues.apache.org/jira/browse/AMQ-5997 - support legacy clients
2015-10-05 12:55:48 +02:00
4a8fec4a66
https://issues.apache.org/jira/browse/AMQ-5983 - mqtt virtual topic queue restore
2015-09-28 13:10:31 +02:00
04ee70a161
https://issues.apache.org/jira/browse/AMQ-5889
...
Adding support for auto detection of wire protocols over a transport.
OpenWire, AMQP, STOMP, and MQTT can all be detected and the broker
will properly handle each one over a given Transport. Currently
auto TCP, NIO, SSL, and NIO+SSL transports can handle auto-detection
of the wire format and client but support could be added in the
future for other transports like websockets.
2015-08-11 19:39:29 +00:00
6cdd750ddc
[maven-release-plugin] prepare for next development iteration
2015-08-10 11:04:26 -04:00
a9eeb03520
[maven-release-plugin] prepare release activemq-5.12.0
2015-08-10 11:04:17 -04:00
457dbd8b64
https://issues.apache.org/jira/browse/AMQ-5919
...
Converting printStackTrace statements to slf4j so that exceptions
are logged properly
2015-08-05 16:29:29 +00:00
a05a9a2129
https://issues.apache.org/jira/browse/AMQ-5552 - added profile for activemq.tests=smoke to run a fast subset of tests that gives a fast verification of a full build
2015-07-09 14:10:38 +01:00
e1c707e813
https://issues.apache.org/jira/browse/AMQ-5856 - fix typo that lead to recursive call - test regression in MQTTConnectTest
2015-07-08 12:18:05 +01:00
455f1ca475
https://issues.apache.org/jira/browse/AMQ-5872
...
The code that adds subscriptions for retroactive subscribers did not
account for the case where the last ack position in the ackLocations
table is used as a placeholder for the next incoming message and there
may not be an element in the messageReference tracker for that index
especially after restart when the index is reloaded. The code needed to
check this when it iterates of the existing message references to add a
value so to avoid the NPE.
Also cleaned up the MQTT tests such that they place their data dir in
./target so that old stores get removed on 'mvn clean'
2015-07-02 17:04:35 -04:00
27edaffded
https://issues.apache.org/jira/browse/AMQ-5856
...
Clean up the MQTT over WebSocket code to allow for handling link
stealing and inactivity monitor. Ensures that the web socket instances
get cleaned up on errors and avoids leaks that might otherwise arise.
Adds new tests for MQTT over WebSocket.
Adds some missing license headers as well.
2015-06-29 18:35:08 -04:00
789eb9abf9
https://issues.apache.org/jira/browse/AMQ-5834
...
Ensure that a publish receives an ACK even when the user is not
authorized to write to the target destination
2015-06-10 14:59:02 -04:00
af999fe2b2
https://issues.apache.org/jira/browse/AMQ-5303
...
Resolves issues with the virtual topic subscription strategy especially
when subscribing durably to the Topic portion of a virtual destination.
2015-06-05 18:05:03 -04:00
47e954d0f6
https://issues.apache.org/jira/browse/AMQ-5303
...
Fix for subscription recovery of durable topic subscriptions using
default subscription strategy and subscribing to a VirtualTopic
instance.
2015-06-04 15:14:52 -04:00
f37b005acf
https://issues.apache.org/jira/browse/AMQ-5776
...
Add better support for maxFrameSize configuration that fits with the
defaults configuration for the broker by allowing the maxFrameSize to be
configured via ?wireFormat.maxFrameSize on STOMP, AMQP, and MQTT.
Previously we only supported transport.wireFormat.maxFrameSize.
2015-06-02 15:25:11 -04:00
3125caee5b
https://issues.apache.org/jira/browse/AMQ-5794
...
implement transport.connectAttemptTimeout option across the transports
fro OpenWire, STOMP, AMQP and MQTT and add tests to cover.
2015-05-26 12:29:23 -04:00
3454a8b596
https://issues.apache.org/jira/browse/AMQ-5781
...
add maxFrameSize to the transport and enforce across the TCP, SSL, NIO
and NIO+SSL transport connectors.
2015-05-18 17:50:55 -04:00
fd2805fe1c
https://issues.apache.org/jira/browse/AMQ-5441
...
Don't dip into the store to recover durable topic subscriptions or queue
subscriptions depending on the subscription strategy in use. The needed
information is always kept in either TopicRegion or QueueRegion even
after restart as all stored destinations are reloaded as the broker is
started.
2015-05-15 16:01:54 -04:00
f5283a9045
https://issues.apache.org/jira/browse/AMQ-5734 - fix intermittent failure - seems the retained empty message gets dispatched so we need to consume it or it may have been dispatched to the client, causing a later failure
2015-04-28 16:18:22 +01:00
9ef4259297
https://issues.apache.org/jira/browse/AMQ-5616
...
Use ConcurrentMap in declarations
2015-04-28 11:15:08 -04:00
45eecf3351
upgrade java paho mqtt client
2015-04-21 15:04:04 +02:00
a4fbe70872
https://issues.apache.org/jira/browse/AMQ-5734
...
Support MQTT 3.1 silent subscription fail
2015-04-20 18:17:09 +02:00
1c72579d7a
https://issues.apache.org/jira/browse/AMQ-5598
...
Parallel connection test, could not reproduce issue.
2015-03-06 16:27:04 -05:00
4f57744934
https://issues.apache.org/jira/browse/AMQ-5594 - mqtt and virtual topic subs; more refined removing of destinations, as we don't want to remove all descendant destination in a wildcard case
2015-03-02 14:40:07 +01:00
101b7123fa
https://issues.apache.org/jira/browse/AMQ-5607
...
Some cleanups of the tests to speed things up.
2015-02-20 19:24:46 -05:00
05c3112402
https://issues.apache.org/jira/browse/AMQ-5594 - virtual topics and wildcards
2015-02-18 18:29:20 +01:00
ae595c95b1
[maven-release-plugin] prepare for next development iteration
2015-01-30 12:46:19 +00:00
4ba1a1689f
[maven-release-plugin] prepare release activemq-5.11.0
2015-01-30 12:46:08 +00:00
bf5a2997c7
[maven-release-plugin] prepare for next development iteration
2015-01-26 16:48:46 +00:00
eec2955bde
[maven-release-plugin] prepare release activemq-5.11.0
2015-01-26 16:48:37 +00:00
64fa706d54
Revert "[maven-release-plugin] prepare release activemq-5.11.0"
...
This reverts commit f47fbe4b89
2015-01-26 16:39:35 +00:00
f47fbe4b89
[maven-release-plugin] prepare release activemq-5.11.0
2015-01-26 16:17:43 +00:00
d5470254af
https://issues.apache.org/jira/browse/AMQ-5530 - default mqtt subscription prefetch
2015-01-26 12:53:56 +01:00
7948d69056
https://issues.apache.org/jira/browse/AMQ-5511 - retained message for zero-byte clientId client
2015-01-09 12:58:53 +01:00
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
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
aedcae139b
Revert "[maven-release-plugin] prepare release activemq-5.11.0"
...
This reverts commit 48b0cf396c
2015-01-05 12:25:58 -05:00
89995f4723
Revert "[maven-release-plugin] prepare for next development iteration"
...
This reverts commit 7b285c6f52
2015-01-05 12:25:47 -05:00
7b285c6f52
[maven-release-plugin] prepare for next development iteration
2014-12-29 12:44:32 +01:00
48b0cf396c
[maven-release-plugin] prepare release activemq-5.11.0
2014-12-29 12:44:20 +01:00
Timothy Bish
Christopher L. Shannon (cshannon)
Dejan Bosanac
gtully
Hadrian Zbarcea