Bug 1004770 - NoClassDefFoundError when trying to run adminshell
Summary: NoClassDefFoundError when trying to run adminshell
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER2
: 6.0
Assignee: Julian Coleman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-05 13:00 UTC by Van Halbert
Modified: 2014-07-09 05:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-06 15:37:18 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-2649 0 Blocker Closed NoClassDefFoundError when trying to run adminshell 2013-12-05 13:55:45 UTC

Comment 2 JBoss JIRA Server 2013-09-05 13:03:36 UTC 
Ramesh Reddy <rareddy> made a comment on jira TEIID-2649

what is the operation you were running for this to occur?
Comment 3 JBoss JIRA Server 2013-09-05 13:35:37 UTC 
Van Halbert <vhalbert> made a comment on jira TEIID-2649

just run:  ./adminshell.sh

and you get the exception.

Also, the file permission on the .sh scripts need to fixed in the assembly to make them executable
Comment 4 JBoss JIRA Server 2013-09-05 13:56:09 UTC 
Steven Hawkins <shawkins> made a comment on jira TEIID-2649

The assembly explicitly sets the .sh permissions and they are executable on my system.  What platform are you using?

I also don't get that exception.  Are you running with a vm that does not support the wildcard classpath?
Comment 7 JBoss JIRA Server 2013-09-05 15:13:42 UTC 
Van Halbert <vhalbert> updated the status of jira TEIID-2649 to Resolved
Comment 8 JBoss JIRA Server 2013-09-05 15:13:42 UTC 
Van Halbert <vhalbert> made a comment on jira TEIID-2649

This is not a teiid project issue.
Comment 16 JBoss JIRA Server 2013-12-05 13:55:49 UTC 
Steven Hawkins <shawkins> updated the status of jira TEIID-2649 to Closed
Note You need to log in before you can comment on or make changes to this bug.