John,
It might have something to do with either a) your JVM or b) the
operating system on the machine in question, or possibly the combination
of the two.
I'd just check to make sure you've got a good JVM installed, the latest
version, etc. I'm not aware of any command line switches or anything to
the JVM which, for example, forces it to use threads instead of seperate
processes.
Your question was probably not answered on this mailing list mostly
because it sounds more like a JVM related question, not an XMLRPC
library related question.
As far as the WebServer class, it only uses threads for connection
requests. There's no choices otherwise, at least that I'm aware of.
The point is though, that the JVM is likely turning these threads into
separate processes, maybe because of lack of threading support in the
operating system kernel itself.
Adam
John Luxford wrote:
Hi folks,
I posted this question a few weeks ago and didn't see any response to
it, so I thought I'd try again. If there's any additional info I can
provide that would help, please let me know.
Thanks in advance,
Lux
On 23-Sep-05, at 9:39 AM, John Luxford wrote:
Hi everyone,
I've got an application using the org.apache.xmlrpc.WebServer class
and I've noticed that on most machines we run it on it is contained
to a single system process and presumably uses threads to divvy out
requests to. On one machine however, starting the same app running
suddenly creates a dozen processes instead of just one, which would
lead me to believe it's creating new processes instead of threads on
that machine.
Is this the case, and if so, is there any way to force it to use a
single process?
Thanks in advance,
Lux
