xTour2 : potential experiences with output

[Bernd Welter]

Here's a distinct description of potential planTours calls... Behaviour also depends on combination of

• Server settings /xserver.conf):

  Code: Select all

      jobs {
          resultRetentionTime = 7d
          fetchedResultRetentionTime = 1h
          zombieRetentionTime = 1d
          jobQueueTimeout = -1
          jobModuleTimeout = -1
      }
  

• Request parameters override server settings

  Code: Select all

    "timeouts": {
      "queueingTimeout": 600000,
      "computationTimeout": 900000
    }
  

Condition	Status	Plan	Example
Rejected	Exception	not available	Code: Select all {"faultInfo":{"$type":"QueueOverflowFault"}, "message":"Failed to enqueue asynchronous request interface com.ptvgroup.xserver.xtour.XTourModuleInterface.planTours()"}
Queuetimeout expired	Exception	not available
Interrupted	Failed	not available	Code: Select all {"faultInfo":{"$type":"RequestTimedOutFault"},"message":"Request has timed out!"}
Intermediate	Success	Suboptimal	Code: Select all "resultLimitations": [ { "reason": "REQUEST_TIMED_OUT", "message": "The request has been stopped during computation. The response is an intermediate but valid response that usually differs from the final response.", "hint": "To get the final response, run the request again with an increased computation timeout." } ]
Terminated	Success	Best available solution