Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-3739

Dynamic VDB that imports another VDB does not get redeployed if the imported VDB is redeployed

    Details

    • Steps to Reproduce:
      Hide

      1. Deploy dynovdb1-vdb.xml
      2. Deploy dynovdb2-vdb.xml
      3. Test your connection to both VDBs (dynovdb1 and dynovdb2), should be successfull.
      4. Via jboss-cli, redeploy or deploy --force the dynovdb1-vdb.xml
      [standalone@localhost:9999 /] deploy --force /home/dsteigne/NotBackedUp/EAP643DV62GA/standalone/deployments/dynovdb1-vdb.xml
      or
      [standalone@localhost:9999 /] /deployment=dynovdb1-vdb.xml:redeploy
      5. Test the connection to both VDBs again, dynovdb1 succeeds but dynovdb2 fails with:

      WARN [org.teiid.SECURITY] (New I/O worker #10) TEIID40011 Processing exception 'TEIID40046 VDB "dynovdb2" version "latest" does not exist.' for session null. Exception type org.teiid.client.security.LogonException thrown from org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:269). Enable more detailed logging to see the entire stacktrace.

      You can see in the log where it undeploys both vdbs but only redeploys dynovdb1:

      08:10:02,567 INFO [org.teiid.RUNTIME] (MSC service thread 1-11) TEIID50026 VDB "dynovdb1.1[]" undeployed.
      08:10:02,568 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50026 VDB "dynovdb2.1[]" undeployed.
      08:10:02,575 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment dynovdb1-vdb.xml (runtime-name: dynovdb1-vdb.xml) in 11ms
      08:10:02,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "dynovdb1-vdb.xml" (runtime-name: "dynovdb1-vdb.xml")
      08:10:02,591 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID40003 VDB dynovdb1.1 is set to ACTIVE
      08:10:02,633 INFO [org.jboss.as.server] (management-handler-thread - 12) JBAS015865: Replaced deployment "dynovdb1-vdb.xml" with deployment "dynovdb1-vdb.xml"

      Show
      1. Deploy dynovdb1-vdb.xml 2. Deploy dynovdb2-vdb.xml 3. Test your connection to both VDBs (dynovdb1 and dynovdb2), should be successfull. 4. Via jboss-cli, redeploy or deploy --force the dynovdb1-vdb.xml [standalone@localhost:9999 /] deploy --force /home/dsteigne/NotBackedUp/EAP643DV62GA/standalone/deployments/dynovdb1-vdb.xml or [standalone@localhost:9999 /] /deployment=dynovdb1-vdb.xml:redeploy 5. Test the connection to both VDBs again, dynovdb1 succeeds but dynovdb2 fails with: WARN [org.teiid.SECURITY] (New I/O worker #10) TEIID40011 Processing exception 'TEIID40046 VDB "dynovdb2" version "latest" does not exist.' for session null. Exception type org.teiid.client.security.LogonException thrown from org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:269). Enable more detailed logging to see the entire stacktrace. You can see in the log where it undeploys both vdbs but only redeploys dynovdb1: 08:10:02,567 INFO [org.teiid.RUNTIME] (MSC service thread 1-11) TEIID50026 VDB "dynovdb1.1[]" undeployed. 08:10:02,568 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50026 VDB "dynovdb2.1[]" undeployed. 08:10:02,575 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment dynovdb1-vdb.xml (runtime-name: dynovdb1-vdb.xml) in 11ms 08:10:02,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "dynovdb1-vdb.xml" (runtime-name: "dynovdb1-vdb.xml") 08:10:02,591 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID40003 VDB dynovdb1.1 is set to ACTIVE 08:10:02,633 INFO [org.jboss.as.server] (management-handler-thread - 12) JBAS015865: Replaced deployment "dynovdb1-vdb.xml" with deployment "dynovdb1-vdb.xml"
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      You have to either restart the server or redeploy dynovdb2-vdb.xml:
      [standalone@localhost:9999 /] /deployment=dynovdb2-vdb.xml:redeploy

      {"outcome" => "success"}

      This is not ideal workaround.

      Show
      You have to either restart the server or redeploy dynovdb2-vdb.xml: [standalone@localhost:9999 /] /deployment=dynovdb2-vdb.xml:redeploy {"outcome" => "success"} This is not ideal workaround.
    • Bugzilla Update:
      Perform

      Description

      When using a Dynamic VDB that imports another VDB it isn't redeployed if the imported VDB is redeployed. You can in the log it undeploys the top VDB and the imported VDB but only redeploys the imported one. The top VDB then doesn't exist until it's redeployed.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                shawkins Steven Hawkins
                Reporter:
                dsteigne Debbie Steigner
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: