e1699d58c8
AMQ-6808 preserve destination for browsed scheduled messages
...
(cherry picked from commit c691124d32
2017-09-15 09:03:58 -04:00
9387451412
https://issues.apache.org/jira/browse/AMQ-6799 - stop the jmx server connector properly
...
(cherry picked from commit 5e656d394c
2017-09-07 12:14:45 -04:00
ccf8dbe28b
https://issues.apache.org/jira/browse/AMQ-6799 - IOExceptionHandler during the startup
...
(cherry picked from commit c7291f1ecf
2017-09-07 12:14:35 -04:00
0924f983f8
[AMQ-6792] fire the failover exception handler before stop to ensure blocked write does not block stop request
...
(cherry picked from commit 63f0b7e20d
2017-09-07 12:14:23 -04:00
d5dfadd8d0
[AMQ-6788] Explain how to fix the problem in the exception
...
(cherry picked from commit 8646bb1010
2017-09-07 12:13:55 -04:00
3b6ba778bd
[AMQ-6643] refine fix to allow wildcard subs to non wildcard subscription queues, enable simple wildcard sub to drain all subscription queues
...
(cherry picked from commit a67c75a9e1
2017-09-07 12:13:40 -04:00
035baf1722
[AMQ-6787] release securty context on failure to addConnection subsequent to auth, resolve leak. fix and test
...
(cherry picked from commit a15626193c
2017-09-07 12:13:29 -04:00
1bba73dcb6
[AMQ-6778] fix and test - no longer gate firing advisory on broker start flag b/c consumers may be present once transport connectors have started
...
(cherry picked from commit ddfa96028c
2017-09-07 12:10:55 -04:00
7ab743a053
[AMQ-6764] add logging of exit of jmx ops such that overlaps and delays are visible in the audit. fix and test
...
(cherry picked from commit d7f70837b7
2017-09-07 12:09:56 -04:00
eca72dc81a
AMQ-6798 - Clean up store usage object on Queue stop
...
When queues are stopped the StoreUsage object needs to be stopped so it
will be removed from the parent StoreUsage. This allows the object to
be garbage collected and prevents a memory leak.
(cherry picked from commit 35bd3ad938
2017-08-24 09:25:13 -04: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
2311749aa2
AMQ-6706 - Protecting preShutdownHooks with an AtomicBoolean
2017-06-20 11:05:29 -04:00
155461a0ba
AMQ-6706 Allow for hooks before broker stop occurs
...
When Camel is run embedded within ActiveMQ it's shutdown is called at
the point the broker is already stopped, this can lead to data loss as
there could be exchanges that have not ended.
This adds the ability to specify preStopHook(s) that can be invoked
during ActiveMQ shutdown but before the broker is shutdown.
With this Camel can gracefully shutdown while the broker is still
started.
2017-06-19 14:29:05 +02:00
b07821ab64
[AMQ-6625] remove kahadbioexceptionhandler by pushing allowIOResumption into persistence adapter. This allows the lease locker to still be used with kahadb for stopStartConnectors support
2017-06-15 17:28:31 +01:00
df3bd83c0d
[AMQ-6703] check for enable audit false
2017-06-15 11:22:20 +01:00
99f3d4c505
[AMQ-6703] have jmx purge clear the audit such that messages can be copied back, fix and test
2017-06-15 10:46:23 +01:00
b6cb0eacea
[AMQ-6702] add maxProducersToAudit and maxAuditDepth to dead letter strategy to cofigure the audit, fix and test
2017-06-13 14:26:15 +01:00
2a0b785a04
AMQ-6698 - Allow timeout of SSL handshake for auto+nio+ssl
...
The handshake now takes place inside of the async task that timesout so
that if the SSL handshake takes too long the connection attempt will
honor protocolDetectionTimeout and actually timeout. Also, change the
default of protocolDetectionTimeout to 30 seconds so it matches the rest
of the broker's default connection timeout settings.
2017-06-08 12:34:15 -04:00
7413ee00e1
[AMQ-6696] zero out usage for forwarded messages such that the original target is no longer referenced. fix and test
2017-06-02 12:23:58 +01:00
d2c0eddaad
[AMQ-6691] allow dlq flag to be set via jmx to allow retry op after a restart - use destinations element for long term persistence
2017-05-31 12:39:48 +01:00
8023b9ee44
[AMQ-6690] do nothing for move/copy jmx ops that try to modify self
2017-05-31 11:26:46 +01:00
00ee9491d9
[AMQ-6678] sync destructive purge on queue view mbean (jmx) to prevent concurrent calls
2017-05-29 11:21:00 +01:00
25f112c5c9
[AMQ-6687] ensure transacted sends blocked on pfc do not resume after tx completion. AMQ-4467 refine the fix such that PFC kicks in such that the cache will accept messsages that push it over it's limit while it is still under the limit
2017-05-25 12:43:08 +01: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
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
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
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
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
d84a58656c
[AMQ-6640] allign use of sync vm transport usage on duplex end of networkconnector with initiator end. only duplexinbound for forwarding is async to allow thread for responses. vm transport options applied in one place and test more deterministic w.r.t the hang scenario
2017-03-29 23:50:47 +01:00
8e00c6c2bc
[AMQ-6640] fix duplicate suppression sync request on responder end of duplex network connector only b/c that has the async local transport. Additional test. Ensure broker sync is conditional on the need for duplicate suppression which should only be necessary in ring topologies when properly configured
2017-03-28 14:49:23 +01:00
c5a8b2c8b1
[AMQ-6625] ensure kahadb stops operation on the first IOException to facilitate auto recovery from partial writes
2017-03-13 13:49:41 +00:00
01b1f7f694
[AMQ-3233] respect policy entry blockedProducerWarningInterval for flow control warning, 0 disables and Xmillis makes it periodic, default period of 30s is not unlike the existing once behaviour. fix and tests
2017-03-03 11:23:23 +00:00
e67d48680f
[AMQ-6614] fix up jmx blockedSendsCount and producer view blocking flag for async send case. fix and test
2017-03-02 17:00:16 +00:00
b6521e292b
[AMQ-6414] additional logging that helped identify root cause
2017-02-27 17:01:16 +00:00
ef84db5e64
AMQ-6610: Fixing JDBC test
...
Durable destinations need to always be loaded on connector start
2017-02-27 07:34:22 -05:00
bab0887ed6
AMQ-6610 - Network connector mbean not registered on reload
...
On network connector add or update after broker start (such as the
runtime plugins) the mbean was not created. There was also a couple of
other properties not set. Fixed the network connector start to be the
same for normal broker start and runtime reload.
2017-02-24 14:05:27 -05:00
fad50812af
[AMQ-6547] revert mod from AMQ-3143 such that waitForSpace respects child usage, fix test and validate mKahadb blocking send
2017-02-14 11:33:59 +00:00
d86c98a687
[AMQ-6587] - fix root cause of deletion candidate seeing sub. contention between adding sub to dests and adding dests to sub, also removing sub from dests twice could leave dest stat negative allowing invalid candidate for gc
2017-02-10 11:38:03 +00:00
c049d3c1f7
Add a simple IDERunner for testing
...
Adds a simple class to run a broker instance with a TCP transport
connector and no persistence enabled for quick tests.
2017-02-07 17:28:28 -05:00
0ee4f5b843
[AMQ-6587] additional contention window with new sub while gc is in progress - need to verify new sub is actually subscribed to the candidate for deletion. Fix and test
2017-02-07 13:53:40 +00:00
9b9e3d3678
https://issues.apache.org/jira/browse/AMQ-6588
...
Add more detail to log output for easier tracking
2017-02-01 16:15:11 -05:00
e415d2921e
[AMQ-6587] ensure subs added to new destination before destination is exposed in the destination map. sort gc contention with wildcard subs and anonymous publish. fix and test
2017-02-01 15:08:46 +00:00
687badb4fd
AMQ-6577: honour usePrefetchExtension in TopicSubscription.
...
AMQ-6577: move usePrefetchExtension flag to AbstractSubscription to promote reuse.
2017-01-30 11:13:57 -05:00
d0c95146c3
https://issues.apache.org/jira/browse/AMQ-6579
...
Remove incorrect dispatch counter increment on message expiration in
TopicSubscription when a pending limit strategy is set
2017-01-25 11:16:43 -05:00
56bb079c82
https://issues.apache.org/jira/browse/AMQ-1940
...
Queue purge now acquires the sendLock to prevent new messages from
coming in while purging. The statistics are no longer zeroed out as
they should properly decrement as messages are removed. These changes
should prevent the statistics from going negative.
2017-01-24 08:46:15 -05:00
Erik Wramner
Dejan Bosanac
gtully
Christian Schneider
Christopher L. Shannon (cshannon)
Zoran Regvart
Timothy Bish
Vasco Veloso