You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by rena <re...@fastinnovation.it> on 2013/08/28 15:59:01 UTC
AMQ 5.4 - 5.8 network broker
Hi,
we have a central server with a broker and a consumer and a lot of client
with local broker connected to the server with network connector.
We use version 5.4.0, all works great, but we have to upgrade to 5.8.0.
Now problems begin:
- if i upgrade server and client together to 5.8.0 all works, but i can't
upgrade all because i have a lot of client.
- if i upgrade server to 5.8.0 and clients stay to 5.4.0, in client admin i
can see active remote consumer, but produced messages remain in local
broker.
- if i upgrade client to 5.8.0 and server stays to 5.4.0, async messages
work, but request-reply messages don't work: server receive message, but
client has no response.
My network connector config is:
<networkConnectors>
<networkConnector uri="static://(tcp://serverhost:61616)"
name="bridge"
duplex="true"
conduitSubscriptions="true"
decreaseNetworkConsumerPriority="false">
</networkConnector>
</networkConnectors>
Any help for the migration?
--
View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-5-4-5-8-network-broker-tp4670813.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: AMQ 5.4 - 5.8 network broker
Posted by rena <re...@fastinnovation.it>.
Dear All,
thank you for your help!
I solved in this way:
1) change configuration in network connector broker client 5.4.0 from
<networkConnectors>
<networkConnector uri="static://(tcp://SERVERURL:61616)"
name="bridge"
duplex="true"
conduitSubscriptions="true"
decreaseNetworkConsumerPriority="false">
</networkConnector>
</networkConnectors>
to
<networkConnectors>
<networkConnector uri="static://(tcp://SERVERURL:61616)"
name="bridge"
duplex="true"
conduitSubscriptions="true"
decreaseNetworkConsumerPriority="false">
<dynamicallyIncludedDestinations>
<queue physicalName=">" />
</dynamicallyIncludedDestinations>
</networkConnector>
</networkConnectors>
2) upgrade server broker from 5.4.0 to 5.8.0
3) All works, also synchronous messages
4) Upgrade each broker client to 5.8.0 and test every message
--
View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-5-4-5-8-network-broker-tp4670813p4671212.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: AMQ 5.4 - 5.8 network broker
Posted by Christian Posta <ch...@gmail.com>.
Check this thread:
http://activemq.2283324.n4.nabble.com/5-7-doesn-t-consume-on-queue-tt4658025.html
On Wed, Sep 4, 2013 at 8:17 AM, Johan Edstrom <se...@gmail.com> wrote:
> I can confirm that you'll need that for propagation of destinations.
>
> On Sep 4, 2013, at 8:43 AM, Gary Tully <ga...@gmail.com> wrote:
>
> > just a thought, I recall an issue with the destination filter, can't
> > recall the exact detail but it may help for the server 5.8 case.
> > mod the clients networkConnector to add:
> >
> > <networkConnector ... ,
> >
> destinationFilter="Legacy,ActiveMQ.Advisory.Consumer.>,ActiveMQ.Advisory.Consumer.Queue.>"
> > ...
> >
> > enabling trace=true on the transportConnector or networkConnector url
> > and trace level logging will let you see the ConsumerInfo for the
> > advisory consumer, in which you can see the
> > value of the ConsumerInfo and the corresponding filter.
> >
> > On 29 August 2013 08:54, rena <re...@fastinnovation.it> wrote:
> >> Thank you christian.
> >>
> >> Unfortunately, i have at least 100 client and upgrade all together
> require
> >> too much time.
> >>
> >> My problem could be resolved using some particular configuration or i
> have
> >> no hope?
> >>
> >>
> >>
> >> --
> >> View this message in context:
> http://activemq.2283324.n4.nabble.com/AMQ-5-4-5-8-network-broker-tp4670813p4670892.html
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
> >
> >
> > --
> > http://redhat.com
> > http://blog.garytully.com
>
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta
Re: AMQ 5.4 - 5.8 network broker
Posted by Johan Edstrom <se...@gmail.com>.
I can confirm that you'll need that for propagation of destinations.
On Sep 4, 2013, at 8:43 AM, Gary Tully <ga...@gmail.com> wrote:
> just a thought, I recall an issue with the destination filter, can't
> recall the exact detail but it may help for the server 5.8 case.
> mod the clients networkConnector to add:
>
> <networkConnector ... ,
> destinationFilter="Legacy,ActiveMQ.Advisory.Consumer.>,ActiveMQ.Advisory.Consumer.Queue.>"
> ...
>
> enabling trace=true on the transportConnector or networkConnector url
> and trace level logging will let you see the ConsumerInfo for the
> advisory consumer, in which you can see the
> value of the ConsumerInfo and the corresponding filter.
>
> On 29 August 2013 08:54, rena <re...@fastinnovation.it> wrote:
>> Thank you christian.
>>
>> Unfortunately, i have at least 100 client and upgrade all together require
>> too much time.
>>
>> My problem could be resolved using some particular configuration or i have
>> no hope?
>>
>>
>>
>> --
>> View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-5-4-5-8-network-broker-tp4670813p4670892.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
> --
> http://redhat.com
> http://blog.garytully.com
Re: AMQ 5.4 - 5.8 network broker
Posted by Gary Tully <ga...@gmail.com>.
just a thought, I recall an issue with the destination filter, can't
recall the exact detail but it may help for the server 5.8 case.
mod the clients networkConnector to add:
<networkConnector ... ,
destinationFilter="Legacy,ActiveMQ.Advisory.Consumer.>,ActiveMQ.Advisory.Consumer.Queue.>"
...
enabling trace=true on the transportConnector or networkConnector url
and trace level logging will let you see the ConsumerInfo for the
advisory consumer, in which you can see the
value of the ConsumerInfo and the corresponding filter.
On 29 August 2013 08:54, rena <re...@fastinnovation.it> wrote:
> Thank you christian.
>
> Unfortunately, i have at least 100 client and upgrade all together require
> too much time.
>
> My problem could be resolved using some particular configuration or i have
> no hope?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-5-4-5-8-network-broker-tp4670813p4670892.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://redhat.com
http://blog.garytully.com
Re: AMQ 5.4 - 5.8 network broker
Posted by rena <re...@fastinnovation.it>.
Thank you christian.
Unfortunately, i have at least 100 client and upgrade all together require
too much time.
My problem could be resolved using some particular configuration or i have
no hope?
--
View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-5-4-5-8-network-broker-tp4670813p4670892.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: AMQ 5.4 - 5.8 network broker
Posted by Christian Posta <ch...@gmail.com>.
For network of brokers, version backward compatibilities are not
guaranteed.
There are definitely changes in how the brokers communicate with each other
across versions. Unfortunately, in your network of brokers, your best bet
is to upgrade all.
On Wed, Aug 28, 2013 at 6:59 AM, rena <re...@fastinnovation.it>wrote:
> Hi,
> we have a central server with a broker and a consumer and a lot of client
> with local broker connected to the server with network connector.
> We use version 5.4.0, all works great, but we have to upgrade to 5.8.0.
> Now problems begin:
> - if i upgrade server and client together to 5.8.0 all works, but i can't
> upgrade all because i have a lot of client.
> - if i upgrade server to 5.8.0 and clients stay to 5.4.0, in client admin i
> can see active remote consumer, but produced messages remain in local
> broker.
> - if i upgrade client to 5.8.0 and server stays to 5.4.0, async messages
> work, but request-reply messages don't work: server receive message, but
> client has no response.
>
> My network connector config is:
> <networkConnectors>
> <networkConnector uri="static://(tcp://serverhost:61616)"
> name="bridge"
> duplex="true"
> conduitSubscriptions="true"
> decreaseNetworkConsumerPriority="false">
> </networkConnector>
> </networkConnectors>
>
>
> Any help for the migration?
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/AMQ-5-4-5-8-network-broker-tp4670813.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta