After upgrading to V14 and Active4D v6 I have a script where the Active4D code doesn't always run.
Active4D is behind apache and I can see the request in the Apache Log but it does not appear that the active4D code in the script is running as I have inserted numerous write to console statements that are not being echoed.
I have Active4D debug logging turned on and don't see any errors.
The script in question is called by a remote application that posts a block of text to A4D. That text is actually a Base64 encoded BLOB that contains an ObjectTools object.
A4D decodes the submission and builds a report. This had run reliably for years prior to this upgrade. We've had success with some submissions, but most seem to fail.
- Put a trace in A4D_OnWebConnection (or the NTK equivalent) before the call to Active4D.
- Post the text from the remote application.
- If the trace is not reached, then 4D is eating the request.
- If the trace is reached, see what the status and response is.
It actually was being called. The A4D method calls a 4D method. The
problem was in the 4D method. Tracing that method verified A4D was being
I had placed write to console calls in Active4D before and after calling
that 4D method. I wasn't seeing any prior expected write to console output
and assume (falsely) that the script was not running.
>> Can anyone provide any debugging suggestions?
>- Put a trace in A4D_OnWebConnection (or the NTK equivalent) before the
>call to Active4D.
>- Post the text from the remote application.
>- If the trace is not reached, then 4D is eating the request.
>- If the trace is reached, see what the status and response is.
>Active4D-dev mailing list
>[hidden email] >http://list.aparajitaworld.com/listinfo/active4d-dev >Archives: http://active4d-nabble.aparajitaworld.com/ >