Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.215.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGXzonP-aMtLCEGwnkWfsBXRZZbGe2YJVR5QEYkC404iLk+h-w@mail.gmail.com>
References: 
 <CAGXzonP-aMtLCEGwnkWfsBXRZZbGe2YJVR5QEYkC404iLk+h-w@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 31 Aug 2011 13:38:02 +0200
Message-ID: 
 <CAGB5yNn+y7fG8MZKEE2Jb-gcy6FeRQVV+2iCasky73cGqe8UpQ@mail.gmail.com>
Subject: Re: pool thread dies after FTP error
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi

The ScheduledPollConsumer have been improved in later releases to be
more resilient and avoid terminating due unhandled exceptions being
thrown.


On Wed, Aug 31, 2011 at 11:24 AM, Sorin Silaghi <sorin7486@gmail.com> wrote=
:
> Hi all,
>
>
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 We have a problem with FTP consumers dying on=
 errors. It
> happened a couple of times on one of our servers but we can't really
> reproduce it. I've looked at the code and I can't figure out why it happe=
ns.
> The only possibilities are that ScheduledPollConsumer throws an exception
> that kills the thread or the consumer gets suspended and never goes back.
> I'm not sure what this last part means but we'll do some more tests and I=
'll
> do some debug if we can reproduce it.
>
>
> Here's the stack trace:
>
> http://pastebin.com/niXtXKJ4
>
> best regards,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Sorin
>


--=20
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/