Switching Sybase off on closing servoy -ga

Classic Servoy
1

A tip regarding closing the Sybase database server when servoy developer is closed was given on the forum some time ago.

This is done by putting ‘-ga’ into the first line of the sybase.config file. It seems to work fine, but then today i noticed my solution had gone mad after i had run a script, which i think updated some records in a remote mysql database.

Very weird things seemed to happen, such as records which existed a second ago couldnt be found. Then i got this error:

JZ00L: Login failed.  Examine the SQLWarnings chained to this exception for the reason(s). java.sql.SQLException: JZ00L: Login failed.  Examine the SQLWarnings chained to this exception for the reason(s).
com.servoy.j2db.persistence.RepositoryException: org.apache.commons.dbcp.DbcpException: java.sql.SQLException: JZ00L: Login failed.  Examine the SQLWarnings chained to this exception for the reason(s). java.sql.SQLException: JZ00L: Login failed.  Examine the SQLWarnings chained to this exception for the reason(s).

Which makes me think that the solution is loosing its connection to the Sybase database during these script and then not being able to connect again. Oddly sybase seems to be still running and the sybase log doesnt show that the database has stopped. When i take the -ga out of the sybase.config script the solution works fine again.

This is unfortunate, because i am using servoy offline (3.5.8) and it is very useful to have the sybase database shut down on quiting, especially since I have nearly cracked an ftp download of the repository to enable updates. By having sybase close automatically on quit, it leaves my users a simple batch script to run to overwrite the old repository with the new ones that servoy has just downloaded to a temporary folder.

Whilst I could tell my users how to close sybase down before running this batch script. It is a lot neater to have Sybase shut itself down when servoy quits.

Does this sound a familiar issue, or am just so off the beaten track with my quirky solutions, that I will have to live with it!.

Thanks

David

2

Didn’t try the -ga option before, so I don’t know what’s going wrong here. When this happens you could try to use another DB tool to connect to sybase and see if it is still useable.

An idea - you should also be able to stop sybase using “dbstop” in the beginning of your batch script. It’s not that neat as using -ga though :).