I tried running the memory usage stats script Pete Freitag describes
here:
http://www.petefreitag.com/item/115.cfm
And it displays this info:
Free Allocated Memory: 250mb
Total Memory Allocated: 253mb
Max Memory Available to JVM: 253mb
% of Free Allocated Memory: 99%
% of Available Memory Allocated: 100%
Evidently JRun thinks it is allocated ~256mb of memory, the amount I
assigned to it in the jvm.config file.
But what Windows thinks is a whole different issue. I would think that
in this situation, what Windows thinks trumps what JRun thinks. Is this
a Windows memory management issue? Not that I'm surprised.
I'm guessing that a memory leak program like fork.cfm listed below
probably wasn't the best program to test this situation with.
At this point, I think I'm confident enough to step forward with actual
load balance testing. I wanted to get this issue out of the way before I
put anything into production. I'll just have to make sure that I don't
write scripts that cause memory leaks. :)
Chris Peters
-----Original Message-----
From: Peters, Chris
Sent: Tuesday, October 05, 2004 10:51 AM
To: CF-Talk
Subject: ColdFusion MX 6.1 Enterprise as JRun J2EE EAR connected to IIS
Has anyone ever installed CF under this configuration?
I have installed several ColdFusion instances on top of JRun and
connected each instance to a respective IIS web site.
I then created a custom jvm.config file for one of the instances and set
-XX:MaxPermSize=256m. I set up a new Windows Service that starts the
JRun instance using the custom jvm.config file.
To test this memory setting, I created a malicious file called fork.cfm
and placed it on the server:
<cffunction name="fork">
Forking...<br />
<cfset fork()>
<cfset fork()>
</cffunction>
<cfset fork()>
As you can see that should cause memory problems on the server (which it
does).
To test this setting, a couple of people on my team refreshed the
daylights out of this script from browers on our local machines, and I
watched the Windows Processes on the server. The amount of memory
displayed for that particluar jrun.exe instance went well past 256 MB,
and topped out somewhere near 400 MB.
If I set the JRun instance to only use 256 MB, why would the Windows
Process top out at 400 MB? Does IIS have a mind of its own in this
configuration, and did JRun actually stop at 256 MB even though Windows
thought it was processing 400 MB?
Of course, Macromedia is unwilling to help me out unless I break out a
credit card, which I am trying to avoid.
I'm asking you guys and several other lists. For sake of documentation,
if this gets answered elsewhere, I'll be sure to post my findings here!
Thanks for any insights you can provide.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
