5 Replies Latest reply on May 11, 2004 10:51 AM by anatoly71

    No Hypersonic - help i've tried all solutions...

    tkmetta Newbie

      Hi all,

      I can't find service=Hypersonic - I'm using jboss3.2.3

      I've searched for this topic & viewed & tried all the ans, but unfortunately i still cannot see the service=Hypersonic in my http://localhost:8080/jmx-console/index.jsp.

      N.B. I've tried many times with different combinations, uncommenting only the beans at bottom of file, uncommenting the connection-url, uncommenting the
      Everytime i change, i restart jboss, but still I don't see the service=Hypersonic appearing.

      Pls help...below is my setting in

      c:/jboss/server/all/deploy/hsqldb-ds.xml

      Thanks. Appreciate your help.
      metta

      ===========hsqldb-ds.xml===========

      <?xml version="1.0" encoding="UTF-8"?>

      <!-- The Hypersonic embedded database JCA connection factory config
      $Id: hsqldb-ds.xml,v 1.1.2.11 2003/09/28 12:31:36 starksm Exp $ -->


      <datasources>
      <local-tx-datasource>

      <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
      <!-- Datasources are not available outside the virtual machine -->
      <jndi-name>DefaultDS</jndi-name>

      <!-- for tcp connection, allowing other processes to use the hsqldb
      database. This requires the org.jboss.jdbc.HypersonicDatabase mbean.
      -->
      <connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url>

      <!-- for totally in-memory db, not saved when jboss stops.
      The org.jboss.jdbc.HypersonicDatabase mbean is unnecessary
      <connection-url>jdbc:hsqldb:.</connection-url>
      -->
      <!-- for in-process db with file store, saved when jboss stops. The
      org.jboss.jdbc.HypersonicDatabase is unnecessary
      -->
      <connection-url>jdbc:hsqldb:/hypersonic/localDB
      </connection-url>

      <!-- The driver class -->
      <driver-class>org.hsqldb.jdbcDriver</driver-class>

      <!-- The login and password -->
      <user-name>sa</user-name>
      <password></password>

      <!--example of how to specify class that determines if exception means connection should be destroyed-->
      <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-->

      <!-- this will be run before a managed connection is removed from the pool for use by a client-->
      <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->

      <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
      <min-pool-size>5</min-pool-size>

      <!-- The maximum connections in a pool/sub-pool -->
      <max-pool-size>20</max-pool-size>

      <!-- The time before an unused connection is destroyed -->
      <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
      <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connections -->
      <idle-timeout-minutes>0</idle-timeout-minutes>

      <!-- sql to call when connection is created
      <new-connection-sql>some arbitrary sql</new-connection-sql>
      -->

      <!-- sql to call on an existing pooled connection when it is obtained from pool
      <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
      -->

      <!-- example of how to specify a class that determines a connection is valid before it is handed out from the pool
      <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionChecker</valid-connection-checker-class-name>
      -->

      <!-- Whether to check all statements are closed when the connection is returned to the pool,
      this is a debugging feature that should be turned off in production -->
      <track-statements>true</track-statements>

      <!-- Use the getConnection(user, pw) for logins
      <application-managed-security/>
      -->

      <!-- Use the security domain defined in conf/login-config.xml -->
      <security-domain>HsqlDbRealm</security-domain>

      <!-- Use the security domain defined in conf/login-config.xml or the
      getConnection(user, pw) for logins. The security domain takes precedence.
      <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
      -->

      <!-- Add this depends tag if you are using the tcp connection url
      -->
      <depends>jboss:service=Hypersonic</depends>
      </local-tx-datasource>

      <!-- This mbean should be used only when using tcp connections. Uncomment
      when the tcp based connection-url is used.
      -->

      <mbean code="org.jboss.jdbc.HypersonicDatabase"
      name="jboss:service=Hypersonic">
      <attribute name="Port">1701</attribute>
      <attribute name="Silent">true</attribute>
      <attribute name="Database">default</attribute>
      <attribute name="Trace">false</attribute>
      <attribute name="No_system_exit">true</attribute>
      </mbean>
      </datasources>


      ===========end hsqldb-ds.xml===========



        • 1. Re: No Hypersonic - help i've tried all solutions...
          Darran Lofthouse Master

          Should probably be server/default/deploy I think that you are editing the wrong file.

          • 2. Re: No Hypersonic - help i've tried all solutions...
            tkmetta Newbie

            thanks. u r right. sorry - i thought all/deploy will take care of everything.

            • 3. Re: No Hypersonic - help i've tried all solutions...
              anatoly71 Newbie

              Hi guys!

              I have a similar problem (Hypersonic doesn't start). I am editing the right file "jboss-3.2.3/server/default/deploy/hsqldb-ds.xml" but I have no luck.

              Any ideas what I could try next? I've searched for answers in the Internet but I just find questions of a similar character and no "howto" that covers the whole issue..

              Is the manual "Getting Started with JBoss" at all meant to be used with jboss3.2.3??

              Have a better day then me,
              Anatoly

              • 4. Re: No Hypersonic - help i've tried all solutions...
                Darran Lofthouse Master

                Can you post your 'hsqldb-ds.xml' here.

                Making the correct changes for Hypersonic does work on 3.2.3 (I have 6 developers here that have made the changes without any problems)

                How are you starting JBoss? Are you passing any parameters to the run script?

                • 5. Re: No Hypersonic - help i've tried all solutions...
                  anatoly71 Newbie

                  Hi!

                  Here is the file:
                  *************************************************************************************
                  <?xml version="1.0" encoding="UTF-8"?>

                  <!-- The Hypersonic embedded database JCA connection factory config
                  $Id: hsqldb-ds.xml,v 1.1.2.11 2003/09/28 12:31:36 starksm Exp $ --
                  >


                  <local-tx-datasource>

                  <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
                  <!-- Datasources are not available outside the virtual machine -->
                  <jndi-name>DefaultDS</jndi-name>

                  <!-- for tcp connection, allowing other processes to use the hsqldb
                  database. This requires the org.jboss.jdbc.HypersonicDatabase mbean.
                  -->
                  <connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url>

                  <!-- for totally in-memory db, not saved when jboss stops.
                  The org.jboss.jdbc.HypersonicDatabase mbean is unnecessary
                  <connection-url>jdbc:hsqldb:.</connection-url>
                  -->
                  <!-- for in-process db with file store, saved when jboss stops. The
                  org.jboss.jdbc.HypersonicDatabase is unnecessary
                  -->
                  <!--<connection-url>jdbc:hsqldb:${jboss.server.data.dir}/hypersonic/localDB
                  </connection-url>
                  -->

                  <!-- The driver class -->
                  <driver-class>org.hsqldb.jdbcDriver</driver-class>

                  <!-- The login and password -->
                  <user-name>sa</user-name>


                  <!--example of how to specify class that determines if exception means connection should be destroye
                  d-->
                  <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</excepti
                  on-sorter-class-name-->

                  <!-- this will be run before a managed connection is removed from the pool for use by a client-->
                  <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->
                  <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
                  <min-pool-size>5</min-pool-size>

                  <!-- The maximum connections in a pool/sub-pool -->
                  <max-pool-size>20</max-pool-size>

                  <!-- The time before an unused connection is destroyed -->
                  <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout a
                  fter last use -->
                  <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads
                  on closed connections -->
                  <idle-timeout-minutes>0</idle-timeout-minutes>

                  <!-- sql to call when connection is created
                  <new-connection-sql>some arbitrary sql</new-connection-sql>
                  -->

                  <!-- sql to call on an existing pooled connection when it is obtained from pool
                  <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
                  -->

                  <!-- example of how to specify a class that determines a connection is valid before it is handed out
                  from the pool
                  <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionC
                  hecker</valid-connection-checker-class-name>
                  -->

                  <!-- Whether to check all statements are closed when the connection is returned to the pool,
                  this is a debugging feature that should be turned off in production -->
                  <track-statements>true</track-statements>

                  <!-- Use the getConnection(user, pw) for logins
                  <application-managed-security/>
                  -->

                  <!-- Use the security domain defined in conf/login-config.xml -->
                  <security-domain>HsqlDbRealm</security-domain>

                  <!-- Use the security domain defined in conf/login-config.xml or the
                  getConnection(user, pw) for logins. The security domain takes precedence.
                  <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
                  -->
                  <!-- Add this depends tag if you are using the tcp connection url
                  -->
                  jboss:service=Hypersonic
                  </local-tx-datasource>

                  <!-- This mbean should be used only when using tcp connections. Uncomment
                  when the tcp based connection-url is used.
                  -->

                  1701
                  true
                  default
                  false
                  true


                  *************************************************************************************

                  I start up jboss just by running "run.sh", maybe I shell say explicitly that I want it to start Hypersonic ? I'm not sure there is something said about it in the manual..

                  /Anatoly