Bug 780032 (SOA-2394)

Summary: EDS adminshell - getSessions() - each session object returned always shows a VDB of null
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Len DiMaggio <ldimaggi>
Component: EDSAssignee: Van Halbert <vhalbert>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0.ER2   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2394
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-14 18:29:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Len DiMaggio 2010-10-08 02:57:45 UTC 
project_key: SOA

With these VDBs deployed

[Interoperability.1[TextFileData[text-connector/file/java:TextFileDS]], weather.1[Weather[Weather/MessageWeather/java:WeatherDS]], ModeShape.1[ModeShapeFunctions[], ModeShape[ModeShape/modeshape/ModeShapeDS]]]

And these in use: Interoperability, weather

Every session created shows a VDB of null:

[session: sessionid=pC2AQPpaMZr3; userName=admin@jmx-console; vdbName=null; vdbVersion=0; createdTime=Thu Oct 07 22:52:13 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=jmx-console; lastPingTime=Thu Oct 07 22:52:53 EDT 2010, session: sessionid=1oGdlWx+B3Te; userName=admin@jmx-console; vdbName=null; vdbVersion=0; createdTime=Thu Oct 07 21:38:34 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=jmx-console; lastPingTime=Thu Oct 07 22:51:30 EDT 2010, session: sessionid=TA2+3kyQ1Wff; userName=admin@jmx-console; vdbName=null; vdbVersion=0; createdTime=Thu Oct 07 21:38:04 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=jmx-console; lastPingTime=Thu Oct 07 22:51:04 EDT 2010, session: sessionid=dEl7em6K6o0u; userName=admin@jmx-console; vdbName=null; vdbVersion=0; createdTime=Thu Oct 07 21:17:04 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=jmx-console; lastPingTime=Thu Oct 07 22:51:04 EDT 2010, session: sessionid=SDyHIyvSgVUg; userName=admin@teiid-security; vdbName=Interoperability; vdbVersion=1; createdTime=Thu Oct 07 22:52:48 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=teiid-security; lastPingTime=Thu Oct 07 22:52:48 EDT 2010, session: sessionid=Sc8tMciQJfbP; userName=admin@teiid-security; vdbName=Interoperability; vdbVersion=2; createdTime=Thu Oct 07 22:52:50 EDT 2010; applicationName=null; clientHostName=localhost.localdomain; IPAddress=127.0.0.1; securityDomain=teiid-security; lastPingTime=Thu Oct 07 22:52:50 EDT 2010]
Comment 1 Van Halbert 2010-10-12 00:38:17 UTC 
Link: Added: This issue depends TEIID-1300
Comment 2 Van Halbert 2010-10-12 14:12:28 UTC 
Admin connections do not require VDB to connect; thus no VDB associated with "admin" connections.    Need to verify if you see other sessions that were jdbc connections that have vdbName=null.
Comment 3 Van Halbert 2010-10-14 18:29:28 UTC 
Per Teiid status,   Admin connections are not made to a specific vdb context and will report the vdb as null.