You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/25 19:27:00 UTC
[jira] [Commented] (TINKERPOP-2353) Error while Shutting Down
Gremlin Server
[ https://issues.apache.org/jira/browse/TINKERPOP-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067019#comment-17067019 ]
ASF GitHub Bot commented on TINKERPOP-2353:
-------------------------------------------
spmallette commented on pull request #1270: TINKERPOP-2353 Added some checks for null in shutdown of server
URL: https://github.com/apache/tinkerpop/pull/1270
https://issues.apache.org/jira/browse/TINKERPOP-2353
The `null` checks seem necessary as failures in `GraphManager` initialization can leave Gremlin Server in a state where it is partially setup so that when shutdown starts those components that were not initialized end up being null and calls to their shutdown methods end up failing.
All tests pass with `docker/build.sh -t -n -i`
VOTE +1
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Error while Shutting Down Gremlin Server
> ----------------------------------------
>
> Key: TINKERPOP-2353
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2353
> Project: TinkerPop
> Issue Type: Bug
> Components: server
> Affects Versions: 3.4.4
> Reporter: Sarthak Ghosh
> Priority: Minor
>
> I have a kubernetes environment where gremlin server is running as a server. While shutting down gremlin-server, I see below mentioned error
> {code}
> 20:23:08.959 [gremlin-server-shutdown] INFO o.a.t.gremlin.server.op.OpLoader - Adding the cypher OpProcessor.
> 20:23:08.963 [gremlin-server-shutdown] INFO o.a.t.gremlin.server.op.OpLoader - Adding the standard OpProcessor.
> 20:23:08.968 [gremlin-server-shutdown] INFO o.a.t.gremlin.server.op.OpLoader - Adding the session OpProcessor.
> 20:23:09.163 [gremlin-server-shutdown] INFO o.a.t.gremlin.server.op.OpLoader - Adding the traversal OpProcessor.
> 20:01:51.200 [gremlin-server-shutdown] INFO o.a.t.gremlin.server.GremlinServer - Shutting down OpProcessor[]
> 20:01:51.201 [gremlin-server-shutdown] INFO o.a.t.gremlin.server.GremlinServer - Shutting down OpProcessor[cypher]
> 20:01:51.201 [gremlin-server-shutdown] INFO o.a.t.gremlin.server.GremlinServer - Shutting down OpProcessor[session]
> 20:01:51.202 [gremlin-server-shutdown] INFO o.a.t.gremlin.server.GremlinServer - Shutting down OpProcessor[traversal]
> 20:01:51.203 [gremlin-server-shutdown] INFO o.a.t.gremlin.server.GremlinServer - Shutting down thread pools.
> 20:01:51.203 [gremlin-server-shutdown] DEBUG o.a.t.gremlin.server.GremlinServer - Shutdown Gremlin thread pool.
> Exception in thread "gremlin-server-shutdown" java.lang.NullPointerException
> at org.apache.tinkerpop.gremlin.server.GremlinServer.stop(GremlinServer.java:255)
> at org.apache.tinkerpop.gremlin.server.GremlinServer.lambda$new$0(GremlinServer.java:103)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Steps carried out
> 1. server start -> *bin/gremlin-server.sh start*
> 2. Check whether graphs mentioned in gremlin-server.yaml have loaded properly or not
> 3. If failure, then stop the server by calling -> *bin/gremlin-server.sh stop*
> 4. Check logs5. Exit environment
--
This message was sent by Atlassian Jira
(v8.3.4#803005)