[
https://issues.jboss.org/browse/JBDS-1514?page=com.atlassian.jira.plugin....
]
Dan Florian commented on JBDS-1514:
-----------------------------------
In Teiid Designer's "Teiid" View, make sure Preview VDBs and Preview Data
Sources are being displayed. You can use the view menu to designate the items you want to
display. Now select one or more Preview Data Sources, or one or more Preview VDBs and use
the context menu to delete them. Still a manual process but much easier than going to the
server. We were trying to keep the preview artifacts transparent to the user but because
of the cleanup issues maybe we should make them more obvious (i.e., make these artifacts
show by default in the view). Fixing TEIIDDES-714 should help with the cleanup.
JBDS does not completely clean up Teiid PREVIEW VDBs and DataSources
--------------------------------------------------------------------
Key: JBDS-1514
URL:
https://issues.jboss.org/browse/JBDS-1514
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: teiid
Affects Versions: 4.0.0.Beta2
Environment: RHEL 6 (CSB) running on a T510 laptop, 3.7Gb of memory
Reporter: Chuck Mosher
Assignee: Dan Florian
Fix For: 4.0.0.CR2
Attachments: FinancialsDemo.zip, LeftoverPreviewDatasources.png,
LeftoverPreviewVDBs.png
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.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira