[ 
https://issues.apache.org/jira/browse/TINKERPOP-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette closed TINKERPOP-2553.
---------------------------------------
    Resolution: Duplicate

> Intermittently failing Kerberos tests
> -------------------------------------
>
>                 Key: TINKERPOP-2553
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2553
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.4.10
>            Reporter: Stephen Mallette
>            Priority: Minor
>
> I'm currently seeing this in Travis and for 3.5.0 (haven't yet confirmed 
> 3.4.x) but I would think that any change we'd need in 3.5.0 would need to 
> backport to {{3.4-dev}}. This test has failed on 3 different build attempts:
> {code}
> [ERROR] Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
> 34.098 s <<< FAILURE! - in 
> org.apache.tinkerpop.gremlin.server.GremlinServerAuditLogDeprecatedIntegrateTest
> [ERROR] 
> shouldAuditLogTwoClientsWithKrb5Authenticator(org.apache.tinkerpop.gremlin.server.GremlinServerAuditLogDeprecatedIntegrateTest)
>   Time elapsed: 3.089 s  <<< ERROR!
> java.util.concurrent.ExecutionException: 
> org.apache.tinkerpop.gremlin.driver.exception.ResponseException: 
> Authenticator is not ready to handle requests
>       at 
> org.apache.tinkerpop.gremlin.server.GremlinServerAuditLogDeprecatedIntegrateTest.shouldAuditLogTwoClientsWithKrb5Authenticator(GremlinServerAuditLogDeprecatedIntegrateTest.java:348)
> Caused by: org.apache.tinkerpop.gremlin.driver.exception.ResponseException: 
> Authenticator is not ready to handle requests
> {code} 
> After some recent changes, I _think_ I notice this error message for the 
> first time:
> {code}
> [WARN] 
> org.apache.tinkerpop.gremlin.server.GremlinServerAuditLogDeprecatedIntegrateTest
>  - Failed to start KDC-Server. Address already in use (Bind failed)
> {code}
> I wonder if that's part of the problem somehow....



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to