You won't see an error in the logs, the error isn't a server error, it is a
client timeout error, what you are looking for in the logs is what is
causing the xmlce or xmlse api call to not finish in less than 120 seconds
On August 10, 2019 6:15:33 PM pascale.sterr...@daimler.com wrote:
Hi LJ,
Hi LJ,
Thank you for the reply ☺
That is the problem I am having. The API/SQL/Filter log is not capturing any
error. I even added the AL log. And that is where I see that the AL is failing
from the Push field that triggers the web service on Create. But I do not see
any error on the filter or
Gustavo,
Pascale notes that he was able to retrieve data using SoapUI in about 40
seconds.
Dave
On Sat, Aug 10, 2019 at 6:14 PM Gustavo Tejo wrote:
> Hi Pascale
>
> Please, test de web service with SoapUI, this help you to testing web
> service response.
>
> El sáb., 10 de agosto de 2019
Pascale,
The only way to troubleshoot this is with API/SQL/Filter logs, then them
on, wait the two mins it takes to generate the error, wait another few
mins, then review the loss, see what ther thread that was used to call the
external service is doing that's causing the timeout.
On August
Hi Pascale
Please, test de web service with SoapUI, this help you to testing web
service response.
El sáb., 10 de agosto de 2019 15:44,
escribió:
> Hi everyone,
>
>
>
> This is on an old dinosaur:
>
> ARS 7.6.4 SP5 (100% custom apps)
>
> Windows 2012
>
> MSSQL 2012
>
> Mid Tier 8.1.SP02
Hi everyone,
This is on an old dinosaur:
ARS 7.6.4 SP5 (100% custom apps)
Windows 2012
MSSQL 2012
Mid Tier 8.1.SP02 Patch 002 201611240104 Hotfix
This is a production issue that is going from bad to worse. It was an
intermittent problem that is now a continuous issue.
We have an API call
6 matches
Mail list logo
