Hi Tim,
Thanks for your reply, yes we have configured one job previously to kill
one pod when two are up. it's working now.
My deployment file is available here if anyone is interested.
https://github.com/imranrazakhan/K8S-HA-ActiveMQ/blob/main/activemq.yaml
Regards,
I assume there aren't any failures earlier in broker1's logs that might be
relevant?
>From those logs, it looks like Kubernetes is shutting down ActiveMQ rather
than ActiveMQ shutting itself down, based largely on the fact that there is
nothing that indicates that ActiveMQ initiated the shutdown.
I have deployed two statefulset replicas of ActiveMQ 5.15.13 as Network
Broker, but second POD activemq-1 is restarting after every 4m51s (I
removed readiness and liveness probes too), I enabled debug logs but could
not find any clue
**ActiveMQ-0:**
http://activemq.apache.org/schema/core";
ed that to
"master" "slave" for convenience,
Full jolokia REST docs here:
https://jolokia.org/reference/html/protocol.html
-Original Message-
From: Rallavagu [mailto:rallav...@gmail.com]
Sent: Wednesday, December 02, 2015 3:38 PM
To: users@activemq.apache.org
Su
jolokia REST docs here:
https://jolokia.org/reference/html/protocol.html
-Original Message-
From: Rallavagu [mailto:rallav...@gmail.com]
Sent: Wednesday, December 02, 2015 3:38 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EXTERNAL ]
Raffi,
BTW, I am unable to get any res
ope that helps
Raffi
-Original Message-
From: Rallavagu [mailto:rallav...@gmail.com]
Sent: Wednesday, December 02, 2015 1:34 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EXTERNAL ]
Raffi, Thanks for the pointer.
Completed a bit of reading and understanding the "upd
1:34 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EXTERNAL ]
Raffi, Thanks for the pointer.
Completed a bit of reading and understanding the "updateClusterClients"
option also read the blog
http://bsnyderblog.blogspot.com/2010/10/new-features-in-activemq-54-au
hosts; the advantage of using LB/wide-IP is avoiding all this complexity at the
client level.
Hope that helps
Raffi
-Original Message-
From: Rallavagu [mailto:rallav...@gmail.com]
Sent: Wednesday, December 02, 2015 1:34 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EXTERNA
ence here
http://activemq.apache.org/failover-transport-reference.html
Hope that helps
Raffi
-Original Message-
From: Rallavagu [mailto:rallav...@gmail.com]
Sent: Tuesday, December 01, 2015 7:33 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EXTERNAL ]
Raffi,
ailto:rallav...@gmail.com]
Sent: Tuesday, December 01, 2015 7:33 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EXTERNAL ]
Raffi, Thanks. This is interesting.
What do you mean by "If connection fails, assuming transport connector is configured to update
client with clu
only, not stomp, ws, amqp:
Full reference here
http://activemq.apache.org/failover-transport-reference.html
Hope that helps
Raffi
-Original Message-
From: Rallavagu [mailto:rallav...@gmail.com]
Sent: Tuesday, December 01, 2015 7:33 PM
To: users@activemq.apache.org
Subject
m: James A. Robinson [mailto:j...@highwire.org]
Sent: Tuesday, December 01, 2015 7:32 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EXTERNAL ]
So when I was building my system I had wanted to use M/S, but the documentation
had indicated the old M/S was deprecated in favor of the n
nt config, but leverage ActiveMQ cluster aware clients library to
manage connection failovers.
Hope that helps,
Raffi
-Original Message-
From: Rallavagu [mailto:rallav...@gmail.com]
Sent: Tuesday, December 01, 2015 2:57 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deplo
gt; Hope that helps,
>
> Raffi
>
>
> -Original Message-----
> From: Rallavagu [mailto:rallav...@gmail.com]
> Sent: Tuesday, December 01, 2015 2:57 PM
> To: users@activemq.apache.org
> Subject: Re: ActiveMQ deployment [ EXTERNAL ]
>
> Now, I am getting a clearer pict
t config, but leverage ActiveMQ cluster aware clients library to
manage connection failovers.
Hope that helps,
Raffi
-Original Message-
From: Rallavagu [mailto:rallav...@gmail.com]
Sent: Tuesday, December 01, 2015 2:57 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EX
using standalone brokers, just use
failover:() protocol from client.
Master/Slave is true failover.
-Original Message-
From: Rallavagu [mailto:rallav...@gmail.com]
Sent: Tuesday, December 01, 2015 1:06 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EXTERNAL ]
Thanks
: Tuesday, December 01, 2015 1:06 PM
To: users@activemq.apache.org
Subject: Re: ActiveMQ deployment [ EXTERNAL ]
Thanks again Johan. As the failover is configured at the client end how would
the configuration for combined deployment look like?
I was thinking on the lines of NOB because the messages are
Thanks again Johan. As the failover is configured at the client end how
would the configuration for combined deployment look like?
I was thinking on the lines of NOB because the messages are forwarded to
other broker(s) thus achieving failover capabilities in case the
original broker is failed
You want to combine them, the NOB is for communication but JMS is still store
and forward, i.e if a machine dies, you can have multiple paths, what was in
the persistence store of said machine is still “dead” until the machine is
revived, that’s where the Master / Slave(s) come in. They’ll jump
Thanks Johan.
My goal is to achieve high availability (with failover) for producer and
consumer in addition to mitigate a situation of "there is a chance that
one broker has producers but no consumers".
As per the documentation, it sounds like NOB is an option which can
offer failover and sc
What you probably want is a combination of HA and communication.
HA I.e master and slave(s) (Depending on storage) gives you uptime.
NOB gives you communication paths and as such scalability and for some value of
it versatility.
You can also use the two above and combine that with bridges to bui
After spending some time reading, with reference to the following link,
http://activemq.apache.org/clustering.html
What I am trying to figure out is if it is possible to achieve a cluster
with fault tolerance deploying with "Networks of brokers" or should I
consider "Master/Slave" in addition
Any takers on this? Thanks.
On 11/24/15 1:37 PM, Rallavagu wrote:
All,
What is the recommended deployment architecture for an enterprise?
1. Master/Slave with replicated Level DB
(http://activemq.apache.org/replicated-leveldb-store.html)
2. Network of Brokers for scalability
3. Hybrid
In ca
All,
What is the recommended deployment architecture for an enterprise?
1. Master/Slave with replicated Level DB
(http://activemq.apache.org/replicated-leveldb-store.html)
2. Network of Brokers for scalability
3. Hybrid
In case of hybrid, is there a reference document that I could use? Than
Hi.
We're working with a IIS server, and we would like to integrate an activeMQ
server into it. Is it possible?
Regards.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-deployment-in-IIS-server-tp4659011.html
Sent from the ActiveMQ - User mailing list ar
On Sun, Oct 5, 2008 at 2:20 PM, akkij <[EMAIL PROTECTED]> wrote:
>
> Thanks Bruce for the reply.
>
> Does it mean that ActiveMQ embedded within tomcat gives better performance
> as there is no network call involved?
If ActiveMQ is embedded in the Tomcat process and you have
applications running in
tocols which
> involves TCP sockets.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMi
On Sun, Oct 5, 2008 at 2:00 PM, akkij <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> We have decided to use ActiveMQ for asynchronous messaging involved in one
> of our projects. I have been going through various documentation related to
> ActiveMQ; however i am looking for a specific information which
> u
lp or pointers would be appreciated.
Thanks in advance,
Akash
--
View this message in context:
http://www.nabble.com/ActiveMQ-deployment-options-tp19828552p19828552.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
29 matches
Mail list logo
