activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohit Anchlia <>
Subject Re: EOFException
Date Thu, 31 Jan 2013 01:58:07 GMT
Thanks for looking:



    <!-- Allows us to use system properties as variables in this
configuration file -->

    <broker xmlns="" brokerName="" persistent="true" dataDirectory="${}">

        <!-- Destination specific policies using destination names or
wildcards -->
                    <policyEntry queue=">" producerFlowControl="true"
memoryLimit="500mb" optimizedDispatch="true" useCache="false">
                          <individualDeadLetterStrategy queuePrefix="DLQ."
useQueueForQueueMessages="true" />
                    <policyEntry topic=">" producerFlowControl="true"

        <!-- Use the following to configure how ActiveMQ is exposed in JMX
            <managementContext createConnector="true"/>

            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
            <networkConnector uri="static:(tcp://
prefetchSize="1" conduitSubscriptions="true" networkTTL="3"/>

            <kahaDB directory="${}/"
enableJournalDiskSyncs="false" indexWriteBatchSize="10000"
indexCacheSize="1000" journalMaxFileLength="200 gb"/>

        <!--  The maximum amount of space the broker will use before
slowing down producers -->
                    <memoryUsage limit="600 mb"/>
                    <storeUsage limit="240 gb" name="foo"/>
                    <tempUsage limit="1000 mb"/>

        <!-- The transport connectors ActiveMQ will listen to -->
            <transportConnector name="openwire" uri="nio://"


        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"/>


On Wed, Jan 30, 2013 at 4:15 PM, Christian Posta

> 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 <
> >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:// failed, reason:,
> > 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*
> twitter: @christianposta

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message