5 Replies Latest reply on Oct 16, 2002 4:50 AM by jono

    Moving from 3.0 to 3.0.2: FirebirdManager is not registered

    rramirez
    rramirez Aug 29, 2002 7:15 PM

      Hi,

      I'm having problems moving to 3.0.2. It seems that the firebird-service.xml is loading before the the firebirdsql.rar file. If I remove the firebird-service.xml file and then start jboss and then put firebird-service.xml file in the deploy directory then I don't get any errors. At this point I can put my jar and war files and they work. Does anyone know how I can fix this? I wasn't getting this with 3.0.0. Here's the error:

      ========================== Error =================================
      14:25:17,796 INFO [MainDeployer] Starting deployment of package: file:/D:/jboss-3.0.2/server/default/deploy/firebird-service.xml
      14:25:17,875 ERROR [URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@6041613f{ url=file:/D:/jboss-3.0.2/server/default/deploy/firebird-service.xml, deployedLastModified=0 }
      org.jboss.deployment.DeploymentException: jboss.jca:service=FirebirdManager is not registered.; - nested throwable: (javax.management.InstanceNotFoundException: jboss.jca:service=FirebirdManager is not registered.)
      at org.jboss.deployment.SARDeployer.create(SARDeployer.java:227)
      at org.jboss.deployment.MainDeployer.create(MainDeployer.java:755)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:615)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy4.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:427)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:648)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:499)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:967)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:396)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy3.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:802)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
      at org.jboss.Main.boot(Main.java:142)
      at org.jboss.Main$1.run(Main.java:375)
      at java.lang.Thread.run(Thread.java:479)
      + nested throwable:
      javax.management.InstanceNotFoundException: jboss.jca:service=FirebirdManager is not registered.
      at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:362)
      at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:528)
      at org.jboss.system.ServiceController.getServiceProxy(ServiceController.java:736)
      at org.jboss.system.ServiceController.create(ServiceController.java:276)
      at org.jboss.system.ServiceController.create(ServiceController.java:242)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy3.create(Unknown Source)
      at org.jboss.deployment.SARDeployer.create(SARDeployer.java:217)
      at org.jboss.deployment.MainDeployer.create(MainDeployer.java:755)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:615)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy4.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:427)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:648)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:499)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:967)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:396)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy3.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:802)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
      at org.jboss.Main.boot(Main.java:142)
      at org.jboss.Main$1.run(Main.java:375)
      at java.lang.Thread.run(Thread.java:479)
      14:25:17,875 INFO [MainDeployer] Starting deployment of package: file:/D:/jboss-3.0.2/server/default/deploy/hsqldb-service.xml
      14:25:17,921 WARN [ServiceController] jboss.jca:service=LocalTxDS,name=hsqldbDS does not implement any Service methods
      14:25:17,921 INFO [JBossManagedConnectionPool] Creating
      14:25:17,921 INFO [JBossManagedConnectionPool] Created


      =======================================================================

      Here's a copy of my firebird-service.xml:

      ============================================= firebird-service.xml ======================================


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

      <!-- ==================================================================== -->
      <!-- New ConnectionManager setup for firebird dbs using jca-jdbc xa driver-->
      <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
      <!-- ==================================================================== -->



      <!--FBManager can be used to create and drop databases.
      Drop is especially useful during testing, since it
      assures a clean start next time. -->

      d:/jboss-3.0.0/server/default/db/andrea.gdb
      sysdba
      masterkey
      false
      false



      <!--make the rar deploy - A BIG HACK till xslt based deployment is written-->
      jboss.jca:service=RARDeployer

      <depends optional-attribute-name="ManagedConnectionFactoryName">

      <!--more hack-->
      <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=Firebird Database Connector


      <config-property>
      <config-property-name>Database</config-property-name>
      <config-property-type>java.lang.String</config-property-type>
      <config-property-value>shuttle/3050:D:/jboss-3.0.2/server/default/db/andrea.gdb</config-property-value>
      </config-property>
      <config-property>
      <config-property-name>UserName</config-property-name>
      <config-property-type>java.lang.String</config-property-type>
      <config-property-value>sysdba</config-property-value>
      </config-property>
      <config-property>
      <config-property-name>Password</config-property-name>
      <config-property-type>java.lang.String</config-property-type>
      <config-property-value>masterkey</config-property-value>
      </config-property>


      AndreaDS



      <depends optional-attribute-name="ManagedConnectionPool">


      5
      50
      5000
      1440
      <!--criteria indicates if Subject (from security domain) or app supplied
      parameters (such as from getConnection(user, pw)) are used to distinguish
      connections in the pool. Choices are
      ByContainerAndApplication (use both),
      ByContainer (use Subject),
      ByApplication (use app supplied params only),
      ByNothing (all connections are equivalent, usually if adapter supports
      reauthentication)-->
      ByContainer


      <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager
      <!-- Include a login module configuration named FirebirdDBRealm.
      Update your login-conf.xml, here is an example for a
      ConfiguredIdentityLoginModule:

      <application-policy name = "FirebirdDBRealm">

      <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
      <module-option name = "principal">sysdba</module-option>
      <module-option name = "userName">sysdba</module-option>
      <module-option name = "password">masterkey</module-option>
      <module-option name = "managedConnectionFactoryName">jboss.jca:service=XaTxCM,name=AndreaDS</module-option>
      </login-module>

      </application-policy>

      NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
      module-option name = "managedConnectionFactoryName"
      must match the object name of the ConnectionManager you are configuring here.
      -->
      <!--comment out this line if you want component managed security or want
      to use the default values in the ManagedConnectionFactoryProperties -->
      <!--
      FirebirdDBRealm
      -->
      <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager

      java:/TransactionManager




      ===========================================================================================================

      Any help would be greatly appreciated.

      Thanks,
      Ruben

      • 2695 Views
      • Tags:
        • 1. Re:  Moving from 3.0 to 3.0.2: FirebirdManager is not regist
          davidjencks
          davidjencks Aug 29, 2002 7:28 PM (in response to rramirez)

          I'm afraid with 3.0.x you will have to number your deployments

          10firebirdsql.rar
          20firebird-service.xml
          ...

          you may also be able to get the right order by putting both in an .ear.

          There is some code that makes mbeans wait for their classes, that worked when I wrote it, but unfortunately I didn't write a test case... so it got broken.

          I think it is working in 4.0, where I added a test case.

            • Actions
          • 2. Re:  Moving from 3.0 to 3.0.2: FirebirdManager is not regist
            jono
            jono Oct 14, 2002 5:47 AM (in response to rramirez)

            Hi,

            I am having the same problem as Ruben, using :
            JBoss-3.0.2
            Firebird-1.0.0.796-Win32

            It appears the load order is the problem, as if I start JBoss with firebirdsql.rar in deploy but not firebird-service.xml, start JBoss, then deploy firebird-service.xml, it works fine.

            Unfortunately for me, renaming the files as suggested does not appear to work and I get errors in the log at startup time (shown at the end of this post).

            I am wondering if I am doing anything wrong. The files have been renamed :
            10firebirdsql.rar
            20firebird-service.xml
            which I assume ensures the rar is loaded first due to name order. They are in the ..\server\default\deploy location.

            I am wondering whether it is worth trying the alternative suggestion and creating an .ear - has anyone had any sucess with this? Or are there any other pointers I can use to help me with this one?

            I am particularly fond of Interbase / Firebird and really want to use it as a DS for my J2EE work with JBoss. I am therefore very keen to solve this one and will be grateful for all help.

            Cheers from New Zealand (home of the America's Cup for now ;)
            Jono.

              • Actions
            • 3. Re:  Moving from 3.0 to 3.0.2: FirebirdManager is not regist
              jono
              jono Oct 14, 2002 5:49 AM (in response to rramirez)

              Sorry, forgot the server.log errors :
              2002-10-14 20:40:24,248 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
              Cause: Incomplete Deployment listing:
              Packages waiting for a deployer:

              Incompletely deployed packages:
              [org.jboss.deployment.DeploymentInfo@25e00eac { url=file:/C:/Java/AS/jboss-3.0.2/server/default/deploy/20firebird-service.xml }
              deployer: org.jboss.deployment.SARDeployer@482923
              status: Deployment FAILED reason: jboss.jca:service=FirebirdManager is not registered.; - nested throwable: (javax.management.InstanceNotFoundException: jboss.jca:service=FirebirdManager is not registered.)
              state: FAILED
              watch: file:/C:/Java/AS/jboss-3.0.2/server/default/deploy/20firebird-service.xml
              lastDeployed: 1034581215576
              lastModified: 1034581215556
              mbeans:
              jboss.jca:service=FirebirdManager (state not available)
              jboss.jca:service=XaTxCM,name=JonoDS (state not available)
              jboss.jca:service=XaTxDS,name=JonoDS (state not available)
              jboss.jca:service=XaTxPool,name=JonoDS (state not available)
              ]MBeans waiting for classes:

              MBeans waiting for other MBeans:
              [ObjectName: jboss.jca:service=FirebirdManager
              state: NOTYETINSTALLED
              I Depend On:
              Depends On Me: ]
              2002-10-14 20:40:24,279 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified that enabled: true
              2002-10-14 20:40:24,279 INFO [org.jboss.deployment.scanner.URLDeploymentScanner] Started
              2002-10-14 20:40:24,279 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-service.xml
              2002-10-14 20:40:24,279 INFO [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Java/AS/jboss-3.0.2/server/default/conf/jboss-service.xml
              2002-10-14 20:40:24,279 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [3.0.2 Date:200208271339] Started in 0m:22s:473ms

                • Actions
              • 4. Re:  Moving from 3.0 to 3.0.2: FirebirdManager is not regist
                paulnardone
                paulnardone Oct 15, 2002 4:32 AM (in response to rramirez)

                Hi I'm using a similar set up to you, 3.0.3 and firebird on win32 and I managed to get it to work by numbering the deployments, but you also need to change your Jboss-service.xml in the conf directory,

                Replace

                org.jboss.deployment.DeploymentSorter

                With this

                org.jboss.deployment.scanner.PrefixDeploymentSorter

                Number the deployments like this

                10firebirdsql.rar
                20firebird-service.xml

                and try putting your app in an EAR file too, numbered after the others

                30myapp.ear

                Paul

                  • Actions
                • 5. Re:  Moving from 3.0 to 3.0.2: FirebirdManager is not regist
                  jono
                  jono Oct 16, 2002 4:50 AM (in response to rramirez)

                  Thanks Paul, that did the trick :)

                  All seems to be configured and operating at this stage - onwards and upwards.

                  Jono

                    • Actions