Find the answer to your Linux question:
Results 1 to 3 of 3
Hi, I am coming 3rd wheel into this problem, however when the user clicks on result.php they get the following error in the: tail -f /var/log/httpd/ssl_error_log [Thu Aug 16 16:00:53 ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2012
    Posts
    18

    70007)The timeout specified has expired php or tomcat error?


    Hi,
    I am coming 3rd wheel into this problem, however when the user clicks on result.php they get the following error in the:

    tail -f /var/log/httpd/ssl_error_log


    [Thu Aug 16 16:00:53 2012] [error] [client 192.168.19.6] (70007)The timeout specified has expired: Error reading request entity data

    I have googled around but still baffled on this one....

    I am under the impression it's the post size in php or tomcat related, has anyone had an error like this before?

    Sorry yes very vague and non-descriptive post however I don't know the system / software installed yet I am asked to "help" lol.

    Can anyone assist or elaborate?

    Thanks

  2. #2
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,376
    Vague questions result in vague answers

    It sounds like this result.php takes longer than what is set as "max_execution_time" in your php.ini.

    As to why: No idea.
    It might be, that this app simply takes long to produce an output.
    In this case, increasing max_execution_time in php.ini might be appropiate.
    Note the sideeffect: The client waiting takes an apache connection and therefore resources.

    It also might be, that result.php is slow or even stalled because of a slow backend.
    Maybe a DB is under high load and/or takes long for a query?


    In any case:
    Imho, only in trivial cases can someone new jump in and solve such a problem right away.
    I would request access to and documentation on
    - the server(s)
    - server setup
    - server update status
    - last server update
    - monitoring and graphing data
    - logs
    - workflow of the application
    - If you really want to make your hands dirty: access to the source code, sql schemes and indexes.
    You must always face the curtain with a bow.

  3. #3
    Just Joined!
    Join Date
    Mar 2012
    Posts
    18
    Thanks for your reply Irithori yes it's very hit and miss.... so to speak ... I will see how this goes if not I will try and let it fizz out!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •