[
https://issues.apache.org/jira/browse/IGNITE-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848352#comment-15848352
]
ASF GitHub Bot commented on IGNITE-4196:
----------------------------------------
GitHub user skalashnikov opened a pull request:
https://github.com/apache/ignite/pull/1486
IGNITE-4196 Added means to specify port for H2 debug console
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4196
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1486.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1486
----
commit ebc293b14f3eed3fc563f3fc11e3d1ecd85f55e9
Author: skalashnikov <[email protected]>
Date: 2017-02-01T13:02:36Z
IGNITE-4196 Added means to specify port for H2 debug console
----
> H2 debug console is always started on artificial port
> -----------------------------------------------------
>
> Key: IGNITE-4196
> URL: https://issues.apache.org/jira/browse/IGNITE-4196
> Project: Ignite
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.7
> Reporter: Valentin Kulichenko
> Assignee: Sergey Kalashnikov
> Fix For: 2.0
>
>
> When H2 debug console is started as described in [1], it always binds to an
> artificial port. This has at least two issues:
> * Sometimes a client wants to connect through firewall. It's impossible to
> open all possible ports for the console.
> * If there is no GUI on server node, console can't be opened in a browser, so
> user has no idea what to do next and how to connect.
> We should:
> * Print out the information about how to connect to the console after it's
> started.
> * Allow to use a specific port provided as a system property.
> [1] https://apacheignite.readme.io/docs/sql-queries#using-h2-debug-console
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
