Journey planner OutOfMemoryException


#1

Hi,
I’ve been noticing that the journey planner api often (1 every 5/6 requests) returns:

“$type”:“Tfl.Api.Presentation.Entities.ApiError, Tfl.Api.Presentation.Entities”,“timestampUtc”:“2018-08-01T21:05:20.2796266Z”,“name”:“Internal”,“exceptionType”:“OutOfMemoryException”,“httpStatusCode”:500,“httpStatus”:“InternalServerError”,“relativeUri”:"/Journey/JourneyResults/1000045/to/1000139?date=20180801&time=2204&timeIs=Departing&journeyPreference=leasttime&mode=tube,bus,dlr,river-bus,tram,cable-car,overground,national-rail,coach,tflrail&accessibilitypreference=NoRequirements&usemultimodalcall=false&cyclePreference=none&walkingSpeed=fast&maxWalkingMinutes=40&maxTransferMinutes=30&nationalSearch=false&walkingOptimization=false",“message”:“An internal server error occurred.”}

using for example the following request:

https://api.tfl.gov.uk/Journey/JourneyResults/1000045/to/1000139?date=20180801&time=2204&timeIs=Departing&journeyPreference=leasttime&mode=tube,bus,dlr,river-bus,tram,cable-car,overground,national-rail,coach,tflrail&accessibilitypreference=NoRequirements&usemultimodalcall=false&cyclePreference=none&walkingSpeed=fast&maxWalkingMinutes=40&maxTransferMinutes=30&nationalSearch=false&walkingOptimization=false

Is this a known issue ?

Thank you

P.S.
I’ve removed app_key and app_id from the sample query above.


#2

can someone reply to this question please ?

Thank you


#3

I’ve had this a LOT too over the last few months. I think I reported it but no response either :cry:

I stopped logging the 500 errors after a while as my logs were filling up, but they were pretty frequent:

2018-07-30 00:49:06: http code 500…
2018-07-30 00:50:54: http code 500…
2018-07-30 00:50:56: http code 500…
2018-07-30 00:50:58: http code 500…
2018-07-30 00:51:01: http code 500…
2018-07-30 00:51:04: http code 500…
2018-07-30 00:51:06: http code 500…
2018-07-30 00:51:08: http code 500…
2018-07-30 00:51:11: http code 500…
2018-07-30 01:59:13: http code 500…
2018-07-30 01:59:15: http code 500…
2018-07-30 01:59:17: http code 500…
2018-07-30 01:59:17: http code 500…
2018-07-30 01:59:19: http code 500…
2018-07-30 01:59:19: http code 500…
2018-07-30 01:59:21: http code 500…
2018-07-30 01:59:23: http code 500…
2018-07-30 02:04:27: http code 500…
2018-07-30 02:04:29: http code 500…
2018-07-30 02:04:29: http code 500…
2018-07-30 02:04:31: http code 500…
2018-07-30 02:04:31: http code 500…
2018-07-30 02:04:33: http code 500…
2018-07-30 02:04:33: http code 500…
2018-07-30 02:04:35: http code 500…
2018-07-30 02:26:59: http code 500…
2018-07-30 02:27:01: http code 500…
2018-07-30 02:27:02: http code 500…
2018-07-30 02:27:03: http code 500…
2018-07-30 03:38:37: http code 500…
2018-07-30 03:38:39: http code 500…
2018-07-30 03:43:02: http code 500…
2018-07-30 03:43:04: http code 500…
2018-07-30 03:43:06: http code 500…
2018-07-30 03:43:08: http code 500…
2018-07-30 04:03:19: http code 500…
2018-07-30 04:03:21: http code 500…
2018-07-30 04:03:23: http code 500…
2018-07-30 04:03:25: http code 500…
2018-07-30 04:53:59: http code 500…
2018-07-30 04:54:02: http code 500…
2018-07-30 05:09:11: http code 500…
2018-07-30 05:09:13: http code 500…
2018-07-30 05:09:15: http code 500…
2018-07-30 05:09:17: http code 500…
2018-07-30 08:08:29: http code 500…
2018-07-30 08:08:32: http code 500…
2018-07-30 08:08:34: http code 500…
2018-07-30 08:08:36: http code 500…


#4

I’ve been getting this a lot recently too, at about 1/7 requests. Is this a known problem @jamesevans?


#5

Hi @milesHopkins

We are experiencing some memory leaking issues on the API that you have noticed here in your requests.

Normally during office hours , we’re responding to these quite quickly, but this is a bit more difficult out-of-hours.

We hope to have a fix (or at least something to improve the performance) next week, so I’ll try to keep you posted on that.

Thanks,
James


#6

any update on this issue please ?


#7

@nakkore We have made some improvements. The issue is by no means fixed yet but you should be experiencing a better service now. We will continue to strive to fully resolve the issues when resources become available. Thanks for your patience!


#8

Hi,
thank you. I can see some improvements and I hope you find soon resources to fix this issue completely.