tracker issue : CF-3041724

select a category, or use search below
(searches all categories and all time range)

Bug 83465:(Watson Migration Closure)I can click Stop on logs that are not stopable

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Raymond Camden / Raymond Camden (Raymond Camden)

Created: 06/30/2010

Components: Administrator, Administrator Console

Versions: 2016,11.0,10.0

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: 0000 / 303781

Priority/Frequency: Normal / Most users will encounter

Locale/System: English / Platforms All

Vote Count: 2


I can click Stop on logs that are not stopable. I do not get any type of error msg.


----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3041724

External Customer Info:
External Company:  
External Customer Name: Raymond Camden
External Customer Email: 5FBC41E943BD265C992015D5
External Test Config: 06/30/2010



This bug has been voted..
Vote by External U.
21896 | November 11, 2011 12:50:18 AM GMT
Why won't this be fixed? I agree it is a small issue, but it took 7 years to give up on it?
Comment by Raymond C.
21888 | July 04, 2017 02:33:54 PM GMT
Update.log not stoppable from admin in CF 10, 11 &12 I see 4 stop buttons enabled on deby.log, eventgateway.log , http.log & monitor.log which are stoppable on CF 9.0.1
Comment by Manas M.
21889 | July 06, 2017 09:38:03 AM GMT
Hi Raymond, Can you please let us specify logs name which are stopped with stop button? What is installation type ( Standalone or J2EE ) and ColdFusion version and update level ? Thanks, Mukesh
Comment by Mukesh K.
21890 | August 01, 2017 08:54:29 AM GMT
@Mukesh: The bug is about the Stop button being enabled for logs that can't be stopped. I'm not sure why you are asking me which ones CAN be stopped. Just click and see for yourself - it should be obvious which logs don't stop.
Comment by Raymond C.
21891 | August 01, 2017 12:55:47 PM GMT
This is hilarious.
Vote by Adam C.
21897 | August 01, 2017 01:01:41 PM GMT
Raymond, I have tried in CF2016 HF4 build and can see stop button is working fine for derby.log , eventgateway.log, http.log, monitor.log, scheduler.log , websocket.log . Only , update.log is not working correctly. Please let us know , if you see any different behavior apart from update.log
Comment by Mukesh K.
21892 | August 01, 2017 01:09:23 PM GMT
@Mukesh: Ok then - well remove the stop button from update.log. That was the entire point of this bug - you have UI that says, "I can stop this log", and it doesn't work. Literally that's it. If you think it is only that one file, then remove (or disable) the stop button for it.
Comment by Raymond C.
21893 | August 01, 2017 01:17:45 PM GMT
For me if I have created a custom log the option to stop logging to it is there and clickable, but when the UI refreshes it does not indicate the logging has been disabled, and indeed one can still log to it. Repro: 1) save this file somewhere: <!--- test.cfm ---> <cflog file="testLog" text="moar logging"> 2) run it 3) go into CFAdmin, you will see an entry on the logging page for testLog.log, and if you check the contents, there's the log entry 4) now click STOP 5) re-run test.cfm 6) observe it is still logging to that file. Now I worked that out in about 1min of thought having read Ray's ticket. How come you couldn't do that, Mukesh? Is it just cos you couldn't be bothered?
Comment by Adam C.
21894 | August 01, 2017 01:20:27 PM GMT
Thanks Adam, Raymond for information. It looks stop button in custom exception log doesn't work .
Comment by Mukesh K.
21895 | August 01, 2017 01:29:46 PM GMT