Because the database name remains, it is not possible to maintain 2 separate instances. E.g. to open scan results for two diff jobs. Which ever instance interacts with the database last over-writes the previous one.
One recommendation would be to create database name randomly or attach epoch time to current database name. Dont know if there is a feature within Java to maintain "session" for thick clients - create a new config file for each instance?
Because the database name remains, it is not possible to maintain 2 separate instances. E.g. to open scan results for two diff jobs. Which ever instance interacts with the database last over-writes the previous one.
One recommendation would be to create database name randomly or attach epoch time to current database name. Dont know if there is a feature within Java to maintain "session" for thick clients - create a new config file for each instance?