[
https://issues.apache.org/jira/browse/ZOOKEEPER-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047233#comment-15047233
]
Hadoop QA commented on ZOOKEEPER-2295:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12776363/ZOOKEEPER-2295-03.patch
against trunk revision 1718511.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3)
warnings.
-1 release audit. The applied patch generated 1 release audit warnings
(more than the trunk's current 0 warnings).
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2985//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2985//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2985//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2985//console
This message is automatically generated.
> TGT refresh time logic is wrong
> -------------------------------
>
> Key: ZOOKEEPER-2295
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2295
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.4.7, 3.5.1
> Reporter: Arshad Mohammad
> Assignee: Arshad Mohammad
> Fix For: 3.4.8, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2295-01.patch, ZOOKEEPER-2295-02.patch,
> ZOOKEEPER-2295-03.patch
>
>
> When Kerberos is used as authentication mechanism some time TGT is getting
> expired because it is not refreshed timely.
> The scenario is as follow:
> suppose now=8 (the current milliseconds)
> next refresh time= 10
> TGT expire time= 9
> *Current behaviour:* Error is logged and TGT refresh thread exits.
> *Expected behaviour:* TGT should be refreshed immediately(now) instead of
> nextRefreshTime
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
