Strange behaviour when setting client_info and module in v$session

Question

Hello,
I've tried to set the CLIENT_INFO field in V$SESSION using DBMS_APPLICATION_INFO.SET_CLIENT_INFO but found a strange behaviour.
Normally the forms modules seems to set the field MODULE in V$SESSION to its name. If I use DBMS_APPLICATION_INFO.SET_CLIENT_INFO the CLIENT_INFO field is set correctly but the MODULE field is set to 'frmweb.exe' instead of the forms modules name.
I also tried to set the MODULE using DBMS_APPLICATION_INFO.SET_MODULE but then strangely the MODULE and MODULE_HASH field of the original frmweb.exe (the main applet?) entry and the entry for the forms module were the same (set to the new module name). From now on every newly opened module had 'frmweb.exe' as the module entry until I closed the forms application.
Example:
Entries in V$SESSION:
-- After start of forms application there is only one entry for the process:
PROCESS           MODULE            MODULE_HASH            CLIENT_INFO
1596:7204         frmweb.exe        854945150
-- When a new forms module is opened it looks like this:
PROCESS           MODULE            MODULE_HASH            CLIENT_INFO
1596:7204         frmweb.exe        854945150
1596:7204         my_module         1929284615
-- When the modified forms module that sets the client_info/module is opened this happens:
PROCESS           MODULE            MODULE_HASH            CLIENT_INFO
1596:7204         mod_module        3097977240
1596:7204         mod_module        3097977240             my client info
1596:7204         my_module         1929284615As one can see the entry of the forms application seems to be overriden (at least the MODULE and MODULE_HASH fields) but the CLIENT_INFO only changes for one of the entries?
The following code is responsible for the changes of CLIENT_INFO and MODULE:
    -- get client info
    client_info :=
        webutil_clientinfo.get_ip_address
        || ' (' ||
        webutil_clientinfo.get_user_name
        || ')'
    -- set client info
    DBMS_APPLICATION_INFO.SET_CLIENT_INFO(client_info);
    -- get module (set action to '')
    DBMS_APPLICATION_INFO.SET_MODULE(name_in('system.current_form'),''); I really don't understand, why it does not work properly.
Any help is appreciated!
Thanks in advance.

Answer 1

This was an application module pooling, activation / passivation issue.
After view objects had been set-up correctly, the problem disappeared.