Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.218.214 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=nigzlY1sPDVhnSA9Ow1SnXsHmYE10TDNttx6Sf6NI/3MBV9X+t8rgXXaz7bhA4CImj
         pzUyrE5psHvC6KhzfDlms21+yJp4k4/JCXthHcl4cEzkuEuDm7jJVvgH2tOnOfUMZ3+A
         zgJ52dwdV0Le94JrWF2eOMmX/N1o/ShSGol6s=
MIME-Version: 1.0
In-Reply-To: <24401653.post@talk.nabble.com>
References: <24401653.post@talk.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Fri, 10 Jul 2009 09:55:45 +0200
Message-ID: <5380c69c0907100055w168d3cc3q19f8e38e4636d7d5@mail.gmail.com>
Subject: Re: JMS publish consuming sockets?
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi

Are your routes InOnly? Eg you do not consume from a JMS queue?

There was a bad default in camel-jms. See the warning on the JMS component =
page.
Maybe it can help.

And have you tried asking on the ActiveMQ forums. Must be an issue
they have heard before.
AMQ have a ton of settings to adjust.


On Thu, Jul 9, 2009 at 2:09 AM, huntc<huntc@mac.com> wrote:
>
> Hi guys,
>
> I've just noticed a problem with my 1.6.0 based application. I believe it
> may be establishing a connection with AMQ for the purposes of publishing =
on
> a topic, and then while retaining that connection, opening another
> connection the next time it needs to publish. This is just a hypothesis b=
ut
> after a good period of time (like a month or two), AMQ runs out of file
> descriptors and complains thus:
>
>
> Could not accept connection : Too many open files
>
>
> Here's my Camel route:
>
>
> from("direct:publishCAT21FeatureCollection").process(
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0cat21Featu=
reCollectionToGMLTransformer).to(
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0"activemq-=
sender:topic:com.classactionpl.javaFlightTopic");
>
>
>
> My spring config for AMQ is (activemq-receiver is defined but actually no=
t
> used by my app at the moment):
>
>
> =A0 =A0 =A0 =A0&lt;bean id=3D"activeMQConnectionFactory"
> class=3D"org.apache.activemq.ActiveMQConnectionFactory"&gt;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;property name=3D"brokerURL"
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0value=3D"${com.classaction=
pl.asterixservices.brokerurl}" /&gt;
> =A0 =A0 =A0 =A0&lt;/bean&gt;
> =A0 =A0 =A0 =A0&lt;bean id=3D"activemq-receiver"
> class=3D"org.apache.activemq.camel.component.ActiveMQComponent"&gt;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;property name=3D"connectionFactory" re=
f=3D"activeMQConnectionFactory"
> /&gt;
> =A0 =A0 =A0 =A0&lt;/bean&gt;
> =A0 =A0 =A0 =A0&lt;bean id=3D"activemq-sender"
> class=3D"org.apache.activemq.camel.component.ActiveMQComponent"&gt;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;property name=3D"connectionFactory"&gt=
;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;bean class=3D"org.apac=
he.activemq.pool.PooledConnectionFactory"&gt;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;constr=
uctor-arg ref=3D"activeMQConnectionFactory" /&gt;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;/bean&gt;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0&lt;/property&gt;
> =A0 =A0 =A0 =A0&lt;/bean&gt;
>
>
> and the broker url:
>
>
> com.classactionpl.asterixservices.brokerurl=3Dfailover:tcp://localhost:61=
616
>
>
> Here's what I see in my Camel application's log file:
>
>
> 2009-07-09 09:47:09,607 [ActiveMQ Task =A0] INFO =A0FailoverTransport
> - Successfully reconnected to tcp://localhost:61616
> 2009-07-09 09:47:25,123 [127.0.0.1:61616] WARN =A0FailoverTransport
> - Transport failed to tcp://localhost:61616 , attempting to automatically
> reconnect due to: java.net.SocketException: Connection reset
> 2009-07-09 09:47:25,132 [ActiveMQ Task =A0] INFO =A0FailoverTransport
> - Successfully reconnected to tcp://localhost:61616
> 2009-07-09 09:48:35,279 [127.0.0.1:61616] WARN =A0FailoverTransport
> - Transport failed to tcp://localhost:61616 , attempting to automatically
> reconnect due to: java.io.EOFException
> 2009-07-09 09:48:35,291 [ActiveMQ Task =A0] INFO =A0FailoverTransport
> - Successfully reconnected to tcp://localhost:61616
> 2009-07-09 09:48:35,337 [ActiveMQ Task =A0] INFO =A0FailoverTransport
> - Successfully connected to tcp://localhost:61616
> 2009-07-09 09:49:35,478 [ActiveMQ Task =A0] INFO =A0FailoverTransport
> - Successfully connected to tcp://localhost:61616
> 2009-07-09 09:51:28,171 [ActiveMQ Task =A0] INFO =A0FailoverTransport
> - Successfully connected to tcp://localhost:61616
> 2009-07-09 09:52:55,163 [ActiveMQ Task =A0] INFO =A0FailoverTransport
> - Successfully connected to tcp://localhost:61616
>
>
> I wouldn't expect so many failovers although it might just be the
> PooledConnectionFactory filling up its pool of connections.
>
> Any ideas?
>
> Kind regards,
> Christopher
> --
> View this message in context: http://www.nabble.com/JMS-publish-consuming=
-sockets--tp24401653p24401653.html
> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com=
.
>


--=20
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus