Comments on: CFTHREAD/Server Monitor Issue

By: Jayesh

Jayesh — Thu, 17 Apr 2008 10:44:52 +0000

Confirming it One more time.Just veridfied the fix. This issue is fixed in CF 8.0.1. Threads really get away from the Active Threads Server Monitoring Table, once they are done executing.

Thanks
Jayesh
Adobe CF Team

By: G M

G M — Thu, 17 Apr 2008 07:07:43 +0000

We updated to 801 and so far have not seen any issues?

Any pointers on specific problems will really help us to be better prepared.

By: Hemant

Hemant — Thu, 17 Apr 2008 07:04:02 +0000

Hi,

The one issue that was reported to us is cfimage locking file issue. And we are in the process of releasing a hotfix for the same next week. We haven't heard of any other issues from users who have upgraded to CF 8.0.1.

Please report any issues using http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform or mail me directly at hkhandel at adobe dot com and we will make sure that they are resolved at the earliest.

Thanks,
Hemant

By: barneyb

barneyb — Thu, 17 Apr 2008 03:20:37 +0000

Antony,

You're understanding correctly – the server monitor is showing incorrect data. I don't know if it's fixed in 8.0.1, but from comments made on this topic by a couple Adobe guys, I'd expect it to be. However, do carefully consider an 8.0.1 update before you do it; there have been a lot of complaints about stuff not working correctly across the upgrade. I can't speak from personal experience, as I've stuck with 8.0 to this point.

By: Antony

Antony — Thu, 17 Apr 2008 02:16:55 +0000

Hi – I'm glad I found this post. I've been trying to find a way to go and kill all the old threads that 'get left behind'. If I'm understanding the above comments correctly – once a thread finishes (without error) it no longer exists, regardless of what the monitor is showing? Has this been corrected in 8.0.1?
Thanks all

By: barneyb

barneyb — Tue, 27 Nov 2007 18:43:25 +0000

Thanks CK.

By: ck

ck — Tue, 27 Nov 2007 09:42:36 +0000

Yeah details of executed threads were not being removed from an internal map if monitoring was not enabled. As rightly pointed out it was a monitoring bug (threads have been working fine, just the data shown in UI was wrong) which is now fixed and should be available in next CF release. You will also be able to see correct spawned from template path even with monitoring disabled.

By: Marc Esher

Marc Esher — Mon, 26 Nov 2007 23:51:10 +0000

I thought I was going bananas when I saw this a while ago. I then ran CF under jmxremote and looked at the active threads in jconsole, saw they weren't there, and chalked it up to a glitch.

I'm glad to know I'm not the only one.

Thanks for the info, Barney.

By: Charlie Arehart

Charlie Arehart — Mon, 26 Nov 2007 22:53:10 +0000

Hey Barney, I can confirm your observation and think it may be a bug in the getallactivethreads method. When monitoring is not enabled (and it seems profiling is not a factor), it increments its size by one for each thread spawned, but it never really populates with data (again, unless profiling is enabled). So it creates a new empty array element. Worse, it doesn't not clear itself on completion of the threads. Similarly, the getCFThreadQueueStats method reports the threads as running as well, when profiling is not enabled. But I can confirm that the threads I'm testing are reporting "completed" in my program that runs and then joins them to view their result. It also doesn't matter if you try to manually terminate the threads. So it does seem you've spotted a bug in the Admin API. Hope you'll report it.

By: Damon Gentry

Damon Gentry — Mon, 26 Nov 2007 21:28:25 +0000

Interesting catch. I'll have to remember that one.