tracker issue : CF-3041747

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

Bug 83515:(Watson Migration Closure)It seems that errors raised in onApplicationEnd() and onSessionEnd() won't show up in the CF Application log files

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Ben Nadel / Ben Nadel (Ben Nadel)

Created: 07/08/2010

Components: Language, Exception Handling

Versions: 9.0

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 / 289881

Priority/Frequency: Normal / Most users will encounter

Locale/System: English / Platforms All

Vote Count: 5

Listed in the version 11.0.03.292480 Issues Fixed doc 
Problem:

It seems that errors raised in onApplicationEnd() and onSessionEnd() won't show up in the CF Application log files.
Method:


Result:

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

Watson Bug ID:	3041747

External Customer Info:
External Company:  
External Customer Name: Ben Nadel
External Customer Email: 703809A54469B8C599201549
External Test Config: 07/08/2010

Attachments:

  1. November 22, 2014 00:00:00: 1_3041747.zip

Comments:

Yeah, this stuff needs to be logged. An exception is an exception, and there should not be a difference in how/whether exceptions get logged. -- Adam
Vote by External U.
21825 | November 11, 2011 12:49:38 AM GMT
I agree with the two previous speakers. Very strange behavior. Should be fixed!
Vote by External U.
21826 | November 11, 2011 12:49:39 AM GMT
It took me some time to realise that such methods do not log any exceptions. Yes, that strange behavior should be changed.
Vote by External U.
21827 | November 11, 2011 12:49:40 AM GMT
This really should be re-opened and resolved. Without logging errors in the events, leads to potential errors never being noticed or resolved.
Vote by External U.
21828 | September 20, 2012 07:20:56 AM GMT
WOW! +1 for sure. How can something like this be marked closed/deferred/not-enough-time?
Vote by External U.
21829 | October 03, 2012 10:39:06 PM GMT
OK, so it's 3.5yrs later now. Do you think you might be able to *FIND TIME* to deal with this? This has just caused us very real grief on a production server. Pls re-open. Pls fix. Cheers. -- Adam
Comment by External U.
21815 | January 09, 2014 03:15:35 PM GMT
Adobe, Why is this still not fixed!? Exceptions must be logged. Thanks!, -Aaron
Comment by External U.
21816 | March 01, 2014 07:07:28 AM GMT
Adobe, HELLO?
Comment by External U.
21817 | March 01, 2014 07:21:50 AM GMT
Exceptions occurring in onApplicationEnd() and onSessionEnd() are getting logged in application.log, exception.log, and coldfusion-out.log files. (Comment added from ex-user id:nawani)
Comment by Adobe D.
21818 | September 02, 2014 03:26:11 AM GMT
Well... no they're not. NB: you claim this is fixed in 289881; ColdFusion 11 is either 289822 or 290107 (Wikipedia says one thing; my install says another). Either way, that's a subsequent build to that in which you say it's fixed, so I would expect it to be fixed in the version I'm running. But this is not the case. Have you posted the wrong build number that it's fixed in? -- Adam
Comment by External U.
21819 | September 02, 2014 03:39:34 AM GMT
Oops, just noticed 289822 is actually *not* after 289881. But I'm bemused why I'm apparently on 290107. Is this because I have the updater-by-email installed here (the one that prevents CF11 from timing out when trying to phone home when behind a firewall)? So which release is 289881?
Comment by External U.
21820 | September 02, 2014 03:58:58 AM GMT
Hi all, I've verified onSessionEnd() and onApplicationEnd() exceptions are logged to application.log, exception.log and coldfusion-out.log (but not coldfusion-error.log) in CF11 Update 3. Just curious.. why not also coldfusion-error.log? Thanks!, -Aaron
Comment by External U.
21821 | November 02, 2014 04:06:55 AM GMT
The onApplicationEnd() and onSessionEnd() errors are still not logged to coldfusion-error.log in CF11 Update 3 (11,0,03,292245(PreRelease)). Repro: 1) remove "Site-wide Error Handler" in CF Admin 2) unzip attached CF-3041747.zip 2) run index.cfm 3) see both errors not logged to coldfusion-error.log (they are logged to application.log, exception.log and coldfusion-out.log) The onApplicationEnd() and onSessionEnd() errors should also be logged to coldfusion-error.log, right? Thanks!, -Aaron
Comment by External U.
21822 | November 21, 2014 09:07:48 PM GMT
All the exceptions thrown within the coldfusion application are supposed to go in exception log and not coldfusion-error log...
Comment by Uday O.
21823 | November 25, 2014 12:36:57 AM GMT
Hi Uday, Thanks for providing that (currently-undocumented) description. I've filed #CF-3861184 to document descriptions for the missing log files. Thanks!, -Aaron
Comment by External U.
21824 | December 02, 2014 11:55:51 PM GMT
Hi Adobe, In CF2016 Update 1, errors thrown in onApplicationEnd() and onSessionEnd() are not logged to any CF log file. So, if this was actually fixed, then there was a regression. Repro: Steps to Reproduce: 1) Browse to index.cfm 2) Wait 10+ seconds 3) See neither error logged in exception.log Application.cfc ----------- component { THIS.name = "ticket_3041747"; THIS.sessionManagement = true; THIS.applicationTimeout = createTimeSpan(0,0,0,10); THIS.sessionTimeout = createTimeSpan(0,0,0,10); function onApplicationEnd() { foo = barOnApplicationEnd; } function onSessionEnd() { foo = barOnSessionEnd; } } index.cfm ----------- empty file Thanks!, -Aaron
Comment by Aaron N.
27836 | May 17, 2018 06:42:30 AM GMT