3 Replies Latest reply on Nov 13, 2002 1:00 PM by David Jencks

    Incomplete Deployment listing error

    Dawid Newbie

      I tried deploy FilePropertiesAdapter o JBoss 3.0.4. Deploying FilePropertiesAdapter.rar works fine. When I deploy FilePropertiesAdapter-service.xml following error occures:

      12:21:29,395 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=LocalTxCM,name=PropertiesFileAdapter
      state: CONFIGURED
      I Depend On: jboss.jca:service=LocalTxDS,name=PropertiesFileAdapter

      Depends On Me: ]

      I don't know what this error mean. Can someone help me?

      Here is my FilePropertiesAdapter-service.xml (I found it in some post in this forum):

      <?xml version="1.0" encoding="UTF-8"?>
      <!-- ===================================================================== -->
      <!-- -->
      <!-- JBoss Server Configuration -->
      <!-- -->
      <!-- ===================================================================== -->

      <!-- ======================================================================-->
      <!-- New ConnectionManager setup for property file adapter example -->
      <!-- ===================================================================== -->

      <depends optional-attribute-name="ManagedConnectionFactoryName">
      <!--embedded mbean-->


      <config-property name="ConnectionURL" type="java.lang.String">c:/temp/test.properties</config-property>

      <!--Below here are advanced properties -->
      <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=PropertiesFileAdapter

      <depends optional-attribute-name="ManagedConnectionPool">
      <!--embedded mbean-->


      <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager
      <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager
      <!--make the rar deploy! hack till better deployment-->

      thx in advance for any help,

        • 1. Re: Incomplete Deployment listing error
          David Jencks Master

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

          • 2. Re: Incomplete Deployment listing error
            Dawid Newbie

            thanks David for your help, now all work fine :).

            I have another question.
            As default Resource Adapter (Connection Factory exactly) is bind in JNDI under java:/xxx context. This context is accessible only in the same JVM. I wondered if is not possible to register RA in Global JNDI Context.
            I was looking in this forum and found two post with similar problem and your answers:
            First was:

            "The java:/context is not accessible outside the jboss vm and jca adapters are not intended to be accessible outside the vm in which they are deployed. "

            and second:

            "Create a stripped down jboss with only the services you need, such as the ConnectionFactory, and run your client in it, and access the java:/xxx namespace in that jvm."

            Is it mean that simple client application (using only CCI)always must access to RA through EJB or another J2EE layer or must install JBoss (or another J2EE server)on its side and deploy RA? Is it required by specification? Lightweight solution is not possible? For me more natural is to take references from JNDI and make simple call on this objects.

            best regards

            • 3. Re: Incomplete Deployment listing error
              David Jencks Master

              In vm only is according to spec. Normally outside a container you don't have a tx manager or security system which are needed for deployment in a container. A simple jndi call returning a ConnectionFactory won't be able to pull those facilities back with it, since the cf doesn't interact with them directly. If it did pull them back, you'd get most of the app server with it.