You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by ievanliu <ie...@qq.com> on 2018/09/13 08:28:21 UTC
Re: cannot consume msg by a duplex network connect broke.
Hi,Tim
This problem happened twice recently...
I try to use static bridge, it really worded,and solve the problem.but we
steel use temp-queue to use request-reply mode by camel,and this need
translate message between different broke,so I can not use static bridge.
I found another this that, when the problem happened , I restart the broker
,but the problem is steel as same.In the end, I shutdown all the broker,and
then start Broke A,later,start Broker B.By this, the problem disappeared.
please help .
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: cannot consume msg by a duplex network connect broke.
Posted by ievanliu <ie...@qq.com>.
sorry Tim, I didn't describe clearly,and I have start a new topic to explain
this problem more clearly,please see there:
http://activemq.2283324.n4.nabble.com/no-consumers-for-the-queue-by-a-duplex-network-connector-td4743534.html
thanks a lot.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: cannot consume msg by a duplex network connect broke.
Posted by Tim Bain <tb...@alumni.duke.edu>.
You previously said that you were statically configuring the network
connectors, but in your last email you talked about advisory topics, which
are only used for dynamically included destinations. Which approach are you
using?
More generally, please post your broker configuration, since that may
explain the behavior you're observing.
Also, are you saying that the network behavior you see is different before
a broker failover than after one? If so, which broker was the one that
failed over?
And to which broker was the consumer connected in each case you described?
Your description of the missing logs in A sound like the consumer is
connected to B, but your paragraph at the end sounded like the opposite. So
a detailed description of how you're interacting with the network of
brokers would help clarify what you're describing.
Tim
On Fri, Sep 14, 2018, 11:23 AM ievanliu <ie...@qq.com> wrote:
> Hi,Tim
>
> this problem happened very often recently.
>
> as run in this architecture: Broke A(a 3 instances jdbc cluster) and Broke
> B(a 3 instances
> jdbc cluster), use duplex network connect, from brokeB to brokeA
>
> once Broker B cluster happened fail-over event(master changed from B1 to
> B2),then the bridge problem happened.
>
> I test that subscribe a queue test_queue to broke B,but in broke A ,there
> even has no queue named test_queue,and there has no advisory topic in broke
> A either
>
> normally,when subscribe a queue,the log is as below:
> [log in brokerA]
> [DEBUG][2018-09-14 16:33:46] localhost adding consumer:
> localhost->bj_172.20.32.111-44717-1536908810883-4:1:1:13 for destination:
>
> queue://amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:338
> addConsumer]
> [DEBUG][2018-09-14 16:33:46] localhost adding destination:
>
> queue://amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:154
> addDestination]
> [DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45, subscriptions=0,
> memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
> pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
> dequeueCount: 0, memUsage:0,
> maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
> doPageInForDispatch]
> [DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45 add sub:
> QueueSubscription:
> consumer=localhost->bj_172.20.32.111-44717-1536908810883-4:1:1:13,
> destinations=0, dispatched=0, delivered=0, pending=0, dequeues: 0,
> dispatched: 0, inflight: 0<--[org.apache.activemq.broker.region.Queue:422
> addSubscription]
> [DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45, subscriptions=1,
> memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
> pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
> dequeueCount: 0, memUsage:0,
> maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
> doPageInForDispatch]
> [DEBUG][2018-09-14 16:33:46] localhost adding destination:
>
> topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:154
> addDestination]
>
>
> [log in BrokerB]
> [DEBUG][2018-09-14 16:33:46] bj_172.20.32.111 adding consumer:
> ID:cloudlab042-46597-1536908807725-7:22:-1:1 for destination:
>
> queue://amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:338
> addConsumer]
> [DEBUG][2018-09-14 16:33:46] bj_172.20.32.111 adding destination:
>
> queue://amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:154
> addDestination]
> [DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45, subscriptions=0,
> memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
> pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
> dequeueCount: 0, memUsage:0,
> maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
> doPageInForDispatch]
> [DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45 add sub:
> QueueSubscription: consumer=ID:cloudlab042-46597-1536908807725-7:22:-1:1,
> destinations=0, dispatched=0, delivered=0, pending=0, dequeues: 0,
> dispatched: 0, inflight: 0<--[org.apache.activemq.broker.region.Queue:422
> addSubscription]
> [DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45, subscriptions=1,
> memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
> pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
> dequeueCount: 0, memUsage:0,
> maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
> doPageInForDispatch]
> [DEBUG][2018-09-14 16:33:46] bj_172.20.32.111 adding destination:
>
> topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:154
> addDestination]
> [DEBUG][2018-09-14 16:33:46] bridging (bj_172.20.32.111 -> localhost),
> consumer: bj_172.20.32.111->localhost-46597-1536908807725-6:1:1:1,
> destination: topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test45,
> brokerPath: [ID:cloudlab042-46597-1536908807725-0:1], message:
>
> ID:cloudlab042-46597-1536908807725-1:1:0:0:87<--[org.apache.activemq.network.DemandForwardingBridgeSupport:1070
> serviceLocalCommand]
>
>
> but when problem happened,and then I subscribe anther queue in brokeB, I
> found,there has no log of this queue bin BrokeA at all.
> in BrokerB,log is as below:[DEBUG][2018-09-14 22:31:53] bj_172.20.32.109
> adding consumer: ID:bfjd-psc-bcop-vm16-60932-1536934894156-5:2:-1:1 for
> destination:
>
> queue://amq_admin_test_nj<--[org.apache.activemq.broker.region.AbstractRegion:338
> addConsumer]
> [DEBUG][2018-09-14 22:31:53] bj_172.20.32.109 adding destination:
>
> queue://amq_admin_test_nj<--[org.apache.activemq.broker.region.AbstractRegion:154
> addDestination]
> [DEBUG][2018-09-14 22:31:53] queue://amq_admin_test_nj, subscriptions=0,
> memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
> pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
> dequeueCount: 0, memUsage:0,
> maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
> doPageInForDispatch]
> [DEBUG][2018-09-14 22:31:53] queue://amq_admin_test_nj add sub:
> QueueSubscription:
> consumer=ID:bfjd-psc-bcop-vm16-60932-1536934894156-5:2:-1:1,
> destinations=0,
> dispatched=0, delivered=0, pending=0, dequeues: 0, dispatched: 0, inflight:
> 0<--[org.apache.activemq.broker.region.Queue:422 addSubscription]
> [DEBUG][2018-09-14 22:31:53] queue://amq_admin_test_nj, subscriptions=1,
> memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
> pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
> dequeueCount: 0, memUsage:0,
> maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
> doPageInForDispatch]
> [DEBUG][2018-09-14 22:31:53] bj_172.20.32.109 adding destination:
>
> topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test_nj<--[org.apache.activemq.broker.region.AbstractRegion:154
> addDestination]
> [DEBUG][2018-09-14 22:32:23] queue://amq_admin_test_nj expiring messages
> ..<--[org.apache.activemq.broker.region.Queue:904 expireMessages]
> [DEBUG][2018-09-14 22:32:23] queue://amq_admin_test_nj expiring messages
> done.<--[org.apache.activemq.broker.region.Queue:910 expireMessages]
>
>
> I can see that this log did not happed:
> "bridging (bj_172.20.32.111 -> localhost), consumer:
> bj_172.20.32.111->localhost-46597-1536908807725-6:1:1:1, destination:
> topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test45, brokerPath:
> [ID:cloudlab042-46597-1536908807725-0:1], message"
>
>
> but there are some queues successfully built network connector from BrokeA
> to BrokeB(the queue in BrokeB has a bridge connect as a consumer)
>
> this really puzzle me.
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
Re: cannot consume msg by a duplex network connect broke.
Posted by ievanliu <ie...@qq.com>.
Hi,Tim
this problem happened very often recently.
as run in this architecture: Broke A(a 3 instances jdbc cluster) and Broke
B(a 3 instances
jdbc cluster), use duplex network connect, from brokeB to brokeA
once Broker B cluster happened fail-over event(master changed from B1 to
B2),then the bridge problem happened.
I test that subscribe a queue test_queue to broke B,but in broke A ,there
even has no queue named test_queue,and there has no advisory topic in broke
A either
normally,when subscribe a queue,the log is as below:
[log in brokerA]
[DEBUG][2018-09-14 16:33:46] localhost adding consumer:
localhost->bj_172.20.32.111-44717-1536908810883-4:1:1:13 for destination:
queue://amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:338
addConsumer]
[DEBUG][2018-09-14 16:33:46] localhost adding destination:
queue://amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:154
addDestination]
[DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45, subscriptions=0,
memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
dequeueCount: 0, memUsage:0,
maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
doPageInForDispatch]
[DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45 add sub:
QueueSubscription:
consumer=localhost->bj_172.20.32.111-44717-1536908810883-4:1:1:13,
destinations=0, dispatched=0, delivered=0, pending=0, dequeues: 0,
dispatched: 0, inflight: 0<--[org.apache.activemq.broker.region.Queue:422
addSubscription]
[DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45, subscriptions=1,
memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
dequeueCount: 0, memUsage:0,
maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
doPageInForDispatch]
[DEBUG][2018-09-14 16:33:46] localhost adding destination:
topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:154
addDestination]
[log in BrokerB]
[DEBUG][2018-09-14 16:33:46] bj_172.20.32.111 adding consumer:
ID:cloudlab042-46597-1536908807725-7:22:-1:1 for destination:
queue://amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:338
addConsumer]
[DEBUG][2018-09-14 16:33:46] bj_172.20.32.111 adding destination:
queue://amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:154
addDestination]
[DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45, subscriptions=0,
memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
dequeueCount: 0, memUsage:0,
maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
doPageInForDispatch]
[DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45 add sub:
QueueSubscription: consumer=ID:cloudlab042-46597-1536908807725-7:22:-1:1,
destinations=0, dispatched=0, delivered=0, pending=0, dequeues: 0,
dispatched: 0, inflight: 0<--[org.apache.activemq.broker.region.Queue:422
addSubscription]
[DEBUG][2018-09-14 16:33:46] queue://amq_admin_test45, subscriptions=1,
memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
dequeueCount: 0, memUsage:0,
maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
doPageInForDispatch]
[DEBUG][2018-09-14 16:33:46] bj_172.20.32.111 adding destination:
topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test45<--[org.apache.activemq.broker.region.AbstractRegion:154
addDestination]
[DEBUG][2018-09-14 16:33:46] bridging (bj_172.20.32.111 -> localhost),
consumer: bj_172.20.32.111->localhost-46597-1536908807725-6:1:1:1,
destination: topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test45,
brokerPath: [ID:cloudlab042-46597-1536908807725-0:1], message:
ID:cloudlab042-46597-1536908807725-1:1:0:0:87<--[org.apache.activemq.network.DemandForwardingBridgeSupport:1070
serviceLocalCommand]
but when problem happened,and then I subscribe anther queue in brokeB, I
found,there has no log of this queue bin BrokeA at all.
in BrokerB,log is as below:[DEBUG][2018-09-14 22:31:53] bj_172.20.32.109
adding consumer: ID:bfjd-psc-bcop-vm16-60932-1536934894156-5:2:-1:1 for
destination:
queue://amq_admin_test_nj<--[org.apache.activemq.broker.region.AbstractRegion:338
addConsumer]
[DEBUG][2018-09-14 22:31:53] bj_172.20.32.109 adding destination:
queue://amq_admin_test_nj<--[org.apache.activemq.broker.region.AbstractRegion:154
addDestination]
[DEBUG][2018-09-14 22:31:53] queue://amq_admin_test_nj, subscriptions=0,
memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
dequeueCount: 0, memUsage:0,
maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
doPageInForDispatch]
[DEBUG][2018-09-14 22:31:53] queue://amq_admin_test_nj add sub:
QueueSubscription:
consumer=ID:bfjd-psc-bcop-vm16-60932-1536934894156-5:2:-1:1, destinations=0,
dispatched=0, delivered=0, pending=0, dequeues: 0, dispatched: 0, inflight:
0<--[org.apache.activemq.broker.region.Queue:422 addSubscription]
[DEBUG][2018-09-14 22:31:53] queue://amq_admin_test_nj, subscriptions=1,
memory=0%, size=0, pending=0 toPageIn: 0, force:false, Inflight: 0,
pagedInMessages.size 0, pagedInPendingDispatch.size 0, enqueueCount: 0,
dequeueCount: 0, memUsage:0,
maxPageSize:200<--[org.apache.activemq.broker.region.Queue:1913
doPageInForDispatch]
[DEBUG][2018-09-14 22:31:53] bj_172.20.32.109 adding destination:
topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test_nj<--[org.apache.activemq.broker.region.AbstractRegion:154
addDestination]
[DEBUG][2018-09-14 22:32:23] queue://amq_admin_test_nj expiring messages
..<--[org.apache.activemq.broker.region.Queue:904 expireMessages]
[DEBUG][2018-09-14 22:32:23] queue://amq_admin_test_nj expiring messages
done.<--[org.apache.activemq.broker.region.Queue:910 expireMessages]
I can see that this log did not happed:
"bridging (bj_172.20.32.111 -> localhost), consumer:
bj_172.20.32.111->localhost-46597-1536908807725-6:1:1:1, destination:
topic://ActiveMQ.Advisory.Consumer.Queue.amq_admin_test45, brokerPath:
[ID:cloudlab042-46597-1536908807725-0:1], message"
but there are some queues successfully built network connector from BrokeA
to BrokeB(the queue in BrokeB has a bridge connect as a consumer)
this really puzzle me.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: cannot consume msg by a duplex network connect broke.
Posted by Tim Bain <tb...@alumni.duke.edu>.
I typically find that dynamically including the destinations is a more
flexible approach rather than statically including them (among other
things, you can use wildcards so you don't have to know the names at
configuration time); would that solve the problem you're hitting with the
temp queues? If not, can you describe the configuration you're using and
the behavior you're seeing?
Make sure you set bridgeTempDestinations=true, as described in
http://activemq.apache.org/networks-of-brokers.html.
Tim
On Sep 13, 2018 3:28 AM, "ievanliu" <ie...@qq.com> wrote:
Hi,Tim
This problem happened twice recently...
I try to use static bridge, it really worded,and solve the problem.but we
steel use temp-queue to use request-reply mode by camel,and this need
translate message between different broke,so I can not use static bridge.
I found another this that, when the problem happened , I restart the broker
,but the problem is steel as same.In the end, I shutdown all the broker,and
then start Broke A,later,start Broker B.By this, the problem disappeared.
please help .
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html