[JBoss JIRA] (TEIID-2223) Compiled Groovy cannot deploy a dynamic VDB, using AdminShell methods, that is recognized as ACTIVE by the Groovy script
12:29 p.m.
Paul Nittel created TEIID-2223:
----------------------------------
Summary: 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
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
12:31 p.m.
[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
Paul Nittel updated TEIID-2223:
-------------------------------
Attachment: weather-vdb.xml
ShortWeatherNoTest.groovy
CrummyWeather.groovy
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
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
12:33 p.m.
[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
Paul Nittel commented on TEIID-2223:
------------------------------------
CrummyWeather.groovy is the non-compiled script. ShortWeatherNoTest needs to be compiled
with groovyc. (I used Groovy 1.8.4.)
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
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
1:13 p.m.
[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2223:
---------------------------------------
Can you repeat your test with latest? Or have you created a bz/gss case for this to be
prioritized for the 7.7 branch?
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
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
1:40 p.m.
[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2223:
----------------------------------
Fix Version/s: Open To Community
Priority: Optional (was: Major)
From Paul - I don't know if it's necessary to do much more
with this. I entered the Jira more for documentation than anything else. Deploying dynamic
VDB from compiled Groovy seems a low probability use case.
From me - moving to open to community to retest in 8.1 or later. Will
resolve as deferred if not picked up in a release or two.
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
10:32 a.m.
[
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.
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
10:56 a.m.
[
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
11:09 a.m.
[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
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
12:30 p.m.
[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
Paul Nittel commented on TEIID-2223:
------------------------------------
I tried this a couple of ways. First I just added a 10 second delay before the getVDBs
call. That consistently showed the VDB as ACTIVE, as Filip predicted. The other way I
immediately did a getVDBs, then waited 10 seconds and repeated the getVDBs (did that 5
times). That consistently failed to show the VDB as ACTIVE. I used adminshell.sh to run
the script. Not compiled.
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
1:51 a.m.
[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
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
3:19 p.m.
[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2223:
---------------------------------------
I would recommend creating a BZ entry then and assigning this to John Lee. Presumably
this will also occur if you take groovy out of picture and a simple debug session will
show if the server is being consulted or where the values are coming from.
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
12:09 p.m.
[
https://issues.jboss.org/browse/TEIID-2223?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2223:
----------------------------------
Assignee: Johnathon Lee (was: Steven Hawkins)
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: Johnathon Lee
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
4248
days inactive
4273
days old
11 comments
4 participants
participants (4)
-
Filip Nguyen (JIRA) -
Paul Nittel (JIRA)
-
Ramesh Reddy (JIRA)
-
Steven Hawkins (JIRA)