[
https://issues.apache.org/jira/browse/TINKERPOP-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17330820#comment-17330820
]
Stephen Mallette commented on TINKERPOP-2504:
---------------------------------------------
I've pulled in
https://github.com/apache/tinkerpop/commit/66bf504eb3ba130a424e615a04f791edb85ccbc7
to {{master}} and backported it to {[3.4-dev}}:
https://github.com/apache/tinkerpop/commit/247d097dc38e325b67536d0ab8867b0a5f6c9155
I still see travis annoyed by "Authenticator is not ready to handle requests"
so something is still amiss. I pushed this to try to combat it in the test
where it failed:
https://github.com/apache/tinkerpop/commit/f653835be1f2efa841a715ab14909d14e7717d53
I doubt that's the root cause, but i can foresee that pre-initializing the
clients individually could have some effect in a low resource environment. If i
keep seeing the "Authenticator is not ready to handle requests" i will likely
close this (since it went a long way to solving travis build issues) and open
one specifically for this "authenticator" problem.
Let's see
> Intermittently failing server/driver integration tests
> ------------------------------------------------------
>
> Key: TINKERPOP-2504
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2504
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver, server
> Affects Versions: 3.4.9
> Reporter: Stephen Mallette
> Priority: Minor
>
> I've noticed this test failing intermittently on Travis and more consistently
> on the {{master}} branch with Docker. It fails with a
> {{ConcurrentModificationException}} (haven't been able to easily get the
> entire stack trace thanks to the docker issue and i've not caught it
> happening in the last few days on Travis). Adding this line of code seems to
> have made the test pass more consistently:
> https://github.com/apache/tinkerpop/commit/4b099b3c84a350aae953cdf517aa11c7017eb2ae
> which would indicate something perhaps fishy with how hosts are being marked
> dead and iterated. Would be nice to get rid of that little hack.
> Another common failure that is fairly consistent is with
> {{GremlinServerAuditLogIntegrateTest.shouldAuditLogWithKrb5Authenticator}}
> {code}
> [ERROR]
> shouldAuditLogWithKrb5Authenticator(org.apache.tinkerpop.gremlin.server.GremlinServerAuditLogIntegrateTest)
> Time elapsed: 3.16 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.GremlinServerAuditLogIntegrateTest.shouldAuditLogWithKrb5Authenticator(GremlinServerAuditLogIntegrateTest.java:222)
> Caused by: org.apache.tinkerpop.gremlin.driver.exception.ResponseException:
> Authenticator is not ready to handle requests
> {code}
> cc/ [~divijvaidya] [~HadoopMarc]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
