On 23 August 2010 21:56, André Warnier wrote:
> and can someone finally explain what "spwaning child processes" means ?
>
It's a UNIXism - a fork() call spawns a child process from a parent
process. Not sure how much further back it goes into the deep, dark and
slightly dank dungeon of operatin
On Mon, Aug 23, 2010 at 10:56 PM, André Warnier wrote:
> and can someone finally explain what "spwaning child processes" means ?
> What are you all doing to these kids ?
>
I apologise about the typo and I deliberately didn't want to use the
term Threads as I was unsure if threads should be used.
and can someone finally explain what "spwaning child processes" means ?
What are you all doing to these kids ?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
On 8/23/2010 11:02 AM, Caldarale, Charles R wrote:
>> From: Wesley Acheson [mailto:wesley.ache...@gmail.com]
>> Subject: Re: How to spwan child processes.
>>
>> Thats my point I thought new Thread() was something I could
> From: Wesley Acheson [mailto:wesley.ache...@gmail.com]
> Subject: Re: How to spwan child processes.
>
> Sorry I don't even know where the specs live. I thought I saw it on
> sun some time ago but can't find it.
I usually search by JSR number.
> If I've offend
On Mon, Aug 23, 2010 at 6:28 PM, Caldarale, Charles R
wrote:
>> From: Wesley Acheson [mailto:wesley.ache...@gmail.com]
>> Subject: Re: How to spwan child processes.
>>
>> "Certain J2EE/JEE applications (for instance those running in EJB and
>> Web containers)
> From: Wesley Acheson [mailto:wesley.ache...@gmail.com]
> Subject: Re: How to spwan child processes.
>
> "Certain J2EE/JEE applications (for instance those running in EJB and
> Web containers) must not spawn new threads; instead all work should be
> performed on the m
On Mon, Aug 23, 2010 at 5:02 PM, Caldarale, Charles R
wrote:
>> From: Wesley Acheson [mailto:wesley.ache...@gmail.com]
>> Subject: Re: How to spwan child processes.
>>
>> Thats my point I thought new Thread() was something I couldn't
>> do (by JEE specs)
>
&g
..
because the container already does so.
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Monday, August 23, 2010 10:02 AM
To: Tomcat Users List
Subject: RE: How to spwan child processes.
> From: Wesley Acheson [mailto:wesley.ache...@gmail.com]
> Subject
> From: Wesley Acheson [mailto:wesley.ache...@gmail.com]
> Subject: Re: How to spwan child processes.
>
> Thats my point I thought new Thread() was something I couldn't
> do (by JEE specs)
I'm curious - where in any of the Java EE specs did you come across that?
> Q
On Mon, Aug 23, 2010 at 4:27 PM, Ronald Klop wrote:
> class OtherAppNotifier implements Runnable {
> public void run() {
> ... doe something...
> }
> }
>
> In your servlet:
>
> doGet() {
> processUserRequest();
> new Thread(new OtherAppNotifier()).start();
> }
>
Thats my point I though
class OtherAppNotifier implements Runnable {
public void run() {
... doe something...
}
}
In your servlet:
doGet() {
processUserRequest();
new Thread(new OtherAppNotifier()).start();
}
You can also use java.util.TimerTask or some other threadpool thing if this
spawns too many t
12 matches
Mail list logo
