Page MenuHomePhabricator

Federated SPARQL queries failing with error 500
Closed, ResolvedPublic


This weekend we have been trying SPARQL federation queries. If we do directly ( ) it fails, if we federate it through another SPARQL server it works ( ). It also works from the SPARQL test instance on wmflabs and a curl from the production Blazegraph server.

Event Timeline

Restricted Application added a project: Discovery. · View Herald TranscriptMay 20 2018, 1:36 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript

The end of the stack trace, for future reference:

Caused by: com.bigdata.rdf.sail.webapp.client.HttpException: Status Code=500, Status Line=Internal Server Error, Response=<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<title>500 Internal Server Error</title>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator,
 root@localhost and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.</p>
<p>More information about this error may be available
in the server error log.</p>

	at com.bigdata.rdf.sail.webapp.client.RemoteRepositoryBase.checkResponseCode(
	at com.bigdata.rdf.sail.webapp.client.RemoteRepositoryManager.tupleResults(
	at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask$ServiceCallTask.doNonBigdataSesameServiceCall(
	at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask$ServiceCallTask.doRemoteServiceCall(
	at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask$ServiceCallTask.doServiceCall(
	... 6 more

Noticed that as well.

Maybe it has something to do with the list of prefixes that is being sent.

When I send data from my local laptop, everything works fine. With curl from production host I get 404. I suspect there's something to do with proxies maybe.

Smalyshev triaged this task as Normal priority.Jun 21 2018, 11:27 PM
Vvjjkkii renamed this task from Federated SPARQL queries failing with error 500 to 0kcaaaaaaa.Jul 1 2018, 1:08 AM
Vvjjkkii raised the priority of this task from Normal to High.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed a subscriber: Aklapper.
CommunityTechBot lowered the priority of this task from High to Normal.
CommunityTechBot renamed this task from 0kcaaaaaaa to Federated SPARQL queries failing with error 500.
CommunityTechBot added a subscriber: Aklapper.
Smalyshev moved this task from Backlog to Next on the User-Smalyshev board.Oct 14 2018, 6:49 PM

If this gets stuck on debugging on our side, I could probably ask around for contact details for the people running . On several other endpoints are also failing. Solving the problem might fix some of the others too.

Some of the endpoints there are dead (I removed them from Wiki, but I keep it in the whitelist in case they'd go back to life). Others fail for unknown reasons, I'll investigate it. Some are listed as failed - e.g. - but work fine for me.

Husky removed a subscriber: Husky.Oct 14 2018, 8:10 PM

Tried it again with Curl and it seems to work OK. I suspect this is the same ALPN issue as in T202785: Federation request to fails.

Tried it again with Curl and it seems to work OK. I suspect this is the same ALPN issue as in T202785: Federation request to fails.

Is that something we need to fix on our side or something that can be fixed on the side?

We probably can't fix it until we migrate to Jetty that supports ALPN. On the other side, it may be possible to fix it if the server would handle non-APLN clients properly but I am not sure how to configure and test it, unfortunately... I don't have too much knowledge into inner workings of ALPN and I have no idea which software runs.

Smalyshev closed this task as Resolved.Nov 14 2018, 7:50 PM
Smalyshev claimed this task.

This seems to work now, looks like upgrade to jetty 9.4 fixed it.