Chris,
> You can use the following in the connectionInitSqls to make sure a suitable
> variable it set
>
> exec dbms_application_info.set_action('INSERTING');
>
> The site http://psoug.org/reference/sys_context.html references a bucket
> load of different context parameters that can be set - CLIENT_IDENTIFIER and
> CLIENT_INFO seem likely candidates. Then each time a connection is added to
> the pool, suitable context parameters are set, and you can view them when
> querying gv$session.
>
> This seems like a suitable fix for the question originally posed.l I would
> like to learn if this won't work, what is wrong with it. Without feedback,
> hard to understand what is wrong
I plan to try this technique soon. It would really help us understand our
oracle load from tomcat vs. applications.
Thanks!
Regards,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
