ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@gridgain.com>
Subject Re: Starting H2 Debug Console On Remote Server
Date Tue, 05 Jul 2016 09:32:28 GMT

Taking into account reply from Sergi I would better try to resolve the following issue

Failed to start a browser to open the URL
http://<ip-addr>:*32842*/frame.jsp?jsessionid=<id>: Browser detection failed
and system property h2.browser not set

Usually it’s possible to set a default browser instance on operating systems.

If you overcome the issue above then everything should work out of the box for you.


> On Jul 4, 2016, at 2:55 PM, pragmaticbigdata <amits.84@gmail.com> wrote:
> Ok. I understand. I need to start the ignite server instance on my local
> machine to view the h2 debug console.
> I have been experiencing web session timeout on the h2 debug console after
> which I see the h2 login screen. If I specify the db name in the jdbc url as
> the random id that was earlier generated like
> "jdbc:h2:mem:cab7dd9d-8b46-4935-82c7-b22ee096fe8d", it does not connect to
> the old database. 
> How can I reconnect after session timeout?
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Starting-H2-Debug-Console-On-Remote-Server-tp6063p6078.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message