> Subject: Re: Populating Oracle v$session.program from Tomcat Context.xml
> From: dfis...@jmlafferty.com
> Date: Mon, 14 Mar 2011 18:08:53 -0700
> To: users@tomcat.apache.org
>
> >>>> We have some working tomcat 6 instances that we'd like to identify
> >>>
> >>>
> >>> Can you use the combination of machine and schema name to identify the
> >>> instance? You didn't detail your environment, but if you have a cluster,
> >>> then the machine name would uniquely identify the instance. If you have
> >>> multiple different instances on the same machine, then surely the schema
> >>> name would allow you to identify which user it is? This covers all
> >>> possibilities unless you have different apps on the same machine in
> >>> different tomcat instances talking to the same schema.
> >>>
> >>> Chris
> >>>
> >>
> >> We are running all of our web-applications from two machines, and they
> >> all use the same schema/username, so unfortunately I need the program,
> >> client_info, module, etc field to identify them.
> >>
> >> We are running a RAC, and I'm querying gv$session which should get me
> >> all cluster member connections.
> >>
> >> As David said, this does work with the thin driver, but I need the
> >> service/load balancing functionality from OCI. Any more suggestions
> >> are welcome!
> >>
> >
> > Does anyone else have any additional thoughts on this? I'd sure
> > appreciate more input.
>
> I did some googling and I think that you will have to actually set this value
> from your code somehow.
>
> This thread is found in multiple places:
> http://www.rhinocerus.net/forum/databases-oracle-misc/569644-setting-v-session-program.html
> a
>
> The attribute is OCI_ATTR_MEMPOOL_APPNAME.
>
> The package used is dbms_application_info.
>
> Google "jdbc api dbms_application_info" and this link
> http://stackoverflow.com/questions/53379/using-dbms-application-info-with-jboss
> may help you ...
>
> I do wonder if using module and action from V$session might be more
> appropriate and fine grained.
>
> Regards,
> Dave
MG>context.xml are for the most part static declrataions loaded at webapp
initialisation
MG>so if i follow your path..read in the base attributes from Tomcat Context
MG>later when the webapp is loaded ..override Oracle specific attributes from
Oracle V$session
MG>from my experience you cannot call OCI from (thin) type4 JDBC Oracle Drivers
MG>be aware OCI loads native binaries (so and .a libs on unix) and dll on
windows.. be prepared to make (Oracle) version specific calls for OCI functions
MG>Martin-
>
> >
> > TIA,
> >
> > Dan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
