![]() |
![]() |
||||||
|
|||||||
| Tags: |
![]() |
|
|||
|
When I terminate a thread in this manner to kill runaway thread:
<cfloop list="#t#" index="i"> <cfif findNoCase('RUNNING', evaluate('#i#.status')) gt 0> <cfsilent> <cfthread action="terminate" name="#i#" /> </cfsilent> </cfif> </cfloop> Each thread that is terminated gets logged in the application log of the CF administrator. How do I keep this from getting logged? |
| Sponsored Links |
|
|||
|
> How do I keep this from getting logged?
Write your code so the threads finish gracefully, without you having to kill them? -- or -- If you have to kill these runaway threads... why is it a problem that their death gets logged? -- Adam |
|
|||
|
>> How do I keep this from getting logged?
>Write your code so the threads finish gracefully, without you having to >kill them? The thread is very simple. Only a few lines of code and it finishes just fine. But, because of the nature of application, about a hundred threads are spawned and the garabage collector normally kills all of them by the time the join is completed. However, sometimes some of those threads hang around for no apparent reason. So, after the threading has been completed, then I would like to check to make sure they have been freed up so they are available for other requests. -- or -- >If you have to kill these runaway threads... why is it a problem that their >death gets logged? Because killing a thread should not be considered an application error. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
- Contact Us
-|-
Adobe Dreamweaver Forums -|-
Archive -|-
Top -|-Rules/Disclaimer-|-Help/Support-|-Advertise