org.springframework.web.client.RestClientException

Error running rest call; nested exception is org.springframework.web.client.HttpClientErrorException: 404 Not Found

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web126

  • via Apache's JIRA Issue Tracker by Greg Senia, 5 months ago
    Error running rest call; nested exception is org.springframework.web.client.HttpClientErrorException: 404 Not Found
  • via Stack Overflow by Purple
    , 2 days ago
    Error running rest call; nested exception is org.springframework.web.client.HttpClientErrorException: 404 Not Found
  • Error running rest call; nested exception is org.springframework.web.client.HttpClientErrorException: 401 Authentication required
  • Stack trace

    • org.springframework.web.client.RestClientException: Error running rest call; nested exception is org.springframework.web.client.HttpClientErrorException: 404 Not Found at org.springframework.security.kerberos.client.KerberosRestTemplate.doExecute(KerberosRestTemplate.java:196) at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:580) at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:498) at org.apache.zeppelin.livy.LivyHelper.executeHTTP(LivyHelper.java:377) at org.apache.zeppelin.livy.LivyHelper.executeCommand(LivyHelper.java:301) at org.apache.zeppelin.livy.LivyHelper.interpret(LivyHelper.java:239) at org.apache.zeppelin.livy.LivyHelper.interpretInput(LivyHelper.java:190) at org.apache.zeppelin.livy.LivySparkInterpreter.interpret(LivySparkInterpreter.java:79) at org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:94) at org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:390) at org.apache.zeppelin.scheduler.Job.run(Job.java:176)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.