Hi Tim,
Please find below the observations.
1. Kill host1 so host2 becomes the master and there is no slave. Connect a
consumer with a URI of tcp://host1:61616. Does it connect? What's in the
consumer's logs?
ActiveMQConnectionFactory connectionFactory = new
ActiveMQConnectionFactory("tcp://pot
Hi Tim,
I was not originally using the options like timeout, etc.
I only used them yesterday.
I will test and let you know.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Active-MQ-Master-Slave-Config-Not-working-tp4728550p4728861.html
Sent from the ActiveMQ - User mail
I understand that this is only a problem when using the failover transport,
and clearly TCP connections to the master are working (otherwise you'd get
no connectivity at all no matter which host was the master).
What I'm trying to do is determine whether the problem (failure to detect
that the mas
Yip. Working on it now.
On Mon, Jul 24, 2017 at 4:07 AM martk <123mar...@web.de> wrote:
> Thanks Clebert. I have tested it with the current master (commit
> f138bc5284c15a3ddc459246d730a2ff316b3e88) and my scenario is working
> (check-for-live-server>true and allow-failback>false).
>
> The versi
Hi Tim,
If I use the regular TCP URL, I am able to connect to the Active server
anytime it is acting as Master.
The issue is happening only if I use the failover URL.
If I use the logic like try {connect to master} catch {connect to slave}, it
is working fine.
--
View this message in context:
Keep in mind too that Artemis started from the HornetQ codebase, and so
many portions of the broker code are more mature than the Artemis release
dates would imply. That's not to say that there haven't been changes, and
bugs, since, but the code wasn't written from the ground up when Artemis
develo
It should like the underlying problem is that the slave broker isn't
rejecting incoming connections (which would be a bug, so thanks for
submitting the JIRA bug), but otherwise it sounds like both failover itself
and shared filesystem KahaDB are working.
Can you please confirm that by making sure
https://issues.apache.org/jira/browse/AMQ-6777
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Active-MQ-Master-Slave-Config-Not-working-tp4728550p4728796.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Please find log below :
Jul 24, 2017 4:45:24 PM
activemqjmsclients.FTTest.ActiveMQJMSClients_Producer run
INFO: Connected - Producer - 3
Jul 24, 2017 4:45:25 PM
activemqjmsclients.FTTest.ActiveMQJMSClients_Producer run
INFO: Connected to :
failover:(tcp://potaplq1lb:61616,tcp:/potaplq1la:6
Hi Tim,
Yes, I am able to see the logs as it should.
And also, the admin UI, I am able to see the queues and details only in the
primary server admin UI. Other one says "Error! Exception occurred while
processing this request, check the log for more information!".
Even when both are up (master an
Thanks Clebert. I have tested it with the current master (commit
f138bc5284c15a3ddc459246d730a2ff316b3e88) and my scenario is working
(check-for-live-server>true and allow-failback>false).
The version of the artemis master pom.xml is 2.2.0-SNAPSHOT. So this would
be in the 2.2.0 release?
--
Vie
Let me know if anyone has any suggestions.
Regards
Neelam
--
View this message in context:
http://activemq.2283324.n4.nabble.com/After-upgrading-activemq-to-5-14-5-to-5-6-0-SSL-communication-to-external-server-is-broken-tp4728762p4728788.html
Sent from the ActiveMQ - User mailing list archive
Currently there is no time line for Apache ActiveMQ Artemis to turn into 6.x
afaik. Nor still any confirmation it will be renamed to that. It may just live
in as it has been for the last few years.
Apache ActiveMQ Artemis, It is used in production environments already (we are
adopting it in my
I have a project integrated with ActiveMQ5.9 client that interacts with
ActiveMQ5.9 broker. As the increasement of data flow(over one thousand per
second), ActiveMQ5.9 broker is not confident as previous(there are some
"inactive channel" and "connection reset" exception in activemq.log).
In
14 matches
Mail list logo
