Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of cjderham@gmail.com designates
 209.85.212.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:reply-to:in-reply-to:references:from:date
         :x-google-sender-auth:message-id:subject:to:content-type;
        b=MpHmVKnOfIXqj2nPuMBH1K88QJ4Ff1RPhxZeDIAC4q36ref72VD59zd8RiytqPwl9a
         /qyfo/9GBSWfjqpd/MlviBzuO/tECPhe8jdET5AUI0VpzWin1XsjnsRbNAU8GNbiAGkf
         N5hmJxIstAPpTwBtFdfS+UBoWU0xTx+h3h6Aw=
MIME-Version: 1.0
Sender: cjderham@gmail.com
Reply-To: chris@derham.me.uk
In-Reply-To: <85F7282D74974107A62C28E8277AF3DB@phoenix>
References: <AANLkTik5_xQhWuJJyEKoKZTiCxuY7h_ZPpyfhi1n79VW@mail.gmail.com>
 <AANLkTik8VXq_17sXsG8_+jyLCAWvcNj4cMGm07WeSDEp@mail.gmail.com>
 <AANLkTi=1dntonAJqmCP5pxiVxdZeqfcax3PEPCOXugoW@mail.gmail.com>
 <AANLkTi=ZNZ05B4+C2RBQdbN_s7uO=Z6L8Zt-2cTOeN8S@mail.gmail.com>
 <AANLkTimuqtRfPxNgS1T0UC4dkXohJt7KZcHUBQPuG5=V@mail.gmail.com>
 <AANLkTimxgaOaCL0a-7sQEH-kdDm1h86hdqHera9V450R@mail.gmail.com>
 <AANLkTimUgrk0_T5QiDWnJvEUL6NB1SsH7uBkVog0AA7k@mail.gmail.com>
 <85F7282D74974107A62C28E8277AF3DB@phoenix>
From: chris derham <chris@derham.me.uk>
Date: Thu, 17 Mar 2011 00:00:32 +0000
Message-ID: <AANLkTi=6yAU6r03N9gAQWcuKy5fUrSg-vvPesfgDGtQ1@mail.gmail.com>
Subject: Re: Populating Oracle v$session.program from Tomcat Context.xml
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=20cf304346f0ccea46049ea25a65

--20cf304346f0ccea46049ea25a65
Content-Type: text/plain; charset=ISO-8859-1

>
>
> The problem he appears to be encountering is that he is unable to customize
> the
> value in v$session.program. The reason for the problem is that he does not
> know
> how to do it either when using the OCI jdbc driver (it is likely not
> possible).
>

Jason,

So oci or thin driver is largely irrelevant. For thin you configure the dbcp
connection pool with

jdbc:oracle:thin:@//[HOST][:PORT]/SERVICE

or if using oci use

jdbc:oracle:oci:@myhost:1521:orcl

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

Chris

--20cf304346f0ccea46049ea25a65--