You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by pollotek <cl...@gmail.com> on 2012/08/07 00:31:05 UTC
Trasport Listener for embedded broker network connectors
I have this application that connects to a stand alone broker and I monitor
this connection with a TransportListener.
I'm changing my architecture to have an embedded broker inside my app and
that embedded broker connected to the stand alone broker.
Is there a way to attach my Transport Listener to the Network Connector
declared in the embedded broker pointing to the stand alone broker?
Thanks,
Claudio
--
View this message in context: http://activemq.2283324.n4.nabble.com/Trasport-Listener-for-embedded-broker-network-connectors-tp4654830.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Trasport Listener for embedded broker network connectors
Posted by Gary Tully <ga...@gmail.com>.
A network connector is quite different, as it keeps a connection and
producer open and funnels all messages over that single producer when
there are local messages and remote demand.
I think making use of message advisories will help your use case.
You can subscribe to the Producer advisory topic to get a notification
(via jms) of producer creation and deletion.
have a read of:
http://activemq.apache.org/advisory-message.html
On 7 August 2012 20:50, pollotek <cl...@gmail.com> wrote:
> I want to be able to monitor when the embedded server establishes or loses
> connection with the stand alone server. My app is divided in producer app
> server nodes and consumer nodes.
>
> I know I can get a list of producers and consumers from the stand alone
> broker by querying JMX stats, but producers only appear on the JMX stats
> when they're actually posting new messages to the broker.
>
> In the case of app servers with embedded brokers that only produce messages,
> I won't be able to tell if they're currently connected to the stand alone
> broker unless I'm able to query the stand alone broker exactly when they're
> posting new messages.
>
> The alternatives here are by keeping track of the status in my Transport
> Listener or by parsing the logs (which is a very undesirable alternative).
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Trasport-Listener-for-embedded-broker-network-connectors-tp4654830p4654866.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://fusesource.com
http://blog.garytully.com
Re: Trasport Listener for embedded broker network connectors
Posted by pollotek <cl...@gmail.com>.
I want to be able to monitor when the embedded server establishes or loses
connection with the stand alone server. My app is divided in producer app
server nodes and consumer nodes.
I know I can get a list of producers and consumers from the stand alone
broker by querying JMX stats, but producers only appear on the JMX stats
when they're actually posting new messages to the broker.
In the case of app servers with embedded brokers that only produce messages,
I won't be able to tell if they're currently connected to the stand alone
broker unless I'm able to query the stand alone broker exactly when they're
posting new messages.
The alternatives here are by keeping track of the status in my Transport
Listener or by parsing the logs (which is a very undesirable alternative).
--
View this message in context: http://activemq.2283324.n4.nabble.com/Trasport-Listener-for-embedded-broker-network-connectors-tp4654830p4654866.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Trasport Listener for embedded broker network connectors
Posted by Gary Tully <ga...@gmail.com>.
Not at the moment. What is the use case?
The discovery network connector does auto reconnects so it handles
failures/retries without intervention and recreates bridges on demand.
On 6 August 2012 23:31, pollotek <cl...@gmail.com> wrote:
> I have this application that connects to a stand alone broker and I monitor
> this connection with a TransportListener.
>
> I'm changing my architecture to have an embedded broker inside my app and
> that embedded broker connected to the stand alone broker.
>
> Is there a way to attach my Transport Listener to the Network Connector
> declared in the embedded broker pointing to the stand alone broker?
>
> Thanks,
>
> Claudio
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Trasport-Listener-for-embedded-broker-network-connectors-tp4654830.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://fusesource.com
http://blog.garytully.com