New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pinging a non existing lock should not result in 500 error #184

Open

paterczm opened this issue Oct 26, 2015 · 1 comment

Labels

bug

Contributor

paterczm commented Oct 26, 2015

PUT https://{{host}}/rest/data/lock/domain/callerId/resourceId/ping

Results in

{
  "errors": [
    {
      "objectType": "error",
      "context": "rest/LockPingCommand/resourceId",
      "errorCode": "rest-crud:RestError",
      "msg": "com.redhat.lightblue.extensions.synch.InvalidLockException: resourceId"
    }
  ],
  "status": "ERROR"
}

Which is descriptive enough, but the result status should not be 500.

The text was updated successfully, but these errors were encountered:

paterczm added the bug label

Contributor Author

paterczm commented Nov 5, 2015

See HttpErrorMapper class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment