A potential issue when using TerminateProcessOnDisconnect in
Posted: Fri Aug 07, 2009 12:03 pm
by JADE Support >> Tue, 24 Jul 2001 1:59:46 GMT
We have recently dealt with a customer problem whereby they were using MS Excel to run a query over their JADE Database using ODBC via a Relational View. The problem they were encountering was that in singleUser mode the query would complete and then Excel would display the expected data. When they ran the same query in multiUser mode, Excel would to all intents and purposes run the query - based on disk activity and elapsed time. However, at about the time the data would normally be returned to Excel, Excel was disappearing without any exceptions or errors and without any information/errors being logged in the sql.log tracing.
We have now determined that this was being caused by the use of the TerminateProcessOnDisconnect=true setting in the [JadeClient] section of the ini file. This was behaving as intended such that when Excel disconnected from the DatabaseServer, the process was terminated. However, this is generally not the desired behaviour and you should therefore use a separate ini file that does not have TerminateProcessOnDisconnect=true in the [JadeClient] section of the ini file.
The TerminateProcessOnDisconnect=true setting in the [JadeClient] section of the ini file could also cause similar issues for ActiveX Exposure connections into JADE and also for clients who have written their own programs to access the DatabaseServer directly via the JOM API.
We have opened an NFS to have comments to this effect added to the JADE Product Information, and we will also create an FAQ for this on the JADE Web Site.
Thanks,
JADE Support.
jadesupport@discoverjade.com.
We have recently dealt with a customer problem whereby they were using MS Excel to run a query over their JADE Database using ODBC via a Relational View. The problem they were encountering was that in singleUser mode the query would complete and then Excel would display the expected data. When they ran the same query in multiUser mode, Excel would to all intents and purposes run the query - based on disk activity and elapsed time. However, at about the time the data would normally be returned to Excel, Excel was disappearing without any exceptions or errors and without any information/errors being logged in the sql.log tracing.
We have now determined that this was being caused by the use of the TerminateProcessOnDisconnect=true setting in the [JadeClient] section of the ini file. This was behaving as intended such that when Excel disconnected from the DatabaseServer, the process was terminated. However, this is generally not the desired behaviour and you should therefore use a separate ini file that does not have TerminateProcessOnDisconnect=true in the [JadeClient] section of the ini file.
The TerminateProcessOnDisconnect=true setting in the [JadeClient] section of the ini file could also cause similar issues for ActiveX Exposure connections into JADE and also for clients who have written their own programs to access the DatabaseServer directly via the JOM API.
We have opened an NFS to have comments to this effect added to the JADE Product Information, and we will also create an FAQ for this on the JADE Web Site.
Thanks,
JADE Support.
jadesupport@discoverjade.com.