[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
Filip Nguyen (JIRA)
jira-events at lists.jboss.org
Thu Oct 11 02:51:02 EDT 2012
[ https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725494#comment-12725494 ]
Filip Nguyen commented on TEIID-2223:
-------------------------------------
> Is it possible you are using the same vdb instance that came back to check the status?
I think I use different instance. The sequence "deployVDB(THE_VDB);getVDBs()" is done in one shell. Afterwards I tried to get the THE_VDB status from newly started adminshell.
> 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
More information about the teiid-issues
mailing list