Inactive sessions with sql_address=00

hi gurus,
db: oracle 11g
application: weblogic
i could see lots of invalid sessions with sql_address=00 and blank sql_id appearing intermittently and causing connection issues.
prev_sql_id of majority of the rows are the same and the sql_text is "select count(*) from dual" !!!
what could be the reason for these invalid sessions? not able to understand the prev sql_text also
please help,
charles

The sessions are not invalid. They are just doing nothing.
Also this does not cause connection problems.
Applications like weblogic have several 'features'
- They frequently execute dummy sql to check database availabilty, like select count(*) from dual
- They don't have persistent connections
This is addressed by setting up shared server and enabling connection pooling.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

  • DBA Reports large number of inactive sessions with 11.1.1.1

    All,
    We have installed System 11.1.1.1 on some 32 bit windows test machines running Windows Server 2003. Everything seems to be working fine, but recently the DBA is reporting that there are a large number of inactive sessions throwing alarms that we are reaching our Max Allowed Process on the Oracle Database server. We are running Oracle 10.2.0.4 on AIX.
    We also have some System 9.3.1 Development servers that point at separate schemas in this environment and we don't see the same high number of inactive connections?
    Most of the inactive connections are coming from Shared Services and Workspace. Anyone else see this or have any ideas?
    Thanks for any responses.
    Keith
    Just a quick update. Originally I said this was only with 11.1.1.1 but we see the same high number of inactive sessions in 9.3. Anyone else see a large number of inactive sessions. They show up in Oracle as JDBC_Connect_Client. Does Shared Service, Planning Workspace etc utilize persistent connections or does it just abandon sessions when the windows service associated with an application is shutdown? Any information or thoughts are appreciated.
    Edited by: Keith A on Oct 6, 2009 9:06 AM

    Hi,
    Not the answer you are looking for but have you logged it with Oracle as you might not get many answers to this question on here.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Kill inactive sessions with no programs run it

    hi all,
    my database is 10gR2 with developer 6i
    the database have huge number of sessions with no programs running it like oracle form, some of those sessions stack in v$session table due to power failure.
    restart server solve the problem, but it is not efficient.
    is there any method to fined witch of database sessions is actually connect to the database and have application running it ?

    This script will give you the complete detail of Session , PID and Program which is running in dagtabase level.
    You can include the "STATUS" coloumn from v$session to get user status.
    Script is like this:
    set echo off;
    set termout on;
    set linesize 80;
    set pagesize 60;
    set newpage 0;
    select
    rpad(c.name||':',11)||rpad(' current logons='||
    (to_number(b.sessions_current)),20)||'cumulative logons='||
    rpad(substr(a.value,1,10),10)||'highwater mark='||
    b.sessions_highwater Information
    from
    v$sysstat a,
    v$license b,
    v$database c
    where
    a.name = 'logons cumulative'
    ttitle "dbname Database|UNIX/Oracle Sessions";
    set heading off;
    select 'Sessions on database '||substr(name,1,8) from v$database;
    set heading on;
    select
    substr(a.spid,1,9) pid,
    substr(b.sid,1,5) sid,
    substr(b.serial#,1,5) ser#,
    substr(b.machine,1,6) box,
    substr(b.username,1,10) username,
    -- b.server,
    substr(b.osuser,1,8) os_user,
    substr(b.program,1,30) program
    from v$session b, v$process a
    where
    b.paddr = a.addr
    and type='USER'
    order by spid;
    ttitle off;
    spool off;
    Save this script with your desire name and run in Database.
    Mukesh

  • Looking for a script to kill all inactive sessions

    Does anyone have a script to kill all INACTIVE sessions (with EXECUTE IMMEDIATE)?

    I suggest you to specify which OS you are talking about.
    The inactive status on the V$SESSION doesn't mean the user is not doing any thing, it only means the oracle server process is not processing any thing by the time it was queried. On OLTP systems Oracle Server Processes remain INACTIVE for more than 95% of the time, so it is advisable to configure shared servers.
    If you are really concerned about idle time, then I suggest you to configure profiles.
    On the pool mechanism you should address the microsoft side, if this, as far as I understood and guessed, application server is IIS.
    I suggest you further reading on the Killing sessions script and different session status (check the sniped status) here:
    Re: session inactive ??
    Re: make a job to delete the sniped sessions
    Re: How do I put a timeout in my DataBase?
    Re: Killing Session with Locks in Linux
    ~ Madrid

  • PL/SQL procedure to kill inactive session

    Hi all ,
    Please i am trying to write a procedure to kill inactive sessions of the shema 'TESTSCHEMA' .This is my first procedure , am not use to pl/sql but i went through many turtorial but have some errors at compliation .when i try to compile the procedure the errors are as below :
    15:50:28 Start Find Objects [TESTSCHEMA@TESTDB_UNIX(2)] ...
    15:50:28 End Find Objects [TESTSCHEMA@ TESTDB_UNIX(2)]
    15:50:32 Start Compiling 1 object(s) ...
    15:50:32 Executing ALTER PROCEDURE fib_dead_cnx_cleanup COMPILE ...
    15:50:32 [13:2] PL/SQL: ORA-00933: SQL command not properly ended
    15:50:32 [9:3] PL/SQL: SQL Statement ignored
    15:50:32 [18:12] PLS-00103: Encountered the symbol "(" when expecting one of the following:
    15:50:32 constant exception <an identifier>
    15:50:32 <a double-quoted delimited-identifier> table LONG_ double ref
    15:50:32 char time timestamp interval date binary national character
    15:50:32 nchar
    15:50:32 The symbol "<an identifier>" was substituted for "(" to continue.
    15:50:32 [18:21] PLS-00103: Encountered the symbol "LOOP" when expecting one of the following:
    15:50:32 := ; not null default character
    15:50:32 The symbol "; was inserted before "LOOP" to continue.
    15:50:32 [27:8] PLS-00103: Encountered the symbol "ALTER" when expecting one of the following:
    15:50:32 begin case declare exit for goto if loop mod null pragma
    15:50:32 raise return select update while with <an identifier>
    15:50:32 <a double-quoted delimited-identifier> <a bind variable> <<
    15:50:32 close current delete fetch lock insert open rollback
    15:50:32 savepoint set sql execute commit forall merge pipe
    15:50:32 Compilation complete - 5 error(s) found
    15:50:32 End Compiling 1 object(s)
    below is the procedure code :
    CREATE OR REPLACE
    PROCEDURE fib_dead_cnx_cleanup
    AS
    l_serial     CHAR(100);
    l_sid CHAR (100);
    l_sid_serial CHAR(100);
    l_count      NUMBER(10,0);
    CURSOR session_cur IS
              SELECT sid,serial#,sid||','||serial# as sid_serial
         FROM v$session
         WHERE username='EBBFCAT' and schemaname='TESTSCHEMA'
         and status='INACTIVE'
    BEGIN
         BEGIN
         l_count := 0;
                   OPEN session_cur;
                        WHILE ( 1 = 1) LOOP
                             BEGIN
                                  FETCH session_cur INTO l_sid ,l_serial,l_sid_serial ;
                                       EXIT WHEN session_cur%NOTFOUND ;
                                  BEGIN
                                       alter system kill session 'l_sid_serial' ;
                                  END;     
                             END;
                        END;
                   CLOSE session_cur;
         END;
    END FIB_DEAD_CNX_CLEANUP;
    Thanks

    Hi,
    Never write, let alone post, unformatted code.
    When posting any formatted text on this site, type these 6 characters:
    &#123;code&#125;
    (small letters only, inside curly brackets) before and after sections of formatted text, to preserve spacing.
    Among the benefits of formatting: you can indent to show the extent of blocks, such as BEGIN-END.
    Different types of blocks need modifiers after the end, such as "END *IF* " and " END *LOOP* ". If each opening statement (BEGIN, IF, LOOP) is directly above its corresponding END, then it's easy to check if you got the right modifier.
    Here's what you code looks like with some formatting, and a couple of corrections added. Look for -- comments.
    CREATE OR REPLACE
    PROCEDURE fib_dead_cnx_cleanup
    AS
         l_serial     CHAR(100);
         l_sid          CHAR (100);
         l_sid_serial     CHAR(100);
         l_count          NUMBER(10,0);
         CURSOR session_cur IS
                SELECT  sid
                ,       serial#
                ,       sid     || ','
                                      || serial#     as sid_serial
                FROM     v$session
                WHERE      username     = 'EBBFCAT'
                and     schemaname     = 'TESTSCHEMA'
                and     status          = 'INACTIVE';          -- need semicolon here
    BEGIN
         BEGIN                                   -- Why?
              l_count := 0;
              OPEN session_cur;
              WHILE ( 1 = 1)
              LOOP
                    BEGIN                         -- Why?
                         FETCH  session_cur
                         INTO   l_sid
                         ,          l_serial
                         ,          l_sid_serial ;
                               EXIT WHEN session_cur%NOTFOUND ;
                         BEGIN                    -- Why?
                             alter system kill session 'l_sid_serial' ;    -- Not a PL/SQL command
                               END;
                          END;
                END LOOP;                         -- LOOP ends with END LOOP
                CLOSE session_cur;
            END;
    END      FIB_DEAD_CNX_CLEANUP;Take baby steps.
    I've been wrtiing PL/SQL for 20 years, and I would never write that much code at once. If you're a beginner, all the more reason to start small. Write as little as possible, test, debug and test again (if necessary). When you have someting working, add 2 or 3 more lines and test again.
    It looks like you have three BEGIN statements that don't serve any purpose. You should get rid of them (and their corresponding END statements, of course).
    One error I did not fix: ALTER SYSTEM is not a PL/SQL statement. It's a SQL statement. You can run a SQL statement inside PL/SQL by using dynamic SQL, where you construct a string containing the SQL statement, and then use dbms_sql or EXECUTE IMMEDIATE to run it.
    Edited by: Frank Kulash on Aug 18, 2009 12:37 PM

  • Old Oracle Session with Tomcat is not kiiling automatically

    Hi,
    I am facing a problem of increasing inactive oracle sessions with tomcat, Old Oracle sessions with tomcat are visible with new one.
    if somebaody did not restarted tomcat gracefully, then does Oracle keep the session connected or is there any way that whenever any one restarted tomcat abnormally, Oracle session can be killed.
    I had restart the database to kill session.

    Could you please tell me that where do i set this parameter in parameter file or sql net file and what is the recommended value, do you have any document on this.
    Another thing tomcat is in other server machine and my database is in different server machine, killing process in tomcat server machine manually may not kill linux process on oracle database machine and therefore oracle sessions are still there.
    Is it possible?
    Edited by: user605066 on 28-Aug-2008 04:59

  • Inactive sessions in v$session.  True problem

    Hi,
    I am working in an Oracle 9i/Weblogic/J2EE platform. And when i look for session info in v$session view, i see that there are many sessions that have a status "Inactive". I already figured out what it means- the session is ACTIVE when it is doing an SQL query at the time and the session is INACTIVE when it is not doing an SQL query at that particular moment.
    But i have questions:
    1) If a client logs in to my webapplication and does a SQL query- then the sessions status is ACTIVE. After that, when the client just leaves (logs out just closes the browser) then Oracle marks that connection as 'INACTIVE'- Oracle does not KILL that session.
    Ok let that be, but can another client then log in to my webapplication (from different computer) and get that same INACTIVE connection and start to use it?? If not, then these "abandoned" connection are truly useless, because they still use ORACLE resources (memory).
    2)Another thing is that there are many INACTIVE sessions in v$session that have a name "plsqldev.exe" in PROGRAM column. That is a database client that i use to connect directly to my DB. But basicly i have only one PL/SQL program with one SQL query window open (this session is marked ACTIVE in v$session). So are these other 10 INACTIVE "plsqldev.exe" sessions meant for new plsql clients that may start to use the database or can only that particular user for whom the session was created at first place use that session?
    And finally- sessions that are INACTIVE and have "plsqldev.exe" as a PROGRAM in v$session - is there any chance that a client logs in to webapplication and then gets that INACTIVE session?
    If not, then these 10 INACTIVE plsqldev sessions (allthough the user has maybe shut down the program) are wasteless for webapplication users and they just starve the database.
    Also a screenshot for illustration.
    Waiting for your comments,
    Thanks!

    If connection pooling is in use then yes a different end-user can reuse the "inactive" session. Remember that ACTIVE and INACTIVE really only refers to if the session is executing SQL at the exact moment you query v$session.
    In the case of a dedicated user connection using a product like Oracle Forms where the user spends much of the time reading and filling in screen fields the Oracle background session can show INACTIVE almost constantly because the queries being ran by the user are very fast.
    Take a look at the last_call_et column. This is the time in seconds from when the last SQL statement was issued (not completed). If this value is resetting then the queries are being done.
    If the time is large and the status is INACTIVE then you could have a 'dead' or 'runaway' background process which is a background process without a front-end process. Those can and should be terminated. For that matter sessions that are idle for long periods of time should probably also be killed. If nothing else runaway and idle sessions may make it appear you are using all your licensed connections even if you really are not.
    Most connection pools wil automatically restart a terminated connection so if you clean-up process terminates an idle pooled connection it should not be a problem.
    HTH -- Mark D Powell --

  • Active vs Inactive sessions

    We are using Oracle 11 as a backend to PowerSchool (a student information system) with 6 application servers (dc-ps-01 thru -06). Using the following SQL, we are seeing numerous INACTIVE sessions vs ACTIVE.
    select
    count(b.machine) as mCount,
    b.machine box,
    b.status,
    b.osuser os_user,
    b.program program
    from
    v$session b, v$process a
    where
    b.paddr = a.addr and type='USER'
    group by
    b.machine,b.osuser,b.program,b.status
    order by
    b.status, mCount desc, box;
    Sample output:
    MCOUNT Box Status OS_USER Program
    *2     DC-PS-01*     ACTIVE     powerschool     JDBC Thin Client
    1     DC-PS-DB1     ACTIVE     DC-PS-DB1$     OMS
    1     DC-PS-DB1     ACTIVE     SYSTEM     ORACLE.EXE (J001)
    1     DC-PS-DB1     ACTIVE     SYSTEM     ORACLE.EXE (J000)
    406     DC-PS-05     INACTIVE     powerschool     JDBC Thin Client
    *44     DC-PS-01*     INACTIVE     powerschool     JDBC Thin Client
    36     DC-PS-03     INACTIVE     powerschool     JDBC Thin Client
    32     DC-PS-04     INACTIVE     powerschool     JDBC Thin Client
    28     DC-PS-02     INACTIVE     powerschool     JDBC Thin Client
    17     DC-PS-06     INACTIVE     powerschool     JDBC Thin Client
    7     DC-PS-DB1     INACTIVE     DC-PS-DB1$     OMS
    While the number of ACTIVE sessions fluctuate, the number of INACTIVE ones do not decrease. Would someone explain the internal working of this?
    Thanks!

    Note that the status column of v$session only shows ACTIVE while the Oracle session background process is busy performing a SQL statement on behalf of the front-end session. If the application spends most of its time with the user entering data onto or reading results off a screen then the session is going to appear INACTIVE most of the time in Oracle.
    Also check the last_call_et to see how long it has been since the session issued a request to Oracle. This is how to tell if the session is truely INACTIVE.
    If the front-end application uses connection pooling then depending on how many connections the application is set to grab and what kind of connection pool session management the front-end product provides you can have a lot of basically unneeded and truely inactive sessions.
    HTH -- Mark D Powell --

  • Inactive sessions increasing in database

    Hi
    Recently i migrated Oracle9i database to oracle10g database 64 bit on windows 2008 server.
    After Migration.Inactive sessions are not automatically flushing from database,and these inactive sessions are reaching maximum sessions limits that leads to Database Hang.
    How can i solve this inactive sessions problem?
    Thanks
    With Regards
    OH

    damorgan wrote:
    desc sys.kottd$Interesting table and custom data type.
    SQL> set long 9999
    SQL> col SQL format a50
    SQL>                  
    SQL> select           
      2          DBMS_METADATA.get_ddl( 'TABLE', 'KOTTD$', 'SYS')        as SQL
      3  from       dual;                                                     
    SQL
      CREATE TABLE "SYS"."KOTTD$" OF "SYS"."KOTTD"
    OIDINDEX  ( PCTFREE 10 INITRANS 2 MAXTRANS 255
      STORAGE(INITIAL 65536 NEXT 1048576 MINEX    
    TENTS 1 MAXEXTENTS 2147483645                 
      PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFF
    ER_POOL DEFAULT)                                 
      TABLESPACE "SYSTEM" )                          
    PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS
    LOGGING                                                 
      STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MA    
    XEXTENTS 2147483645                                     
      PCTINCREASE 0 FREELISTS 1 FREELIST GRO                
    UPS 1 BUFFER_POOL DEFAULT)                              
      TABLESPACE "SYSTEM"                                   
    SQL>
    SQL>
    SQL> select
      2          DBMS_METADATA.get_ddl( 'TYPE', 'KOTTD', 'SYS')        as SQL
      3  from       dual;                                                   
    ERROR:                                                                  
    ORA-31603: object "KOTTD" of type TYPE not found in schema "SYS"        
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105                            
    ORA-06512: at "SYS.DBMS_METADATA", line 2805                            
    ORA-06512: at "SYS.DBMS_METADATA", line 4333                            
    ORA-06512: at line 1                                                    
    no rows selected
    SQL>
    SQL> col attr_name format a30
    SQL> col attr_type_name format a30
    SQL> select                      
      2          attr_no,
      3          attr_name,
      4          attr_type_name
      5  from       dba_type_attrs
      6  where      type_name = 'KOTTD'
      7  and        owner = 'SYS'
      8  order by attr_no;
       ATTR_NO ATTR_NAME                      ATTR_TYPE_NAME
             1 KOTTDKVN                       UNSIGNED BINARY INTEGER(32)
             2 KOTTDSCH                       VARCHAR2
             3 KOTTDNAM                       VARCHAR2
             4 KOTTDUVN                       VARCHAR2
             5 KOTTDTC                        UNSIGNED BINARY INTEGER(16)
             6 KOTTDTDS                       CANONICAL
             7 KOTTDNDS                       CANONICAL
             8 KOTTDFLG                       UNSIGNED BINARY INTEGER(16)
             9 KOTDVSN                        UNSIGNED BINARY INTEGER(16)
            10 KOTTDBDY                       KOTTB
    10 rows selected.
    SQL> -- not even a varchar2 attr of the data type "accessible"
    SQL> select KOTTDNAM from sys.kottd$ where rownum < 11;
    select KOTTDNAM from sys.kottd$ where rownum < 11
    ERROR at line 1:
    ORA-00904: "KOTTDNAM": invalid identifier
    SQL> -- Calling the constructor? Oracle no likes..
    SQL> select KOTTD( null, 'test','test','test',null,null,null,null,null,null) from dual;
    select KOTTD( null, 'test','test','test',null,null,null,null,null,null) from dual
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [qctcte1], [0], [], [], [], [], [], []
    SQL>

  • Inactive sessions increasing database

    Hi
    We are using oracle11.5.10.2 on windows 2000 server and database version 10.2.0.3
    we are facing problem with inactive sessions,grdually inactive sessions increasing and thats leads database crash.
    Temporary i increased processes parameter value tp 400 prviously it was 200
    Most of inactive session from apps user only
    How can i fix this problem?
    Thanks
    With Regards
    OH

    Hi,
    Please see these threads.
    how to kill inactive sessions????????
    how to kill inactive sessions????????
    Inactive sessions in Database
    Re: Inactive sessions in Database
    Regards,
    Hussein

  • INACTIVE SESSIONS GROWING

    1. 9.2.0.4 - 64bit (MTS) (DB-A)
    2. 10.2.0.2.0 - 64 bit (DB-B)
    3. 10.2.0.2.0 - 64 bit (DB-C)
    We are having a process which starts with a trigger on a table in DB-A,
    The code in Trigger calls to a procedure which inturn access tables of user X
    in DB-C through DB link, and a procedure of user Y in DB-B through DB-Link
    connecting to user Z in DB-B.
    While doing this process some of the sessions originated from DB-A to DB-B and
    DB-C becomes Inactive and the number of Inactive sessions keep growing
    consuming memory.
    Thanks
    JD

    Hi,
    >>becomes Inactive...
    Maybe you should investigate and query the V$SESSION_WAIT view in order to displays the events for which these inactive sessions have just completed waiting or are currently waiting. The other view V$SYSTEM_EVENT displays the total number of times all the sessions have waited for the events in that view.
    Take a look on this doc below for more information:
    Oracle Wait Events
    http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents.htm#REFRN101
    Cheers

  • AUTOMATICALLY KILL  INACTIVE SESSIONS

    Hi all. we are using oracle 8.1.6 on windows-2000 with 2gb ram. we facing
    ora-12500 listner failed to start a dedicated server.
    error and for this we made certain changes. we also added a parameter in sqlnet.ora at server side sqlnet.expire_time=10.. for automatically killing inactive sessions but it did not helped and many sessions remain in v$session. i wana know what should we do to kill inactive sessions. because i think when the sessions reach more than 300 then we face problem of listner failed. thanks for u'r valueable comments in advance as well.
    best wishes
    muhammad mohsin chattha

    Hi Nicolas, what you say is correct, but, unless the user try to do something (and receives an error),
    those sessions will show up as SNIPED in V$SESSION, and never go away.
    We can create a procedure to kill these sessions, something like this :  1  CREATE OR REPLACE PROCEDURE Kill_Sessions   IS
      2      Stmt           VARCHAR2(200);
      3      V_Sid          VARCHAR2(30);
      4      V_Serial       VARCHAR2(30);
      5      V_Username     VARCHAR2(30);
      6      CURSOR pri IS
      7      SELECT Sid, Serial#, Username
      8      FROM V$Session
      9      WHERE Username Is Not Null
    10      And Username not like 'SYS%'
    11      And Status = 'SNIPED';
    12  BEGIN
    13      FOR usr in pri LOOP
    14      V_Sid     := usr.Sid;
    15      V_Serial  := Usr.Serial#;
    16      Stmt      := 'ALTER SYSTEM KILL SESSION ''' || V_Sid || ',' || V_Serial || '''';
    17      Execute Immediate(Stmt);
    18      END LOOP;
    19* END;
    20  /  and execute it every minute (change 1440 to change the frequence) :SQL> Declare
      2     Out_Var Int;
      3  Begin
      4     Dbms_Job.Submit(Out_Var,
      5     'Kill_Sessions;',
      6     Sysdate,
      7     'Sysdate+1/1440' );
      8* End;
    SQL> /
    PL/SQL procedure successfully completed.
    SQL> commit;
    Commit complete.
    SQL>

  • About Inactive Sessions

    Hello everybody:
    I need some help, this is my situation:
    Every day when I arrive to my job I have to kill inactive session from other days, e.g Today I had to kill a lot of Inactive Session of Yesterday.
    How could I did this by other way.
    Thanks

    Hiow are you determining that the session is inactive? If you are only looking at v$session.status then be aware that you cannot determine if a session is truely INACTIVE from this column alone. You must also look at last_call_et.
    The reason is that Oracle only considers a session ACTIVE while it is processing SQL (or pl/sql) and with a dedicated session and a connect pooled front-end or a client like Forms where the user spends a lot of time filling in the screen or reviewing results then while you see an INACTIVE status in two queries of v$session 30 seconds apart while the session may have run 8 fast short SQL statements in between your viewing v$session. The last_call_et column woud reflect the activity but it is unlikely you would catch the ACTIVE status.
    HTH -- Mark D Powell --

  • OC4J inactive sessions

    I have OC4j server running on one box and the oracle database
    is on different server. We connect through JDBC.
    It looks like the application server does not close inactive sessions.
    Because of this temporary tablespace on database server gets filled
    up. I tried increasing it 4g but the problem looks like
    of inactive sessions.
    How do I specify timeout period for inactivity?
    I am using Oracle 9iAS Containers for J2ee (1.0.2.2.1)
    How do I clean up inactive sessions/processes.
    Satish Juware

    Yes,
    I am talking about inactive data connections. My application does not
    have any ejb module.It does have web module with servlets and JSPs.
    We do not use JNDI or data-sources.xml file for specifying
    username, SID, host:port to specify where database is.
    Insted we code thise values iside a servlet called DBconnection.
    IN that case should I still Specify inactivity timeout period
    in data-sources.xml.
    In the application code how do I make sure that connection is
    closed.
    Thanks !
    Satish Juware
    Hi Satish,
    I assume the "session" you are referring to is what I refer to as
    a database "connection".
    If the OC4J debug messages are accurate and reliable, then OC4J does,
    most definitely, close inactive database connections, after a certain
    "timeout" period. You configure this in your "data-sources.xml" file.
    Unfortunately I am not at work now, so I can't show you what mine
    looks like, but I suggest you do a search for information regarding
    the "data-sources.xml" file. I recommend searching the following URLs:
    http://www.orionserver.com
    http://www.orionsupport.com
    http://www.atlassian.com
    http://www.elephantwalker.com
    Hope this helps you.
    Good Luck,
    Avi.

  • Inactive Sessions Getting Automatically Generated in Database

    I am facing a strange problem of getting huge number of inactive sessions getting generated th the database server which leads to it's connection closure.
    The Error reads as "Failed to check out an Application due to connection failure of Application Module."
    This happens each time I execute the following code:
    String amDefName = "amendprgo.model.CSDInvFRCAmendPrgoServices";
    String configName = "CSDInvFRCAmendPrgoServicesLocal";
    ApplicationModule app1 = Configuration.createRootApplicationModule(amDefName,configName) ;
    String voInstanceName="prgoHdrRO";
    ViewObject prgoHdrROVO =app1.createViewObjectFromQueryStmt(voInstanceName,"select * from INV_PRGO_HDR");
    prgoHdrROVO.setWhereClause("PRGO_ID="+tempRow.getAttribute("PrgoId")+" and DEPOT_CD = '0' and ITEM_CAT = 'I3' ");
    prgoHdrROVO.executeQuery();
    if(prgoHdrROVO.getEstimatedRowCount()>0){
    return true;
    I know there is a process of creating connection and View Object in Model part in JDeveloper, but I want to know why this problem happens.

    ApplicationModule app1 = Configuration.createRootApplicationModule(amDefName,configName) ;is your problem as it causes at least one (sometimes more) connections to open. As you don't free the resource after using it the connection remains open even if you can't access it anymore.
    You should call Configuration.releaseApplicationModule(...), with the application module you created before returning.
    On the other side you shoulnd not even call createRootApplicationModule in the first place (as it causes trouble if you don't deeply know what the framework do with a root application module).
    Can you tell us the use case which make you call createRootApplicationModule()? We might find a better solution.
    Timo
    Edited by: Timo Hahn on 19.05.2011 13:45
    PS: something to read http://blogs.oracle.com/jdevotnharvest/entry/when_to_use_createrootapplicationmodule_in_oracle_adf and http://radio-weblogs.com/0118231/2009/08/20.html#a959

Maybe you are looking for