6 Replies Latest reply on Feb 1, 2013 12:33 PM by Frank Langelage

    Adding resource-adapter connection-definition fails sometimes, Race Condition?

    Frank Langelage Master

      Problems with resource-adapters reappeared.

      The rar-file controller.rar is present in deployments folder and deployed.

      In standalone.xml there is no resource-adapter defined using controller.rar.

       

      My first cli file:

      if (outcome != success) of /subsystem=resource-adapters/resource-adapter=controller.rar:read-resource

          /subsystem=resource-adapters/resource-adapter=controller.rar:add(archive=controller.rar, transaction-support=NoTransaction)

      end-if

      if (outcome != success) of /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc:read-resource

          /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc:add(jndi-name="java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector", class-name="biz.mbisoftware.fn.jca.controllerconnector.ManagedConnectionFactoryImpl", enabled=true)

          /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=ClientService:add(value="JCAClient")

          /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=SocketTimeout:add(value="0")

          /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=Encoding:add(value="ISO-8859-15")

          /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=ServerName:add(value="sb2000")

          /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=PortNumber:add(value="6500")

          /subsystem=resource-adapters/resource-adapter=controller.rar:activate

      end-if

       

      Executing this is just fine.

      Output of jboss-cli.sh:

      #1 /subsystem=resource-adapters/resource-adapter=controller.rar:add(archive=controller.rar, transaction-support=NoTransaction)

      #1 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc:add(jndi-name="java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector", class-name="biz.mbisoftware.fn.jca.controllerconnector.ManagedConnectionFactoryImpl", enabled=true)

      #2 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=ClientService:add(value="JCAClient")

      #3 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=SocketTimeout:add(value="0")

      #4 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=Encoding:add(value="ISO-8859-15")

      #5 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=ServerName:add(value="sb2000")

      #6 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=mbi2e-lafr-sb2000-ipc/config-properties=PortNumber:add(value="6500")

      #7 /subsystem=resource-adapters/resource-adapter=controller.rar:activate

       

      Entries in server.log:

      00:02:41,607 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector

      00:02:41,612 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer#createObjectsAndInjectValue] IJ020002: Deployed: file:/mbi/tools/jboss/7.2/standalone/tmp/vfs/temp165646327ca2133/controller.rar-8229ffcec3d6382d/contents/

      00:02:41,621 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector]

       

      Resource-adapater and connection definiton are there. Also visible through management console.

       

      Now trying to add an connection-definition, running the same script as just replacing 'mbi2e-lafr-sb2000-ipc' by 'mbi2e-lafr-sb2000-ipc'.

      Output of jboss-cli.sh:

      #1 /subsystem=resource-adapters/resource-adapter=controller.rar:add(archive=controller.rar, transaction-support=NoTransaction)

      #1 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=hgm2e-langfr-sb2000-ipc:add(jndi-name="java:/eis/hgm2e-langfr-sb2000-ipc/ControllerConnector", class-name="biz.mbisoftware.fn.jca.controllerconnector.ManagedConnectionFactoryImpl", enabled=true)

      #2 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=hgm2e-langfr-sb2000-ipc/config-properties=ClientService:add(value="JCAClient")

      #3 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=hgm2e-langfr-sb2000-ipc/config-properties=SocketTimeout:add(value="0")

      #4 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=hgm2e-langfr-sb2000-ipc/config-properties=Encoding:add(value="ISO-8859-15")

      #5 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=hgm2e-langfr-sb2000-ipc/config-properties=ServerName:add(value="sb2000")

      #6 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=hgm2e-langfr-sb2000-ipc/config-properties=PortNumber:add(value="6501")

      #7 /subsystem=resource-adapters/resource-adapter=controller.rar:activate

       

      Entries in server.log:

      00:03:42,783 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector]

      00:03:42,802 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector

      00:03:42,807 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/hgm2e-langfr-sb2000-ipc/ControllerConnector

      00:03:42,817 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer#createObjectsAndInjectValue] IJ020002: Deployed: file:/mbi/tools/jboss/7.2/standalone/tmp/vfs/temp165646327ca2133/controller.rar-8229ffcec3d6382d/contents/

      00:03:42,823 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector]

      00:03:42,834 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/hgm2e-langfr-sb2000-ipc/ControllerConnector]

       

      Everything still fine in this case.

       

      Now a third connection-definition.

      Output of jboss-cli.sh:

      #1 /subsystem=resource-adapters/resource-adapter=controller.rar:add(archive=controller.rar, transaction-support=NoTransaction)

      #1 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=maj2e-langfr-dev:add(jndi-name="java:/eis/maj2e-langfr-dev/ControllerConnector", class-name="biz.mbisoftware.fn.jca.controllerconnector.ManagedConnectionFactoryImpl", enabled=true)

      #2 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=maj2e-langfr-dev/config-properties=ClientService:add(value="JCAClient")

      #3 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=maj2e-langfr-dev/config-properties=SocketTimeout:add(value="0")

      #4 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=maj2e-langfr-dev/config-properties=Encoding:add(value="ISO-8859-15")

      #5 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=maj2e-langfr-dev/config-properties=ServerName:add(value="sb2000")

      #6 /subsystem=resource-adapters/resource-adapter=controller.rar/connection-definitions=maj2e-langfr-dev/config-properties=PortNumber:add(value="6506")

      #7 /subsystem=resource-adapters/resource-adapter=controller.rar:activate

       

      But this time in server.log:

      00:04:20,941 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector

      00:04:20,952 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector]

      00:04:20,955 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/hgm2e-langfr-sb2000-ipc/ControllerConnector]

      00:04:20,955 ERROR [org.jboss.msc.service.fail#startFailed] MSC00001: Failed to start service jboss.ra.deployment."controller.rar_3": org.jboss.msc.service.StartException in service jboss.ra.deployment."controller.rar_3": org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [controller]

              at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:131)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.3.GA.jar:1.0.3.GA]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.3.GA.jar:1.0.3.GA]

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_38]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_38]

              at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38]

      Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [controller]

              at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:115)

              ... 5 more

      Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/mbi/tools/jboss/7.2/standalone/tmp/vfs/temp165646327ca2133/controller.rar-8229ffcec3d6382d/contents/

              at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2456)

              at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$AS7RaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:183)

              at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:108)

              ... 5 more

      Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.connector.connection-factory.java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector is already registered

              at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.3.GA.jar:1.0.3.GA]

              at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.3.GA.jar:1.0.3.GA]

              at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.3.GA.jar:1.0.3.GA]

              at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.3.GA.jar:1.0.3.GA]

              at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.3.GA.jar:1.0.3.GA]

              at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.3.GA.jar:1.0.3.GA]

              at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractAS7RaDeployer.bindConnectionFactory(AbstractResourceAdapterDeploymentService.java:278)

              at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2218)

              ... 7 more

       

      00:04:21,026 INFO  [org.jboss.as.controller#tick] JBAS014774: Service status report

      JBAS014775:    New missing/unsatisfied dependencies:

            service jboss.resourceadapters.ra."controller.rar".maj2e-langfr-dev (missing) dependents: [service jboss.resourceadapters.ra."controller.rar".maj2e-langfr-dev.PortNumber, service jboss.resourceadapters.ra."controller.rar".maj2e-langfr-dev.ClientService, service jboss.resourceadapters.ra."controller.rar".maj2e-langfr-dev.ServerName, service jboss.resourceadapters.ra."controller.rar".maj2e-langfr-dev.SocketTimeout, JBAS014799: ... and 2 more ]

       

      The :activate failed and caused an exception.

       

      This behaviour is not really reproducable. What got my attention is the order of the messages appearing.

      When succesful we have Unbound, Register, Deployed, Bound.

      00:03:42,783 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector]

      00:03:42,802 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector

      00:03:42,807 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/hgm2e-langfr-sb2000-ipc/ControllerConnector

      00:03:42,817 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer#createObjectsAndInjectValue] IJ020002: Deployed: file:/mbi/tools/jboss/7.2/standalone/tmp/vfs/temp165646327ca2133/controller.rar-8229ffcec3d6382d/contents/

      00:03:42,823 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector]

      00:03:42,834 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/hgm2e-langfr-sb2000-ipc/ControllerConnector]

      This seems to really make sense to me.

       

      When not succesful we have Register, Unbound, Failure.

      00:04:20,941 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector

      00:04:20,952 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbi2e-lafr-sb2000-ipc/ControllerConnector]

      00:04:20,955 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/hgm2e-langfr-sb2000-ipc/ControllerConnector]

      But this does not make sense to me. The new regsitration is done before the unbinding has finished?

       

      To me this seems to be a bug.

      Maybe something is done in parallel not in strict sequence. Sometimes its succesful, sometimes not, depending on which thread gets CPU time first?

        • 2. Re: Adding resource-adapter connection-definition fails sometimes, Race Condition?
          Frank Langelage Master

          Yes.

           

          From git://github.com/jbossas/jboss-as                       
          * branch        master -> FETCH_HEAD                
          First, rewinding head to replay your work on top of it...    

          Fast-forwarded master to 5775cda83b64c00795431bbe6f80748610122948.

          • 3. Re: Adding resource-adapter connection-definition fails sometimes, Race Condition?
            Stefano Maestri Expert

            Hi Frank,

            I'm not sure I'm understanding what you are trying to do. If I well get your scripts, they are doing different activation of the same archive at each run, and I don't see in any cases a :remove for previous activation.

            You can of course do it, but you should use different name for different activation, while as I can see you are always using controller.rar as resource-adapter name. If I'm wrong and you are in some way removing previous activation please correct me (and even if you restart server between scripts run).

             

            I'll check why DMR is permitting you to do that (which is in the end wrong), but if you are doing that please try to fix your scripts using different resource-adapter name for each activation. Maybe this race condition is a pure seide effect of using same name for different activation, and the solution will be to avoid this situation.

             

            If you are trying to get some behavior using this sidce effect, please describe me what you want to do exactly.

             

            regards

            S.

            • 4. Re: Adding resource-adapter connection-definition fails sometimes, Race Condition?
              Frank Langelage Master

              You told me to call :acticvate after adding a new connection definition.

              See https://community.jboss.org/message/725604#725604.

               

              I simply want 1 resource-adapter named "controller.rar" with multiple connection definitions, added when needed.

              So the script checks first, if resource-adapter is already there. If not, then it's created.

              Then it checks if the conneciton-definition is already there, if not create and configure it.

              At the end :activate, to activate the new configuration.

               

              I've running a server in the office build with sources as of 11. January 2013. Here everything works fine.

              One resource-adapter with currently 15 conneciton-definitions. See message lines from server.log below.

               

              And without :activate the new connection definition is not bound to JNDI. Connection definition is visible via jboss-cli and web console, enabled, etc. but JNDI lookup fails.

               

              And I see no need to :remove anything. I just want to :add if not there.

               

              I remember I had other problems when creating a respource-adapter for each of the connections definitions, so that each resource-adapter has only one connection-definiton.

              One problem I can remember is, that web console only displays the archive name, not the resource-adapter name and somehow gets into trouble there.

               

              15:23:08,190 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/pms350i-ifx117/ControllerConnector]

              15:23:08,190 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbio2e-o10lx/ControllerConnector]

              15:23:08,191 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbi2in-ifx115/ControllerConnector]

              15:23:08,192 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mie350i-ifx115/ControllerConnector]

              15:23:08,193 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbi2e-gp3/ControllerConnector]

              15:23:08,193 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/feb081022i-o10lx/ControllerConnector]

              15:23:08,193 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbi350i-ifx117/ControllerConnector]

              15:23:08,194 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/rec20120816b-o10lx/ControllerConnector]

              15:23:08,194 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbi350e-ifx117/ControllerConnector]

              15:23:08,194 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbio350e-o10lx/ControllerConnector]

              15:23:08,195 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mbio350i-o10lx/ControllerConnector]

              15:23:08,192 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/mie350e-ifx115/ControllerConnector]

              15:23:08,193 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/tea071025-o10lx/ControllerConnector]

              15:23:08,195 INFO  [org.jboss.as.connector.deployment#transition] JBAS010410: Unbound JCA ConnectionFactory [java:/eis/cor2e-20110613-o10lx/ControllerConnector]

              15:23:08,235 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbi2in-ifx115/ControllerConnector

              15:23:08,241 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mie350e-ifx115/ControllerConnector

              15:23:08,243 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/hgm2e-ifx115/ControllerConnector

              15:23:08,245 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/pms350i-ifx117/ControllerConnector

              15:23:08,246 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbi350i-ifx117/ControllerConnector

              15:23:08,247 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/rec20120816b-o10lx/ControllerConnector

              15:23:08,249 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbi350e-ifx117/ControllerConnector

              15:23:08,250 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbio350e-o10lx/ControllerConnector

              15:23:08,251 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mie350i-ifx115/ControllerConnector

              15:23:08,253 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbio350i-o10lx/ControllerConnector

              15:23:08,254 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbi2e-gp3/ControllerConnector

              15:23:08,256 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/mbio2e-o10lx/ControllerConnector

              15:23:08,258 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/tea071025-o10lx/ControllerConnector

              15:23:08,260 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/feb081022i-o10lx/ControllerConnector

              15:23:08,262 INFO  [org.jboss.as.connector.deployment#bindConnectionFactory] JBAS010406: Registered connection factory java:/eis/cor2e-20110613-o10lx/ControllerConnector

              15:23:08,266 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer#createObjectsAndInjectValue] IJ020002: Deployed: file:/gp3/mbi/tools/jboss/7.x.8080/standalone/tmp/vfs/tempbe038d239e88833b/controller.rar-5e24c29b9a66fb78/contents/

              15:23:08,273 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mie350i-ifx115/ControllerConnector]

              15:23:08,273 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbio2e-o10lx/ControllerConnector]

              15:23:08,273 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbio350i-o10lx/ControllerConnector]

              15:23:08,274 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/rec20120816b-o10lx/ControllerConnector]

              15:23:08,274 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbi2e-gp3/ControllerConnector]

              15:23:08,274 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbio350e-o10lx/ControllerConnector]

              15:23:08,274 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mie350e-ifx115/ControllerConnector]

              15:23:08,274 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbi350e-ifx117/ControllerConnector]

              15:23:08,275 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/tea071025-o10lx/ControllerConnector]

              15:23:08,275 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/cor2e-20110613-o10lx/ControllerConnector]

              15:23:08,275 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbi2in-ifx115/ControllerConnector]

              15:23:08,275 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/pms350i-ifx117/ControllerConnector]

              15:23:08,276 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/hgm2e-ifx115/ControllerConnector]

              15:23:08,276 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/mbi350i-ifx117/ControllerConnector]

              15:23:08,276 INFO  [org.jboss.as.connector.deployment#transition] JBAS010401: Bound JCA ConnectionFactory [java:/eis/feb081022i-o10lx/ControllerConnector]

              • 5. Re: Adding resource-adapter connection-definition fails sometimes, Race Condition?
                Stefano Maestri Expert

                Frank Langelage wrote:

                 

                You told me to call :acticvate after adding a new connection definition.

                See https://community.jboss.org/message/725604#725604.

                 

                I simply want 1 resource-adapter named "controller.rar" with multiple connection definitions, added when needed.

                So the script checks first, if resource-adapter is already there. If not, then it's created.

                Then it checks if the conneciton-definition is already there, if not create and configure it.

                At the end :activate, to activate the new configuration.

                 

                Yup, it's correct. I had not understand. And yes you don't need to remove anything

                 

                Frank Langelage wrote:

                 

                I've running a server in the office build with sources as of 11. January 2013. Here everything works fine.

                One resource-adapter with currently 15 conneciton-definitions. See message lines from server.log below.

                 

                Yup that's fine. And has problem re-appeared in last master?

                 

                Frank Langelage wrote:

                 

                 

                And without :activate the new connection definition is not bound to JNDI. Connection definition is visible via jboss-cli and web console, enabled, etc. but JNDI lookup fails.

                 

                Yup, it's what :activate do: apply configs and bound to jndi

                 

                Frank Langelage wrote:

                 

                I remember I had other problems when creating a respource-adapter for each of the connections definitions, so that each resource-adapter has only one connection-definiton.

                One problem I can remember is, that web console only displays the archive name, not the resource-adapter name and somehow gets into trouble there.

                This problem is soleved in last master. Every RA has its own name, serialized into "id" attribute in xml. But anyway your config (just one RA and more than one CF) should work too.

                 

                I'll try it out. JUst add any infos you think could help if you recall anything.

                 

                Thanks

                S.

                • 6. Re: Adding resource-adapter connection-definition fails sometimes, Race Condition?
                  Frank Langelage Master

                  Stefano Maestri schrieb:

                   

                  Yup that's fine. And has problem re-appeared in last master?

                   

                   

                  Cannot say exactly when it re-appeared.

                  Do not deploy multiple ear's requiring the multiple connection-definitions.

                  Mostly only dealing with a single connection-definition and a single ear.

                   

                  So I can only say, that the problem came up again between 11 and 30 of January.

                  Within this time the was an update of ironjacamar from 1.0.14.Final to 1.0.15.Final, besides a lot of others.

                  I might try with the older version of ironjacamar if you think this could be a cause for the problem.