Thanks for looking: failover:(tcp:// daamq300.ie.i.net:61616?connectionTimeout=10000&soTimeout=8000&wireFormat.tcpNoDelayEnabled=true,tcp://daamq304.ie.i.net:61616?connectionTimeout=10000&soTimeout=8000&wireFormat.tcpNoDelayEnabled=true,tcp://daamq305.ie.i.net:61616?connectionTimeout=10000&soTimeout=8000&wireFormat.tcpNoDelayEnabled=true,tcp://daamq306.ie.i.net:61616?connectionTimeout=10000&soTimeout=8000&wireFormat.tcpNoDelayEnabled=true)?randomize=true&jms.prefetchPolicy.all=1
<beans xmlns="http://www.springframework.org/schema/beans"; xmlns:amq="http://activemq.apache.org/schema/core"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd";> <!-- Allows us to use system properties as variables in this configuration file --> <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/> <broker xmlns="http://activemq.apache.org/schema/core"; brokerName=" daamq305.ie.i.net" persistent="true" dataDirectory="${activemq.data}"> <!-- Destination specific policies using destination names or wildcards --> <destinationPolicy> <policyMap> <policyEntries> <policyEntry queue=">" producerFlowControl="true" memoryLimit="500mb" optimizedDispatch="true" useCache="false"> <deadLetterStrategy> <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true" /> </deadLetterStrategy> </policyEntry> <policyEntry topic=">" producerFlowControl="true" memoryLimit="500mb"> </policyEntry> </policyEntries> </policyMap> </destinationPolicy> <!-- Use the following to configure how ActiveMQ is exposed in JMX --> <managementContext> <managementContext createConnector="true"/> </managementContext> <!-- The store and forward broker networks ActiveMQ will listen to. We'll leave it empty as duplex network will be configured by another broker Take a look at activemq-static_network-broker2.xml for example --> <networkConnectors> <networkConnector uri="static:(tcp://daamq300.ie.i.net:61616 ,tcp://daamq304.ie.i.net:61616,tcp://daamq306.ie.i.net:61616)" prefetchSize="1" conduitSubscriptions="true" networkTTL="3"/> </networkConnectors> <persistenceAdapter> <kahaDB directory="${activemq.data}/daamq305.ie.i.net/kahadb" enableJournalDiskSyncs="false" indexWriteBatchSize="10000" indexCacheSize="1000" journalMaxFileLength="200 gb"/> </persistenceAdapter> <!-- The maximum amount of space the broker will use before slowing down producers --> <systemUsage> <systemUsage> <memoryUsage> <memoryUsage limit="600 mb"/> </memoryUsage> <storeUsage> <storeUsage limit="240 gb" name="foo"/> </storeUsage> <tempUsage> <tempUsage limit="1000 mb"/> </tempUsage> </systemUsage> </systemUsage> <!-- The transport connectors ActiveMQ will listen to --> <transportConnectors> <transportConnector name="openwire" uri="nio://0.0.0.0:61616" enableStatusMonitor="true"/> </transportConnectors> </broker> <!-- Enable web consoles, REST and Ajax APIs and demos Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details --> <import resource="jetty.xml"/> </beans> On Wed, Jan 30, 2013 at 4:15 PM, Christian Posta <christian.po...@gmail.com>wrote: > Please post your broker config and what URL you're using on the client > side. EOFException in the broker logs usually means the client didn't > disconnect properly > > > On Wed, Jan 30, 2013 at 5:11 PM, Mohit Anchlia <mohitanch...@gmail.com > >wrote: > > > With nio we often see this error even though all MQ servers are up and > > running. We are using 5.7.0. Client then hangs and failover never > > reconnects. > > > > WARN transport.failover.FailoverTransport [ActiveMQ Transport: > Transport > > (tcp://100.145.3.166:61616) failed, reason: java.io.EOFException, > > attempting to automatically reconnect > > > > Right after this error I check on netstat and I see TIMED_WAIT as if the > > connection was killed. And after that mq client never reconnects. Is this > > some issue that has been experienced before and the second problem is > that > > failover doesn't seem to be working > > > > > > -- > *Christian Posta* > http://www.christianposta.com/blog > twitter: @christianposta >
