2 Replies Latest reply on Oct 19, 2005 3:51 PM by adrian.brock

    Bean NOTYETINSTALLED

    gavkearney

      I'm using jboss 4.0.2 and HSQL 1.7.2 but my hypersonic bean won't deploy and is causing all sorts of problems later on in my application, heres the stack:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.ejb:persistencePolicy=database,service=EJBTimerService
       State: CONFIGURED
       I Depend On:
       jboss.jca:name=DefaultDS,service=DataSourceBinding
      
      ObjectName: jboss:service=juddi
       State: CONFIGURED
       I Depend On:
       jboss.jca:name=DefaultDS,service=DataSourceBinding
      
      ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
       State: CONFIGURED
       I Depend On:
       jboss:service=TransactionManager
       jboss.jca:name=DefaultDS,service=DataSourceBinding
      
      ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=Invoker
       jboss.web:service=WebServer
      
      ObjectName: jboss.mq:service=StateManager
       State: CONFIGURED
       I Depend On:
       jboss.jca:name=DefaultDS,service=DataSourceBinding
       Depends On Me:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq:service=DestinationManager
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=MessageCache
       jboss.mq:service=PersistenceManager
       jboss.mq:service=StateManager
       Depends On Me:
       jboss.mq.destination:name=testTopic,service=Topic
       jboss.mq.destination:name=securedTopic,service=Topic
       jboss.mq.destination:name=testDurableTopic,service=Topic
       jboss.mq.destination:name=testQueue,service=Queue
       jboss.mq.destination:name=AOUT1,service=Queue
       jboss.mq.destination:name=AOUT2,service=Queue
       jboss.mq.destination:name=JMS1,service=Queue
       jboss.mq.destination:name=A,service=Queue
       jboss.mq.destination:name=B,service=Queue
       jboss.mq.destination:name=C,service=Queue
       jboss.mq.destination:name=D,service=Queue
       jboss.mq.destination:name=ex,service=Queue
       jboss.mq.destination:name=IN1,service=Queue
       jboss.mq.destination:name=IN2,service=Queue
       jboss.mq.destination:name=IN3,service=Queue
       jboss.mq.destination:name=IN4,service=Queue
       jboss.mq.destination:name=OUT1,service=Queue
       jboss.mq.destination:name=OUT2,service=Queue
       jboss.mq.destination:name=OUT3,service=Queue
       jboss.mq.destination:name=OUT4,service=Queue
       jboss.mq.destination:name=SYSTEM,service=Queue
       jboss.mq.destination:name=DEAD,service=Queue
       jboss.mq.destination:name=INVALID,service=Queue
       jboss.mq.destination:name=HOLDING,service=Queue
       jboss.mq.destination:name=REPLY,service=Queue
       jboss.mq.destination:name=RETURN,service=Queue
       jboss.mq:service=SecurityManager
       jboss.mq.destination:name=DLQ,service=Queue
      
      ObjectName: jboss.mq:service=PersistenceManager
       State: CONFIGURED
       I Depend On:
       jboss.jca:name=DefaultDS,service=DataSourceBinding
       Depends On Me:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=testTopic,service=Topic
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq.destination:name=securedTopic,service=Topic
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq.destination:name=testDurableTopic,service=Topic
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq.destination:name=testQueue,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq.destination:name=AOUT1,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=AOUT2,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=JMS1,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=A,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=B,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=C,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=D,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=ex,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=IN1,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=IN2,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=IN3,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=IN4,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=OUT1,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=OUT2,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=OUT3,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=OUT4,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=SYSTEM,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=DEAD,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=INVALID,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=HOLDING,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=REPLY,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq.destination:name=RETURN,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq:service=Invoker
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=TracingInterceptor
       Depends On Me:
       jboss.mq:service=InvocationLayer,type=HTTP
       jboss.mq:service=InvocationLayer,type=JVM
       jboss.mq:service=InvocationLayer,type=UIL2
      
      ObjectName: jboss.mq:service=TracingInterceptor
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=SecurityManager
       Depends On Me:
       jboss.mq:service=Invoker
      
      ObjectName: jboss.mq:service=SecurityManager
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       Depends On Me:
       jboss.mq.destination:name=testTopic,service=Topic
       jboss.mq.destination:name=securedTopic,service=Topic
       jboss.mq.destination:name=testDurableTopic,service=Topic
       jboss.mq.destination:name=testQueue,service=Queue
       jboss.mq:service=TracingInterceptor
       jboss.mq.destination:name=DLQ,service=Queue
      
      ObjectName: jboss.mq.destination:name=DLQ,service=Queue
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
      ObjectName: jboss.mq:service=InvocationLayer,type=JVM
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=Invoker
      
      ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
       State: CONFIGURED
       I Depend On:
       jboss.mq:service=Invoker
      
      ObjectName: jboss.jca:name=DefaultDS,service=LocalTxCM
       State: CONFIGURED
       I Depend On:
       jboss.jca:name=DefaultDS,service=ManagedConnectionPool
       jboss.jca:service=CachedConnectionManager
       jboss.security:service=JaasSecurityManager
       jboss:service=TransactionManager
       Depends On Me:
       jboss.jca:name=DefaultDS,service=DataSourceBinding
      
      ObjectName: jboss.jca:name=DefaultDS,service=ManagedConnectionPool
       State: CONFIGURED
       I Depend On:
       jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
       Depends On Me:
       jboss.jca:name=DefaultDS,service=LocalTxCM
      
      ObjectName: jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
       State: CONFIGURED
       I Depend On:
       jboss:database=highwaydb,service=Hypersonic
       jboss.jca:name='jboss-local-jdbc.rar',service=RARDeployment
       Depends On Me:
       jboss.jca:name=DefaultDS,service=ManagedConnectionPool
      
      ObjectName: jboss.jca:name=DefaultDS,service=DataSourceBinding
       State: CONFIGURED
       I Depend On:
       jboss.jca:name=DefaultDS,service=LocalTxCM
       jboss:service=invoker,type=jrmp
       Depends On Me:
       jboss.ejb:persistencePolicy=database,service=EJBTimerService
       jboss:service=juddi
       jboss:service=KeyGeneratorFactory,type=HiLo
       jboss.mq:service=StateManager
       jboss.mq:service=PersistenceManager
      
      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss:database=highwaydb,service=Hypersonic
       State: NOTYETINSTALLED
       Depends On Me:
       jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
      


      Here's a copy of my hsqldb-ds.xml file:

      <?xml version="1.0" encoding="UTF-8"?>
      
      <!-- The Hypersonic embedded database JCA connection factory config
      $Id: hsqldb-ds.xml,v 1.15 2004/09/15 14:37:40 loubyansky 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 necessary
       <connection-url>jdbc:hsqldb:.</connection-url>
      -->
       <!-- for in-process persistent db, saved when jboss stops. The
       org.jboss.jdbc.HypersonicDatabase mbean is necessary for properly db shutdown
      -->
       <!--<connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url> -->
       <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>
       <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 returnfed to the pool,
       this is a debugging feature that should be turned off in production -->
       <track-statements>false</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>
       -->
      
       <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
       <metadata>
       <type-mapping>Hypersonic SQL</type-mapping>
       </metadata>
      
       <!-- This mbean can be used when using in process persistent hypersonic -->
       <depends>jboss:service=Hypersonic,database=highwaydb</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>
      
      
       <!-- This mbean can be used when using in process persistent db
       <mbean code="org.jboss.jdbc.HypersonicDatabase"
       name="jboss:service=Hypersonic,database=highwaydb">
       <attribute name="Database">highwaydb</attribute>
       <attribute name="InProcessMode">true</attribute>
       </mbean>-->
      </datasources>
      
      


      If anybody could enlighten me as to why this bean won't start i'd be very greatful, thanks.

      post back if you want to see more code, thanks
      Gavin

        • 1. Re: Bean NOTYETINSTALLED
          gavkearney

          If anybody can help me on this subject i would be very greatful as its causing me serious hassle

          • 2. Re: Bean NOTYETINSTALLED

            http://wiki.jboss.org/wiki/Wiki.jsp?page=BadPostBump


            --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
            ObjectName: jboss:database=highwaydb,service=Hypersonic
            State: NOTYETINSTALLED


            And why is not installed? Because it is commented out!
            <!-- This mbean can be used when using in process persistent db
             <mbean code="org.jboss.jdbc.HypersonicDatabase"
             name="jboss:service=Hypersonic,database=highwaydb">
             <attribute name="Database">highwaydb</attribute>
             <attribute name="InProcessMode">true</attribute>
             </mbean>-->
            


            And what does this have to do with JCA? Nothing!

            Please take your future questions to the beginners forum.