GemConnect and user action libraries
During session logout, GemStone normally clears the user action caches
and unloads the associated user action libraries. But when GemConnect
is used, the release of the GemConnect user action library causes various
problems due to signals sent from Oracle background processes being dispatched
to now non-existent signal handlers. To avoid this, we now keep the user
action libraries loaded across session logouts when GemConnect is used.
This is normally invisible to the user, but could have side effects on
sessions which load other user action libraries along with GemConnect,
and repeatedly login/logout and load/reload the libraries. Possible problems
could include spurious errors about the libraries already being loaded
when the reload is attempted. Also, space management will be less than
optimal, as the libraries are not being cleared.
Workaround
Modify code to ignore "user action library already loaded" errors.
Last updated: 10/2/23