Status/Resolution/Reason: Closed/Withdrawn/NotABug
Reporter/Name(from Bugbase): Rob Bilson / Rob Bilson (Rob Bilson)
Created: 03/16/2012
Components: Logging
Versions: 10.0
Failure Type:
Found In Build/Fixed In Build: Public Beta /
Priority/Frequency: Major / Most users will encounter
Locale/System: English / Platforms All
Vote Count: 0
Problem Description:
I'm seeing some more odd/incorrect behavior with scheduled task logging. This time it's around logging of misfire events. I have two different scenarios with similar outcomes:
1. I created a clustered task and it started executing fine. This is when I first discovered that successful task execution wasn't being logged. So I went ahead and changed the contents of the file that I was calling to test to this:
<cfset sleep(15000)>
Hello world
I then set my task timeout to 5 seconds. The next time the task fired, ColdFusion logged the following in scheduler.log:
Mar 16, 2012 3:03 PM Information QuartzScheduler_MyClusteredScheduler-RBILS7-TP1331933591818_MisfireHandler
Task DEFAULT.CLUSTER_TEST_1 misfired.
Note that the task is set to execute every 2 minutes. I let things continue on for another 10 minutes or so. When I looked in scheduler.log again, there were no additional errors logged for any of the misfires that had occurred since the first one was logged. I checked the http.log and verified that the URL had indeed been called. For some reason ColdFusion isn't logging subsequent misfires.
2. I decided to try this on a fresh ColdFusion instance that wasn't clustered. I created a new task that called the same url that forced a timeout. This time, no misfire was logged at all. I checked and no scheduler.log file existed. So, I tried pausing/restarting the task. Those events caused ColdFusion to create the scheduler.log file and they were logged (see related bug 3140184 for more context). So, now that the scheduler.log file existed, I figured that the next time the task fired off and misfired it would be logged. Well, the task executed and misfired, but no log entry was ever created.
Steps to Reproduce:
Actual Result:
Expected Result:
Any Workarounds:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3140191
External Customer Info:
External Company:
External Customer Name: Rob Brooks-Bilson
External Customer Email:
External Test Config: My Hardware and Environment details:Attachments:
Comments: