Hmmm,

Well, I have some requests (like data imports of 50,000 + records) and some
long string parsing routines, so I think setting it down to 2 or 3 would
not be appropriate as alot of requests might queu up in that time. I have
it set at 20 on a dual Xeon 1.8  w/ 3 gigs of ram.

I could try lowering it and see if that helps I guess. 10 requests would be
fine, as the server is never really over that anyways. And its usually
under 3, but as I explained there are those occasions where 3 would not be
enough considering some of the longer requests that are possible.

Bryan wrote:
When a simple parsing error occurs (let's say code like this with a missing
end bracket <cfset MyVar = "Hello World").  Just that missing ">" causes
JRun to start eating memory until the server grinds to a halt!!  I would
tend to think an error should be thrown right off the bat...but nope...that
comes about 5 minutes later when all the memory is gone...nice huh ;-)

Really?  Wow, I have never seen or heard of that? That must kill in a
shared hosting environment. Actually, my friend who runs an ISP says he's
going to stop doing CF hosting because they can't keep CF up. I can
understand that in a shared hosting environment, but on a single site on a
single server, I should be able to keep it stable I think.

I checked Macromedia's site and actually, I do not have a bunch of the
latest hot fixes installed. So I'm gonna run through that tonight  and get
that rectified and see if it helps.

When the crash occurs, pages just server up the "unable to connect to Jrun
Server' page. I do not know what the CPU or memory usage was prior to the
crash, cause, it was not being logged.

Brook

At 01:32 PM 7/12/2004, you wrote:
>How many simultaneous processes are you allowing?  The default of 10?
>Try chopping it down.  Minimum is 1 per processor.
>
>I found I had to go to this on my shared-hosting server.  A
>dual-processor box, but with all the stuff going on its possible for a
>thread to hang and not release its memory.  memory usage increases and
>available threads decrease until *poof*.  Cutting the number of
>processes to 1 per processor gave me total stability, although I'm
>sure I could have bumped it up a process or two.  That particular box
>is plenty fast at 2 processes so I left it alone.
>
>The default of 10 could be way too much or not enough.  Depends
>completely on your application.
>
>--
>--Matt Robertson--
>MSB Designs, Inc.
>mysecretbase.com
>
>----------
>[<http://www.houseoffusion.com/lists.cfm/link=t:4>Todays Threads]
>[<http://www.houseoffusion.com/lists.cfm/link=i:4:170123>This Message]
>[<http://www.houseoffusion.com/lists.cfm/link=s:4>Subscription]
>[<http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=905.825.4>Fast
>  Unsubscribe] [<http://www.houseoffusion.com/signin/>User Settings]
>[<https://www.paypal.com/cgi-bin/webscr?amount=&item_name=House+of+Fusion&business=donations%40houseoffusion.com&undefined_quantity=&cmd=_xclick>Donations
>and Support]
>
>----------
><http://www.houseoffusion.com/banners/view.cfm?bannerid=40>
>aaa2720.jpg
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to