-
Bug
-
Resolution: Done
-
Major
-
7.1.1.Final
-
None
When the ResourceAdapter#start(BoostrapContext) method is invoked on an annotation based 1.6 JCR resource adapter the naming context is read only. Binding values results in the following exception:
20:56:07,321 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.ra.deployer."sample-rar-1.0.0-SNAPSHOT": org.jboss.msc.service.StartException in service jboss.ra.deployer."sample-rar-1.0.0-SNAPSHOT": JBAS010446: Failed to start RA deployment [sample-rar-1.0.0-SNAPSHOT] at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService.start(ResourceAdapterDeploymentService.java:105) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07] Caused by: org.jboss.jca.deployers.common.DeployException: IJ020051: Unable to start com.github.marschall.kotlin.rar.implementation.SampleAdapter at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:354) at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2187) at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1046) at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService$AS7RaDeployer.doDeploy(ResourceAdapterDeploymentService.java:186) at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService.start(ResourceAdapterDeploymentService.java:102) ... 5 more Caused by: java.lang.UnsupportedOperationException: JBAS011859: Naming context is read-only at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.java:126) at org.jboss.as.naming.WritableServiceBasedNamingStore.unbind(WritableServiceBasedNamingStore.java:98) at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:85) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:244) at org.jboss.as.naming.InitialContext.rebind(InitialContext.java:195) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:252)
The problem seems to be while org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(StartContext) does WritableServiceBasedNamingStore.pushOwner() to make the naming context writable org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterDeploymentService.start(StartContext) does not do it.
- relates to
-
WFLY-2502 Naming context read-only during ResourceAdapter#stop()
- Closed