[
https://issues.apache.org/jira/browse/TINKERPOP-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555751#comment-17555751
]
Yang Xia edited comment on TINKERPOP-2734 at 6/17/22 8:12 PM:
--------------------------------------------------------------
A PR with potential fix is up [https://github.com/apache/tinkerpop/pull/1697] :
"Could not reproduce the issue without given reproduction steps, and also seems
that it would require specific server circumstance.
However, investigation of the log traces the reporter included in the ticket
gives clues of where to look, and a potential but unlikely NPE was logically
deduced. Unsure if this will fix this specific user's problem but worth fixing
regardless.
As a side effect, also reduces an unneeded coupling due to inheritance on the
Client type."
was (Author: xiazcy):
A PR with potential fix is up
[https://github.com/apache/tinkerpop/pull/1697|https://github.com/apache/tinkerpop/pull/1697.]:
"Could not reproduce the issue without given reproduction steps, and also seems
that it would require specific server circumstance.
However, investigation of the log traces the reporter included in the ticket
gives clues of where to look, and a potential but unlikely NPE was logically
deduced. Unsure if this will fix this specific user's problem but worth fixing
regardless.
As a side effect, also reduces an unneeded coupling due to inheritance on the
Client type."
> NullPointerException when calling Client chooseConnection()
> -----------------------------------------------------------
>
> Key: TINKERPOP-2734
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2734
> Project: TinkerPop
> Issue Type: Bug
> Components: driver
> Affects Versions: 3.5.2
> Reporter: Mark Bennett
> Priority: Major
>
> This is similar to TINKERPOP-2597 and reported fixed in gremlin driver 3.5.2.
> However, we are still getting intermittent null pointer exceptions, and our
> stack trace it a bit different:
> {code:java}
> java.lang.NullPointerException: null
> at
> org.apache.tinkerpop.gremlin.driver.Client$SessionedClient.chooseConnection(Client.java:813)
> at org.apache.tinkerpop.gremlin.driver.Client.submitAsync(Client.java:390)
> at org.apache.tinkerpop.gremlin.driver.Client.submitAsync(Client.java:373)
> at org.apache.tinkerpop.gremlin.driver.Client.submitAsync(Client.java:298)
> at org.apache.tinkerpop.gremlin.driver.Client.submit(Client.java:250)
> {code}
> In addition we see this in our logs:
> class=org.apache.tinkerpop.gremlin.driver.ConnectionPool
> Signalled closing of connection pool on Host\{..}
> class=org.apache.tinkerpop.gremlin.driver.Client
> Could not initialize client for Optional[..]
> Seeing a lot of this too:
> Timed-out (16000 MILLISECONDS) waiting for connection on Host{}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
