Page 1 of 1

xTour2 : potential experiences with output

Posted: Wed Feb 05, 2025 10:30 am
by 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
      }
    
ConditionStatusPlanExample
RejectedExceptionnot available

Code: Select all

{"faultInfo":{"$type":"QueueOverflowFault"},
"message":"Failed to enqueue asynchronous request interface com.ptvgroup.xserver.xtour.XTourModuleInterface.planTours()"}
Queuetimeout expiredExceptionnot available
InterruptedFailednot available

Code: Select all

{"faultInfo":{"$type":"RequestTimedOutFault"},"message":"Request has timed out!"}
IntermediateSuccessSuboptimal

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."
    }
  ]
TerminatedSuccessBest available solution