5 Replies Latest reply on Jul 18, 2013 4:52 AM by wdfink

    increase in open cursor (oracle11g)

    hohokampeople

      Hi

        

          We have just migrated to JBoss AS 7.1.1.Final. However we've been encountering an increase in open cursor.

          Do we need to update the jdbcadapter (current version used IronJacamar 1.0.9.Final)?    

         

       

         

          Here's sample of our dataSource Config:

       

         

        <xa-datasource jndi-name="java:DataSourceXS" pool-name="ExampleXADS">

                <driver>oracle</driver>

                 <xa-datasource-property name="URL">jdbc:oracle:thin:@UMSQUAL:1521:oradb1</xa-datasource-property>

                 <xa-pool>

                      <min-pool-size>8</min-pool-size>

                      <max-pool-size>32</max-pool-size>

                      <prefill>true</prefill>

                 </xa-pool>

                 <security>

                      <user-name>sa</user-name>

                      <password>sa</password>

                 </security>

              </xa-datasource>

                  <validation>
                    <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
                    <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
                    <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
      </validation>

              <timeout>
                <blocking-timeout-millis>5000</blocking-timeout-millis>
              </timeout>

              <drivers>

                 <driver name="oracle" module="com.oracle.ojdbc6">

                     <xa-datasource-class>oracle.jdbc.OracleDriver</xa-datasource-class>

                  </driver>

              </drivers>

       

      <driver name="oracle" module="com.oracle.ojdbc">
        

      </driver>

        • 1. Re: increase in open cursor (oracle11g)
          jesper.pedersen

          Use WildFly 8.0.0.Alpha2+

          • 2. Re: increase in open cursor (oracle11g)
            hohokampeople

            hi Jesper,

             

                why we should use wildfy 8.0.0.Alpha2 and not Jboss AS 7.1.1.Final?

                is there a compatibility issue between JBoss AS 7.1.1.FInal and Oracle 11g?

            • 3. Re: increase in open cursor (oracle11g)
              jesper.pedersen

              7.1.1 is very old, and I only support latest community version as we fix bugs all the time. So any reports against 7.1.1 will be ignored.

               

              If you are looking for something more stable than WildFly 8.0.0 Alpha2 buy a subscription for Red Hat JBoss Enterprise Application Platform 6.1.

              1 of 1 people found this helpful
              • 4. Re: increase in open cursor (oracle11g)
                hohokampeople

                Hi

                 

                  But JBoss AS 7.1.1 was just released last year.

                 

                  Anyway,  Do we have other option aside from using WildFly 8.0.0.Alpha2+?

                 

                  

                • 5. Re: increase in open cursor (oracle11g)
                  wdfink

                  bruno bruno schrieb:

                   

                    But JBoss AS 7.1.1 was just released last year.

                    

                  that is a long time ago for an active community project. As Jesper mentioned there are lots of fixes and new features and if you need changes you have to use the latest community version.

                  Other option is to find the related bug and backport the fix using the sources and patch your installation.

                   

                  If you want to have a supported version you can buy a subscription and use the JBoss Enterprise Application Platform (EAP), here the latest release is EAP6.1 which is based on the community AS7.2.

                  With the EAP subscripton you can open a support ticked and if there is a bug you can have a patch for that, as the EAP version will be supported for a longer time, see the Red Hat support policy page

                  1 of 1 people found this helpful