Is your CF Install up to date? Check this page:
http://www.macromedia.com/support/coldfusion/ts/documents/cfmx61_issues.htm

and make sure you have this patch:
http://www.macromedia.com/support/coldfusion/ts/documents/cfmx61_sqlserver_c
pu.htm
If your server is dual-cpu, then 50% cpu could = 100% for 1 processor,
therefore the above patch would fix it.

I have this problem on one of my servers too, even still, after all the
patches. Our latest blind guess in the dark is that the server is too busy,
so we're going to CFMX with J2EE using multiple CF servers. I can only hope
that solves it for us.

Keep us all posted if you figure anything out.

-nathan strutz

  -----Original Message-----
  From: Darron J. Schall [mailto:[EMAIL PROTECTED]
  Sent: Thursday, December 04, 2003 9:46 AM
  To: CF-Talk
  Subject: Re: Random "Could not connect to JRun Server" error

  Thanks for the suggestion, but this situation is a little different.  In
my
  case the entire CFMX server dies.  None of the pages will serve out
  anymore - ColdFusion becomes completely unresponsive, and refreshing the
  page doesn't help.  To fix it, we have to stop IIS, restart ColdFusion,
then
  restart IIS.

  We're not using getPageContext anywhere in our applications...

  It's really weird that CFMX just dies completely, and JRun hangs at 50%
CPU
  usage... but only on 1 of our 3 boxes.

  -d

  ----- Original Message -----
  From: Sparrow-Hood, Walter
  To: CF-Talk
  Sent: Thursday, December 04, 2003 11:36 AM
  Subject: RE: Random "Could not connect to JRun Server" error

  We've had the same problem - at least the same error message.  If you
  refresh the page then it completes the request properly.  I traced it down
  to using getPageContext().Forward.  I could never figure out why it was
  causing a problem - I changed the statement to getPageContext().Include
  (which in my case didn't affect the logic) and everything works fine.  I
  suspect that somehow it was getting confused, couldn't find the page it
was
  looking for and timed out.  It seemed to happen most when it was
forwarding
  to another directory.  Some other people have had the same problem but
I've
  never seen a solution (or an explanation for that matter).

  Walt
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to