Last updated on OCTOBER 19, 2016
Applies to:Oracle Applications Framework - Version 220.127.116.11 to 12.1.3 [Release 11.5.10 to 12.1]
Oracle iRecruitment - Version 18.104.22.168 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
This problem can occur on any platform.
JDBC sessions are not deallocated by the 'per.irc.candidateSelfService.server.VisitorAM' application module. The number of JDBC connections for the VisitorAM is high and seems to keep increasing over time. This can be verified using the SQL noted below:
select s.machine, s.username, s.module, s.inst_id, count(*) how_many
from (select distinct PROGRAM, PADDR, machine, username, module, inst_id from gV$SESSION) s, gv$process p
where s.paddr = p.addr
and p.inst_id = s.inst_id
group by s.machine,s.username, s.module, s.inst_id
One can additionally notice that the number of sessions taken by the GUEST user is high and tends to increase in number over time. This can be verified using the SQL noted below:
select user_name, count(*) How_many_sessions
from icx_sessions icx, fnd_user u
where icx.user_id = u.user_id
and disabled_flag != 'Y'
and PSEUDO_FLAG = 'N'
and (last_connect + decode(FND_PROFILE.VALUE('ICX_SESSION_TIMEOUT'), NULL,limit_time,0,limit_time,FND_PROFILE.VALUE('ICX_SESSION_TIMEOUT')/60)/24) > sysdate
and counter < limit_connects
group by user_name
order by 2 desc
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms