e5de25f4fc
NO-JIRA: Add missing license headers
2018-01-29 08:10:50 -05:00
f96a20e831
[AMQ-6891] apply fix and test from Radek Kraus with thanks. Pending cursor adds are now dropped on rollback
2018-01-26 13:18:00 +00:00
8c77e9553e
[AMQ-6880] fix filter match logic when transport connector updateClusterFilter is in play
2018-01-03 16:07:06 +00:00
a8a032af09
AMQ-6861 Allow customisation of network bridge creation logic.
2017-12-20 22:00:54 -05:00
56baba96c6
AMQ-6875 - Use the correct destination for Virtual destination consumers
...
when using Virtual Topics
2017-12-14 16:01:10 -05:00
9d98ee253f
sync code default with config default to use jvm mbean server
2017-11-24 10:36:52 +00:00
151e17abfe
[AMQ-6854] - periodic log warn on store limits reached in the same way
2017-11-21 14:56:02 +00:00
08aa5118ff
(AMQ-6858) - add extra precautionary check for demand subs
...
also remove test that intermittently fails with timing issues
2017-11-16 07:44:33 -05:00
6013441a9a
AMQ-6858 - handle resync of network proxy durables after restart
...
We need to properly handle the re-addition of network proxy durables
after the brokers are restarted so removal is done properly
2017-11-15 08:56:43 -05:00
3ca439cada
AMQ-6858 - Allow configuration of the client Id token in network bridge
...
The client id token that is used to separate parts of a generated local
client id in a network bridge should be configurable so bridge names and
broker names can contain underscores if desired
2017-11-14 15:23:26 -05:00
41211c78d1
AMQ-6858 - reworking durable subscription propagation fix
...
Significantly reworking previous fix so that the client id is properly
changed when tracking network proxy subscriptions. This makes it so
removal is done properly
2017-11-13 11:07:43 -05:00
96ce14b278
AMQ-6858 - Fix several durable subscription bridge propagation issues
...
Durable network proxy subs will now be properly created across multiple
bridges when 3 or more brokers are used. Demand will be properly synced
and removed.
2017-11-09 11:21:18 -05:00
b29ccf3488
[AMQ-6854] log warn if page in is blocked on usage preventing dispatch. Reuse blockedProducerWarningInterval to tweak reporting
2017-11-02 16:04:30 +00:00
03b19b9da4
[AMQ-6847] limit the retry loop to one iteration overa all pending messages such that new additions are not replayed to avoid duplicates
2017-11-01 11:26:36 +00:00
2ea5d1420b
[AMQ-6847] pause dispatch for message move to avoid redelivery with pending ack/remove/audit rollback
2017-10-27 11:40:06 +01:00
8e576be1d9
[AMQ-6849] - fix sendFailIfNoSpaceAfterTimeout policy entry default value
2017-10-26 11:36:03 +01:00
6da08b245e
[AMQ-6849] provide a virtualTopic dropOnResourceLimit attribute, default to false.
...
Enabling will allow dispatch to continue even when end to some consumer queues
fail due to resource constraints.
The existing systemUsage sendFailIfNoSpace and sendFailIfNoSpaceAfterTimeout are
promoted to destination policy options allowing selective destinations to fail a
send with an exception. The global system usage options are still in place.
When dropOnResourceLimit=true dispatch will continue in the event that any
subscription queue throws a resource limit exception on send failure.
2017-10-25 14:53:20 +01:00
41a100766c
[AMQ-6824] - fix up prefetchExtension growth on transaction completion and delivered ack and tie in boolean usePrefetchExtension
2017-09-26 11:30:18 +01:00
c691124d32
AMQ-6808 preserve destination for browsed scheduled messages
2017-09-15 09:02:36 -04:00
5e656d394c
https://issues.apache.org/jira/browse/AMQ-6799 - stop the jmx server connector properly
2017-09-01 13:02:53 +02:00
35bd3ad938
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.
2017-08-24 09:24:36 -04:00
c7291f1ecf
https://issues.apache.org/jira/browse/AMQ-6799 - IOExceptionHandler during the startup
2017-08-24 14:04:36 +02:00
63f0b7e20d
[AMQ-6792] fire the failover exception handler before stop to ensure blocked write does not block stop request
2017-08-11 12:58:51 +01:00
8646bb1010
[AMQ-6788] Explain how to fix the problem in the exception
2017-08-08 20:55:56 +02:00
a67c75a9e1
[AMQ-6643] refine fix to allow wildcard subs to non wildcard subscription queues, enable simple wildcard sub to drain all subscription queues
2017-08-08 16:38:11 +01:00
a15626193c
[AMQ-6787] release securty context on failure to addConnection subsequent to auth, resolve leak. fix and test
2017-08-04 13:46:16 +01:00
ddfa96028c
[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
2017-07-25 13:02:13 +01:00
d7f70837b7
[AMQ-6764] add logging of exit of jmx ops such that overlaps and delays are visible in the audit. fix and test
2017-07-10 14:10:05 +01:00
a9fe4e33c3
[maven-release-plugin] prepare for next development iteration
2017-06-27 13:41:28 -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
Christopher L. Shannon (cshannon)
gtully
Łukasz Dywicki
Erik Wramner
Dejan Bosanac
Christian Schneider
Zoran Regvart