Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-1514

JBDS does not completely clean up Teiid PREVIEW VDBs and DataSources

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 4.0.0.CR2
    • 4.0.0.Beta2
    • teiid
    • None
    • Hide

      Import the attached Teiid Model project (FinancialsDemo.zip) into JBDS. Execute a preview on the BrokerageModel.AccountValue virtual table. This will cause the full 30 Preview vdb's to be deployed. Then exit the modeler and examine the Preview models left on the server (both vdb's and datasources). 14 Preview VDBs seem to be consistently undeleted.

      Show
      Import the attached Teiid Model project (FinancialsDemo.zip) into JBDS. Execute a preview on the BrokerageModel.AccountValue virtual table. This will cause the full 30 Preview vdb's to be deployed. Then exit the modeler and examine the Preview models left on the server (both vdb's and datasources). 14 Preview VDBs seem to be consistently undeleted.

    Description

      When exiting JBDS after using the Teiid Designer perspective to conduct previews of models, those models are not all removed from the server after JBDS is closing. This is with a normal close. An informational window comes up saying "Teiid Server cleanup (30 jobs running)", and 30 Previews is indeed the right number to clean up. However, the clean-up task exits without removing all of them. See attached screenshot. Also, the Preview datasources never seem to be cleaned up, and I would expect that they should be (see the second screenshot).

      I am flagging this as major since there could be a resultant massive accumulation of Previews in the server, especially since many users won't know to look for them to delete them by hand.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. TEIIDDES-714 Designer should clean up preview vdbs every time Teiid Server connection is made.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              dflorian@redhat.com Daniel Florian (Inactive)
              cmosher-se-jboss Charles Mosher (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: