4 Replies Latest reply on Mar 24, 2016 12:29 PM by Marco Ardito

    8.13.x server bundle: ExampleDS can't be removed

    Marco Ardito Master

      I cannot remove bundled ExampleDS datasource. I can disable it but doing so, it seems to create problems to bundled olingo/odata wars and elsewhere.

      I already reported this on another thread  8.13 server bundle + webconsole 2.5.1, problems..., with 8.13.2,

      but today it happened again with the brand new 8.13.3. I guess there's a problem somewhere.

       

      I just

      - unzipped the server bundle,

      - copied my own user/role properties files

      - started the server

       

      ON the web console I find

      - one JDBC datasource 'ExampleDS' (enabled)

      - one teiid-olingo-8.13.3-odata4.war deployment (active)

      - one teiid-odata-8.13.3-odata2.wardeployment (active)

       

      If I try to remove ExamplerDS I get

      =============================

      Unknown error

       

      Unexpected HTTP response: 500

       

      Request

      {

          "enabled" => true,

          "jndi-name" => "java:jboss/datasources/ExampleDS",

          "user-name" => "sa",

          "password" => "sa",

          "security-domain" => "",

          "pool-name" => "",

          "transaction-isolation" => "",

          "new-connection-sql" => "",

          "validate-on-match" => false,

          "stale-connection-checker-class-name" => "",

          "exception-sorter-class-name" => "",

          "share-prepared-statements" => false,

          "jta" => true,

          "use-ccm" => true,

          "set-tx-query-timeout" => false,

          "statistics-enabled" => false,

          "track-statements" => "NOWARN",

          "use-fast-fail" => false,

          "allow-multiple-users" => false,

          "connection-url" => "jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE",

          "driver-class" => "",

          "datasource-class" => "",

          "driver-name" => "h2",

          "valid-connection-checker-class-name" => "",

          "check-valid-connection-sql" => "",

          "background-validation" => false,

          "name" => "ExampleDS",

          "operation" => "remove",

          "address" => [

              ("subsystem" => "datasources"),

              ("data-source" => "ExampleDS")

          ]

      }

       

      Response

       

      Internal Server Error

      {

          "outcome" => "failed",

          "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies:

      Service jboss.naming.context.java.jboss.datasources.ExampleDS was depended upon by service jboss.naming.context.java.module.\"teiid-olingo-8.13.3-odata4\".\"teiid-olingo-8.13.3-odata4\".DefaultDataSource, service jboss.naming.context.java.module.\"teiid-odata-8.13.3-odata2\".\"teiid-odata-8.13.3-odata2\".DefaultDataSource",

          "rolled-back" => true

      }

      =============================

       

      so, it's rolled back.

       

      Now, I can disable ExampleDS with success, but then, if I try to remove the disabled ExampleDS, I get the same identical error message, and it's roleld back, I still get a disabled ExampleDS...

       

      Then just switching to the deployments tab, I get also

      =============================

      Unable to load deployments

       

      Unexpected HTTP response: 500

       

      Request

      {

      "operation" => "read-children-resources",
      "address" => undefined,
      "child-type" => "deployment",
      "include-runtime" => true,
      "recursive" => true

      }

       

      Response

       

      Internal Server Error

      {

      "outcome" => "failed",
      "rolled-back" => true

      }

      =============================

       

      With ExampleDS disabled, if I first remove the bundled olingo/odata .wars, only then I can remove ExampleDS.

       

      But then, if I try to deploy a simple jdbc driver jar:

       

      =============================

      [standalone@localhost:9990 /] deploy jars/jtds-1.3.0.jar

      15:16:15,549 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5)  WFLYSRV0027: Starting deployment of "jtds-1.3.0.jar" (runtime-name: "jtds-1.3.0.jar")

      15:16:15,588 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5)  WFLYJCA0005: Deploying non-JDBC-compliant driver class net.sourceforge.jtds.jdbc.Driver (version 1.3)

      15:16:15,592 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1)  WFLYJCA0018: Started Driver service with driver-name = jtds-1.3.0.jar

      15:16:15,600 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1)  WFLYCTL0013: Operation ("deploy") failed - address: ({"deployment" => "jtds-1.3.0.jar"}) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.\"jtds-1.3.0\".\"jtds-1.3.0\".DefaultDataSource is missing [jboss.naming.context.java.jboss.datasources.ExampleDS]"]}

      15:16:15,601 ERROR [org.jboss.as.server] (management-handler-thread - 1)  WFLYSRV0021: Deploy of deployment "jtds-1.3.0.jar" was rolled back with the following failure message: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.\"jtds-1.3.0\".\"jtds-1.3.0\".DefaultDataSource is missing [jboss.naming.context.java.jboss.datasources.ExampleDS]"]}

      15:16:15,602 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4)  WFLYJCA0019: Stopped Driver service with driver-name = jtds-1.3.0.jar

      15:16:15,616 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8)  WFLYSRV0028: Stopped deployment jtds-1.3.0.jar (runtime-name: jtds-1.3.0.jar) in 15ms

      15:16:15,617 INFO  [org.jboss.as.controller] (management-handler-thread - 1)  WFLYCTL0183: Service status report

      WFLYCTL0184:    New missing/unsatisfied dependencies:

            service jboss.naming.context.java.app."jtds-1.3.0".env (missing) dependents: [service jboss.deployment.unit."jtds-1.3.0.jar".jndiDependencyService]

            service jboss.naming.context.java.jboss.datasources.ExampleDS (missing) dependents: [service jboss.naming.context.java.module."jtds-1.3.0"."jtds-1.3.0".DefaultDataSource]

            service jboss.naming.context.java.module."jtds-1.3.0"."jtds-1.3.0".DefaultContextService (missing) dependents: [service jboss.deployment.unit."jtds-1.3.0.jar".jndiDependencyService]

            service jboss.naming.context.java.module."jtds-1.3.0"."jtds-1.3.0".DefaultDataSource (missing) dependents: [service jboss.deployment.unit."jtds-1.3.0.jar".jndiDependencyService]

            service jboss.naming.context.java.module."jtds-1.3.0"."jtds-1.3.0".DefaultManagedExecutorService (missing) dependents: [service jboss.deployment.unit."jtds-1.3.0.jar".jndiDependencyService]

            service jboss.naming.context.java.module."jtds-1.3.0"."jtds-1.3.0".DefaultManagedScheduledExecutorService (missing) dependents: [service jboss.deployment.unit."jtds-1.3.0.jar".jndiDependencyService]

            service jboss.naming.context.java.module."jtds-1.3.0"."jtds-1.3.0".env (missing) dependents: [service jboss.deployment.unit."jtds-1.3.0.jar".jndiDependencyService]

       

      {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.\"jtds-1.3.0\".\"jtds-1.3.0\".DefaultDataSource is missing [jboss.naming.context.java.jboss.datasources.ExampleDS]"]}}}

       

      =============================

       

      Why can't I remove ExampleDS?

       

      Marco