The error in the stacktrace is complaining that it is unable to find any credentials for the OS user executing the request. This is usually cause by one of three conditions:
- not setting the location of the JAAS config correctly (which causes us to fall back to the default of using the TGT cache & often leading to 2.)
- an empty local ticket cache (when not using a keytab)
- credentials for the specified principal missing from the keytab
The first thing I'd check is that you have set the java.security.auth.login.config
system property to the location of your JAAS config file (the DseClient file) correctly?
If you have and are still seeing the error, you can check the contents of the keytab with klist -e -t -k /path/to/keytab
Another useful tip for debugging is to set -Dsun.security.krb5.debug=true
which will dump lots of detailed info to stdout.