Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-8618

BootstrapContext wasn't found when reloading server with distributed workmanager

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 11.0.0.Beta1
    • None
    • JCA

      On single node, set up distributed workmanager:

      /subsystem=jca/distributed-workmanager=newdwm:add(name=newdwm)
      /subsystem=jca/distributed-workmanager=newdwm/short-running-threads=newdwm:add(queue-length=10,max-threads=10)
      /subsystem=jca/bootstrap-context=customContext1:add(name=customContext1,workmanager=newdwm)
      run-batch
      reload
      

      We should now have our distributed workmanager correctly linked with the customContext1. When we now deploy the dwmtest.ear (attached, same as in JBEAP-9422), everything is OK and we can access the admin objects, schedule work, etc.
      However, when the server is reloaded or restarted, the deployment fails and the following exception is thrown:

      15:03:59,758 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 67) MSC000001: Failed to start service jboss.ra.deployer."dwmtest.ear#dwm.rar": org.jboss.msc.service.StartException in service jboss.ra.deployer."dwmtest.ear#dwm.rar": WFLYJCA0046: Failed to start RA deployment [dwmtest.ear#dwm.rar]
      	at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService$1.run(ResourceAdapterDeploymentService.java:174)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:745)
      	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
      Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start org.jboss.as.test.integration.jca.rar.DistributedResourceAdapter1
      	at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:343)
      	at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2009)
      	at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService$WildFLyRaDeployer.doDeploy(ResourceAdapterDeploymentService.java:226)
      	at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService.start(ResourceAdapterDeploymentService.java:124)
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:745)
      Caused by: java.lang.IllegalStateException: The BootstrapContext couldn't be created: customContext1
      	at org.jboss.jca.core.bootstrapcontext.BootstrapContextCoordinator.createBootstrapContext(BootstrapContextCoordinator.java:215)
      	at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:331)
      	... 8 more
      Caused by: java.lang.IllegalArgumentException: The BootstrapContext wasn't found: customContext1
      	at org.jboss.jca.core.bootstrapcontext.BootstrapContextCoordinator.createBootstrapContext(BootstrapContextCoordinator.java:196)
      	... 9 more
      

      If dwmtest.ear is deployed without first setting up customContext1, the exact same exception is thrown (though it is expected and valid in that case).

      Note that the attached deployment requires the context to be customContext1 as defined in its ironjacamar.xml.

              smaestri@redhat.com Stefano Maestri
              smaestri@redhat.com Stefano Maestri
              Richard Janik Richard Janik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: