Re: many java processes on debian when spawning enhydra

Thanks Stefan, your response is reassuring and makes a
lot of sense.  This was my first Linux test deployment
and it threw me off a bit.  Windows tends to hide
things a bit (ok, a lot).  

thanks again,
David

--- Stefan Armbruster <sarmbruster@xxxxxx> wrote:
> Hi David,
> 
> not speaking especially on Enhydra 5, more generally
> on Java on Linux...
> 
> Quoting a post on some other mailinglist 
> "I think what you're looking for is the difference
> between green threads
> and
> native threads. If you search for this it
> java.sun.com you should be able to
> find all about it. In short it boils down to mapping
> Java threads to native
> OS threads or emulating threads inside the Java VM
> (=green threads). Both
> have their advantages and disadvantages. For
> example, if I recall correctly,
> green threads perform better because there is no
> need for context switching
> at kernel level; however, you need to treat green
> threads as cooperative
> instead of pre-emptive multi-threading, so you need
> to use Thread.yield() or
> sleep() or do I/O, for example"
> 
> 30 threads is fine. I'm running Tomcat with ~20
> Applications deployed
> makeing a total of ~200 threads.
> 
> Regards,
> Stefan
> 
> Am Mon, 2003-07-21 um 18.46 schrieb David Young:
> > I'm getting at least 30 spawned Java processes
> when I
> > startup enhydra5.1 on our debian box.  Is this
> normal?
> >  If not, any suggestions?
> > 
> > thanks,
> > David
> > _______________________________________________
> > Enhydra mailing list
> > Enhydra@xxxxxxxxxxx
> >
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra
> 
> _______________________________________________
> Enhydra mailing list
> Enhydra@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra


=====