Hello.
I'm using an internet translation, so sorry if it's hard to understand.
When I perform the following operations, the HSQLDB in memory is not deleted and remains.
Set memory=true and password=password to the connection URL, and use UcanAccessDriver#connect to connect to the accdb file with no password set. The connection succeeds.
With the HSQLDB in memory, connect to the accdb file connected in step 1 again with the password unset. The connection will fail and the following Exception will be thrown.
The activeConnection that was incremented in step 2 continues to remain, so the DbReference#shutdown set in the Timer is not called.
The first is that UCanAccess is behaving in such a way that if I connect to an accdb file that does not have a password set by including the password in the connection URL, the password will be set in the HSQLDB.
The second is that DbReference#shutdown set to Timer is not called if an Exception occurs after the activeConnection is incremented in the UcanaccessConnection constructor.
Are there any countermeasures or fixes planned for these?
The version I'm using
ucanaccess-5.0.1
jackcess-3.0.1
jackcess-encrypt-3.0.0
hsqldb-2.5.0
Last edit: takumi inoue 2021-09-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
I'm using an internet translation, so sorry if it's hard to understand.
When I perform the following operations, the HSQLDB in memory is not deleted and remains.
stack trace
I believe there are two problems.
The first is that UCanAccess is behaving in such a way that if I connect to an accdb file that does not have a password set by including the password in the connection URL, the password will be set in the HSQLDB.
The second is that DbReference#shutdown set to Timer is not called if an Exception occurs after the activeConnection is incremented in the UcanaccessConnection constructor.
Are there any countermeasures or fixes planned for these?
The version I'm using
ucanaccess-5.0.1
jackcess-3.0.1
jackcess-encrypt-3.0.0
hsqldb-2.5.0
Last edit: takumi inoue 2021-09-01
No, they were unknown errors, but I'll verify the bugs ASAP and let you know here when the fixes will be released.
Last edit: Marco Amadei 2021-09-03