What makes this more mysterious is that while I was having the problem I
changed to a different Web App and 4D Database and saw the same problem. I used
the same version of 4d,, but the a completely different database. Really weird.
As for the “Reuse temporary contexts” is enabled but according
hummm.. do you have you web server configuration “Reuse temporary contexts”
enabled?
Because that MIGHT (no idea if what I’ll say is indeed true, just a wild guess)
cause your web process to be reused.
Thus if while handling one request on err handling got enabled, that might stay
‘active’ as lo
Julio,
I put ON ERR CALL (), note without the quotes, in on web connection and
that itself threw an error as expected and the error messages started working
again even after taking it back out.
Strange. Before posting to the web I had put a call to Method called on
error, got b
You can use the "Method called on error” function to determine the name of the
method that was set by an “ON ERR CALL”.
Example of using this to temporarily change the ON ERR CALL and then putting it
back:
C_TEXT($currentOnErrMethod)
$currentOnErrMethod:=Method called on error
ON ERR CALL(
Hey John, have you by any chance added an ON ERR CALL() during your web
process, and are thus trapping errors yourself? Because that would cause your
process to continue on w/o throwing any 4D error.
I don’t think there is a way t detect if you’re trapping errors, nothing I see
in debug can tell
This may be a dumb question as I am not sure why or how this worked before
today.
Up until today, whenever 4D encountered any kind of error in my code while
handling an HTTP request the code was immediately aborted and my web app got a
response that included the method name, line number and err
6 matches
Mail list logo
