]
Dmitrii Pogorelov commented on WFLY-13144:
------------------------------------------
[~shawkins] thx a lot! I tried the idea to remove the connection-definitions before
removing the resource-adapter and it worked! The workaround for the workflow which I
described in scope of the issue is the following (to remove the jcaDemo_VDB_ID_1 resource
adapter after restarting WildFly server):
{code:java}
/subsystem=resource-adapters/resource-adapter=jcaDemo_VDB_ID_1/connection-definitions=jcaDemo_VDB_ID_1:remove{allow-resource-service-restart=true}
/subsystem=resource-adapters/resource-adapter=jcaDemo_VDB_ID_1:remove{allow-resource-service-restart=true}
{code}
Resource Adapter can't be deleted after restarting server
---------------------------------------------------------
Key: WFLY-13144
URL:
https://issues.redhat.com/browse/WFLY-13144
Project: WildFly
Issue Type: Bug
Components: JCA
Affects Versions: 14.0.1.Final, 11.0.0.Final, 17.0.1.Final
Reporter: Dmitrii Pogorelov
Assignee: Ivo Studensky
Priority: Critical
Attachments: jca-demo-1.0.rar, jcademo-source-code.rar
The issue is related to the WFLY-6774 issue. I'm working with Teiid and should
create/delete resource adapters many times, especially resource adapters based on the same
archive. The WFLY-6774 fix works well before the restarting server allowing me to
create/delete resource adapters without restarting the server. Once I restart the server
and try to remove a resource adapter based on an archive I'll get the following
error:
{code:noformat}
[standalone@localhost:9990 /]
/subsystem=resource-adapters/resource-adapter=jcaDemo_VDB_ID_1:remove{allow-resource-service-restart=true}
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0171: Removing services has lead
to unsatisfied dependencies:
Service jboss.resourceadapters.ra.jcaDemo_VDB_ID_1 was depended upon by service
jboss.deployment.unit.\"jca-demo-1.0.rar\".INSTALL",
"rolled-back" => true
}
{code}
After showing the error server will rollback the "remove" command deploying the
jca-demo-1.0.rar archive again and re-creating the jcaDemo_VDB_ID_1 resource adapter. As a
result I can't remove the resource adapter via cli commands, it can be removed only
manually (removing the resource adapter in standalone.xml). The bug can be reproduced (at
least versions which I checked) on WildFly 11.0.0.Final, WildFly 14.0.1.Final and WildFly
17.0.1.Final.