You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Mark Bennett (Jira)" <ji...@apache.org> on 2022/04/08 21:23:00 UTC
[jira] [Updated] (TINKERPOP-2733) NullPointerException when calling chooseConnection(Client.java:813)
[ https://issues.apache.org/jira/browse/TINKERPOP-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Bennett updated TINKERPOP-2733:
------------------------------------
Description:
This is similar to TINKERPOP-2597 and reported fixed in gremlin driver 3.5.2. However, we are still getting the 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{address=va7prod1pes7yiiuy4h.gremlin.cosmos.azure.com/20.49.102.64:443
class=org.apache.tinkerpop.gremlin.driver.Client
Could not initialize client for Optional[.removed for security purposes.]
was:
This is similar to what was reported in TINKERPOP-2597 and reported fixed in gremlin driver 3.5.2. However, we are still getting the 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{address=va7prod1pes7yiiuy4h.gremlin.cosmos.azure.com/20.49.102.64:443
class=org.apache.tinkerpop.gremlin.driver.Client
Could not initialize client for Optional[.removed for security purposes.]
> NullPointerException when calling chooseConnection(Client.java:813)
> -------------------------------------------------------------------
>
> Key: TINKERPOP-2733
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2733
> Project: TinkerPop
> Issue Type: Bug
> Components: driver
> Affects Versions: 3.5.2
> Environment: Production
> 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 the 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{address=va7prod1pes7yiiuy4h.gremlin.cosmos.azure.com/20.49.102.64:443
> class=org.apache.tinkerpop.gremlin.driver.Client
> Could not initialize client for Optional[.removed for security purposes.]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)