[jira] [Updated] (IGNITE-4196) H2 debug console is always started on artificial port

2017-01-26 Thread Vladimir Ozerov (JIRA)

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

Vladimir Ozerov updated IGNITE-4196:

Assignee: (was: Valentin Kulichenko)

> 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
> 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 
> port 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.4#6332)


[jira] [Updated] (IGNITE-4196) H2 debug console is always started on artificial port

2016-11-17 Thread Valentin Kulichenko (JIRA)

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

Valentin Kulichenko updated IGNITE-4196:

Fix Version/s: (was: 1.8)
   2.0

> 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: Valentin Kulichenko
> 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 
> port 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.4#6332)