Unwanted output to stdout - can it be avoided or is it a bug?

Hello,

I get in my program a GSSException (expected, and does not harm):

GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos Ticket)

at sun.security.jgss.krb5.Krb5InitCredential.getInstance(Krb5InitCredential.java:133)

at sun.security.jgss.krb5.Krb5MechFactory.getCredentialElement(Krb5MechFactory.java:72)

at sun.security.jgss.GSSManagerImpl.getCredentialElement(GSSManagerImpl.java:149)

at sun.security.jgss.GSSCredentialImpl.add(GSSCredentialImpl.java:389)

at sun.security.jgss.GSSCredentialImpl.<init>(GSSCredentialImpl.java:60)

at sun.security.jgss.GSSCredentialImpl.<init>(GSSCredentialImpl.java:37)

at sun.security.jgss.GSSManagerImpl.createCredential(GSSManagerImpl.java:96)

However, this backtrace is printed to stdout from the GSSCredentialImpl

constructor which can be considered ugly ...

Is this intended, or is this possibly a bug?

Regards

Alexander Schr鰀er

[1011 byte] By [alexschroedera] at [2007-10-3 1:34:37]
# 1

This error from Java GSS is printed with it's backtrace to the standard error stream. Starting from Java SE 6 (Mustang), this backtrace is no longer printed.

Although if you successfully authenticate, you should not be getting this error.

You can download latest Java SE 6 from:

http://download.java.net/jdk6/binaries/

Seema

Seema-1a at 2007-7-14 18:32:39 > top of Java-index,Security,Kerberos & Java GSS (JGSS)...