AM Activation/Passivation Problem

Question

Dear All,
Jdeveloper 11.1.1.5.0 + ADF faces + ADF BC
I have a procedure in database that just inserts the data in a table but doesnot commits..
Below is the procedure
Procedure p_insert_emp_test
Is
Begin
Insert Into emp_r (Emp_Id,f_Name,l_Name,Dept_Id) Values(1234,'santosh','vaza',1);
End p_insert_emp_test;Now i have a client method in AM that invokes this procedure and executes the viewobject, as below
    public Connection getCurrentConnection() {
        Statement st = null;
        try {
            st = getDBTransaction().createStatement(0);
            return st.getConnection();
        } catch (SQLException s) {
            s.printStackTrace();
            return null;
        } finally {
            if (st != null)
                try {
                    st.close();
                } catch (Exception s2) {
    public void callInsert(){
        CallableStatement cs = null;
        String stmt = "test_pkg1.p_insert_emp_test()";
        try{
            cs =
            getCurrentConnection().prepareCall("begin " + stmt + "; end;");
            cs.execute();
        }catch(SQLException e){
            throw new JboException(e);
        }finally {
            try {
                cs.close();
            } catch (SQLException ex) {
        getEmpRView1().executeQuery();
     * Container's getter for EmpRView1.
     * @return EmpRView1
    public ViewObjectImpl getEmpRView1() {
        return (ViewObjectImpl)findViewObject("EmpRView1");
    }Now i have a Page that has this method added as button and a af:table that is binded to this VO.
Every Operation is default with no customization.
Now i have 2 views in above scenario :
1. Now i uncheck 'Enable Application Module Pooling' and run my application.
After clicking insertProc button the data is not showed in table
2. Now i check 'Enable Application Module Pooling' and run my application.(Default)
After clicking insertProc button the data is showed in table
I want to test the appln with AM pooling set to false, But this causes Problem. I have a similar scenario as above and want my apln to run with around 100 users consurrently accessing my appln.
Please guys tell me what is mistake in above given approach and give me necesary suggestions.
Regards,
Edited by: Santosh Vaza on Aug 17, 2012 11:16 AM

Answer 1

Hi,
Thanks Frank for your valuable reply,
Even with AM pooling there is no guarantee you get the same AM back (and even the database session could be another one) so that the best way out of this is to commit changes you apply via PL/SQL.
    <AppModuleConfig DeployPlatform="LOCAL" jbo.project="pkgla.LA_Model" name="SyVwPlApplicationDet_AMLocal" ApplicationName="loanapplnmaster.SyVwPlApplicationDet_AM">
         <AM-Pooling jbo.ampool.initpoolsize="35" jbo.recyclethreshold="100" jbo.ampool.maxavailablesize="100"/>
         <Database jbo.locking.mode="optimistic"/>
         <Security AppModuleJndiName="loanapplnmaster.SyVwPlApplicationDet_AM"/>
         <Custom JDBCDataSource="jdbc/ILPADS"/>
      </AppModuleConfig>*<AM-Pooling jbo.ampool.initpoolsize="35" jbo.recyclethreshold="100" jbo.ampool.maxavailablesize="100"/>*
Even after i do above change in configuration in AM, I assume i could get same AM back for that particular user .. ? Assuming under the load of <= 100 ... ?
Pls reply..
Regards,
Edited by: Santosh Vaza on Aug 17, 2012 12:10 PM