Re: JDBC thin client connections

  • From: Irfan Momin <irfanwiz@xxxxxxxxx>
  • To: ora-apps-dba@xxxxxxxxxxxxx
  • Date: Tue, 17 Jul 2007 07:44:39 -0700 (PDT)

Hello Maris,

Thanx for the suggestion.  I will try it out and reply back.

Regards,
Irfan Momin
Oracle Applications DBA


----- Original Message ----
From: Maris Elsins <elmaris@xxxxxxxxx>
To: ora-apps-dba@xxxxxxxxxxxxx
Sent: Tuesday, July 17, 2007 6:25:01 PM
Subject: Re: JDBC thin client connections

Hi,

The problem is definitely in your DBC file (unless you have other application 
using the JDBC connections)

You have:
FND_JDBC_BUFFER_MAX=50%
FND_MAX_JDBC_CONNECTIONS=500

Which actually means that maximum number of JDBC connection for *each* JVM is 
500 and connections will be reused only when number of connections reaches 50% 
of FND_MAX_JDBC_CONNECTIONS = 250. So.... you will have to have a lot of 
connections to get them reused. 

I suggest you to change the FND_JDBC_BUFFER_MAX to a more reasonable value, 
like FND_JDBC_BUFFER_MAX=10;
I have a quite busy environment which works OK even with FND_JDBC_BUFFER_MAX=5

If you notice that this change increases load on you middle-tier too much (the 
load generated by reusing and managing the connection pool), you can increase 
the FND_JDBC_BUFFER_MAX step by step until the load is OK for you. 

If this doesn't help you enough. You can try increasing the 
FND_JDBC_BUFFER_DECAY_SIZE (how many connections the pool maintenance thread 
will try to free on each run) to let's say 30 and reduce 
FND_JDBC_BUFFER_DECAY_INTERVAL (how often the pool maintenance thread runs in 
seconds) to 45 to force the old sessions be released more aggressively. 

Don't do all the changes at once, change the parameters one by one.  I guess 
reducing the FND_JDBC_BUFFER_MAX should give you the desired effect, but you'll 
see.

hope this helps,
Maris Elsins 


On 7/17/07, Irfan Momin <irfanwiz@xxxxxxxxx> wrote:
Hello Raghavendra,
 
I traced the entries for all possible JMV's like OACore, Forms, Disco, etc in 
the XML file.  All have value one (1), which I think is minimum right? 
 
Still so many processes are spawned. why??
 
Regards,
Irfan Momin
Oracle Applications DBA


 
----- Original Message ----
From: Raghavendran Ravichandran < coolexpresso@xxxxxxxxx>
To: ora-apps-dba@xxxxxxxxxxxxx
Sent: Monday, July 16, 2007 11:38:37 AM 
Subject: Re: JDBC thin client connections

Hi , 

   One More Add-ons . 

The OACore is available in the XML File . 
The N-procs parameter defines the number of JVM's allocated for an Instance . 
Hence , Please change the nprocs value of OACORE in XML in a test Instance and 
try . 

The XML FILE entry is as follows :

<oacore_nprocs oa_var="s_oacore_nprocs">1</oacore_nprocs>

This entry is available only in AP Tier . 

Also , i would like to specify another suggestion . 

If its fine for you please change the Max Processes and Max Sessions Variable 
in Database Init.ora File . 

Thanks and Best Regards,
Raghavendra R 


On 7/15/07, Avadhani mys < avadhanimys@xxxxxxxxx> wrote: 
Hi Irfan,
One cannot confirm the status of the process as inactive by checking in 
v$session,Some processes  starts child processes and the master process some 
time becomes as inactive, 
But as Abdul stated you can change the parameter from 500 to 100 this will 
prevent the program being started, 



On 7/12/07, Kareem Abdul < akareem_qa@xxxxxxxxx > wrote: 
Hi Irfan,
 
Check the metalink Id : 278868.1
 
understand the parameters, you can tune according to your situation.
 
Regards
Abdul Kareem


Irfan Momin <irfanwiz@xxxxxxxxx> wrote:
Hello Abdul,

Thanx for your reply.  I am not able identify "no of JVMs for OACoreGroup in 
jserv.conf".  Can you please help me identifying this parameter. 

One more thing I would like to mention here is that even when the users are not 
doing any activity on Oracle Applications like a scenario where Oracle Apps is 
just started, I see as many as 97 JDBC thin client connections.  Does following 
your suggestion reduce the count of initial spawning of JDBC connections. 

But, the main question here still remains.  How can one get rid of this 
connections gracefully. 

Regards,
Irfan Momin
Oracle Applications DBA

----- Original Message ----
From: Kareem Abdul < akareem_qa@xxxxxxxxx>
To: ora-apps-dba@xxxxxxxxxxxxx
Sent: Thursday, July 12, 2007 6:59:13 PM 
Subject: Re: JDBC thin client connections


Hi Irfan,
 
Work around,
 
Reduce your FND_MAX_JDBC_CONNECTIONS=500 to 100. 
 
JDBC connections are made and kept for live by Jserv for quick connectivity. If 
your instance don't have lot of users (both Forms & Self Service) reduce this 
paramater to 100 and 
evaluate situation. 
 
After changing the dbc file you need to bounce.
 
If you run autoconfig for some reason then settings will be reverted back. so 
be careful on autoconfig. 
 
Once you identified proper settings then change in context file and run 
autoconfig so that change will be effect permenantly.
 
Extras
By setting 100 you are limiting the OACoreGroup JVM to serve only 100 
connections. For more users connections increase the no of JVMs for OACoreGroup 
in jserv.conf instead increasing FND_MAX_JDBC_CONNECTIONS.
 
If performance is an issue you need to check jvm memory parameters.
 
Hope this helps you.
 
Regards
Abdul Kareem
 


Irfan Momin <irfanwiz@xxxxxxxxx> wrote:
Hello All,

I am facing a problem with Oracle 11.5.10 R2 Instance.  Too many JDBC thin 
client connections are spawned.  The issue is that these connections do not 
terminate automatically there by eating up resources.  


   SERIAL# USERNAME                       PROGRAM                               
                       STATUS   LOGIN_TIME            LAST_ACTIVITY
---------- ------------------------------ 
------------------------------------------------------------ -------- 
--------------------- ---------------------
       830 APPLSYSPUB                     JDBC Thin Client                      
                       INACTIVE 11-JUL-07 19:41       11-JUL-07 19:53 
        99 APPLSYSPUB                     JDBC Thin Client                      
                       INACTIVE 11-JUL-07 18:44       11-JUL-07 18:46
        21 APPLSYSPUB                     JDBC Thin Client                      
                       INACTIVE 11-JUL-07 18:39       11-JUL-07 18:55 
        89 APPLSYSPUB                     JDBC Thin Client                      
                       INACTIVE 11-JUL-07 19:43       12-JUL-07 00:12
        85 APPLSYSPUB                     JDBC Thin Client                      
                       INACTIVE 11-JUL-07 18:18       11-JUL-07 18:30
        12 APPLSYSPUB                     JDBC Thin Client                      
                       INACTIVE 11-JUL-07 18:43       11-JUL-07 18:00
        52 APPS                           JDBC Thin Client                      
                       INACTIVE 12-JUL-07 02:07       12-JUL-07 03:50
        68 APPS                           JDBC Thin Client                      
                       INACTIVE 12-JUL-07 02:46       12-JUL-07 03:41 
       421 APPS                           JDBC Thin Client                      
                       INACTIVE 12-JUL-07 02:19       12-JUL-07 03:11
       278 APPS                           JDBC Thin Client                      
                       INACTIVE 12-JUL-07 02:19       12-JUL-07 03:34
.......
112 rows selected.

As you can see there are 112 INACTIVE connections. that too of JDBC type.

I have following hardware configuration.
RAM                 2GB 

Processor
model name      : AMD Opteron(tm) Processor 865
stepping        : 0
cpu MHz         : 1803.035
cache size      : 1024 KB

and following Oracle settings

SQL> sho parameter sga

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE 
sga_max_size                         big integer 840M
sga_target                           big integer 572M

I have also changed values of DBC file.  Below is the output of the DBC file.

#DB Settings
#Wed Jul 11 17:59:34 EDT 2007
GUEST_USER_PWD=GUEST/ORACLE 
APPL_SERVER_ID=290D803B34628364E040E90A140A547A37706787018120898103192181257228
FND_JDBC_BUFFER_DECAY_INTERVAL=60
APPS_JDBC_DRIVER_TYPE=THIN
FND_JDBC_BUFFER_MIN=8
DB_NAME=R10TECH
GWYUID=APPLSYSPUB/PUB
FND_JDBC_BUFFER_MAX=50%
FND_JDBC_STMT_CACHE_FREE_MEM=TRUE
FND_JDBC_STMT_CACHE_SIZE=200
TWO_TASK=R10TECH
FND_MAX_JDBC_CONNECTIONS=500
FND_JDBC_USABLE_CHECK=true
FNDNAM=APPS
FND_JDBC_PLSQL_RESET=false
DB_PORT=1521
FND_JDBC_CONTEXT_CHECK=true
FND_JDBC_BUFFER_DECAY_SIZE=15
DB_HOST=soclxs3db21.solnet.com 

Even making changes in the DBC file did not do any good.  Please comment if my 
DBC settings are correct.  

I also tried setting editing sqlnet.ora with sqlnet.expire_time option but no 
good.

NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
SQLNET.EXPIRE_TIME= 2

I am in need for a solution desperately.  Any help on this one ids greatly 
appreciated.

Thanx in Advance.

Regards,
Irfan Momin
Oracle Applications DBA 








Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. 




Get the Yahoo! toolbar and be alerted to new email wherever you're surfing. 





Yahoo! oneSearch: Finally, mobile search that gives answers , not 


Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, 
photos & more. 






-- 
R.Raghavendran
Associate Consultant 
Oracle Solution Service India Pvt. Ltd 
Bangalore 
9886764039.





Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.


       
____________________________________________________________________________________
Building a website is a piece of cake. Yahoo! Small Business gives you all the 
tools to get online.
http://smallbusiness.yahoo.com/webhosting 

Other related posts: