07.12.2017 19:15, Jiří Činčura wrote:
For example, one instance run in user session (for ex. embedded
connection)
and second instance run as a service.
That was original idea for hunting - disabling that somehow and then
waiting where something breaks. I'm at least blindly trying to find some
application doing this.
You may detect embedded connection in ON CONNECT trigger using
RDB$GET_CONTEXT('SYSTEM', 'NETWORK_PROTOCOL')
it returns NULL for embedded connection.
Also sometimes the error pops up from "on connect" or "on begin
transaction" trigger, not when attaching. Right now for example:
At trigger 'DBCONNECT' line: 6, col: 3 ---> Database is probably already
opened by another engine instance in another Windows session
This trigger is only accessing MON$ATTACHMENTS.
This is very strange. Does it put corresponding message into firebird.log ?
If yes - how exactly it looks ?
Regards,
Vlad
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
