You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by spp <su...@gmail.com> on 2015/11/25 09:19:11 UTC

Duplex NetworkConnector: bridge stopped

Hi guys, 
  I got a problem with cluster of brokers: after a period of time (not
exactly sure how much, a few days usually) from startup, the network
connector bridge between brokers stopped, and restart of brokers make all
things get to normal, then it happens again.
I cannot reproduce the problem manually.

It's very similar to this issue
https://issues.apache.org/jira/browse/AMQ-553. 

AMQ version: 5.12.0
CentOS 6.3
Java 1.8.0_51

the logs related: 

2015-11-25 15:26:28,512 | INFO  | Establishing network connection from
vm://ite18-mop-amq512?async=false to tcp://10.23.249.91:8027 |
org.apache.activemq.network.DiscoveryNetworkConnector | ActiveMQ Task-4832

2015-11-25 15:26:28,532 | WARN  | Failed to add Connection
ite18-mop-amq512->ite17-mop-amq512-20849-1447220156775-107716:1 due to
javax.jms.InvalidClientIDException: Broker: ite18-mop-amq512 - Client:
NC_ite17-mop-amq512_inbound_ite18-mop-amq512 already connected from
vm://ite18-mop-amq512#77296 | org.apache.activemq.broker.TransportConnection
| triggerStartAsyncNetworkBridgeCreation:
remoteBroker=tcp:///10.23.249.91:8027@39966, localBroker=
vm://ite18-mop-amq512#215424

2015-11-25 15:26:28,533 | INFO  | Network connection between
vm://ite18-mop-amq512#215424 and tcp:///10.23.249.91:8027@39966 shutdown due
to a local error: javax.jms.InvalidClientIDException: Broker:
ite18-mop-amq512 - Client: NC_ite17-mop-amq512_inbound_ite18-mop-amq512
already connected from vm://ite18-mop-amq512#77296 |
org.apache.activemq.network.DemandForwardingBridgeSupport |
triggerStartAsyncNetworkBridgeCreation:
remoteBroker=tcp:///10.23.249.91:8027@39966, localBroker=
vm://ite18-mop-amq512#215424

2015-11-25 15:26:28,538 | INFO  | ite18-mop-amq512 bridge to
ite17-mop-amq512 stopped |
org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ
BrokerService[ite18-mop-amq512] Task-43098


config at ite18-mop-amq512: 

        <networkConnectors>
            <networkConnector uri="static:(tcp://10.23.249.91:8027)"
                              duplex="true"
                              userName="xxxxx"
                              password="xxxxx"
                              checkDuplicateMessagesOnDuplex="true"/>
        </networkConnectors>

broker 'ite17-mop-amq512' has ip 10.23.249.91


Any suggestions?

Regards,
Song






--
View this message in context: http://activemq.2283324.n4.nabble.com/Duplex-NetworkConnector-bridge-stopped-tp4704264.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Duplex NetworkConnector: bridge stopped

Posted by Tim Bain <tb...@alumni.duke.edu>.
Do you see the same behavior if you remove the username and password from
the configuration?  Same question for the duplicate check.

Also, JIRA says that issue doesn't exist when I follow that link; can you
confirm the number?
On Nov 25, 2015 1:34 AM, "spp" <su...@gmail.com> wrote:

> Hi guys,
>   I got a problem with cluster of brokers: after a period of time (not
> exactly sure how much, a few days usually) from startup, the network
> connector bridge between brokers stopped, and restart of brokers make all
> things get to normal, then it happens again.
> I cannot reproduce the problem manually.
>
> It's very similar to this issue
> https://issues.apache.org/jira/browse/AMQ-553.
>
> AMQ version: 5.12.0
> CentOS 6.3
> Java 1.8.0_51
>
> the logs related:
>
> 2015-11-25 15:26:28,512 | INFO  | Establishing network connection from
> vm://ite18-mop-amq512?async=false to tcp://10.23.249.91:8027 |
> org.apache.activemq.network.DiscoveryNetworkConnector | ActiveMQ Task-4832
>
> 2015-11-25 15:26:28,532 | WARN  | Failed to add Connection
> ite18-mop-amq512->ite17-mop-amq512-20849-1447220156775-107716:1 due to
> javax.jms.InvalidClientIDException: Broker: ite18-mop-amq512 - Client:
> NC_ite17-mop-amq512_inbound_ite18-mop-amq512 already connected from
> vm://ite18-mop-amq512#77296 |
> org.apache.activemq.broker.TransportConnection
> | triggerStartAsyncNetworkBridgeCreation:
> remoteBroker=tcp:///10.23.249.91:8027@39966, localBroker=
> vm://ite18-mop-amq512#215424
>
> 2015-11-25 15:26:28,533 | INFO  | Network connection between
> vm://ite18-mop-amq512#215424 and tcp:///10.23.249.91:8027@39966 shutdown
> due
> to a local error: javax.jms.InvalidClientIDException: Broker:
> ite18-mop-amq512 - Client: NC_ite17-mop-amq512_inbound_ite18-mop-amq512
> already connected from vm://ite18-mop-amq512#77296 |
> org.apache.activemq.network.DemandForwardingBridgeSupport |
> triggerStartAsyncNetworkBridgeCreation:
> remoteBroker=tcp:///10.23.249.91:8027@39966, localBroker=
> vm://ite18-mop-amq512#215424
>
> 2015-11-25 15:26:28,538 | INFO  | ite18-mop-amq512 bridge to
> ite17-mop-amq512 stopped |
> org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ
> BrokerService[ite18-mop-amq512] Task-43098
>
>
> config at ite18-mop-amq512:
>
>         <networkConnectors>
>             <networkConnector uri="static:(tcp://10.23.249.91:8027)"
>                               duplex="true"
>                               userName="xxxxx"
>                               password="xxxxx"
>                               checkDuplicateMessagesOnDuplex="true"/>
>         </networkConnectors>
>
> broker 'ite17-mop-amq512' has ip 10.23.249.91
>
>
> Any suggestions?
>
> Regards,
> Song
>
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Duplex-NetworkConnector-bridge-stopped-tp4704264.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>