[teiid-issues] [JBoss JIRA] (TEIID-2223) Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725389#comment-12725389 ] 

Ramesh Reddy commented on TEIID-2223:
-------------------------------------

Even with 7.x the metadata objects are not cached. Is it possible you are using the same vdb instance that came back to check the status? You have to make another call to getVDBs to get a updated state.
                
> 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