mms should return 500 if triplestore times out

[dlamoris]

there seems to be some intermittent auth check failure when doing a model/lock query:
current config includes 2 groups that have admin cluster policy
when a user that's in both groups does a query, it sometimes responds with
org.openmbee.mms5.Http403Exception: User user (group1, group2) is not authorized to perform specified action on resource: User user does not exist or does not belong to any authorized groups.

[dlamoris]

i think the 403 was just a red herring due to the triplestore returning 500 for a different reason (in this case timed out) - i believe what happened was the first query timedout with a 500, we then check the auth again and that also timed out

[dlamoris]

obsolete