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 long as that process stays up and is reused.
Then, if you by any chance restart 4D, all those processes are gone and will start afresh. Did you by any chance restart 4D and it started behaving as expected again? > On Apr 24, 2018, at 1:34 PM, John Baughman via 4D_Tech <[email protected]> > wrote: > > 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 back an empty string, and 4D continued to ignore my otherwise > forced errors. But after having 4D choke on the bad ON ERR CALL, it started > catching errors again. Go figure. > > John > >> On Apr 24, 2018, at 1:58 AM, Julio Carneiro via 4D_Tech >> <[email protected]> wrote: >> >> 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 me that. But using your test code, you can add an ON >> ERR CALL(“”) right before your bad statement and see if 4D catches it. If >> you do get a 4D error back it’ll indicate your were trapping errors, not 4D. >> >> hth >> julio >> >>> On Apr 24, 2018, at 2:11 AM, John Baughman via 4D_Tech >>> <[email protected]> wrote: >>> >>> 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 error >>> description. >>> >>> Like I said, I do not know why it did that, but I liked it as I could >>> detect the error in my web app and throw up a message box telling me what >>> was wrong. All of a sudden 4D just keeps on going. >>> >>> For example, test=test on a line all by itself will in a normal process >>> throw an error. Before today In a web process it would terminate the >>> process and send back the error. Now the web app no longer gets the error. >>> What it does get back depends on how the error affected my xml response. >>> >>> If I put a TRACE before test=test 4D honors the TRACE, but just keeps on >>> trucking after I tell it to continue. If I put the TRACE after test=test, >>> the TRACE is ignored and the web app gets back whatever my later code is >>> able to send back. >>> >>> I didn’t change anything. Any ideas? >>> >>> John >>> >> >> -- >> Julio Carneiro >> [email protected] >> >> >> >> ********************************************************************** >> 4D Internet Users Group (4D iNUG) >> FAQ: http://lists.4d.com/faqnug.html >> Archive: http://lists.4d.com/archives.html >> Options: https://lists.4d.com/mailman/options/4d_tech >> Unsub: mailto:[email protected] >> ********************************************************************** > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** -- Julio Carneiro [email protected] ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
