Multiple instances of jrun.exe running?

[NuckNuck]

Is it common for there to be more than one instance of jrun.exe running in a non-clustered installation of CF7? There have been episodes where jrun.exe seems to get taxed on moderately size queries. After looking at Task Manager on Win2K3 server - there are sometimes 3 or 4 instances of jrun.exe running. The first instance is usually very high (ex. 450 MB) while the other instance(s) hover around the 10-15 MB mark and remain constant. Does this sound like an issue that can be controlled by CFAdmin or are there issues with our configuration:

Win2K3 Server (VMWare instance)
CF7.01 (yes we know it needs a patch)
512 MB RAM

Any thoughts on this is appreciated.

Thanks.

[Newsgroup_User]

> Is it common for there to be more than one instance of jrun.exe running in a
> non-clustered installation of CF7?

Yes.

A multi-server install (not a clustered) of CF could well have one instance
of JRUN.EXE running for each CF instance. There's usually at least two: one
for the initial CF instance, and one for the JMC. You can switch the JMC
one off (starting it on the off-chance you need it, which is almost never).


> The first instance is usually very high (ex. 450 MB) while the other

That's not especially high for a CF app server. We generally allocate the
max 1.3GB (on Windows) to the JVM that each CF instance is using.


> 512 MB RAM

OK, that's not even enough RAM for a PC workstation these days, let alone a
server! W2k3 itself needs around a minimum of 400MB to run. The default
install of CF will want another 512MB.

I would not run a desktop PC on less than 2GB RAM these days. And make
that 4GB for a server. A low-spec'ed one.

--
Adam