b9fd189d56
https://issues.apache.org/jira/browse/AMQ-5253
...
Add accessors with the correctly spelled name and deprecate the old
ones.
2014-07-21 16:08:59 -04:00
4d4766e3a3
Fix small typo in the docs
...
This closes #35
2014-07-16 10:35:23 -04:00
3b5d89a78b
https://issues.apache.org/jira/browse/AMQ-5277 - jdbc store make use of entryLocator on ack
2014-07-14 17:02:19 +01:00
a9b8d98ed7
https://issues.apache.org/jira/browse/AMQ-5086 - init of broker got dropped after mutex wait - testWaitFor was failing
2014-07-14 17:02:18 +01:00
433912f79a
https://issues.apache.org/jira/browse/AMQ-5271
...
Add an in-memory variant of the disk based JobScheduler store to allow
for an embedded broker to have scheduler support without needing to use
the disk based version.
2014-07-10 12:16:34 -04:00
0709c2cc1d
https://issues.apache.org/jira/browse/AMQ-5213 - fix failing jmock test - resolve inconsistency in camel case attribute naming in a few mbeans
2014-07-10 13:51:08 +01:00
bf1c57b33d
AMQ-5265 - fix race condition for task
2014-07-09 16:43:30 +02:00
ccf4b9f34f
https://issues.apache.org/jira/browse/AMQ-5262
...
close connections when the connector is stopped.
2014-07-08 16:20:21 -04:00
74846bb2b4
https://issues.apache.org/jira/browse/AMQ-3758
...
Refactor the scheduler store into a more KahaDB style store that can
recover from various problems like missing journal files or corruption
as well as rebuild its index when needed. Move the scheduler store into
a more configurable style that allows for users to plug in their own
implementations. Store update from legacy versions is automatic.
2014-07-07 12:28:11 -04:00
6521549ec8
AMQ-5086. Fix the timeout arithmetic
2014-07-03 14:53:30 -04:00
106f759571
https://issues.apache.org/jira/browse/AMQ-5251
...
Synchronize method and remove old deprecated schedule method.
2014-06-28 10:21:34 -04:00
cfce36197e
https://issues.apache.org/jira/browse/AMQ-5086
...
Avoid a possible uneeded wait.
2014-06-09 16:21:00 -04:00
5016c4d4f2
https://issues.apache.org/jira/browse/AMQ-5086
...
Ensure that wait for started on vm transport factory actually waits for
start, currently it doesn't really check started or wait porperly.
2014-06-09 15:40:03 -04:00
27b3a7c344
https://issues.apache.org/jira/browse/AMQ-5212 - ensure uncontented access to concurrent destination map avoides deadlock, rerework https://issues.apache.org/jira/browse/AMQ-4952 to differenciate duplicates from send and recovered messages from the store. https://issues.apache.org/jira/browse/AMQ-3454 benefits from getDestinationMap(destination) to get direct access to the map to determine existance. Additional test
2014-06-09 12:32:33 +01:00
785faa06be
disable autofail system.exit - it kills a surefire forked test run
2014-06-09 12:32:32 +01:00
845e62af76
https://issues.apache.org/jira/browse/AMQ-5218 - DestinationsPlugin
2014-06-09 12:48:02 +02:00
707940f1a6
https://issues.apache.org/jira/browse/AMQ-5214
...
Check for security error on responses and log a warning so there is a
record of the event
2014-06-05 16:16:01 -04:00
25f1fe8460
https://issues.apache.org/jira/browse/AMQ-5213
...
Adds a Log4JConfigViewMBean for use in configuring runtime logger
levels.
2014-06-05 14:39:56 -04:00
fa086396a7
[maven-release-plugin] prepare for next development iteration
2014-06-05 11:59:29 +02:00
58dd93e42e
[maven-release-plugin] prepare release activemq-5.10.0
2014-06-05 11:59:17 +02:00
6c703ac6ee
https://issues.apache.org/jira/browse/AMQ-5209
...
Add MessageId and original destination info to the advisory message
properties.
2014-06-04 13:30:42 -04:00
c2cf78542f
[maven-release-plugin] prepare for next development iteration
2014-06-04 11:33:17 +02:00
5bc741f227
[maven-release-plugin] prepare release activemq-5.10.0
2014-06-04 11:33:03 +02:00
1591960887
fixing licenses
2014-06-03 14:03:28 +02:00
14fcd7cbea
https://issues.apache.org/jira/browse/AMQ-5160 - make runtime configuration plugin work properly with destination filters
2014-06-03 13:26:43 +02:00
aa2dfb60aa
https://issues.apache.org/jira/browse/AMQ-5160 - fix XBeanConfigTest test
2014-06-02 17:50:28 +02:00
3ba129561c
https://issues.apache.org/jira/browse/AMQ-5160 - start/stop wrapped policy
2014-06-02 13:22:25 +02:00
9d656731ab
https://issues.apache.org/jira/browse/AMQ-4555 - fix regression that groupClass cannot be set on <cachedLDAPAuthorizationMap/>
2014-05-26 16:42:38 +02:00
6c859676b3
Fixed AMQ-5160, fixed durable subscription retroactive recovery
2014-05-26 11:07:19 +02:00
42ad1039cb
Fixed AMQ-5160, restored previous DurableSubscription behaviour of only recovering messages when cursor is empty, retained messages are always recovered
2014-05-26 11:07:19 +02:00
c915b19a20
Fixed AMQ-5160, removed producer's retain property from retained messages
2014-05-26 11:07:19 +02:00
78950ec596
Fixed AMQ-5160, changed DurableTopicSubscription to only recover retroactive messages for retroactive topics or consumers
2014-05-26 11:07:19 +02:00
8947a09eaa
Fixed AMQ-5160, force durable subscriptions to always recover retroactive messages
2014-05-26 11:07:19 +02:00
5576dc5d74
Fixed AMQ-5160, fixed browse() to include messages from wrapped policy
2014-05-26 11:07:18 +02:00
a581d010aa
Fixed AMQ-5160, Added RegionBroker.getConnectionContext(), made Topic.recoverRetroactiveMessages() public to force message recovery from MQTTProtocolConverter for duplicate subscriptions, added new tests for retained messages and JMX interoperability
2014-05-26 11:07:18 +02:00
bcb60a482c
Partial fix for AMQ-5160, attempts to resolve retained messages using subscription recovery policy, but fails to resend retained messages for duplicate subscriptions
2014-05-26 11:07:18 +02:00
541ed8cf0c
https://issues.apache.org/jira/browse/AMQ-5140
...
Add some checks to prevent any chance of an ArithmaticException because
of divide by zero.
2014-05-05 16:12:50 -04:00
94b404d0ab
Fixed AMQ-5160, allowed wildcard subscriptions for future destinations, added tests for wildcard authorization, fixed consumer and producer AdvisoryTopic names for composite destinations by replacing ',' with '‚'
2014-05-05 10:06:06 +02:00
a38a7c0093
Initial fix for AMQ-5160 to support subscription authorization for destination filters
2014-05-05 10:06:06 +02:00
c5c1495330
https://issues.apache.org/jira/browse/AMQ-5136 - fix and test (thanks barlabanov)
2014-04-30 17:08:20 +01:00
ad1f751a41
https://issues.apache.org/jira/browse/AMQ-5077 - reduce reader thread work when client uses async send; async store updates can now queue up to the destination memory limit b/c they don't block the send thread. Pending store writes are now tracked in memory usage. This allows a client to quickly provide a burst of messages to fill the destination cache bounded only by network bandwidth
2014-04-30 16:13:18 +01:00
4eb5097f22
https://issues.apache.org/jira/browse/AMQ-5165 - fix for destination stats name
2014-04-30 10:44:47 +02:00
3f32507f78
Use autocrlf consistently for line endings
2014-04-29 14:18:37 -04:00
ec35588e56
https://issues.apache.org/jira/browse/AMQ-4182 - remove remaining use of finalize()
2014-04-24 16:06:01 +02:00
08bb172f3c
https://issues.apache.org/jira/browse/AMQ-5077 - provide concurrentSend option to composite destinations such that fanout can occur in parallel, resulting in write batching. little perf test that shows a large improvement in send rate w/o concurrentStoreAndDispatch
2014-04-23 15:02:24 +01:00
e947927511
https://issues.apache.org/jira/browse/AMQ-5149 - potential deadlock
2014-04-16 15:44:02 +02:00
7646526c0a
https://issues.apache.org/jira/browse/AMQ-5141 - send messages to dlq using broker security context
2014-04-14 17:05:53 +02:00
307005ab4f
https://issues.apache.org/jira/browse/AMQ-5138
2014-04-07 10:58:08 -04:00
a554c7ca84
https://issues.apache.org/jira/browse/AMQ-5052
...
tone down noisy log
2014-03-31 18:42:37 -04:00
bc326c8e57
https://issues.apache.org/jira/browse/AMQ-5122
...
tone down logging of warn to just exception message, full exception
logged as debug.
2014-03-31 18:34:58 -04:00
Timothy Bish
gtully
Jeff Genender
Hadrian Zbarcea
Dejan Bosanac
Dhiraj Bokde
Timothy Bish
Dhiraj Bokde