To change the PHP Timeout, add or change the value of max_execution_time in
php.ini. (http://is.gd/dpl2k)

To set the MS SQL Server timeout add or edit mssql.timeout in the php.ini.
(http://is.gd/dpl0w)

As for the time out being only 1 or 2 minutes, keep in mind you can use the
set_time_limit function increase the time out for a single script.
Actually, calling set_time_limit actually resets the timer, so if you use
it repeatedly you can let a script run indefinitely. Others might feel
differently, but I feel the best practice is to set your max_execution_time
to what is reasonable (and even responsible) for the average PHP script to
run on your site. By that standard, even 30 seconds is probably more than
enough. If you have need longer, use the set_time_limit functions to give
those specific scripts more time. In general, I think that is considered
the more "secure" approach, but I guess it is a matter of preference.


web400-bounces@xxxxxxxxxxxx wrote on 07/12/2010 12:44:47 PM:

[image removed]

Re: [WEB400] time out problem

Larry Kleinman

to:

Web Enabling the AS400/iSeries

07/12/2010 01:03 PM

Sent by:

web400-bounces@xxxxxxxxxxxx

Please respond to Web Enabling the AS400 / iSeries

You are right, Matt, thanks! The log specifically says that we timed
out. So now my question is: what do I change in the php.ini file? I
see
a lot of "time out" directives, some of which seem to relate to sockets,
MySQL, and other stuff. Which do I change? Also, why do you say that
I
probably do not want this to be above a minute or two? It is possible
that I will be getting as many as 10,000 records, and will be calling an
API from a mailblast site (called MailChimp), and this might take more
than a minute or two.


Larry Kleinman
Kleinman Associates, Inc.
212-949-6469
203-255-4100



MattLavinder@xxxxxxxxxxxxxxxxxxx
Sent by: web400-bounces@xxxxxxxxxxxx
07/12/2010 11:37 AM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc
web400@xxxxxxxxxxxx, web400-bounces@xxxxxxxxxxxx
Subject
Re: [WEB400] time out problem







Check your PHP error log is. The location is specified in your php.ini.
If it isn't specified, the messages will be in your Apache log. If you
see
a "Maximum execution time of XX seconds exceeded then PHP timed out. You
can increase the PHP timeout in your php.ini file. The default is 30
seconds. You probably don't want this to be above a minute or two.
There
will most likely be a message from the SQL Server extension if the
time-out
is happening there.

web400-bounces@xxxxxxxxxxxx wrote on 07/12/2010 10:23:51 AM:

[image removed]

[WEB400] time out problem

Larry Kleinman

to:

web400

07/12/2010 10:52 AM

Sent by:

web400-bounces@xxxxxxxxxxxx

Please respond to Web Enabling the AS400 / iSeries

First my apologies for posting this previously as a response to a
completely unrelated post. I didn't realize that that confused the
server
as well as some mail clients.

I am reposting this now, hopefully correctly, since I got no response
to
the original post, I suspect due to my incorrect posting.



Hi folks - Table NAME (in the script below) has about 10,000 rows in
it.
When I run it using ZEND CORE, all I get is the word "top" showing up.
(It

takes a minute or so). When I run it with some additional selection
criteria, so that I get about 7500 rows, it works fine - the "echo
$count"

statement at the end displays the count. How can I tell whether this
is
a

time out in getting the data from the SQL server, or in the Apache or
Zend

server, or in the browser?

<html>
<head></head>
<body>

<?php
echo "top";

$conn = mssql_connect('FBC_DEV_106','xxx','xxxx');
if ($conn) {
mssql_select_db("FBC_DEV_106");

$query = "SELECT * from NAME ";


$sql_result = mssql_query($query);

if($sql_result) {
while ($array = mssql_fetch_array($sql_result)) {
$count = $count + 1;
}
echo $count;

}


}

?>

</body>
</html>



Larry Kleinman
Kleinman Associates, Inc.
212-949-6469
203-255-4100
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
______________________________________________________________________
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
______________________________________________________________________

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.