[
https://issues.jboss.org/browse/TEIID-3022?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-3022:
----------------------------------
Fix Version/s: 8.8
Will address in 8.8 with proactive termination of sessions. Will later look at adding
back some form of lazy undeploy such that it doesn't complete until all sessions have
been terminated.
refine removed vdb handling
---------------------------
Key: TEIID-3022
URL:
https://issues.jboss.org/browse/TEIID-3022
Project: Teiid
Issue Type: Quality Risk
Security Level: Public(Everyone can see)
Components: Server
Affects Versions: 8.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.8
With TEIID-2105 the server will reject requests against a non-active vdb, which includes
a removed vdb. This is against the original intent of allowing for lazy cleanup. We
should either have a vdb remove proactively terminate all sessions and fully cleanup or we
should reinstate the lazy logic. At this point it probably makes the most sense to go the
first route as there is other logic (materialization management for one) now checking the
vdb state and assuming that removal will invalidate the vdb.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)