go to the initORA file in oracle installation and check the value for the param

PROCESSES
(OR)
select value from v$parameter where name='processes';

select
*
--b.machine box,
--b.status,
--b.osuser os_user,
--b.program program,
-- last_call_et
from
v$session b, v$process a
where
b.paddr = a.addr and type='USER'
and b.status = 'INACTIVE';
-- Please check the time of the session being created
--Inactive sessions connected from web application for more than 1 hour
select p.spid, s.sid,s.last_call_et/3600 last_call_et ,s.status,s.action,
s.module,s.program,t.disk_reads,lpad(t.sql_text,30) "Last SQL"
from gv$session s, gv$sqlarea t,gv$process p
where s.sql_address =t.address and
s.sql_hash_value =t.hash_value and
p.addr=s.paddr and
s.status='INACTIVE'
and s.program='JDBC Thin Client'
and s.last_call_et > 3600
order by last_call_et;
If you see the number of inactive or active programs linked to your web applicat
ion is more than the v$parameter setting, then the problem is with the JDBC conn
ection.
Temp solution:
Kill all the inactive processes associated with the web application program.
Use kill session syntax with PID

Please go through this link for the detailed information on inactive process and
killing the sessions which are inactive
http://www.dba-oracle.com/t_inactive_sessions.htm