gtully
060817552d
[AMQ-4261] use WARN level for producer flow control events, DEBUG if blockedProducerWarningInterval=0
2018-03-02 12:17:24 +00:00
gtully
b57f4f3211
[no jira] extend the timeout b/c it was on the margins
2018-03-01 11:38:16 +00:00
gtully
82c9f9531e
[AMQ-6907] add selectorAware option to conditionalNetworkBridgeFilterFactory such that replay back to origin can happen if there are no matching local consumers
2018-02-28 16:07:52 +00:00
gtully
efaf9cd77e
[AMQ-6906] jdbc store; ensure rolled back prepared ack messages are recovered asap
2018-02-28 13:31:12 +00:00
gtully
dd2572bcb1
[AMQ-6891] test and fix non tx variant of this leak
2018-01-30 10:51:30 +00:00
Christopher L. Shannon (cshannon)
e5de25f4fc
NO-JIRA: Add missing license headers
2018-01-29 08:10:50 -05:00
gtully
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
gtully
ec6fa19099
[AMQ-6815] rework to drop the batch reference from Location such that batches are free for gc when index pages are agressively cached
2018-01-11 12:56:40 +00:00
Łukasz Dywicki
a8a032af09
AMQ-6861 Allow customisation of network bridge creation logic.
2017-12-20 22:00:54 -05:00
Carlo Dapor
b40e5f93bd
[AMQ-6601] AMQ with master and slave broker, shutting down slave causes dead-lock.
2017-12-18 23:08:22 -05:00
Christopher L. Shannon (cshannon)
56baba96c6
AMQ-6875 - Use the correct destination for Virtual destination consumers
...
when using Virtual Topics
2017-12-14 16:01:10 -05:00
Christopher L. Shannon (cshannon)
5fa0bbd515
AMQ-6871 - By default only send generic platform details
...
The default behavior by the OpenWire client will be to send generic
platform details to the server with a new flag to send more specific
information.
2017-12-06 08:41:51 -05:00
Christopher L. Shannon (cshannon)
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
Christopher L. Shannon (cshannon)
2e3a7f6114
(AMQ-6858) - test fix
2017-11-15 09:21:44 -05:00
Christopher L. Shannon (cshannon)
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
Christopher L. Shannon (cshannon)
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
Christopher L. Shannon
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
Christopher L. Shannon (cshannon)
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
gtully
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
gtully
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
gtully
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
gtully
005403e94b
[no jira] more lenient for ci builds - intermittetnt failure
2017-10-27 11:37:04 +01:00
gtully
8e576be1d9
[AMQ-6849] - fix sendFailIfNoSpaceAfterTimeout policy entry default value
2017-10-26 11:36:03 +01:00
gtully
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
gtully
be6f4b69c1
[no jira] calm this test a bit due to oom in ci builds
2017-10-25 13:08:00 +01:00
gtully
578eacab45
[AMQ-6824] remove time dependency in test assertion
2017-09-28 11:36:11 +01:00
gtully
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
Timothy Bish
61d3231d36
AMQ-6809 Fix issue where stream message getBytes returned wrong value
...
StreamMessage implementation should return zero when the full value of a
written byte array has been consumed before then returning -1 on the
next read. Ands fix and additional testing of ActiveMQStreamMessage
2017-09-20 15:50:09 -04:00
Erik Wramner
c691124d32
AMQ-6808 preserve destination for browsed scheduled messages
2017-09-15 09:02:36 -04:00
gtully
a359d8152c
[AMQ-6277] take account of producer audit not being updatated on recovery check, avoid unnecessary partial journal replay
2017-09-15 13:48:03 +01:00
Dejan Bosanac
5e656d394c
https://issues.apache.org/jira/browse/AMQ-6799 - stop the jmx server connector properly
2017-09-01 13:02:53 +02:00
Christopher L. Shannon (cshannon)
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
Dejan Bosanac
c7291f1ecf
https://issues.apache.org/jira/browse/AMQ-6799 - IOExceptionHandler during the startup
2017-08-24 14:04:36 +02:00
gtully
068b7946ce
[AMQ-6643][AMQ-5594] fix test regression to reflect match strategy
2017-08-09 11:40:39 +01:00
gtully
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
gtully
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
gtully
206f77adac
[AMQ-6778] - fix test regression that needs to account for presence of correct advisory dests
2017-07-26 11:58:04 +01:00
gtully
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
gtully
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
Christopher L. Shannon (cshannon)
a9fe4e33c3
[maven-release-plugin] prepare for next development iteration
2017-06-27 13:41:28 -04:00
Christopher L. Shannon (cshannon)
5f0d6943cb
[maven-release-plugin] prepare release activemq-5.15.0
2017-06-27 13:41:01 -04:00
gtully
d70852eec8
[AMQ-6625] fix mock test expectation regression
2017-06-16 10:29:32 +01:00
gtully
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
gtully
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
gtully
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
Christopher L. Shannon (cshannon)
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
gtully
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
gtully
c50dc6ff00
[AMQ-6693] ignore the long term connection associated with the broker context, fix and test
2017-06-01 12:00:04 +01:00
gtully
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
gtully
8023b9ee44
[AMQ-6690] do nothing for move/copy jmx ops that try to modify self
2017-05-31 11:26:46 +01:00