98165c4b69
https://issues.apache.org/jira/browse/AMQ-6228
...
Create a better error message that for the invalid frame size error.
2016-03-31 16:52:34 -04:00
9a866cf567
https://issues.apache.org/jira/browse/AMQ-5486
...
Default to caller runs policy on task rejection.
2016-03-28 13:55:09 -04:00
e0c5499964
https://issues.apache.org/jira/browse/AMQ-6221
...
Synchronizing ActiveMQText message on state changes for the content and
text fields so that they are always changed together. This will prevent
race conditions where data can be lost when using concurrent store and
dispatch.
2016-03-22 15:51:31 +00:00
ea09159a40
https://issues.apache.org/jira/browse/AMQ-6218
...
Fixing copy method of ActiveMQTextMessage to prevent a race condition
when concurrent store and dispatch is used with Queues
We may need explicity synchronization between the text and content fields
in the future if other issues pop up
2016-03-21 19:38:18 +00:00
e2b4ca2c59
https://issues.apache.org/jira/browse/AMQ-6108
...
Update the threads created by the SelectorManager to be daemon threads.
2016-03-15 14:03:12 -04:00
946e62d702
https://issues.apache.org/jira/browse/AMQ-6203
...
Rewrite older acks that can be preventing GC of log files.
2016-03-14 11:04:57 -04:00
078f39f589
https://issues.apache.org/jira/browse/AMQ-6199 - apply CursorMemoryHighWaterMark to topic subscriptions
2016-03-08 16:45:06 +00:00
ca5912d9fa
https://issues.apache.org/jira/browse/AMQ-6184 - improve nio transport scalability; get back core pool size
2016-02-25 13:43:21 +01:00
934a30a327
https://issues.apache.org/jira/browse/AMQ-6184 - improve nio transport scalability
2016-02-25 12:07:51 +01:00
0f445a535f
https://issues.apache.org/jira/browse/AMQ-6177
...
Fixing CronParserTest so that it checks 24 hour format properly when
using a timezone shifted by 30 minutes
Thanks to Jamie Goodyear for the patch
2016-02-22 12:50:07 +00:00
90726a60af
https://issues.apache.org/jira/browse/AMQ-6153
...
Only setting the socketBufferSize in TcpTransport if the value is
greater than 0 as other values are illegal.
2016-02-08 16:13:01 +00:00
5f7a81f928
https://issues.apache.org/jira/browse/AMQ-6142
...
Fixing a race condition that exists in the decompress method of
ActiveMQBytesMessage that can cause an invalid length to be read.
2016-02-01 17:27:19 +00:00
acbe31fcb5
https://issues.apache.org/jira/browse/AMQ-6137 - deal with 'special' escape chars in like selector expression
2016-01-22 15:30:16 +00:00
4ecff14030
NO-JIRA Update master version to 5.14.0-SNAPSHOT to match the eventual
...
release version.
2016-01-20 12:40:20 -05:00
a3fa0da6ec
https://issues.apache.org/jira/browse/AMQ-6130 - java beans @Transient annotation
2016-01-18 09:38:09 +01:00
4ea435bf46
https://issues.apache.org/jira/browse/AMQ-5336
...
URI comparison needs to be done using the host / port comparison method
instead of string equality due to other features like nested options
which can alter the URIs and lead to continued attempts to reconnect to
the transport that's already connected when priority backup is used.
2016-01-15 18:07:56 -05:00
5adbafef3b
https://issues.apache.org/jira/browse/AMQ-6108
...
Ensure that executor threads are created as daemon threads, fix a
try/finaly block, clean up some warnings.
2016-01-14 16:47:23 -05:00
ebcc1b4eae
https://issues.apache.org/jira/browse/AMQ-6126
...
Add more configuration options to TaskRunnerFactory
2016-01-14 10:41:56 -05:00
9287055338
https://issues.apache.org/jira/browse/AMQ-6125
...
Ensure that the redelivery policy is never null in the consumer.
2016-01-13 18:08:18 -05:00
db1506a592
https://issues.apache.org/jira/browse/AMQ-6124 - fix and test - propagate broker info from prestarted backup transport
2016-01-12 14:00:13 +00:00
16bc0f0d75
https://issues.apache.org/jira/browse/AMQ-6089 - support TMNOFLAGS as a scan end to allow looping calls to recover to terminate
2016-01-06 12:54:20 +00:00
8e2176d93c
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.
2015-12-28 16:41:14 +00:00
b9dcb010f7
https://issues.apache.org/jira/browse/AMQ-6077
...
Making new values in ActiveMQObjectMessage transient which fixes HTTP
serialization
2015-12-15 19:37:05 +00:00
eeec0c07b0
https://issues.apache.org/jira/browse/AMQ-6077 - define default values (based on system property) for connection factory and object message
2015-12-15 13:34:02 +01:00
94446e53dc
https://issues.apache.org/jira/browse/AMQ-6077 - define object message trusted packages on connection factory
2015-12-14 13:50:42 +01:00
c78eddce7e
revert sync ack send for https://issues.apache.org/jira/browse/AMQ-3519 due to rework in https://issues.apache.org/jira/browse/AMQ-5068 - sync send no longer needed because redelivered flag is persisted before dispatch. This avoids a roundtrip overhead on individual ack, ie priority or nonBlockingRedelivery options in the mix
2015-12-11 17:05:49 +00:00
9c4ef26d5c
with failover the reported exception may be wrapped by the failover listener
2015-12-09 12:30:29 +00:00
cfb4ca9f54
[maven-release-plugin] prepare for next development iteration
2015-11-30 13:48:58 +00:00
abfe038ddf
[maven-release-plugin] prepare release activemq-5.13.0
2015-11-30 13:48:11 +00:00
0a12bcb928
https://issues.apache.org/jira/browse/AMQ-2191 https://issues.apache.org/jira/browse/AMQ-3529 - rework fixes to remove uncertanty from dealing with intettuptedexception. Sync requests will trap interrupts that ocurr while waiting for responses and fail the connection with an interruptedioexception. Interrupts pending before requests will be suppressed, allowing possible clean shutdown. It is not safe to replay openwire ops b/c they are not idempotent, the only safe option is to have a teardown of the broker side state from a close
2015-11-27 12:21:56 +00:00
4a27b72377
https://issues.apache.org/jira/browse/AMQ-6042
...
Apply fix and test from Martin Lichtin to preserve the rollback cause in
all ack modes.
2015-11-20 16:18:27 -05:00
934f3cea7e
release the connection even if broker communication fails
2015-11-19 07:48:56 -08:00
15412bae64
AMQ4221Test - remove system exit as it breaks surefire fork, https://issues.apache.org/jira/browse/AMQ-6004 interrupt causes errors on shutdown. Two are sorted but the check for errors in the logs may still cause intermittent failures
2015-11-18 16:08:29 +00:00
d7a3b9406b
https://issues.apache.org/jira/browse/AMQ-6029 - make certs available to tunnle servlet - HttpsNeedClientAuthSendAndReceiveTest regression, add javax.security so login exceptions can propogate over http - https://issues.apache.org/jira/browse/AMQ-6013
2015-11-18 16:08:29 +00:00
cc81680e10
https://issues.apache.org/jira/browse/AMQ-6027
...
Adding support for consumers on virtual destinations to create network
demand. This behavior is turned off by default but can be enabled.
For example, if a consumer comes online for a queue that is part of a
VirtualTopic, this will cause a network of brokers to forward messages
because a demand subscription will be created. Same for if a consumer
comes online for a forwarded destination from a composite
destination.
There is also an option to enable flow based on the existence of a
virtual destination if the virtual destination is forwarding to a
Queue.
Full configuration instructions for this feature will be on the wiki page.
2015-11-09 20:07:43 +00:00
8136e67b40
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
2015-10-30 12:01:08 +00:00
9ddd162d25
https://issues.apache.org/jira/browse/AMQ-4361 - implement suggestion from Sam hendley with thanks, avoid the IllegalMonitorStateException
2015-10-22 15:49:44 +01:00
6f524bfea0
https://issues.apache.org/jira/browse/AMQ-6017 - respect ioBufferSize for nio transport
2015-10-22 11:41:17 +02:00
5d697cff3b
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
2015-10-21 14:02:56 +01:00
e100638244
https://issues.apache.org/jira/browse/AMQ-6013 - init serializable packages statically
2015-10-20 12:30:57 +02:00
a7e2a44fe8
https://issues.apache.org/jira/browse/AMQ-6013 - restrict classes which can be serialized inside the broker
2015-10-16 15:44:23 +02:00
4adc8e4f4e
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
2015-10-08 12:11:16 +00:00
9a78bc689f
https://issues.apache.org/jira/browse/AMQ-5961
...
Prevent deadlock by moving calls to afterCommit
and afterRollback out of synchronized blocks.
https://issues.apache.org/jira/browse/AMQ-5961
Lock list but keep global hashmap out for deadlock protection.
https://issues.apache.org/jira/browse/AMQ-5961
Lock safely in isInXATransaction.
https://issues.apache.org/jira/browse/AMQ-5961
Don't synchronize on list as we have an exclusive reference.
2015-10-01 13:31:00 +00:00
fc25535748
https://issues.apache.org/jira/browse/AMQ-5854 - fix intermittent test failure
2015-09-30 11:41:08 +01:00
8514e38135
https://issues.apache.org/jira/browse/AMQ-5951 - scenario wheere transaction command can block, additional test and further fix
2015-09-30 11:41:08 +01:00
8d982479e9
https://issues.apache.org/jira/browse/AMQ-5854 - fix and test. Ensure transaction rollback if there are pending acks during a failover reconnect. Reliably tracking pending acks to eusure possible redelivery is too complex in the context of acks getting dropped by failover or ignored by the subscription, in addition to being sent async. Couple that with multiple consumers on the same connection and the locking of message delivery; only safe course is to ensure rollback outcome.
2015-09-28 14:29:57 +01:00
ee4672baaf
https://issues.apache.org/jira/browse/AMQ-5972 - wildcard policy entries not applied in correct order
2015-09-17 11:08:21 +02:00
ae9af4b8b2
https://issues.apache.org/jira/browse/AMQ-5951 - ensure failover oneway won't retry if reconnect will not happen
2015-08-31 15:55:44 +01:00
e14aca871c
https://issues.apache.org/jira/browse/AMQ-5889
...
-Cleaned up missing license headers and refactored packages.
-Added configuration options for a protocol detection timeout and
for the max number of connections accepted at the same time.
-Fixed a regression with connection counts
-Also added some more tests
2015-08-13 14:41:29 +00:00
e5a94bfee2
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
2015-08-12 16:07:34 +01:00
Timothy Bish
Christopher L. Shannon (cshannon)
gtully
Dejan Bosanac
Romain Manni-Bucau
erik-wramner