[
https://issues.apache.org/jira/browse/TINKERPOP-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156977#comment-16156977
]
stephen mallette commented on TINKERPOP-1737:
---------------------------------------------
[~jeromatron] which way were you setting {{maxContentLength}} to get this
error? I guessed that you meant with {{:remote connect}} so I bumped the
{{maxContentLength}} to something really big in the {{remote.yaml}} file and it
failed with a semi-reasonable error. also, I don't find that the error leaves
the console broken which is what i was more worried about. I was able to
correct the yaml file and issue the {{remote connect}} again and it worked
fine. Could you please clarify the problem you were seeing?
> Validate and throw an exception when maxContentLength overflows
> ---------------------------------------------------------------
>
> Key: TINKERPOP-1737
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1737
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.2.5
> Reporter: Jeremy Hanna
> Priority: Trivial
>
> If you set the {{maxContentLength}} to higher than {{Integer.MAX_VALUE}} it
> won't error out but the gremlin console is broken. We should probably do
> some sort of validation on startup and then fail fast with an appropriate
> error message instead.
> This can happen if people don't want to worry about the value and set it
> arbitrarily high and don't know that it's an integer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
