Silly question: is there enough disk space on the drive
with the logs?
We've seen this before and, lo-and-behold, monitoring
failed (or was
ignored) and the machine a 0 kb free on the D drive
(where the logs were).
Plenty of space on C meant that Windows and CF was
running fine... just no
I logged a bug in March for onSessionEnd. It was just fixed, and I
expect it will be released with a cumulative updater soon.
Bug 59913- onSessionEnd event does not fire unless
This.Sessiontimeout is defined in Application.cfc. The default
session timeout in CFAdmin is ignored.
Maybe this
Thanks Steven,
I don't believe that was the case -- in any event I did make sure to
define sessiontimeout in the Application.cfc pseudo-constructor. I've
managed to get the onSessionEnd code working in spite of my logging /
error trapping problems...
As it turns out I suspect IIS has been
A normally operating CFMX7 installation should log errors which occur
during the onSessionEnd stage to the application.log right? My server
seems to have stopped logging these errors -- or for that matter
_anything_ including cflog tags in the application.log ...
my first day of serious testing /
-Original Message-
From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 04, 2005 11:20 PM
To: CF-Talk
Subject: trapping/logging errors in onSessionEnd in application.log
A normally operating CFMX7 installation should log errors which occur
during the onSessionEnd
5 matches
Mail list logo
