Another thing to check is the Java Heap Size setting.  We have details on our blog re 
changing this if necessary here 

http://www.webapper.net/index.cfm?fuseaction=Fuseblog.ShowComments&ArticleID=20021111014905

This does relate to a Websphere CFMX installation but hopefully is a guide.

Kind Regards - Mike Brunt

Original Message -----------------------
>I can only find errors that I have encountered during development (i.e.
>template not found for a cfinclude statement) nothing that gives any
>info as to why this server might be so slow.
>

A couple quick thoughts:

1) Are you logging slow pages via the option in the MX Admin? Try setting 
the threshold for that to a low value (say, 10 seconds) for a little bit so 
that you can develop a small catalog of pages that are taking longer than 
they should.

2) I am using MX for J2EE for JRun on Solaris (w/ Apache 2.0.47) out in 
production right now. One thing I have noticed is that when I first start up 
my MX instances, either JRun or MX runs rather "sluggishly" (not egregious, 
but noticeable) for the first little bit. After a time (I'm narrowing it 
down still, but it's in the low minutes range), things pick up considerably. 
My hunch is that either JRun or MX is taking time to cache certain processes 
(and not just the class files) and acquire the memory space it needs to 
function smoothly.

3) Have you used any of IPlanet's logging/debugging features to see if it's 
the underlying J2EE engine that may be having some problems? I have never 
used IPlanet, so I can't point you to anything specific, but JRun comes with 
an impressive aresenal of logging/debugging features built into it such that 
it's a few XML tweaks to get the logging/debugging up and running. Of 
course, this last point is one where you only want to try this in your 
dev/staging environment (duh).

4) One thing I've learned is that simply running "top" is not sufficient 
when dealing with Java applications. You also need to use vmstat and other 
diagnostic tools to more efficiently track virtual memory usage. Perhaps 
your application is generating a ton of object, thus consuming your 
allocated VM space? That's something that "top" won't indicate on its own. 
Also, read up a bit (if you're not already familiar) with the various 
garbage collection mechanisms. Perhaps your current collector is not the 
most efficient option?

Hope this helps get you going.

Regards,
Dave.

_________________________________________________________________
Use custom emotions -- try MSN Messenger 6.0! 
http://www.msnmessenger-download.com/tracking/reach_emoticon


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/lists.cfm?link=t:4
Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Signup for the Fusion Authority news alert and keep up with the latest news in 
ColdFusion and related topics. 
http://www.fusionauthority.com/signup.cfm

Reply via email to