4 Replies Latest reply on Aug 26, 2002 11:22 AM by John Katilie

    JBoss 3.0.1 Error Deploying Resource Adapter

    John Katilie Newbie

      We have a Resource Adapter that deploys and runs under JBoss 3.0.0 without problems. Because of other None Adapter problem we are attempting to upgrade to 3.0.1. Under this release we are unable to deploy our adapter and get the following messages:

      07:36:31,390 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean ope
      ration 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:

      Incompletely deployed packages:

      MBeans waiting for classes:

      MBeans waiting for other MBeans:
      [ObjectName: jboss.jca:service=NoXaTxCM,name=jkra
      state: CONFIGURED
      I Depend On: jboss.jca:service=RARDeployer
      jboss.jca:service=NoXaTxDS,name=jkra
      jboss.jca:service=NoXaTxPool,name=jkra
      jboss.jca:service=CachedConnectionManager
      jboss.security:name=JaasSecurityManager

      Depends On Me: ]
      07:36:31,390 INFO [URLDeploymentScanner] Started
      07:36:31,406 INFO [MainDeployer] Deployed package: file:/D:/JBoss/jboss-3.0.1_t
      omcat-4.0.4/server/default/conf/jboss-service.xml
      07:36:31,406 INFO [Server] JBoss (MX MicroKernel) [3.0.1 Date:200208122231] Sta
      rted in 0m:16s:500ms

      The Service.xml that works with JBoss 3.0.0 and not 3.0.1 is:

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



      <!-- ==================================================================== -->
      <!-- jkConnector -->
      <!-- ==================================================================== -->


      <!-- jkConnector Resource adapter, for the Fresno prototype -->

      <!--new configuration for new ConnectionManager-->

      <!--make the rar deploy!-->
      jboss.jca:service=RARDeployer

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

      <!--hack till better deployment system-->
      <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=jkConnector

      <!--real attributes-->
      jkConnector



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

      0
      50
      5000
      15
      <!--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)-->
      ByContainerAndApplication



      <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager
      java:/jaas/EntireXRealm

      <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager







      I did not create our original service.xml file that works under 3.0.0 and am just starting to understand it. I've attempted a number of changes with no luck.

      Any and all help is appreciated. Also, what/where is the best documentation in describing the services.xml files.

      Thanks in Advance, John Katilie