I don't believe JConsole will natively hook into Java 1.4.

Sounds like you're going to doing thread dumps.

Do a google search for them, and you will find several articles.

Mark

On Wed, Jan 7, 2009 at 9:24 AM, Matthew <matthewbchamb...@gmail.com> wrote:
>
> Hi guys,
>
> Sorry, I should have given more info.
>
> @Steve: I'm not sure if it's a CF web service but I'm pretty sure it
> isn't. I think it may be Java.
>
> @Mark: not sure which point you were refering to with your first
> question? It's running on a CF7 server. So I'm guessing I'll need to
> use JConsole. Where do I start?
>
> Cheers
> Matthew
>
> On Jan 7, 7:42 am, "Mark Mandel" <mark.man...@gmail.com> wrote:
>> What makes you think this is the case?
>>
>> What version of CF are you on?
>>
>> If you are on CF8, you can use either - snapshots via the server
>> monitor, a tool like JConsole, or thread dumps to find out exactly
>> what is causing the infinite loop.
>>
>> Mark
>>
>>
>>
>> On Tue, Jan 6, 2009 at 5:20 PM, Matthew <matthewbchamb...@gmail.com> wrote:
>>
>> > Hi everyone
>>
>> > From time to time our website appears to hand. I believe it is CF (or
>> > JRun) chocking because each time it happens I can still connect to the
>> > web server via FTP, RDP, DB access. When I look at the Task Manager
>> > jrun.exe is using max CPU. If I restart the CF service or End Process
>> > on jrun.exe everything recovers.
>>
>> > I'm pretty sure I know which bit of code is causing the problem. It's
>> > a web service call to a 3rd party (used quite a lot by users on the
>> > website). Most of the time when the website hangs I can't browse to
>> > the 3rd party's web service. I've tried setting timeouts on the web
>> > service call by using CFINVOKE, CreateObject, CFOBJECT etc but no
>> > improvement. I need to allow for up to 60s because some of the calls
>> > are quite complex.
>>
>> > I'm trying to work out why it's hanging. I suspect that because CF is
>> > allowing 8 simaltaneous requests and each gets 60 seconds then once
>> > all these slots are taken up everyone else goes on a queue and with
>> > all that load the server appears to hang because it's in constant use
>> > i.e. after 60 seconds user 1 gets his timeout so user 9 takes position
>> > 8 and round and round it goes and it never stops because with constant
>> > traffic taking up 8 request slots and all taking up resources for 60
>> > seconds it appears to hang. Does this make sense?
>>
>> > So the question is: how do I save the server from getting into this
>> > state. I'm thinking I need some sort of scheduled task which probes
>> > the web service every 10 seconds to work out if it's up. Perhaps if it
>> > times out (3 times just to be sure) I shut of the web service (which
>> > means the rest of the website is still up). The scheduled task keeps
>> > running until no timeout occurs and then it re-activates the web
>> > service for everyone else. Has anyone been through something like this
>> > before? How did you work around it?
>>
>> > Cheers
>> > Matthew
>>
>> --
>> E: mark.man...@gmail.com
>> W:www.compoundtheory.com
> >
>



-- 
E: mark.man...@gmail.com
W: www.compoundtheory.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to 
cfaussie+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to