2b3f0e5958
add some logging to diagnose ci failure
2017-05-04 10:23:13 +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
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
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
98c5866c75
https://issues.apache.org/jira/browse/AMQ-6418
...
Properly setting the transport properties on the
AutoNIOSSLTransportServer and fixing the Stomp protocol to set the peer
certs when using auto+ssl
2016-09-06 10:17:05 -04:00
ed0e786b60
https://issues.apache.org/jira/browse/AMQ-6414
...
Changing the nio+ssl transports to trigger a serviceRead after start up
to prevent blocking. The prevents the channels from not reading in
certain cases, most notably with the auto+nio+ssl transport when used
for a network bridge. Also added a couple tests and changed a network
bridge test to test out auto+nio+ssl.
2016-09-01 11:39:46 -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
667ea7c640
https://issues.apache.org/jira/browse/AMQ-6345
...
disabling failed assertion for test as it is expected based on how this
test is usin the client
2016-07-07 18:23:50 +00:00
b5b087d558
https://issues.apache.org/jira/browse/AMQ-6345
...
Moving PINGREQ tests into its own test class so they aren't run more
than once
2016-07-07 13:53:58 +00:00
6dacef1c95
https://issues.apache.org/jira/browse/AMQ-6345
...
The MQTT transport will now throw an exception if a PINGREQ is sent to
the broker if a CONNECT packet has not been received first as the spec
says CONNECT must be the first packet sent.
2016-07-06 15:59:25 +00: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
d9c4048292
Clean up and adjust test timeouts for CI
2016-05-16 11:24:50 -04:00
ab434ee776
Refactor test which has some flawed assumptions about the incoming
...
messages based on subscriptions that it makes. Adds better thread
safety as well.
2016-05-13 18:30:44 -04:00
91d277ccb0
Make the result value in the listener volatile since it is read from and
...
written to in multiple threads without sync.
2016-05-09 16:11:06 -04:00
27799fec97
https://issues.apache.org/jira/browse/AMQ-5880
...
Update to latest MQTT client release to resolve this issue.
2016-05-02 16:21:34 -04:00
6d20cba0e4
https://issues.apache.org/jira/browse/AMQ-6253 - mqtt composite destinations support for virtual topic subscriptions
2016-04-15 11:00:39 +02:00
f3544f248f
https://issues.apache.org/jira/browse/AMQ-5886
...
Ensure we reject protocol version that we don't currently support.
2016-03-03 12:41:59 -05:00
5d6d42ce97
https://issues.apache.org/jira/browse/AMQ-5883
...
https://issues.apache.org/jira/browse/AMQ-5884
https://issues.apache.org/jira/browse/AMQ-5885
Add additional validation of Topic names used in subscribe and
unsubscriobe that test for spec compliance.
2016-03-02 12:30:54 -05:00
8ef44452a2
https://issues.apache.org/jira/browse/AMQ-5880
...
Adds a test for the issue that is ignored for now while we wait for a
fixed MQTT client release.
2016-03-01 16:18:16 -05:00
19c9404916
https://issues.apache.org/jira/browse/AMQ-5882
...
removing illegal wildcard characters used in topics for some MQTT tests
2016-02-29 13:29:44 +00:00
1b38b27ed2
https://issues.apache.org/jira/browse/AMQ-5882
...
Fail to publish if the topic name in the publish packet contains a wild
card character as per the MQTT V3.1 and V3.1.1 spec.
2016-02-28 17:54:23 +00:00
6e2edf08c3
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
2016-02-26 13:42:16 -05:00
c530b69e16
https://issues.apache.org/jira/browse/AMQ-5881
...
Fail the connect if the password is set but the username bit is not as
per the V3.1.1 spec requirements.
2016-02-25 19:08:22 -05: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
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
gtully
Christopher L. Shannon (cshannon)
Hadrian Zbarcea
Timothy Bish
Dejan Bosanac