mORMot Open Source

Yes, for cloud, I would definitively use FPC + Linux x86_64 which is now stable enough for production.
If you can afford to pay the huge money for Windows cloud hosting, I guess you can either just use FPC + Win32 (which works fine), or afford to pay for Delphi Win64 compiler...

Anyway, for our problem, I don't see any easy way to circumvent this general exception issue.

For mORMotMVC, what we may do is add a new way of redirection.
For instance, we may add a new threadvar in which we put the exception to be raised, outside of the TServiceMethodExecute.RawExecute() scope.

I've enabled the logs, built with debug information, then the logs shows on FPC / Win64:

2/25/2018 14:38:50.608	Exception	    EMVCApplication {"Message":"Error=404"} at   $00000001001C1E02  ARTICLEVIEW,  line 337 of MVCViewModel.pas
2/25/2018 14:38:50.624	Exception OS	    EExternalException (C0000005) at   $00000001000F5725  RAWEXECUTE,  line 60856 of ../../mORMot.pas

But in fact, the error happens when the exception is raised in the low-level CallMethod() function.
Sounds like if the exception is not propagated by FPC outside this function.

So the try..finally in TServiceMethodExecute.RawExecute() is not working as expected.

What is weird is that it works just fine on Win32.
On Win64, it also works when compiled with Delphi, but not when compiled with FPC.