Hi,
I see... I guess in this case there is no other way than to manually set the
address. It's a bit unfortunate, maybe it could be solved in some way. If
somebody has an idea - patches are always welcome.
Regards,
Thomas
--
You received this message because you are subscribed to the Google
If I don't set it, communication from my app to the local H2 db uses the
company network, which is required for startup. However, upon disconnecting
(losing wireless coverage) which happens on occasion, subsequent calls to the
db errored out during development. If this should fail over by
Hi,
I wonder why you need to set the property...
As my application must be able to function off-network, I cannot be bound
to the company IP
By default, the listener is bound to all available network adapters, meaning
you should not need to set this property. What happens if you don't set the
System.setProperty(h2.bindAddress, 127.0.0.1);
On 13 October 2011 21:44:41, beetle wrote:
Hmm, pehaps adding it as a straight property in the config is not
appropriate, so i tried adding it to the URL as such:
property name=connection.urljdbc:h2:C:\journal\H2DB
Ahhh, thank you Noel. I had conveniently (or inconveniently)
forgotten that this was a JVM property when I read thru the
documentation. Setting this directly as listed above just prior to
creating my session object worked as advertised. Sometimes we just
need someone to point out the obvious
Hmm, pehaps adding it as a straight property in the config is not
appropriate, so i tried adding it to the URL as such:
property name=connection.urljdbc:h2:C:\journal\H2DB
\HNDLDATA;IFEXISTS=TRUE;AUTO_SERVER=TRUE;DB_CLOSE_DELAY=5;BINDADDRESS=127.0.0.1/
property
however, this throws the following
