[jira] [Commented] (AMQ-6835) DemanForwardBridge not being built occasionally
[ https://issues.apache.org/jira/browse/AMQ-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261764#comment-16261764 ] Cadmean commented on AMQ-6835: -- [~gtully]That works. Thanks a lot! > DemanForwardBridge not being built occasionally > > > Key: AMQ-6835 > URL: https://issues.apache.org/jira/browse/AMQ-6835 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.13.4, 5.15.2 > Environment: SuseLinux 11SP4 > JAVA JDK 1.7 >Reporter: Cadmean > > Env: > ActiveMQ version: 5.15.0 > 8 ActiveMQ Broker to form a mesh topology with "duplex=false messageTTL=-1 > consumerTTL=1". See: > {code:java} > >duplex="false" messageTTL="-1" dynamicOnly="false" /> > > {code} > 8000 clients are connected to brokers using > failover:(tcp://ip1:61616,ip2:61616,ip3:61616,...). These clients are > non-durable subscribers subscribe to Topics according to there IP addresses. > For example: client 192.168.10.1 subscribes to TOPIC://VLAN.192.168.10 > In this case, I got about 200 topics in my ActiveMQ broker cluster. > The problem is demand forward bridges where not created occasionally. > For example: > Client 192.168.10.1 is connecting to Broker A and subscribing > TOPIC://VLAN.192.168.10. > Producer is connecting to Broker B and sending messages to > TOPIC://VLAN.192.168.10. > Normally client can receive message, which are sent to Broker B by the > producer, from Broker A since A and B are in the same cluster. > However, I found some of the clients in Broker A cannot receive any message. > When checking the subscribers of the topic, I found the bridge to Broker B is > missing. > I realize that whether the demand forward bridge is created depending on > advisory consumer messages. So I try to receive ConsumerInfo of the client > from "ActiveMQ.Advisory.Consumer.VLAN.192.168.10" and resend this > ConsumerInfo message to the same topic > "ActiveMQ.Advisory.Consumer.VLAN.192.168.10". > Then the client could receive messages correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMQ-6835) DemanForwardBridge not being built occasionally
[ https://issues.apache.org/jira/browse/AMQ-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259174#comment-16259174 ] Gary Tully commented on AMQ-6835: - is the discarding policy in place for topics - this covers advisory topics also and should be removed in your use case. https://github.com/apache/activemq/blob/41a100766c19655816d575841ba559d33c63313d/assembly/src/release/conf/activemq.xml#L55 > DemanForwardBridge not being built occasionally > > > Key: AMQ-6835 > URL: https://issues.apache.org/jira/browse/AMQ-6835 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.13.4, 5.15.2 > Environment: SuseLinux 11SP4 > JAVA JDK 1.7 >Reporter: Cadmean > > Env: > ActiveMQ version: 5.15.0 > 8 ActiveMQ Broker to form a mesh topology with "duplex=false messageTTL=-1 > consumerTTL=1". See: > {code:java} > >duplex="false" messageTTL="-1" dynamicOnly="false" /> > > {code} > 8000 clients are connected to brokers using > failover:(tcp://ip1:61616,ip2:61616,ip3:61616,...). These clients are > non-durable subscribers subscribe to Topics according to there IP addresses. > For example: client 192.168.10.1 subscribes to TOPIC://VLAN.192.168.10 > In this case, I got about 200 topics in my ActiveMQ broker cluster. > The problem is demand forward bridges where not created occasionally. > For example: > Client 192.168.10.1 is connecting to Broker A and subscribing > TOPIC://VLAN.192.168.10. > Producer is connecting to Broker B and sending messages to > TOPIC://VLAN.192.168.10. > Normally client can receive message, which are sent to Broker B by the > producer, from Broker A since A and B are in the same cluster. > However, I found some of the clients in Broker A cannot receive any message. > When checking the subscribers of the topic, I found the bridge to Broker B is > missing. > I realize that whether the demand forward bridge is created depending on > advisory consumer messages. So I try to receive ConsumerInfo of the client > from "ActiveMQ.Advisory.Consumer.VLAN.192.168.10" and resend this > ConsumerInfo message to the same topic > "ActiveMQ.Advisory.Consumer.VLAN.192.168.10". > Then the client could receive messages correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMQ-6835) DemanForwardBridge not being built occasionally
[ https://issues.apache.org/jira/browse/AMQ-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259167#comment-16259167 ] Cadmean commented on AMQ-6835: -- I've tried version 5.15.0. The problem still exist. I also modify DemanForwardBridgeSupport claas (added some logs) to see what was going on there. And I found the problem is: *Advisory messages (about adding a consumer) are not received by all the brokers(in the same cluster). * For example, I have Broker A,B,C. The consumer is connected to C and subscribed TOPIC1. C will send a advisory message of ConsumerInfo to Broker A and B. A gets the message but B doesnt. And sadly producer is connected to B, so the message will never received by the consumer. The problem happens when thousands of clients creating consumers at the same time. > DemanForwardBridge not being built occasionally > > > Key: AMQ-6835 > URL: https://issues.apache.org/jira/browse/AMQ-6835 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.13.4 > Environment: SuseLinux 11SP4 > JAVA JDK 1.7 >Reporter: Cadmean > > Env: > ActiveMQ version: 5.13.4 > 8 ActiveMQ Broker to form a mesh topology with "duplex=false messageTTL=-1 > consumerTTL=1". See: > {code:java} > >duplex="false" messageTTL="-1" dynamicOnly="false" /> > > {code} > 8000 clients are connected to brokers using > failover:(tcp://ip1:61616,ip2:61616,ip3:61616,...). These clients are > non-durable subscribers subscribe to Topics according to there IP addresses. > For example: client 192.168.10.1 subscribes to TOPIC://VLAN.192.168.10 > In this case, I got about 200 topics in my ActiveMQ broker cluster. > The problem is demand forward bridges where not created occasionally. > For example: > Client 192.168.10.1 is connecting to Broker A and subscribing > TOPIC://VLAN.192.168.10. > Producer is connecting to Broker B and sending messages to > TOPIC://VLAN.192.168.10. > Normally client can receive message, which are sent to Broker B by the > producer, from Broker A since A and B are in the same cluster. > However, I found some of the clients in Broker A cannot receive any message. > When checking the subscribers of the topic, I found the bridge to Broker B is > missing. > I realize that whether the demand forward bridge is created depending on > advisory consumer messages. So I try to receive ConsumerInfo of the client > from "ActiveMQ.Advisory.Consumer.VLAN.192.168.10" and resend this > ConsumerInfo message to the same topic > "ActiveMQ.Advisory.Consumer.VLAN.192.168.10". > Then the client could receive messages correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMQ-6835) DemanForwardBridge not being built occasionally
[ https://issues.apache.org/jira/browse/AMQ-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200311#comment-16200311 ] Timothy Bish commented on AMQ-6835: --- First thing to do would be to test with a recent release as the one you are using is quite old, if that still shows a problem then a reproducer is needed. > DemanForwardBridge not being built occasionally > > > Key: AMQ-6835 > URL: https://issues.apache.org/jira/browse/AMQ-6835 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 5.13.4 > Environment: SuseLinux 11SP4 > JAVA JDK 1.7 >Reporter: Cadmean > > Env: > ActiveMQ version: 5.13.4 > 8 ActiveMQ Broker to form a mesh topology with "duplex=false messageTTL=-1 > consumerTTL=1". See: > {code:java} > >duplex="false" messageTTL="-1" dynamicOnly="false" /> > > {code} > 8000 clients are connected to brokers using > failover:(tcp://ip1:61616,ip2:61616,ip3:61616,...). These clients are > non-durable subscribers subscribe to Topics according to there IP addresses. > For example: client 192.168.10.1 subscribes to TOPIC://VLAN.192.168.10 > In this case, I got about 200 topics in my ActiveMQ broker cluster. > The problem is demand forward bridges where not created occasionally. > For example: > Client 192.168.10.1 is connecting to Broker A and subscribing > TOPIC://VLAN.192.168.10. > Producer is connecting to Broker B and sending messages to > TOPIC://VLAN.192.168.10. > Normally client can receive message, which are sent to Broker B by the > producer, from Broker A since A and B are in the same cluster. > However, I found some of the clients in Broker A cannot receive any message. > When checking the subscribers of the topic, I found the bridge to Broker B is > missing. > I realize that whether the demand forward bridge is created depending on > advisory consumer messages. So I try to receive ConsumerInfo of the client > from "ActiveMQ.Advisory.Consumer.VLAN.192.168.10" and resend this > ConsumerInfo message to the same topic > "ActiveMQ.Advisory.Consumer.VLAN.192.168.10". > Then the client could receive messages correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)