[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2223:
---------------------------------------
For 7.7.1 a vdb can be reported as inactive after it is deployed if it is pending a
metadata load, so that is an acceptable initial result.
Any other queries from now on to THE_VDB status (e.g. through
adminshell) outputs INACTIVE
That definitely is problematic. It's not expected that AS would be caching the mapped
objects though. Based upon our arquillian tests we don't see this behavior in 8.0+
since there's quite a few tests that rely on status changes.
Compiled Groovy cannot deploy a dynamic VDB, using AdminShell
methods, that is recognized as ACTIVE by the Groovy script
------------------------------------------------------------------------------------------------------------------------
Key: TEIID-2223
URL:
https://issues.jboss.org/browse/TEIID-2223
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 7.7.2
Reporter: Paul Nittel
Assignee: Steven Hawkins
Priority: Optional
Fix For: Open To Community
Attachments: CrummyWeather.groovy, ShortWeatherNoTest.groovy, weather-vdb.xml
This is a weird case. If I deploy a dynamic VDB from a compiled Groovy script, it is not
seen as ACTIVE by the script. The server log shows it is active.
If I use a non-compiled Groovy script, it all works fine.
To add to the intrigue, if the compiled script periodically polls to see if the VDB is
active, and I go to the Virtual Databases display in RHQ, the script magically sees the
VDB as ACTIVE.
I'm attaching the materials used in this test.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira