Page 1 of 1

500 - Internal server error.

Posted: Tue Feb 28, 2017 2:56 pm
by columbs
Hello everyone,

we have been using the xTour Internet for a few month. We have got an account for https://xtour-eu-n-test.cloud.ptvgroup.com/

We noticed that if we send a big request to xTour we get the following after more or less 3 minutes.

Code: Select all

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>500 - Internal server error.</title>
</head>
<body>
<div id="header"><h1>Server Error</h1></div>
<div id="content">
 <div class="content-container"><fieldset>
  <h2>500 - Internal server error.</h2>
  <h3>There is a problem with the resource you are looking for, and it cannot be displayed.</h3>
 </fieldset></div>
</div>
</body>
</html>


As temporary solution we have set availableMachineTime="120" ( at the beginning we have set availableMachineTime="150", but in some case like balancing plan isn't enough, see similar case here:
http://xserver.ptvgroup.com/forum/viewt ... 1392#p1392 )

my questions are: is it possible to get more resource for xServer internet? Is it a difference between the test and the prod account?
I ask also in order to know if for us it would be better to have a local xTour server or not.

Thank you in advance and best regards from Berne,
Sebastiano

Re: 500 - Internal server error.

Posted: Tue Feb 28, 2017 3:34 pm
by columbs
I have an update.
It seems that the issue of 3 minutes cannot be solved/changed. The solution seems to be to use asynchronous planing (i.e. startPlanBasicTours in our case).

Could you confirm that?

Thank you in advance.

Re: 500 - Internal server error.

Posted: Thu Mar 02, 2017 3:56 pm
by Oliver Heilig
Hello Sebastiano,

yes, xServer internet has a timeout limit of about 3 minutes. So every request that has a potentially long response time (i.e. xTour-requests, and xRoute/xLocate batch rerquests) should be invoked as job.

Regards

Oliver

Re: 500 - Internal server error.

Posted: Fri Mar 03, 2017 3:15 pm
by columbs
Hello Oliver,
thank you for your response.
We have implemend the solution using jobs and it works so far. :)

regards,
Sebastiano

Re: 500 - Internal server error.

Posted: Wed Sep 04, 2019 12:27 pm
by Bernd Welter
Hi there,

just received a complaint about the 3min timeout. Just for your information:

the limit of 3 minutes is a setting of Microsoft Azure - PTV has no influence on this.
Therefore it is very important to use the asynchronuos protocol (start=>watch=>-fetch-functions).

Best regards,
Bernd