Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8036779

sun.security.krb5.KdcComm interprets kdc_timeout as msec instead of sec

XMLWordPrintable

    • b16
    • x86
    • os_x
    • Verified

        FULL PRODUCT VERSION :
        jdk1.7.0_51.jdk
        java version "1.7.0_51"
        Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
        Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)



        ADDITIONAL OS VERSION INFORMATION :
        OS X 10.9.2 Build 13C64
        Darwin i7.local 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64

        A DESCRIPTION OF THE PROBLEM :
        sun.security.krb5.KdcComm uses kdc_timeout value using Config, and interprets its value as millisecond, which causes really fast fails. It really should be considered as second.

         http://www.daemon-systems.org/man/krb5.conf.5.html
        [libdefaults]
        kdc_timeout = time
        Maximum time to wait for a reply from the kdc,
        default is 3 seconds.

        REGRESSION. Last worked in version 6u45


        REPRODUCIBILITY :
        This bug can be reproduced always.

        CUSTOMER SUBMITTED WORKAROUND :
        System.setProperty("java.security.krb5.conf", "/dev/null");

          1.
          		 Release Note: Support the "s" (second) unit for kdc_timeout in krb5.conf Sub-task Closed Weijun Wang  

              weijun Weijun Wang
              webbuggrp Webbug Group
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: