On 1/29/06, Nikola Milutinovic <[EMAIL PROTECTED]> wrote:
> Leon Rosenberg wrote:
> > On 1/27/06, Duan, Nick <[EMAIL PROTECTED]> wrote:
> >
> >> Spawning your own threads in a web app is usually not recommended.
> >>
> >
> > Why?
> >
>
> Well, you have to take care of them manually or some code has
Leon Rosenberg wrote:
> On 1/27/06, Duan, Nick <[EMAIL PROTECTED]> wrote:
>
>> Spawning your own threads in a web app is usually not recommended.
>>
>
> Why?
>
Well, you have to take care of them manually or some code has to do it.
If forgotten, those threads can stop TC from shutting d
On 1/27/06, Duan, Nick <[EMAIL PROTECTED]> wrote:
> Spawning your own threads in a web app is usually not recommended.
Why?
regards
Leon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECT
Message-
From: Gehl, Pascal [mailto:[EMAIL PROTECTED]
Sent: Friday, January 27, 2006 9:02 AM
To: users@tomcat.apache.org
Subject: Asynchronous messaging in tomcat
Hi,
I know we are not supposed to do this but is there a big inconvenience
to do asynchronous message consuming in tomcat 5+ (by
Hi,
I know we are not supposed to do this but is there a big inconvenience
to do asynchronous message consuming in tomcat 5+ (by spawning a daemon
thread for my message listener ?)
Is it true that if a I create a thread on my own I won't have access to
the tomcat JNDI context ?
I ask this becau
