I have a DBF Server running on a Linux machine. The configuration I have been using works well, so I decided to create a definition that has 'Auto run' set to ensure the DBF server deamon is automatically started when the Linux machine is rebooted.
When I rebooted the Linux machine, and then run my application, it gets a 'java.net.ConnectException: Connection refused' when connecting to the DBF Server.
Next, I started the DBF Server UI (DBF_JDBC30.jar com.hxxt.sql.admin.Admin); the configuration defined with 'Auto run' was displayed and appeared to be started (as it has the blue icon with triangle facing right). This time the application had no problems inserting entries into the DBF tables.
Finally, I closed down the DBF UI; I presume the DBF server deamon should be left running. This time there was a 'java.net.ConnectException: Connection refused' when my application tried to connect to the server.
I assumed that the purpose of the 'Auto run' on the configuration is to ensure that the 'auto run' configured service is automatically started.
The version of DBF_JDBC30.jar was created on 14/06/2005.
Is this a bug?
Now DBFServer won't continue to run as a daemon background when you quit Dbadmin GUI. 'Auto run' is a switch to start a DBF service when Dbadmin GUI start. Since you need such a function, we may add a 'Daemon run' switch or a OpenAPI.function to run an invisible DBFServer daemon automatically. Your advice is valuable and welcome. Thanks for your response.