GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/2345
ARTEMIS-2108 Potential StackOverflowError when load balancing disabled
You can merge this pull request into a Git repository by running:
$ git pull
It was actually something i meant to send last month. Wasnt related to the PR
you mention.
Quite a few pr's from contributors included questions about release schedule.
And without a clear cadence policy its not possible to give this.
Also as a user having a clear cadence of a product makes it
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/2344
ARTEMIS-2107 clarify identity for authn failures in notification
You can merge this pull request into a Git repository by running:
$ git pull
I have tried to do bug releases every 6 weeks.. sometimes it takes
longer depending on what's broken.
The thing that probaby caused you to send this was our discussion on
the PR? I think we are due for a 2.7.0, hence I thought about moving
into 2.7.0 and not doing 2.6.x any longer. WE can still
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/2343
ARTEMIS-2106 log broker start failure
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-2106
I see users asking sometimes when would bug fix y or feature x be available.
I see alot of other apache projects have a clear feature and bug release
cadence policy, which helps users know and expect what timescales to expect
stuff.
Also it stops problems of features being held up behind some
Github user gemmellr commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2187#discussion_r222357714
--- Diff:
artemis-core-client/src/main/java/org/apache/activemq/artemis/api/core/client/SendAcknowledgementHandler.java
---
@@ -41,4 +41,13 @@
Github user jbertram commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2187#discussion_r222356400
--- Diff:
artemis-core-client/src/main/java/org/apache/activemq/artemis/api/core/client/SendAcknowledgementHandler.java
---
@@ -41,4 +41,13 @@
Github user clebertsuconic commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2187#discussion_r222350527
--- Diff:
artemis-core-client/src/main/resources/activemq-version.properties ---
@@ -20,4 +20,4 @@
Github user gtully closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2341
---
GitHub user gtully reopened a pull request:
https://github.com/apache/activemq-artemis/pull/2341
ARTEMIS-2103 - use the full openwire consumer queue for the mapped viâ¦
â¦rtual topic queue binding, fix and test
You can merge this pull request into a Git repository by running:
GitHub user gtully opened a pull request:
https://github.com/apache/activemq-artemis/pull/2341
ARTEMIS-2103 - use the full openwire consumer queue for the mapped viâ¦
â¦rtual topic queue binding, fix and test
You can merge this pull request into a Git repository by running:
Thanks for the quick response.
We have configured the broker to allow "ANONYMOUS" access yet but the
problem was that the client didn't set the SASL layer when connneting.
After adding this layer the simple client connects and sends information to
the broker.
The receiver has been modified in
13 matches
Mail list logo
