I've also had this problem but I doubt if the bindaddress has anything to do with it. By default the server socket will be bound to INADDR_ANY. (This is the same as the tomcat security issue I referred to some time back). Will investigate ...
Bob 2010/4/10 Lars Helge Øverland <[email protected]>: > I have had the same problem. Why don't you test it, you can set props > from the command line when starting live.. > > 2010/4/10, Knut Staring <[email protected]>: >> I am unable to connect to the H2 database through the H2 console while DHIS2 >> is running, despite AUTO_SERVER being indicated in hibernate.properties >> (default for DHIS Live). >> >> >From the following message, it seems that perhaps we need to set >> System.setProperty("h2.bindAddress", ...) before loading the >> org.h2.Driver class (and before starting the server) >> >> http://groups.google.com/group/h2-database/msg/7526244fde1a0e58 >> >> -- >> Cheers, >> Knut Staring >> > > -- > Sendt fra min mobile enhet > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
