GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/720
SSL improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-656
Alternatively you can review
Github user bennetelli commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/718#discussion_r74622899
--- Diff:
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/vertx/ActiveMQVertxUnitTest.java
---
@@ -792,4
Github user bennetelli commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/718#discussion_r74622451
--- Diff:
integration/activemq-vertx-integration/src/main/java/org/apache/activemq/artemis/integration/vertx/ActiveMQVertxLogger.java
---
@@
Github user clebertsuconic commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/718#discussion_r74618261
--- Diff:
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/vertx/ActiveMQVertxUnitTest.java
---
@@
Github user clebertsuconic commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/718#discussion_r74617660
--- Diff:
integration/activemq-vertx-integration/src/main/java/org/apache/activemq/artemis/integration/vertx/ActiveMQVertxLogger.java
---
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/595
There's no way to determine here if the Rolledback was caused by a timed
out.. or something else (like an error or something).
I had been involved on tests where I was
I didn't really understand your original use-case, but what you're saying about
replication masters and slaves is true. A replicated slave will not start
without being able to contact its master since it doesn't know if it has
up-to-date data. This is noted in the documentation [1].
Justin
Okay found out something during my experiments.
When in master slave - replication mode, then we have to know which has the
latest data.
If both master and slave are down. Then configure the one with the latest
data as the master and the other one slave.
Then turn them back on and the
Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/701
@clebertsuconic I think probably the best solution is to fail multiple
clients with the same ID and find an alternate way to handle shared
subscriptions consistently across all protocols.
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/719
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/719
Fixing issues found through examples
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis log
11 matches
Mail list logo