A transaction problem in cluster environment,help!

Question

          I need to take a complicated data operation which will have to call sevearl SQL
          sentences to add datas into DB in a circle. In order to minimize the cost of DB
          connection, I use one connection to create 5 statements,which are used to add
          datas repeatedly. You can read the corresponding codes below. These codes run
          very well in stand-alone environment,but problem occurs when changed to cluster
          environment. The console shows that it's timeout because the transaction takes
          too long time. But when it runs in stand-alone environment,it completes in less
          than one second! In both situations I use the same TX data source. I guess when
          changed to cluster environment,the transaction processing becomes very complicated
          and then it leads to dead-lock. Anybody agrees with this, or has any experience
          about it before? Help,thanks a lot!
          conn = getConnection();
          pstmt3 = conn.prepareStatement
          (DBInfo.SQL_RECEIPTPACK_CREATE);
          pstmt4 = conn.prepareStatement
          (DBInfo.SQL_RECEIPT_CREATE);
          pstmt5 = conn.prepareStatement
          (DBInfo.SQL_RECEIPTPACKAUDIT_INSERT_ALL);
          pstmt6 = conn.prepareStatement
          (DBInfo.SQL_RECEIPTAUDIT_INSERT_ALL);
          int count = (endno+1-startno)/quantity;
          for(int i=0;i<count;i++)
          int newstartno = startno +
          i*quantity;
          int newendno = newstartno +
          quantity - 1;
          String newStartNO =
          Formatter.formatNum2Str(newstartno,ConstVar.RECEIPT_NO_LENGTH);
          String newEndNO =
          Formatter.formatNum2Str(newendno,ConstVar.RECEIPT_NO_LENGTH);
          pstmt1 = conn.prepareStatement
          (DBInfo.SQL_RECEIPTPACK_SEQ_NEXT);
          rs1 = pstmt1.executeQuery();
          if(!rs1.next()) return -1;
          int packid = rs1.getInt(1);
          cleanup(pstmt1,null,rs1);
          pstmt3.setInt(1,packid);
          pstmt3.setString(2,newStartNO);
          pstmt3.setString(3,newEndNO);
          pstmt3.setInt(4,quantity);
          pstmt3.setLong(5,expiredt);
          pstmt3.setInt
          (6,ConstVar.ID_UNIT_TREASURY);
          pstmt3.setInt
          (7,Status.STATUS_RECEIPTPACK_REGISTERED);
          pstmt3.setLong(8,proctm);
          pstmt3.setInt(9,procUserid);
          pstmt3.setInt
          (10,ConstVar.ID_UNIT_TREASURY);
          pstmt3.setInt(11,typeid);
          pstmt3.addBatch();
          //audit
          pstmt5.setInt(1,procUserid);
          pstmt5.setInt(2,packid);
          pstmt5.setInt
          (3,OPCode.OP_RCT_RGT_RECEIPTPACK);
          pstmt5.setLong(4,0);
          pstmt5.setLong(5,proctm);
          pstmt5.addBatch();
          for(int
          j=newstartno;j<=newendno;j++)
          String receiptNO =
          Formatter.formatNum2Str(j,ConstVar.RECEIPT_NO_LENGTH);
          pstmt2 =
          conn.prepareStatement(DBInfo.SQL_RECEIPT_SEQ_NEXT);
          rs2 =
          pstmt2.executeQuery();
          if(!rs2.next()) return -
          1;
          int receiptid =
          rs2.getInt(1);
          cleanup
          (pstmt2,null,rs2);
          pstmt4.setInt
          (1,receiptid);
          pstmt4.setString
          (2,receiptNO);
          pstmt4.setInt
          (3,Status.STATUS_RECEIPT_REGISTERED);
          pstmt4.setDouble
          (4,00.0);
          pstmt4.setInt(5,0);
          pstmt4.setDouble
          (6,00.0);
          pstmt4.setDouble
          (7,00.0);
          pstmt4.setDouble
          (8,00.0);
          pstmt4.setInt
          (9,procUserid);
          pstmt4.setLong
          (10,proctm);
          pstmt4.setLong
          (11,expiredt);
          pstmt4.setInt(12,0);
          pstmt4.setInt
          (13,packid);
          pstmt4.setInt
          (14,typeid);
          pstmt4.addBatch();
          //audit
          pstmt6.setInt
          (1,procUserid);
          pstmt6.setInt
          (2,receiptid);
          pstmt6.setInt
          (3,OPCode.OP_RCT_RGT_RECEIPTPACK);
          pstmt6.setLong(4,0);
          pstmt6.setLong
          (5,proctm);
          pstmt6.addBatch();
          pstmt3.executeBatch();
          cleanup(pstmt3,null);
          pstmt5.executeBatch();
          cleanup(pstmt5,null);
          pstmt4.executeBatch();
          cleanup(pstmt4,null);
          pstmt6.executeBatch();
          cleanup(pstmt6,null);
          

Answer 1

Hello,
Are you using any kind of Load Balancer, like an F5. I am currently troubleshooting this issue for one of our ADF apps and I originally suspected the F5 was not sending traffic correctly. We have not set the adf-config file for HA and the dev team will fix that. But my concern is that will just hide my F5 issue.
Thanks,
-Alan