activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From talavera <atalav...@gmail.com>
Subject Re: Networked brokers dropping/suppressing messages
Date Mon, 27 May 2013 16:35:14 GMT
Using "masterslave:" works, although the log still shows a somewhat weird
behaviour, I've pasted it below.

It looks like broker B doesn't realize of the connection failure and rejects
at first the new incoming network connector from broker A.
(I'm not testing a failover, but a lost connection between brokers)

Anyways, I started getting duplicates. It seems I needed
auditNetworkProducers="true" in the transport.
And then... lost messages again :(

And again they're being suppressed:
2013-05-27 16:08:55,298 | DEBUG | suppressing duplicate message send 
[ID:corerec1-48878-1369670925644-1:64:1:1:74] from network producer with
producerSequenceId [74] less than last stored: 76 |
org.apache.activemq.broker.ProducerBrokerExchange | ActiveMQ Transport:
tcp:///10.95.178.21:37549@62618

I find the ID's root several times in the producer's log
(corerec1-48878-1369670925644-1:64)

Can these session/connection IDs get duplicated?

-----------------
2013-05-27 14:51:20,967 | WARN  | Transport (tcp://10.95.178.22:62618)
failed, reason:  org.apache.activemq.transport.InactivityIOException:
Channel was inactive for too (>30000) long: tcp://10.95.178.22:62618, not
attempting to automatically reconnect |
org.apache.activemq.transport.failover.FailoverTransport | ActiveMQ
InactivityMonitor Worker
2013-05-27 14:51:20,967 | INFO  | Network connection between
vm://rec1_master#0 and unconnected shutdown due to a local error:
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too (>30000) long: tcp://10.95.178.22:62618 |
org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ
InactivityMonitor Worker
2013-05-27 14:51:20,970 | INFO  | Establishing network connection from
vm://rec1_master?async=false&network=true to
failover:(tcp://corerec2:62618,nio://slave2:62602)?randomize=false&maxReconnectAttempts=0
| org.apache.activemq.network.DiscoveryNetworkConnector | Simple Discovery
Agent-1
2013-05-27 14:51:20,973 | INFO  | Successfully connected to
tcp://corerec2:62618 |
org.apache.activemq.transport.failover.FailoverTransport | ActiveMQ Failover
Worker: 46376251
2013-05-27 14:51:20,979 | WARN  | Failed to add Connection
ID:corerec1-60717-1369666090596-3:1, reason:
javax.jms.InvalidClientIDException: Broker: rec1_master - Client:
nc1_master_rec2_inbound_rec1_master already connected from
vm://rec1_master#0 | org.apache.activemq.broker.TransportConnection |
triggerStartAsyncNetworkBridgeCreation: remoteBroker=unconnected,
localBroker= vm://rec1_master#2
2013-05-27 14:51:20,980 | INFO  | Network connection between
vm://rec1_master#2 and tcp://corerec2:62618 shutdown due to a local error:
javax.jms.InvalidClientIDException: Broker: rec1_master - Client:
nc1_master_rec2_inbound_rec1_master already connected from
vm://rec1_master#0 |
org.apache.activemq.network.DemandForwardingBridgeSupport |
triggerStartAsyncNetworkBridgeCreation: remoteBroker=unconnected,
localBroker= vm://rec1_master#2
2013-05-27 14:51:20,984 | INFO  | rec1_master bridge to master_rec2 stopped
| org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ
BrokerService[rec1_master] Task-210
2013-05-27 14:51:21,987 | INFO  | Establishing network connection from
vm://rec1_master?async=false&network=true to
failover:(tcp://corerec2:62618,nio://slave2:62602)?randomize=false&maxReconnectAttempts=0
| org.apache.activemq.network.DiscoveryNetworkConnector | Simple Discovery
Agent-2
2013-05-27 14:51:21,989 | INFO  | Successfully connected to
tcp://corerec2:62618 |
org.apache.activemq.transport.failover.FailoverTransport | ActiveMQ Failover
Worker: 1840307907
2013-05-27 14:51:21,994 | INFO  | Network connection between
vm://rec1_master#4 and tcp://corerec2:62618(master_rec2) has been
established. | org.apache.activemq.network.DemandForwardingBridgeSupport |
triggerStartAsyncNetworkBridgeCreation: remoteBroker=unconnected,
localBroker= vm://rec1_master#4
2013-05-27 14:51:30,974 | INFO  | Network Could not shutdown in a timely
manner | org.apache.activemq.network.DemandForwardingBridgeSupport |
ActiveMQ BrokerService[rec1_master] Task-205
2013-05-27 14:51:30,974 | INFO  | rec1_master bridge to master_rec2 stopped
| org.apache.activemq.network.DemandForwardingBridgeSupport | ActiveMQ
BrokerService[rec1_master] Task-205



--
View this message in context: http://activemq.2283324.n4.nabble.com/Networked-brokers-dropping-suppressing-messages-tp4662747p4667512.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message