Bug 780818 (SOA-3264) - Request better exception message when connecting to an invalid VDB name
Summary: Request better exception message when connecting to an invalid VDB name
Keywords:
Status: CLOSED WORKSFORME
Alias: SOA-3264
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-15 14:26 UTC by dsteigne
Modified: 2011-08-18 14:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-18 14:57:57 UTC
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


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

Description dsteigne 2011-08-15 14:26:00 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007rETd
project_key: SOA

When accessing a VDB with the incorrect name (in my case, a typo), the exception suggests that it's either down to an invalid logon and/or access problems. This is mis-leading and time-consuming to track down: 

09:52:35,991 WARN [SECURITY] Processing exception 'VDB "XXX" version "latest" does not exist.' for session null. Exception type org.teiid.client.security.LogonException thrown from org.teiid.services.SessionServiceImpl.getActiveVDB(SessionServiceImpl.java:228). Enable more detailed logging to see the entire stacktrace.
Comment 1 Van Halbert 2011-08-15 14:41:02 UTC 
Link: Added: This issue Cloned to SOA-3266
Comment 2 Van Halbert 2011-08-18 14:57:57 UTC 
The client exception I get (from squirrel) is:

Remote org.teiid.client.security.LogonException: VDB "bqt" version "latest" does not exist.

This is using 7.4.

The project indicates there is nothing to be fixed and we don't want to list what the available vdb's are for security purposes.
Note You need to log in before you can comment on or make changes to this bug.