Hello,
We had a case where the slave node of a replicating master/slave pair failed
over due to either network outage or congestion issues on the master resulting
in a split-brain situation. Is there a way to have the slave automatically fail
back when it regains the connection to the master?
Hello,
Is it possible to force a replicating slave of a two-node Artemis cluster to
start as live if it cannot connect to the live server in the cluster?
Configuring the broker as a master manually every time there is a case that
both brokers are shut down and the original master stays offline
dvise you against openWire+LargeMessage+replication...
probably move to core client if you really want to keep large messages.
On Wed, May 23, 2018 at 2:30 AM, Ilkka Virolainen <ilkka.virolai...@bitwise.fi>
wrote:
> The issue has now manifested itself twice. The first message logged by t
:733)
[artemis-journal-2.5.0.jar:2.5.0]
... 8 more
-Original Message-
From: Ilkka Virolainen <ilkka.virolai...@bitwise.fi>
Sent: 15. toukokuuta 2018 10:53
To: users@activemq.apache.org
Subject: Artemis 2.5.0 - Replication Failure During Compacting
Hello,
Hello,
I have a replicating master-slave -pair of Artemis 2.5.0. It seems to mainly
work as it should, but it started logging replication failures after having run
for a week. I have included my broker configuration in [1]. There are also
exceptions on the client side after the replication
,
- Ilkka
-Original Message-
From: Clebert Suconic <clebert.suco...@gmail.com>
Sent: 3. toukokuuta 2018 18:26
To: users@activemq.apache.org
Subject: Re: Artemis 2.5.0 - Colocated scaledown cluster issues
On Wed, May 2, 2018 at 3:01 AM, Ilkka Virolainen <ilkka.virolai...@bitwise.f
Hello,
As well as some previous issues [1] I have some problems with my Artemis
cluster. My setup [2] is a symmetric two node cluster of colocated instances
with scaledown. As well as the node restart causing a problematic state in
replication [1] there are other issues, namely:
1) After
a workaround for the
underlying issue.
- Ilkka
-Original Message-
From: Ilkka Virolainen <ilkka.virolai...@bitwise.fi>
Sent: 14. maaliskuuta 2018 11:08
To: users@activemq.apache.org
Subject: RE: Artemis 2.5.0 - Problems with colocated scaledown
Excluding tcp-connectors and leavin
-0a002711, backupAvailable=false]
...
Why is there an endless unsuccessful backup voting taking place with backupsize
-1 and null nodeid?
Best regards,
- Ilkka
-Original Message-
From: Ilkka Virolainen [mailto:ilkka.virolai...@bitwise.fi]
Sent: 13. maaliskuuta 2018 16:46
To: users
/IssueExample/src/main/resources/activemq
-Original Message-
From: Ilkka Virolainen [mailto:ilkka.virolai...@bitwise.fi]
Sent: 9. maaliskuuta 2018 14:21
To: users@activemq.apache.org
Subject: Artemis 2.5.0 - Problems with colocated scaledown
Hello,
I have some issues with scaledown of colocated
Hello,
I have some issues with scaledown of colocated servers. I have a symmetric
statically defined cluster of two colocated nodes configured with scale down.
The situation occurs thus:
1. Start both brokers. They form a connection and replicate.
2. Close server1
-> Server shuts down,
connection dying to a
concurrentmodificationexception so I remain optimistic.
Thank you!
Best regards,
- Ilkka
-Original Message-
From: Ilkka Virolainen [mailto:ilkka.virolai...@bitwise.fi]
Sent: 8. maaliskuuta 2018 10:29
To: users@activemq.apache.org
Subject: RE: Artemis 2.4.0 - Issues
Message-
From: Clebert Suconic [mailto:clebert.suco...@gmail.com]
Sent: 8. maaliskuuta 2018 2:08
To: users@activemq.apache.org
Subject: Re: Artemis 2.4.0 - Issues with memory leaks and JMS message
redistribution
Can you try master?
On Wed, Mar 7, 2018 at 2:11 AM, Ilkka Virolainen <ilkka.viro
this so I can make progress tomorrow.
Thanks.
On Tue, Mar 6, 2018 at 8:40 AM Ilkka Virolainen <ilkka.virolai...@bitwise.fi>
wrote:
> While the memory leak is now fixed in master (thanks Justin!),
> unfortunately more issues regarding the load balancing have occurred.
&g
This is just now in PR
https://github.com/apache/activemq-artemis/pull/1933
> On 6 Mar 2018, at 09:39, Ilkka Virolainen <ilkka.virolai...@bitwise.fi> wrote:
>
> Sounds good, thanks!
>
> Here's the JIRA: https://issues.apache.org/jira/browse/ARTEMIS-1731
>
> Best regards,
&
(ActiveMQThreadFactory.java:118)
[artemis-commons-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
-Original Message-
From: Ilkka Virolainen [mailto:ilkka.virolai...@bitwise.fi]
Sent: 1. maaliskuuta 2018 16:59
To: users@activemq.apache.org
Subject: RE: Artemis 2.4.0 - Issues with memory leaks and JMS
- Startup fails when XSD validation cannot access
Internet
We can pull in this schema into the build so it’s included.
Will try look at this today.
Can you raise a JIRA?
Sent from my iPhone
> On 6 Mar 2018, at 07:39, Ilkka Virolainen <ilkka.virolai...@bitwise.fi> wrote:
>
> He
Hello,
After a recent change allowing splitting up the broker configuration across
multiple files, starting Artemis fails when the server running broker has no
Internet access. xml:specialAttrs references in artemis-configuration.xsd fail
because the schema location
#L2747
Best regards,
- Ilkka
-Original Message-
From: Ilkka Virolainen [mailto:ilkka.virolai...@bitwise.fi]
Sent: 27. helmikuuta 2018 15:20
To: users@activemq.apache.org
Subject: RE: Artemis 2.4.0 - Issues with memory leaks and JMS message
redistribution
Hello,
- I don't have consumers
a reproducible test-case?
Justin
On Fri, Feb 23, 2018 at 4:38 AM, Ilkka Virolainen <
ilkka.virolai...@bitwise.fi> wrote:
> I'm still facing an issue with somewhat confusing behavior regarding
> message expiration in the DLQ, maybe related to the memory issues I've
> been having. My
?
-Original Message-
From: Ilkka Virolainen [mailto:ilkka.virolai...@bitwise.fi]
Sent: 22. helmikuuta 2018 13:38
To: users@activemq.apache.org
Subject: RE: Artemis 2.4.0 - Issues with memory leaks and JMS message
redistribution
To answer my own question in case anyone else is wondering about
memory leaks
persists I will try to provide a reproducible test case.
Thank you for your help, Justin.
Best regards,
- Ilkka
[1] https://issues.apache.org/jira/browse/ARTEMIS-1644
-Original Message-
From: Ilkka Virolainen [mailto:ilkka.virolai...@bitwise.fi]
Sent: 22. helmikuuta 2018
1] https://activemq.apache.org/artemis/docs/latest/clusters.html
On Wed, Feb 21, 2018 at 5:39 AM, Ilkka Virolainen <
ilkka.virolai...@bitwise.fi> wrote:
> Hello,
>
> I am using Artemis 2.4.0 to broker messages through JMS queues/topics
> between a set of clients. Some are
Hello,
I am using Artemis 2.4.0 to broker messages through JMS queues/topics between a
set of clients. Some are Apache NMS 1.7.2 ActiveMQ clients and others are using
Artemis JMS client 1.5.4 included in Spring Boot 1.5.3. Broker topology is a
symmetric cluster of two live nodes with static
24 matches
Mail list logo
