GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/1553
1.5.next fixes towards 1.x
These are fixes that would make a nice 1.5.next release.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis 1.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1553.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1553
----
commit fd2891b3c682ab0402e452f26584bf0f54a795d4
Author: xstefank <[email protected]>
Date: 2017-02-08T15:41:37Z
ARTEMIS-950 Change log level from INFO to WARN for "Invalid "host" value
"0.0.0.0" detected for..." when Artemis is bound to 0.0.0.0
(cherry picked from commit 93ebbfdeaaa3f79c76d6028703c3c7b23bb3783e)
(cherry picked from commit d402f67f4e6c14072213c2a2936edb032cee751b)
commit b803030359a6e215927157c62505119a1476d86c
Author: Dmitrii Tikhomirov <[email protected]>
Date: 2017-05-24T13:18:16Z
ARTEMIS-1180 Artemis is logging warnings during server shut down
(cherry picked from commit 2443eaaa003ef913187c14dbc567544788224821)
commit 70f95129b01d775fc217dbe21f9892895178a823
Author: Andy Taylor <[email protected]>
Date: 2017-06-12T15:20:43Z
ARTEMIS-1224 - change the journal file size to nearest multiple
https://issues.apache.org/jira/browse/ARTEMIS-1224
(cherry picked from commit 30a6ac703efe3539d13152f9311bedd7fd68aa9d)
commit ef2e187312f5e851da2a44fb6e701eee31c1d6d8
Author: Howard Gao <[email protected]>
Date: 2017-06-26T08:19:09Z
ARTEMIS-1220 removing broken test
Testsuite won't compile
commit f5e34404d5a9c6e30318597d01d41d5f09d596a4
Author: Howard Gao <[email protected]>
Date: 2017-06-28T16:03:47Z
ARTEMIS-1221 Duplicated ID causes LargeMessage lost at backup
When a large message is replicated to backup, a pendingID is generated
when the large message is finished. This pendingID is generated by a
BatchingIDGenerator at backup.
It is possible that a pendingID generated at backup may be a duplicate
to an ID generated at live server.
This can cause a problem when a large message with a messageID that is
the same as another largemessage's pendingID is replicated and stored
in the backup's journal, and then a deleteRecord for the pendingID
is appended. If backup becomes live and loads the journal, it will
drop the large message add record because there is a deleteRecord of
the same ID (even though it is a pendingID of another message).
As a result the expecting client will never get this large message.
So in summary, the root cause is that the pendingIDs for large
messages are generated at backup while backup is not alive.
The solution to this is that instead of the backup generating
the pendingID, we make them all be generated in advance
at live server and let them replicated to backup whereever needed.
The ID generater at backup only works when backup becomes live
(when it is properly initialized from journal).
(cherry picked from commit d50f577cd50df37634f592db65200861fe3e13d3)
commit 183f5ffc7b2e6903624f82f39c838746f3954ad7
Author: Martyn Taylor <[email protected]>
Date: 2017-06-30T10:30:04Z
NO-JIRA Remove artemis-feature dep from integration tests
commit ab72645db4fb81c148adbabee40f0955c349687c
Author: Clebert Suconic <[email protected]>
Date: 2017-07-25T21:46:22Z
ARTEMIS-1305 Fix checkstyle and traces
https://issues.jboss.org/browse/JBEAP-9235
commit 0e690dd77b233a4364e407aa61d7b5905e28e098
Author: Martyn Taylor <[email protected]>
Date: 2017-07-26T14:35:15Z
NO JIRA Remove failing tests due to cherrypick
commit 05d8d29d7b6b55554335ee072e1697ed3a59e58e
Author: Clebert Suconic <[email protected]>
Date: 2017-08-18T19:01:33Z
ARTEMIS-1353 Initial replication of large messages out of executor
This is based on the work @jbertram made at the github pr #1466 and the
discussions we had there
(cherry picked from commit ce6942a9aa9375efaa449424fe89de2db3f22e36)
commit 3f152c0e9b49e2c660b932857c8c3b030a14c739
Author: Erich Duda <[email protected]>
Date: 2017-08-22T19:48:19Z
ARTEMIS-1368 Artemis gets to state when it doesn't respond to producer
There is a leak on replication tokens in the moment when a backup is
shutdowned or killed and the ReplicationManager is stopped. If there
are some tasks (holding replication tokens) in the executor, these
tokens are simply ignored and replicationDone method isn't called on
them. Because of this, some tasks in OperationContextImpl cannot be
finished.
(cherry picked from commit 88a018e17fd49097de1186c65e25cd0af578b6a9)
(cherry picked from commit d6cbc0aa885fa88beb7f1b2450cdfe4da9466947)
commit 09f2e3b1930b86f9b889547d8ab575850b98afea
Author: psakar <[email protected]>
Date: 2017-08-24T10:38:05Z
add licenses tag to pom.xml
commit bd978454c393d2d79c0fffd2ec84121146e41f92
Author: Martyn Taylor <[email protected]>
Date: 2017-09-08T14:00:35Z
ARTEMIS-1418 AIO Shutdown on IOError and logging
(cherry picked from commit 520a40b1a1431fb0fdc1666c556342410a56e4eb)
commit c41e81bf975e440e5464b2b603620b408fdd6456
Author: Justin Bertram <[email protected]>
Date: 2017-09-12T16:17:08Z
ARTEMIS-1417 Failback not working on NFSv4
With NFSv4 it is now necessary to lock/unlock the byte of the server
lock file where the state information is written so that the
information is then flushed to the other clients looking at the file.
(cherry picked from commit 2ec173bc708daca163c9356cf12440432abc61c4)
commit 8f934a76c66a5e4123542817d87e63988c91778a
Author: Paul Ferraro <[email protected]>
Date: 2017-08-23T23:51:30Z
NO-JIRA: Allow subclasses to more easily override BroadcastEndpointFactory
used during connection factory creation.
(cherry picked from commit 4bf204c01225e058a5b723e301e53a79f3128f3a)
----
---
