Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
From: "Pon Umapathy K.S." <umapathy@cisco.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Subject: RE: Tomcat's ThreadPool and InheritableThreadLocal variables
Date: Thu, 4 Dec 2003 20:16:41 +0530
Message-ID: <PKENLKKHMAIHMKALBABDKEIKECAA.umapathy@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <9C5166762F311146951505C6790A9CF8013DF7CE@US-VS1.corp.mpi.com>
Importance: Normal

> -----Original Message-----
> From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
> Sent: Thursday, December 04, 2003 7:40 PM
> To: Tomcat Users List
> Subject: RE: Tomcat's ThreadPool and InheritableThreadLocal variables
>
>
>
> Howdy,
> Why don't you just test it if it's so urgent instead of waiting for a
> reply from us? ;)
>

Thanks for responding.I had already kinda tested it.But thought,i would get
it confirmed from the gurus. ;)

> I think the variables will stay with the thread, as they're not bound to
> the lifetime of the request.  This is a far from optimal design
> (actually I think InheritableThreadLocal is just evil and shouldn't be
> used).You might want to try tomcat 5 and its request listeners, as
> these provide the proper lifecycle for what you're trying to do.
>

The problem is it's already decided that we are to use tomcat 3.3.1a for our
application and we have to live with it.I'll just try to find some way to
work around this issue.

Is there some release note or something regarding this which i can refer to?

> Yoav Shapira
> Millennium ChemInformatics
>
>
> >-----Original Message-----
> >From: Pon Umapathy K.S. [mailto:umapathy@cisco.com]
> >Sent: Thursday, December 04, 2003 7:09 AM
> >To: Tomcat List
> >Subject: Tomcat's ThreadPool and InheritableThreadLocal variables
> >
> >Hi,
> > A query regarding InheritableThreadLocal variables in the tomcat
> context.
> >
> >To explain the problem i am facing:
> > If i am correct,for each request,tomcat uses a thread from it's
> threadpool
> >to process the request.
> > Suppose during one of these requests,i set the value of a
> >InheritableThreadLocal variable.Once this request is processed,the
> thread
> >will be available for use from the ThreadPool.Does tomcat reset the
> value
> >of
> >the InheritableThreadLocal variable which was set by the previous
> request
> >processing?(it should,ideally). The tomcat version i am using is
> >3.3.1a.Also
> >use the struts framework model.
> >
> > It seems to me that the InheritableThreadLocal value which was set by
> a
> >previous request on a thread is still retained when that thread is
> reused
> >for processing another request.Are there any known issues regarding
> this?
> > Would be really helpful if someone can answer this.A bit urgent.Thanks
> in
> >advance.
> >
> >Regards,
> >Umapathy
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
>
> This e-mail, including any attachments, is a confidential
> business communication, and may contain information that is
> confidential, proprietary and/or privileged.  This e-mail is
> intended only for the individual(s) to whom it is addressed, and
> may not be saved, copied, printed, disclosed or used by anyone
> else.  If you are not the(an) intended recipient, please
> immediately delete this e-mail from your computer system and
> notify the sender.  Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org