Frank Schönheit wrote: > ... insightful info. about OO Base connection management ...
Thanks, Frank. Your advice is very helpful to me to choose the next direction for diagnosing this OO Base problem of connection to embedded HSQL DB (*.odb). Meanwhile, I have successfully identified a part of the code managing the corrupted connection state info. I have temporarily made OO Base HSQL connection work. Details are provided below. Please advise if there is a way to extract the connection state info. Maybe more insight can be gleaned from the data. Suggestions on strategies to diagnose this problem are very welcome. Based on this incident, OO Base connection to HSQL *.odb seems vulnerable to malicious virus attack. Remote connection objects, including OO BeanShell, MS Net, Java, etc., can initiate connection to OO Base and deliberately mess up OO Base connection management. I do not know if OO Base connection to other types of databases can be corrupted as I do not have time to test. Ironically I still have not figured out how I messed up the OO Base connection. Thanks to all who have advised. Ray --- Hypothesis: My instinct has suggested from the very beginning that it is more likely caused by a corrupted connection state info. since connections to non-HSQL DB in OO Base still work. I just have no idea where the culprit state info. storage is located. I temporarily made OO Base work by adding another version of Java JRE. Now 2 versions of JRE exist on my PC. The working and failure behavior of OO Base HSQL connections can now be turned on and off reproducibly by alternating OO Java reference between Java JRE's. Java JRE 1.5.0-08 OO Base currently working Java JRE 1.4.2-07 OO Base currently not working --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
