That seems like a restricted solution that the Consumer should be a servlet.
May I know why?
What I have is a standalone Consumer (for testing purposes). Not sure how
the Production systems are, but the standalone Consumer dies as soon as the
Master is down. I have been looking for a solution to t
Consumer can do failover in web project. Consumer should be a servlet! You
can have a try!
On Tue, Aug 21, 2012 at 2:38 AM, joesan [via ActiveMQ] <
ml-node+s2283324n4655327...@n4.nabble.com> wrote:
> Did you find a solution to this? I have more or less the same issue. My
> Producer can fail-over
>>So, that request-response recipe uses temporary destinations to route
messages. Your use-case is that of request-throttling and load-balancing the
'service'.
Not really. There is no service but a transport queue which could be IPC for
that matter. I may not have explained it well but I have the
So, that request-response recipe uses temporary destinations to route
messages. Your use-case is that of request-throttling and load-balancing
the 'service'. Why not use something designed for that purpose like nginx
and its http_limit_conn module? ActiveMQ does have the producer
flow-control featu
Torsten, I just tried the configuration you suggested. I made my consumer
Network Connectors duplex and I still don't see any messages making it to
the consumers.
If I connect with JMX to the stand alone broker I can see under
org.apache.activemq.broker.Connection.openwire my 3 producers connected
Thanks a lot for the code. I looked at it but if you can provide some
comments it might help as I am only familiar with whats at
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
and not inner workings.
But first question that comes to mind is if HTTP is right proto
To register an HttpCallback, you can create a class with a simple method
like below and just register the messagelistener at message publish time
(since your producers seem to know the message route upfront). This can be
called in a pooled thread on the client side:
void invokeEndpoint() {
Did you find a solution to this? I have more or less the same issue. My
Producer can fail-over but my Consumer dies as soon as the master dies.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/master-slave-consumer-can-not-failover-tp4653639p4655327.html
Sent from the Acti
Thanks. Few clarifications:
>>register an http-callback in the garb of a message listener
I am not sure I follow how to do this. (Note: We are using CMS instead of
JMS here). Is there a code snippet (JMS itself) that can quickly explain
what should be done ?
As to why we want to do that is due t
Sorry, the previous post was truncated by the forum. Here it is again:
1. Create an embedded ActiveMQ TCP broker with failover enabled
2. Connect to the embedded ActiveMQ TCP broker with failover URL
3. Stop connection and embedded ActiveMQ TCP broker
4. Create an embedded ActiveMQ SSL broker w
Attached is a ZIP file with all necessary code, libraries, and certificates.
The project can be opened in Netbeans. Make sure to change the running
directory to the folder enclosed in the ZIP file. Everything else is
specified as a relative path.
The code is very simple and demonstrates the test
So you can always register an http-callback in the garb of a message listener
during the time of msg publication. When the client execs your listener and
runs the callback, it can do http post/get, etc to whatever other broker url
you want to route the msg to.
I am not sure what multiple broke
Hi Gaurav,
Would 2 broker not work otherwise though. Please see similar question below.
I understand that one broker would work but what if I need to run 2 brokers
(no embedded/embedded).
link:
http://activemq.2283324.n4.nabble.com/Implementing-Request-Response-mechanism-td4655304.html
--
Vie
I looked at
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
However I have a question on this. I have multiple clients and a servers.
Each have their own local broker. Client needs to send message to server's
broker and setJMSreply to it's own (client's) local brok
You can use any file system that supports proper file locking, e.g. NFSv4 or
GFS.
http://activemq.apache.org/shared-file-system-master-slave.html
Hope this helps,
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On Aug 19, 2012, at 8:58 AM, Eugene Brian Ong wrote:
> Hi,
>
> We wa
15 matches
Mail list logo
