[
https://issues.apache.org/jira/browse/TINKERPOP3-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP3-785.
---------------------------------------
Resolution: Fixed
Fix Version/s: 3.1.0-incubating
> Gremlin Server Not Properly Reporting Port Conflict
> ---------------------------------------------------
>
> Key: TINKERPOP3-785
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-785
> Project: TinkerPop 3
> Issue Type: Bug
> Components: server
> Affects Versions: 3.0.0-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Fix For: 3.0.1-incubating, 3.1.0-incubating
>
>
> It is possible to start two instances of Gremlin Server where the second
> doesn't immediately throw an error and stop. On shutdown of that second
> server an exception is thrown because the shutdown future never properly sets
> the channel as it completes exceptionally:
> {code}
> Exception in thread "gremlin-server-shutdown" java.lang.NullPointerException
> at
> org.apache.tinkerpop.gremlin.server.GremlinServer.stop(GremlinServer.java:203)
> at
> org.apache.tinkerpop.gremlin.server.GremlinServer.lambda$new$45(GremlinServer.java:80)
> at
> org.apache.tinkerpop.gremlin.server.GremlinServer$$Lambda$8/1845904670.run(Unknown
> Source)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
