3 Replies Latest reply on Apr 9, 2003 10:35 PM by David Jencks

    jca15 deployment problem with JBoss 4

    jw Newbie

      (JBoss 4, built from CVS HEAD April 6th)

      The rar seems to deploy ok (containing the classes as jar + ra.xml standard jca 1.5 deploymen descriptor).
      But trying to deploy the service-xml, I get these messages (it's an outbound adapter):

      12:19:31,357 INFO [MainDeployer] Starting deployment of package: file:/D:/projects/checkouts/jboss-head/build/output/jboss-4.0.0alpha/server/default/deploy/bdbadapter-service.xml
      12:19:31,377 INFO [SARDeployer] looking for nested deployments in : file:/D:/projects/checkouts/jboss-head/build/output/jboss-4.0.0alpha/server/default/deploy/bdbadapter-service.xml
      12:19:31,437 INFO [ServiceConfigurator] class not found for mbean jboss.jca:service=MCF,name=bdbadapter_factory
      12:19:31,457 INFO [ServiceController] returning from create for service jboss.jca:service=MCF,name=bdbadapter_factory, invalid transition from CLASSMISSING
      12:19:31,457 INFO [JBossManagedConnectionPool] Creating
      12:19:31,457 INFO [JBossManagedConnectionPool] Created
      12:19:31,457 INFO [ServiceController] Returning from start request for service: jboss.jca:service=CM,name=bdbadapter_factory, invalid transition from state CONFIGURED
      12:19:31,457 INFO [ServiceController] Returning from start request for service: jboss.jca:service=MCF,name=bdbadapter_factory, invalid transition from state CLASSMISSING
      12:19:31,457 INFO [JBossManagedConnectionPool] Starting
      12:19:31,467 INFO [JBossManagedConnectionPool] Started
      12:19:31,467 INFO [ServiceController] Returning from start request for service: jboss.jca:service=CM,name=bdbadapter_factory, invalid transition from state CONFIGURED
      12:19:31,467 INFO [MainDeployer] Deployed package: file:/D:/projects/checkouts/jboss-head/build/output/jboss-4.0.0alpha/server/default/deploy/bdbadapter-service.xml
      12:19:31,467 ERROR [URLDeploymentScanner] MBeanException: Incomplete Deploymentlisting:
      Packages waiting for a deployer:

      Incompletely deployed packages:

      MBeans waiting for classes:
      [jboss.jca:service=MCF,name=bdbadapter_factory]MBeans waiting for other MBeans:
      [org.jboss.system.ServiceContext@cbcb5b {
      objectName: jboss.jca:service=CM,name=bdbadapter_factory
      state: CONFIGURED
      dependencies: [jboss.jca:service=LocalTxPool,name=bdbadapter_factory_pool, jboss.jca:service=CachedConnectionManager, jboss.jca:service=MCF,name=bdbadapter_factory, jboss.security:service=JaasSecurityManager]
      }, org.jboss.system.ServiceContext@18adc49f {
      objectName: jboss.jca:service=MCF,name=bdbadapter_factory
      state: CLASSMISSING
      dependants: [jboss.jca:service=CM,name=bdbadapter_factory]
      }]
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:

      Incompletely deployed packages:

      MBeans waiting for classes:
      [jboss.jca:service=MCF,name=bdbadapter_factory]MBeans waiting for other MBeans:
      [org.jboss.system.ServiceContext@cbcb5b {
      objectName: jboss.jca:service=CM,name=bdbadapter_factory
      state: CONFIGURED
      dependencies: [jboss.jca:service=LocalTxPool,name=bdbadapter_factory_pool, jboss.jca:service=CachedConnectionManager, jboss.jca:service=MCF,name=bdbadapter_factory, jboss.security:service=JaasSecurityManager]
      }, org.jboss.system.ServiceContext@18adc49f {
      objectName: jboss.jca:service=MCF,name=bdbadapter_factory
      state: CLASSMISSING
      dependants: [jboss.jca:service=CM,name=bdbadapter_factory]
      }]

      *** END OUTPUT *******************************************

      What I did was to take the example XML-descriptor from /jboss-head/testsuite/src/resources/jca/jdbc/META-INF/jboss-service.xml
      and edited it like this:

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





      bdbadapter_factory

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




      <config-property name="PropertyUrl" type="java.lang.String">H:/bdb/bdbadapter.properties</config-property>
      <config-property name="DbEnvPath" type="java.lang.String">H:/bdb</config-property>
      <config-property name="CacheSizeGigabytes" type="java.lang.Integer">0</config-property>
      <config-property name="CacheSizeBytes" type="java.lang.Integer">8388608</config-property>
      <config-property name="CachePieces" type="java.lang.Integer">0</config-property>
      <config-property name="LogDirectory" type="java.lang.String">D:/logs</config-property>
      <config-property name="LogSwitch" type="java.lang.Boolean">true</config-property>



      <!--Below here are advanced properties -->
      <!--hack-->
      <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=Berkeley DB Resource Adapter





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


      3
      10
      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)-->
      ByContainer



      <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager

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




        • 1. Re: jca15 deployment problem with JBoss 4
          David Jencks Master

          You pretty much have to use a *-ds.xml file on jb4. Look at say firebird-ds.xml as an example: for an inbound adapter there is an example in the test suite.

          Old *-service.xml files for datasources won't work on jb4. Even on jb3.2 I strongly recommend *-ds.xml files

          • 2. Re: jca15 deployment problem with JBoss 4
            jw Newbie

            ...tried this -ds.xml without success.
            The RAR archive deploys without error messages.
            Then the -ds-descriptor also deploys without errors.

            But when I try to get a reference by either
            lookup("java:logger_factory");
            or
            lookup("java:/logger_factory");
            or
            lookup("logger_factory");
            the EJB always gets "Name not found" from JNDI

            What do I need to put in the -ds.xml ?


            <?xml version="1.0" encoding="UTF-8"?>
            <connection-factories>
            <tx-connection-factory>

            <jndi-name>logger_factory</jndi-name>

            <adapter-display-name>Chronological Logger Resource Adapter</adapter-display-name>

            <connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>

            <xa-transaction/>

            <user-name>admin</user-name>

            admin

            <min-pool-size>1</min-pool-size>

            </tx-connection-factory>
            </connection-factories>

            • 3. Re: jca15 deployment problem with JBoss 4
              David Jencks Master

              java:/logger_factory would be the right name.

              Are any mbeans reported as incompletely deployed? Can you see the cf in jndi view?

              Are you 100% sure the adapter-display-name is correct?

              Please show the server.log excerpt from when the *-ds.xml deployment start until it completes.