Re: Bug in SunNativeProvider

2018-01-04 Thread Valerie Peng
Great, thanks! Valerie On 1/4/2018 4:51 AM, Jan Kalina wrote: Described issues was accepted into Oracle JDK issues: 1) SunNativeProvider.INSTANCE initialization: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8194073 2) Uninitialized cb->initiator_address: https://bugs.java.com/bug

Re: Bug in SunNativeProvider

2018-01-04 Thread Jan Kalina
Described issues was accepted into Oracle JDK issues: 1) SunNativeProvider.INSTANCE initialization: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8194073 2) Uninitialized cb->initiator_address: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8194630 (fixing patches are include

Re: Bug in SunNativeProvider

2017-12-19 Thread Valerie Peng
I will take a look. Do you happen to have a test case that I can reproduce the issue? Thanks, Valerie On 12/14/2017 9:20 AM, Jan Kalina wrote: Attaching patch, which fixes described issue for me. On Thu, Dec 14, 2017 at 4:03 PM, Jan Kalina > wrote: I has foun

Re: Bug in SunNativeProvider

2017-12-14 Thread Jan Kalina
Attaching patch, which fixes described issue for me. On Thu, Dec 14, 2017 at 4:03 PM, Jan Kalina wrote: > I has found bug in SunNativeProvider: > > When debug messages are enabled, JDK confirms GSS library was loaded with > mechs: > > [GSSLibStub_init] libName=/usr/lib64/libgssapi_krb5.so.2.2 >