[
https://issues.apache.org/jira/browse/TINKERPOP3-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP3-696.
---------------------------------------
Resolution: Fixed
Fixed via Gremlin Server's {{LifeCycleHook}}
> Gremlin-server running gremlin-groovy[scripts] on new session
> -------------------------------------------------------------
>
> Key: TINKERPOP3-696
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-696
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: server
> Reporter: Dylan Millikin
> Assignee: stephen mallette
> Priority: Minor
> Fix For: 3.0.0.GA
>
>
> Hey,
> I don't know if this is expected behavior, it seems like it may be but on the
> off chance it isn't : When sending a request to gremlin-server with
> {{opProcessor = 'session'}} the session is properly created but the
> initializing scripts set in the {{gremlin-server.yaml}} configuration are run
> every time. Resulting in the following warning:
> {code}[WARN] GremlinExecutor - Could not initialize gremlin-groovy
> ScriptEngine with scripts/generate-classic.groovy as script could not be
> evaluated - javax.script.ScriptException: java.lang.IllegalArgumentException:
> Vertex with id already exists: 1{code}
> This comes from the fact that {{scriptEngines}} are loaded on session
> creation. I'm guessing this is required? But running initializing scripts
> could be dangerous.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
