GraphQL java.util.concurrent.TimeoutException after approximate a minute when doing journey planning with AsyncGraphQLFetchers

[miklcct]

NOTE: this issue system is intended for reporting bugs and tracking progress in software development. For all other usage and software development questions or discussion, please post a question in our chat room: https://gitter.im/opentripplanner/OpenTripPlanner.

Expected behavior

It returns itineraries

Observed behavior

The GraphQL API throws an exception with java.util.concurrent.TimeoutException after about a minute

Version of OTP used (exact commit hash or JAR name)

2.4.0

Data sets in use (links to GTFS and OSM PBF files)

Great Britain DfT GTFS + National Rail GTFS generated from dtd2mysql

The problem doesn't appear when only London data is loaded in the server, where the journeys are returned in about 20 seconds, or when AsyncGraphQLFetchers is disabled, where the journey plan takes minutes to load.

Command line used to start OTP

java -jar otp.shaded.jar --load --serve .

Router config and graph build config JSON

otp-config.json

{
  "otpFeatures": {
    "TransferConstraints": false,
    "GtfsGraphQlApi": true,
    "SandboxAPITravelTime": true,
    "SandboxAPIParkAndRideApi": true,
    "ParallelRouting": false,
    "ActuatorAPI": true,
    "AsyncGraphQLFetchers": true,
    "FaresV2": true,
    "FlexRouting": false
  }
}

router-config.json

{
  "routingDefaults": {
    "wheelchairAccessibility": {
      "trip": {
        "onlyConsiderAccessible": false,
        "unknownCost": 600,
        "inaccessibleCost": 3600
      },
      "stop": {
        "onlyConsiderAccessible": false,
        "unknownCost": 600,
        "inaccessibleCost": 3600
      },
      "elevator": {
        "onlyConsiderAccessible": false
      },
      "inaccessibleStreetReluctance": 25,
      "maxSlope": 0.08333,
      "slopeExceededReluctance": 50,
      "stairsReluctance": 25
    },
    "walkBoardCost": 300,
    "bikeBoardCost": 600,
    "walkReluctance": 1.68,
    "waitReluctance": 1.76
  },
  "updaters": [
    {
      "type": "vehicle-positions",
      "url": "https://data.bus-data.dft.gov.uk/api/v1/gtfsrtdatafeed/?api_key=445a01ae6d34cd773c6f2838eadde6282eb6e22d&boundingBox=${BOUNDING_BOX}",
      "feedId": "DfT",
      "frequency": "PT10S"
    },
    {
      "type" : "siri-sx-updater",
      "url" : "https://data.bus-data.dft.gov.uk/api/v1/siri-sx?api_key=445a01ae6d34cd773c6f2838eadde6282eb6e22d",
      "feedId" : "DfT",
      "timeout" : "30s"
    }
  ],
  "transit": {
    "transferCacheRequests": [
      {"modes": "WALK", "walkBoardCost": 300, "walkReluctance": 1.68},
      {"modes": "WALK", "walkBoardCost": 300, "walkReluctance": 1.68, "wheelchairAccessibility": {"enabled": true}},
      {"modes": "WALK", "walkBoardCost": 0, "walkReluctance": 1.0},
      {"modes": "WALK", "walkBoardCost": 0, "walkReluctance": 1.0, "wheelchairAccessibility": {"enabled": true}}
    ]
  }
}

Note that the reluctances in the request are not the same as the pre-cached ones

Steps to reproduce the problem

1. Start OTP with the above config with GB wide data
2. Plan a journey in London with non-default reluctances and walking speed

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days

[miklcct]

push - issue still exists with 2.6.0-SNAPSHOT