Ok, I see. Probably you need to specify is at a special H2 attribute which is not supported in Ignite basing on the previous replies. However basically H2 console is used for debugging purposes which should satisfy default timeout.
How quick does it expire on your side? How do you use H2 console, what is your use case? — Denis > On Jul 5, 2016, at 2:05 PM, pragmaticbigdata <[email protected]> wrote: > > I don't think the debug console session timeout problem would be resolved > with this fix. Are you sure? > I started ignite on my local machine and I am able to access the h2 debug > console but the UI session times out after a certain duration. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Starting-H2-Debug-Console-On-Remote-Server-tp6063p6099.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
