![]() Maybe their VPN gateway is running an obsolete version of VPN server? Maybe, for the users' UX they're using Java Applet based VPN clients? New browsers don't allow running Java Applets (NPAPI in Firefox was abandoned in 2018). The answer lies probably in some kind of security policies in that company. So, ending Firebird attachments using SQL is the only option left for me - if such option exists at all? ![]() Database shutdown is out of the question - DB is in production mode. I have contacted the VPN administrator to cancel VPN sessions, but it takes time. Is there way how can I (using SYSDBA connection) end those other Firebird attachments from my current Firebird session? So - VPN sometimes retains sessions and those VPN sessions keeps the Firebird attachments in existences. When I am connectiong once more to the VPN and database I can see in the mon$attachments that the previous connection/attachment is still existing and its unresolved transactions are causing deadlock errors (that belong to the previous attachment - this can be verified exactly by the transaction number that is reported in the error message of deadlock error). ![]() Sometimes I just forget disconnect from database and I cancel/disonnect VPN session only. I am using VPN (Endpoint Security, Check Point) to establish connection to the Firebird 2.1 database from IBExpert on my computer. ![]()
0 Comments
Leave a Reply. |