7b5150fbe3
[maven-release-plugin] prepare release activemq-5.12.3
2016-02-03 13:33:25 -05:00
5f0064622e
[maven-release-plugin] prepare for next development iteration
2016-01-05 15:44:57 +00:00
6ccbbce23d
[maven-release-plugin] prepare release activemq-5.12.2
2016-01-05 15:44:06 +00:00
bf35f42bb6
https://issues.apache.org/jira/browse/AMQ-6109
...
The chooseValue method in DestinationMap will now always return the
exact match, if there is one, else it will then sort as before.
(cherry picked from commit 8e2176d93c
2015-12-29 12:48:08 +00:00
ec50d23caa
Revert "[maven-release-plugin] prepare release activemq-5.12.2"
...
This reverts commit f4a05c4573
2015-12-18 17:43:08 +00:00
340d095588
Revert "[maven-release-plugin] prepare for next development iteration"
...
This reverts commit 33d8bde31a
2015-12-18 17:43:04 +00:00
33d8bde31a
[maven-release-plugin] prepare for next development iteration
2015-12-16 15:02:41 +00:00
f4a05c4573
[maven-release-plugin] prepare release activemq-5.12.2
2015-12-16 15:00:53 +00:00
2ae189e700
https://issues.apache.org/jira/browse/AMQ-6077
...
Making new values in ActiveMQObjectMessage transient which fixes HTTP
serialization
(cherry picked from commit b9dcb010f7
2015-12-16 14:41:45 +00:00
c3339bc0fb
https://issues.apache.org/jira/browse/AMQ-6016 - ensure xstream inits transients to default values when it bypasses the default creation method through object deserialization. Can make it more general if there are ever more instances of this. It avoids the need to check for null and sync
...
(cherry picked from commit 8136e67b40
2015-12-16 14:41:37 +00:00
b84785d5d0
https://issues.apache.org/jira/browse/AMQ-6016 - rework fix for https://issues.apache.org/jira/browse/AMQ-2106 - account group assignment on a per destination basis to prevent modification during consumer ordering
...
(cherry picked from commit 5d697cff3b
2015-12-16 14:41:14 +00:00
4ceda81e07
Revert "[maven-release-plugin] prepare release activemq-5.12.2"
...
This reverts commit 9d789cd28e
2015-12-15 18:16:44 +00:00
ab43a15c99
Revert "[maven-release-plugin] prepare for next development iteration"
...
This reverts commit 21aa3ff35b
2015-12-15 18:16:05 +00:00
21aa3ff35b
[maven-release-plugin] prepare for next development iteration
2015-12-15 16:19:29 +00:00
9d789cd28e
[maven-release-plugin] prepare release activemq-5.12.2
2015-12-15 16:18:53 +00:00
9a0298f3e9
https://issues.apache.org/jira/browse/AMQ-6077 - define default values (based on system property) for connection factory and object message
...
(cherry picked from commit eeec0c07b0
2015-12-15 12:52:30 +00:00
7a262b74db
https://issues.apache.org/jira/browse/AMQ-6077 - define object message trusted packages on connection factory
...
(cherry picked from commit 94446e53dc5e02e305ea
2015-12-14 19:13:49 +00:00
7eb9b218b2
https://issues.apache.org/jira/browse/AMQ-6013 - init serializable packages statically
2015-12-03 19:22:45 +01:00
e7a4b53f79
https://issues.apache.org/jira/browse/AMQ-6013 - restrict classes which can be serialized inside the broker
2015-12-03 19:22:30 +01:00
d9a79d172b
release the connection even if broker communication fails
...
(cherry picked from commit 934f3cea7e
2015-11-20 13:37:03 +00:00
88d157faf5
[maven-release-plugin] prepare for next development iteration
2015-10-12 17:21:40 +00:00
21c8b4695f
[maven-release-plugin] prepare release activemq-5.12.1
2015-10-12 17:20:52 +00:00
a0d8a15465
https://issues.apache.org/jira/browse/AMQ-6004
...
Calling socketHandlerThread.interrupt() on TcpTransportServer stop to
make sure the broker shutsdown cleanly.
Patch applied with thanks to Erik Godding Boye
(cherry picked from commit 4adc8e4f4e
2015-10-08 12:14:06 +00:00
70a49b0fa2
https://issues.apache.org/jira/browse/AMQ-5972 - wildcard policy entries not applied in correct order
...
(cherry picked from commit ee4672baaf
2015-09-17 12:03:00 +00:00
3619724d97
https://issues.apache.org/jira/browse/AMQ-5951 - ensure failover oneway won't retry if reconnect will not happen
...
(cherry picked from commit ae9af4b8b2
2015-08-31 13:34:54 -04:00
6668f7b14f
https://issues.apache.org/jira/browse/AMQ-5794 - duplex network case calls start twice and would start a connect check timer in error. Fix is to only start connectiontimeout if we have not already started the rest of the monitoring
...
(cherry picked from commit e5a94bfee2
2015-08-12 12:52:19 -04:00
497d5b4f79
Update version for next patch release iteration.
2015-08-10 17:04:32 -04: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
41ee3ec8de
https://issues.apache.org/jira/browse/AMQ-5921
...
Add back support for type void and test.
2015-08-07 11:00:44 -04:00
d8c0ff1417
Fix javadoc warnings.
2015-08-05 19:01:08 -04:00
61b2f6b40e
Fix some javadoc warnings and spelling errors in the docs.
2015-08-05 18:13:42 -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
da36f78a6a
https://issues.apache.org/jira/browse/AMQ-5596
...
Remove some additional references to old JMS Streams properties.
2015-08-03 17:11:44 -04:00
3348ade99b
https://issues.apache.org/jira/browse/AMQ-5914
...
Ensure a new pull request is sent, adds test.
2015-08-03 14:41:56 -04:00
310c2bb059
https://issues.apache.org/jira/browse/AMQ-5857
...
Fixing a potential race condition in the storeContent
method of ActiveMQTextMessage
2015-07-31 18:32:02 +00:00
b84413a314
https://issues.apache.org/jira/browse/AMQ-5907
...
recompute the timeout value and send a new pull request if the message
received exceeds the configure redelivery maximum.
2015-07-30 17:17:55 -04:00
84ec047d2f
https://issues.apache.org/jira/browse/AMQ-5857
...
Changing ActiveMQTextMessage to clear out the text field on marshal to
a ByteSequence to prevent the data from being stored in memory twice.
2015-07-30 16:59:05 +00:00
b9b27b968b
https://issues.apache.org/jira/browse/AMQ-5893
...
Ensure that unacknowledged messages are removed from the Audit so they
are able to be redelivered to another consumer on this connection
2015-07-16 10:46:11 -04:00
c85c7c1472
AMQ-5400 - rework to remove static lock - impacted parallel delivery and hense performance. Fix and additional tet
2015-07-16 12:38:52 +01:00
ad8879d283
https://issues.apache.org/jira/browse/AMQ-5368 - improve nio ssl handshake performance - use soTimeout for handshake selector
2015-07-13 13:34:22 +02:00
18300c6514
https://issues.apache.org/jira/browse/AMQ-5621
...
Clean up, convert all to JUnit 4 style tests, replace system.out calls
with loggers.
2015-07-10 17:14:48 -04:00
f10aab6428
https://issues.apache.org/jira/browse/AMQ-5851
...
resolves #123
This commit resolves an issue where unmatched acknowledgement
messages could be received when running a MDB consumer and
sending messages with a short TTL. The expiration logic when
receiveing an expired Message Ack will now only expire messages
in dispatch relating to the received ack, not all expired messages
in the dispatch list.
2015-07-09 16:46:21 +01: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
52e4527125
https://issues.apache.org/jira/browse/AMQ-5368 - improve nio ssl handshake performance
2015-07-09 12:53:58 +02:00
13044decce
https://issues.apache.org/jira/browse/AMQ-5848
...
Use the latest openwire version marshallers in the KahaDB store when
starting from a clean install, drop back to the version used in the
existing store if one is found.
2015-07-08 17:29:32 -04:00
785b16bf9e
https://issues.apache.org/jira/browse/AMQ-5748
...
Added a getMessageSize method to MessageStore to support retrieving the
total message size of all stored messages for a destination. Added a
new storeMessageSize statistic to DestinationStatistics.
2015-07-07 18:03:27 +00:00
7a68ad5d98
https://issues.apache.org/jira/browse/AMQ-4814
...
Remove of a durable subscription when the keepDurableSubActive flag is
true (default) did not actually stop and cleanup the still active cursor
due to the fact that the cursor checks the flag of its subscription to
see if it should stay active when its stop method is called. The
subscription needs to disable that flag when the subscription is being
removed so that the cursor will correctly shutdown.
2015-07-06 18:21:20 -04:00
c38a61d7ae
https://issues.apache.org/jira/browse/AMQ-5340
...
Clean up a bit, extend test timeout to account for slow CI machines,
remove System prints and replace with LOG.
2015-07-06 16:47:58 -04:00
174dcbff2a
https://issues.apache.org/jira/browse/AMQ-5340
...
A QueueBrowser no longer checks expiry on messages to prevent a
browser from hanging in between the hasMoreElements check and actually
getting a message. This means that if messages were in the queue when
the browser started it will receive messages even if they are now
expired. Even though the browser will get the expired message, the
broker will still expire it to prevent future access to it.
Thanks to Henno Vermeulen for providing a test case.
2015-07-06 16:13:52 -04:00
Daniel Kulp
Christopher L. Shannon (cshannon)
gtully
Dejan Bosanac
Romain Manni-Bucau
Timothy Bish