activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From liangwb2001 <liangwb2...@gmail.com>
Subject Network Of Brokers member print error continued after other one member restart
Date Wed, 30 May 2012 01:20:40 GMT
I'm test A,B,C three broker clusters in 5.6.0, when restart A broker, B and C
brokers log error, the following is my case;
1. 3 brokers topology:
	ip				hostname		brokerName
	192.168.0.38	t4				liangtest1
	192.168.0.48	t1				liangtest2
	192.168.0.253	debian160		liangtest3
2. broker config:
	<broker xmlns="http://activemq.apache.org/schema/core"
brokerName="liangtest1" dataDirectory="${activemq.data}"
networkConnectorStartAsync="true">
        <destinationPolicy>
            <policyMap>
                <policyEntries>
                    <policyEntry queue=">" producerFlowControl="false"
memoryLimit="64mb" enableAudit="false">
						<networkBridgeFilterFactory>
							<conditionalNetworkBridgeFilterFactory replayWhenNoConsumers="true"/>
						</networkBridgeFilterFactory>
                    </policyEntry>
                    <policyEntry topic=">" producerFlowControl="false"
memoryLimit="64mb">
                    </policyEntry>
                </policyEntries>
            </policyMap>
        </destinationPolicy>
        <managementContext>
            <managementContext createConnector="false"/>
        </managementContext>
        <networkConnectors>
			<networkConnector uri="multicast://239.255.2.3:6156"
name="queues_connector" networkTTL="6"
decreaseNetworkConsumerPriority="true" conduitSubscriptions="false">
				<excludedDestinations>
					<topic physicalName=">"/>
				</excludedDestinations>
				</networkConnector>
					<networkConnector uri="multicast://239.255.2.3:6156"
name="topic_connector" networkTTL="3" conduitSubscriptions="true">
						<excludedDestinations>
							<queue physicalName=">"/>
                        </excludedDestinations>
					</networkConnector>
				</networkConnectors>
		</networkConnectors>
		<persistenceAdapter>
			<kahaDB directory="${activemq.base}/data/kahadb"
enableJournalDiskSyncs="false" indexWriteBatchSize="10000"
indexCacheSize="1000"/>
        </persistenceAdapter>
        <systemUsage>
			<systemUsage>
				<memoryUsage>
					<memoryUsage limit="1 gb" />
				</memoryUsage>
				<storeUsage>
					<storeUsage limit="100 gb" />
				</storeUsage>
				<tempUsage>
					<tempUsage limit="100 gb" />
				</tempUsage>
			</systemUsage>
		</systemUsage>
        <transportConnectors>
            <transportConnector name="openwire" uri="tcp://0.0.0.0:61716"
discoveryUri="multicast://239.255.2.3:6156" auditNetworkProducers="true"
updateClusterClients="true"
				rebalanceClusterClients="true" updateClusterClientsOnRemove="true"/>
        </transportConnectors>
    </broker>
3. when stop liangtest1:
	liangtest2 log:
		WARN | Network connection between vm://liangtest2#2 and
tcp://t1/192.168.0.38:61716 shutdown due to a remote error:
java.io.EOFException
		INFO | liangtest2 bridge to liangtest1 stopped
		WARN | Network connection between vm://liangtest2#0 and
tcp://t1/192.168.0.38:61716 shutdown due to a remote error:
java.io.EOFException
		INFO | liangtest2 bridge to liangtest1 stopped
	liangtest3 log continued:
		INFO | liangtest3 bridge to liangtest1 stopped
		WARN | Network connection between vm://liangtest3#0 and
tcp://t4/192.168.0.38:61716 shutdown due to a remote error:
java.io.EOFException
		INFO | liangtest3 bridge to liangtest1 stopped
		INFO | Establishing network connection from
vm://liangtest3?async=false&network=true to tcp://t4:61716
		INFO | Establishing network connection from
vm://liangtest3?async=false&network=true to tcp://t4:61716
		INFO | liangtest3 Shutting down
		INFO | liangtest3 Shutting down
		WARN | Could not start network bridge between:
vm://liangtest3?async=false&network=true and: tcp://t4:61716 due to:
java.net.ConnectException: Connection refused
		WARN | Could not start network bridge between:
vm://liangtest3?async=false&network=true and: tcp://t4:61716 due to:
java.net.ConnectException: Connection refused
   then start liangtest1:
    liangtest2 log continued:
		 INFO | Establishing network connection from
vm://liangtest2?async=false&network=true to tcp://t1:61716
		 INFO | Establishing network connection from
vm://liangtest2?async=false&network=true to tcp://t1:61716
		 WARN | Failed to add Connection ID:debian160-39660-1338282999558-76:1,
reason: javax.jms.InvalidClientIDException: Broker: liangtest2 - Client:
topic_connector_liangtest3_outbound already connected from
tcp://192.168.0.253:40488
		 WARN | Async error occurred: javax.jms.InvalidClientIDException: Broker:
liangtest2 - Client: topic_connector_liangtest3_outbound already connected
from tcp://192.168.0.253:40488
		javax.jms.InvalidClientIDException: Broker: liangtest2 - Client:
topic_connector_liangtest3_outbound already connected from
tcp://192.168.0.253:40488
				at
org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:223)
				at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85)
				at
org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:65)
				at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85)
				at
org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:85)
				at
org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:91)
				at
org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:715)
				at
org.apache.activemq.broker.jmx.ManagedTransportConnection.processAddConnection(ManagedTransportConnection.java:79)
				at
org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:139)
				at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:292)
				at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:150)
				at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
				at
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
				at
org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:229)
				at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
				at
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:222)
				at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:204)
				at java.lang.Thread.run(Thread.java:619)
		 WARN | Failed to add Connection ID:debian160-39660-1338282999558-77:1,
reason: javax.jms.InvalidClientIDException: Broker: liangtest2 - Client:
queues_connector_liangtest3_outbound already connected from
tcp://192.168.0.253:40487
    liangtest3 log continued:
		 INFO | Establishing network connection from
vm://liangtest3?async=false&network=true to tcp://t1:61716
		 INFO | Establishing network connection from
vm://liangtest3?async=false&network=true to tcp://t1:61716
		 WARN | Failed to add Connection ID:debian160-39660-1338282999558-77:2,
reason: javax.jms.InvalidClientIDException: Broker: liangtest3 - Client:
queues_connector_liangtest2_inbound_liangtest3 already connected from
vm://liangtest3#6
		 WARN | Failed to add Connection ID:debian160-39660-1338282999558-76:2,
reason: javax.jms.InvalidClientIDException: Broker: liangtest3 - Client:
topic_connector_liangtest2_inbound_liangtest3 already connected from
vm://liangtest3#4
		 INFO | Network connection between vm://liangtest3#149 and
tcp://t1/192.168.0.48:61716 shutdown due to a local error:
javax.jms.InvalidClientIDException: Broker: liangtest3 - Client:
queues_connector_liangtest2_inbound_liangtest3 already connected from
vm://liangtest3#6
		 INFO | Network connection between vm://liangtest3#148 and
tcp://t1/192.168.0.48:61716 shutdown due to a local error:
javax.jms.InvalidClientIDException: Broker: liangtest3 - Client:
topic_connector_liangtest2_inbound_liangtest3 already connected from
vm://liangtest3#4

	I don't know what wrong with it.

--
View this message in context: http://activemq.2283324.n4.nabble.com/Network-Of-Brokers-member-print-error-continued-after-other-one-member-restart-tp4652814.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message