Timeout from scriptcase but not from SP on server

Scriptcase 9 General
#1

I have a lengthy update wrapped in a series of transactions…maybe 85 million rec. If I run it as a stored proc on the server via Navicat (Windows/mysql/php 8.3/apache) it runs fine. If I call the same SP from a scriptcase app, it times out. The my.ini settings are pretty maxed out for time outs and doubt that it is since it runs off the server. I’ve looked at some php settings. Is there something in particular I might be missing?

m

1 Like
#2

Hi,

This is a common issue when calling stored procedures from Scriptcase. The timeout in Scriptcase is controlled separately from MySQL/server settings. Here are a few things to check:

  1. PHP max_execution_time – In your Scriptcase project settings or php.ini, increase it (e.g. max_execution_time = 600).
  2. PHP default_socket_timeout – Also in php.ini, set it higher (e.g. default_socket_timeout = 600).
  3. Scriptcase connection timeout – In your database connection settings inside Scriptcase, look for a timeout parameter and increase it.
  4. Apache TimeOut directive – If running under Apache, the default is 300 seconds. Increase it in httpd.conf.
  5. Consider running async – For very long operations (85M records is a lot!), you might want to trigger the SP via a background job rather than a direct app call.

The key difference is that Navicat runs the query directly on the server, while Scriptcase calls it over a PHP/Apache stack — so all those layers have their own timeouts.

Hope this helps!