0 Replies Latest reply on Jun 8, 2006 6:52 AM by First Name

    JBOSS Problems after specifying prepared-statement-cache-siz

    First Name Newbie

      Hi ,

      My first post in this forum , hope to get a quick resolution :)

      I am using Jboss 4.0.0 on Oracle

      In order to improve the app performance , I had specified prepared-statement-cache-size as 50 as follows ,

      <jndi-name>jdbc/sct</jndi-name> <connection-url>jdbc:oracle:thin:@confidential:1560:sct1</connection-url>
      <max-pool-size>120</max-pool-size> <prepared-statement-cache-size>50</prepared-statement-cache-size>
      <new-connection-sql>select sysdate from dual</new-connection-sql>
      <check-valid-connection-sql>select sysdate from dual</check-valid-connection-sql>

      After doing this , I start getting the following exception ,

      java.sql.SQLException: Closed Statement
      at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
      at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:222)
      at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:285)
      at oracle.jdbc.driver.OracleStatement.ensureOpen(OracleStatement.java:5681)
      at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:409)
      at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:366)
      at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeQuery(CachedPreparedStatement.java:57)
      at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:296)
      at com.ge.sct.SiteText.getSiteTextFromDB(SiteText.java:292)

      Could anybody please tell the reasons for this ?

      Also can anybody also provide for any such other config changes , by which
      I can improve the app perfiormance .

      This is a single app server env , and currently we are exploring ways to improve load-test performance .Already have increased heap size to 768 mb and kept log4j logging at error(to save I/O during load test) , Apache webserver's httpd.conf is also tweaked to ensure no bottlenecks are present as web server makes requests to the app server during a load test. We keep on running into 503 (Temp Service not avail ) and a few response time problems during the load test once the concurrent user-load hits 40 users.