There is no programmatic way to add a cluster-connection. The
cluster-connection is such a fundamental piece of the broker's
configuration it really has to be there when the broker starts. Also,
there is no mechanism to persist a cluster-connection configuration other
than in the XML (unlike
This definitely belongs to Dev.
I want to get more involved with Kubernetes. I am setting time apart
into this for upcoming weeks. Right now I don't have much information
to help you.. but please keep us informed of your discoveries :)
On Thu, Jun 7, 2018 at 2:53 AM, Victor wrote:
> Hi all,
>
>
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/2127
I will put it on 2.6.2
---
Github user gaohoward commented on the issue:
https://github.com/apache/activemq-artemis/pull/2122
@mtaylor I've created another jira (ARTEMIS-1916) and the PR
https://github.com/apache/activemq-artemis/pull/2128
I also updated this PR. This PR should be merged after
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/2128
You have 2 PRs open for JMX why not use a single one?
---
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2127
---
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2123
---
Github user gaohoward commented on the issue:
https://github.com/apache/activemq-artemis/pull/2128
@clebertsuconic I split it because Martyn suggested that this doesn't
belong to a test PR. (see Martyn's comment)
---
As Justin says there is currently no way to add a cluster connection
dynamically. However, I also have a use case where it would be nice to be
able to dynamically add or destroy a cluster connection. I will probably
take a look when I get some time to see if there's a way that the behavior
can
GitHub user gaohoward opened a pull request:
https://github.com/apache/activemq-artemis/pull/2128
ARTEMIS-1916 Remove Jmx ArtemisRMIServerSocketFactory
The ArtemisRMIServerSocketFactory doesn't do anything special,
instead the existence of this impl class causes jmx client
+1
On Wed, Jun 6, 2018 at 4:22 PM, Francesco Nigro wrote:
> +1
>
> *built and run some tests
>
> Il giorno mer 6 giu 2018 alle ore 16:45 Timothy Bish
> ha scritto:
>
> > On 06/04/2018 08:35 PM, Clebert Suconic wrote:
> > > I would like to propose an Apache ActiveMQ Artemis 2.6.1 release. This
Thanks guys,
I will definitely try the JGroups configuration with KUBE_PING.
I'll keep an eye on the list for possible clustering updates and in the
meantime, I will try to do my best with the helm chart and JGroups.
In the big scheme of things, what I'm trying to do is to have a Docker
image
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/2129
ARTEMIS-1917 support logging HTTP access
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1917
Hi all,
I'm having some fun trying to figure out the ideal way to deploy an
ActiveMQ Artemis cluster in Kubernetes.
I started by creating a Helm Chart (think of it as a deb/rpm package for
Kubernetes) where I can just install a Symmetric cluster of 8 nodes with
the following commands:
helm
Github user gaohoward commented on the issue:
https://github.com/apache/activemq-artemis/pull/2122
@mtaylor ok, will do another jira. The code change is to remove the
RMIServerSocketFactory because it does nothing special and it causes jmx client
fail to connect (don't know why,
15 matches
Mail list logo
