Bug 780330 (SOA-2738)

Summary: Admin console shows no information about sessions
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Boris Belovic <bbelovic>
Component: EDSAssignee: Van Halbert <vhalbert>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.1.0.ER5CC: bbelovic
Target Milestone: ---   
Target Release: 5.1.0.CR1   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2738
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-10 15:32:50 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 Boris Belovic 2011-01-04 17:35:37 UTC
project_key: SOA

Admin console shows no session information. The results table is empty even if the session is active (= connections to VDB weren't closed).

Comment 1 Van Halbert 2011-01-04 17:35:38 UTC
Link: Added: This issue Cloned from TEIID-1416


Comment 2 Van Halbert 2011-01-04 17:36:09 UTC
Security: Added: Public


Comment 3 Anne-Louise Tangring 2011-01-04 19:37:03 UTC
Approved as blocker for SOA 5.1.0

Comment 5 Boris Belovic 2011-02-09 12:10:25 UTC
I have a question here. I am using two scenarios for verifying this issue.

First scenario:

1. connect to VDB, execute statements
2. Thread.sleep(45000) - enough time to check admin-console
3. look into admin console, I see there information about session
4. call close() on Connection instance - invalidating session, admin console shows no sessions

Second scenario:
1. connect to VDB, execute statements
2. don't call close() on Connection at all. Here I expect that session is not invalidated immediately, there is some timeout
3. look into admin-console, expect to see information about session there, but admin-console shows no sessions

Why is admin console empty in second scenario? I'd expect that it will contain session information since the session wasn't invalidated -> close() method wasn't call.