[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

[ https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin... ] Filip Nguyen commented on TEIID-2223: ------------------------------------- I believe this bug is not actually related to compiled Groovy classes. So it may be more important than we think. I have found out that even the following script recognizes vdb as INACTIVE (compiled to Java or not): {code:title=Script.groovy|borderStyle=solid} connectAsAdmin( "mms://" + SERVER + ":31443", "admin", "admin", "WxConn" ) deployVDB(THE_VDB) def av = getVDBs() for ( v in av ) { println( " " + v.getName() + "." + v.getVersion() + " status: " + v.getStatus() ) } {code} The important thing is not to have any delay between lines deployVDB and getVDBs. This outputs THE_VDB as INACTIVE even though the VDB actually gets deployed into ACTIVE state. Any other queries from now on to THE_VDB status (e.g. through adminshell) outputs INACTIVE. If the above script is modified to have delay (Thread.sleep) between deployVDB and getVDBs the THE_VDB is already seen as ACTIVE. It seems that the status is somehow cached in JBoss AS managed properties or something. -- 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