alexwlchan
commented
6 years ago So the expedient fix would be to remove any JP2 images from your storage.
I suspect the long timeout is being caused by blocking in this code:
and eventually something in the stack times out the request and returns a 500 (although a 504 might be more appropriate).
The correct fix is to ensure that code doesn't block if the command hangs.
nmaekawa
at harvardx we don't usually have jp2, so we don't bother to install anything to deal with it (kakadu nor openjp2).
But say that i have the loris/tests/img in my storage and someone decides to request it. What I see is that this request returns a 500 after a while (I think 2min).
I can remove the jp2 entry from transformers section in loris.conf and that will return a 500 faster. Or I can prevent jp2 to reach loris (like have nginx in front of loris and send a 404 for jp2 requests).
This is really a minor thing, but it would be good to have a way to disabled jp2, or other source format the we decided not to support.