Bug 780330 (SOA-2738) - Admin console shows no information about sessions
Summary: Admin console shows no information about sessions
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2738
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0.CR1
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-04 17:35 UTC by Boris Belovic
Modified: 2011-02-10 15:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-10 15:32:50 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2738 0 None None None Never

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.


Note You need to log in before you can comment on or make changes to this bug.