[jboss-jira] [JBoss JIRA] Updated: (AS7-1188) Possible to remove a jdbc driver from a server-group, when still in use

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/AS7-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated AS7-1188:
----------------------------------

    Component/s: JCA


I see two issues here:

1) The removal created an unsatisfied dependency, as the console logging shows, but that unsatisfied dependency did not trigger a rollback of the operation. I think this is a general problem, where the ServiceVerificationHandler mechanism used to detect errors caused by runtime ops does not deal with service removals.

2) Whether or not the driver removal should be allowed, resulting in a cascading removal of the datasource and anything that depends on the datasource. Based on the console logging it seems this isn't meant to happen. Heiko in the JIRA description expresses an opinion that it shouldn't happen. I think that's fine; don't let it happen.

> Possible to remove a jdbc driver from a server-group, when still in use
> -----------------------------------------------------------------------
>
>                 Key: AS7-1188
>                 URL: https://issues.jboss.org/browse/AS7-1188
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management, JCA
>    Affects Versions: 7.0.0.CR1
>            Reporter: Heiko Rupp
>            Assignee: Brian Stansberry
>
> [domain at localhost:9999 /] /server-group=main-server-group/deployment=postgresql-9.0-801.jdbc4.jar:remove
> {
>     "outcome" => "success",
>     "result" => {"server-groups" => [("main-server-group" => {"master" => {
>     "host" => "master",
>     "response" => {"outcome" => "success"}
> }})]}
> }
> [domain at localhost:9999 /] /profile=default/subsystem=datasources/data-source=postgres:read-resource
> {
>     "outcome" => "success",
>     "result" => {
>         "background-validation" => undefined,
>         "background-validation-minutes" => undefined,
>         "blocking-timeout-wait-millis" => undefined,
>         "connection-url" => "jdbc:postgresql://127.0.0.1:5432/rhqdev",
>         "driver-name" => "postgresql-9.0-801.jdbc4.jar",
> Console says
> [Server:server-two] 13:55:09,768 INFO  [org.jboss.as.server.controller] (pool-1-thread-4) Undeployed "postgresql-9.0-801.jdbc4.jar"
> [Server:server-two] 13:55:09,769 INFO  [org.jboss.as.controller] (pool-1-thread-4) Service status report
> [Server:server-two]    New missing/unsatisfied dependencies:
> [Server:server-two]       service jboss.jdbc-driver.postgresql-9_0-801_jdbc4_jar (missing)
> and after reboot:
> [Server:server-one] 13:58:20,938 INFO  [org.jboss.as.controller] (Controller Boot Thread) Service status report
> [Server:server-one]    New missing/unsatisfied dependencies:
> [Server:server-one]       service jboss.jdbc-driver.postgresql-9_0-801_jdbc4_jar (missing)
> I think removing the driver from a server group should not be possible if a datasource still refers to it.
> Basically the same way I can't remove a deployment from /deployment, while still in use in /server-group=x/deployment.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira