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 james.strachan@gmail.com
 designates 209.85.220.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=N06QHT+vc8KMOrhQTOb+pRLU9RmR5EmpFDGAapfogp3FDTxALawnGiQg/SgYXAGcXk
         0DOCyMxYLAG0yVjhTZDA6RCblQIK4FQPCAmK5KEPTIhMJd/TGK5mMcs8+7AEpeHhhqe3
         mVM/n9rUjXxSZB7/7WVI660BnFikGTYSKIqt8=
MIME-Version: 1.0
In-Reply-To: <5380c69c0903242208o6922e1cj4280d4527a901e4d@mail.gmail.com>
References: <22202167.post@talk.nabble.com> <22500700.post@talk.nabble.com>
	<5380c69c0903132320m7546444bm6a3d4c4077557f2c@mail.gmail.com>
	<22537092.post@talk.nabble.com> <22538055.post@talk.nabble.com>
	<5380c69c0903160623r7ecdfc28lde28362e70386620@mail.gmail.com>
	<22539534.post@talk.nabble.com>
 <5380c69c0903160835xaec293dkae61016480602330@mail.gmail.com>
	<22681944.post@talk.nabble.com>
 <5380c69c0903242208o6922e1cj4280d4527a901e4d@mail.gmail.com>
Date: Wed, 25 Mar 2009 09:02:39 +0000
Message-ID: <ec6e67fd0903250202n2313b50etbf4912809e6f7385@mail.gmail.com>
Subject: Re: Delayer: "Transport disposed" at JVM-Shutdown
From: James Strachan <james.strachan@gmail.com>
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

We maybe need to introduce some clean shutdown mechanism into
consumers; so we can tell all the consumers we're about to shutdown;
then they can gracefully stop processing the current route's message -
then we actually stop the consumers (then the endpoints & components
etc). Stopping routes midway through (eg cancelling timers) could lead
to other kinds of warning messages. I guess the downside of this could
make shutdown take a while to complete - also if routes invoke other
routes you still could have issues where one route wants to send to
another route which is now closed.

So its always gonna be pretty hard to shut down Camel cleanly without
any error messages at all. Maybe we just hide error messages once
shutdown starts? :)


On 25/03/2009, Claus Ibsen <claus.ibsen@gmail.com> wrote:
> On Tue, Mar 24, 2009 at 3:42 PM, Markus Reil <gistenjunge@gmx.de> wrote:
>>
>> Hi,
>>
>> thanks for your help.
>> But I am still experiencing the same problem. The sleep does not get
>> interrupted (2.0-M1).
>> Do you have any idea why this happens? Let me know if you need more
>> information.
> Can you show the complete route? And point out where the message is
> when you shutdown.
>
>
>>
>> Thanks,
>> Markus
>> --
>> View this message in context:
>> http://www.nabble.com/Delayer%3A-%22Transport-disposed%22-at-JVM-Shutdown-tp22202167p22681944.html
>> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
>


-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/