You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Dylan Millikin (JIRA)" <ji...@apache.org> on 2015/05/21 07:05:00 UTC

[jira] [Updated] (TINKERPOP3-696) Gremlin-server running gremlin-groovy[scripts] on new session

     [ https://issues.apache.org/jira/browse/TINKERPOP3-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dylan Millikin updated TINKERPOP3-696:
--------------------------------------
    Description: 
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:

{{noformat}}[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{{noformat}}

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.

  was:
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:

{{[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}}

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.


> 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: Bug
>          Components: server
>            Reporter: Dylan Millikin
>            Priority: Minor
>
> 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:
> {{noformat}}[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{{noformat}}
> 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)