Bug 780111 (SOA-2482) - java.net.URISyntaxException starting jboss-soa-p-5 (i.e. with Teiid) installed on LINUX under folder name containing spaces
Summary: java.net.URISyntaxException starting jboss-soa-p-5 (i.e. with Teiid) installe...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2482
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA, EDS
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER9
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-26 17:30 UTC by Barry LaFond
Modified: 2011-02-08 17:15 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
server_error.log (8.02 KB, text/x-log)
2010-10-26 17:31 UTC, Barry LaFond
no flags Details
server.log.SOA2482.Reopen (991.15 KB, application/octet-stream)
2011-02-08 15:43 UTC, Len DiMaggio
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 780455 0 high CLOSED Failure running SOA-P 5.1 server with space character in directory tree string 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-2482 0 None None None Never

Internal Links: 780455

Description Barry LaFond 2010-10-26 17:30:59 UTC
Steps to Reproduce: See Description
project_key: SOA

Installed jboss-soa-p-5 in a folder under a "Test Designer Folder" folder. Installed EDS on top of it and ran the "ant" build to configure SOA for Teiid and Modeshape.

Installed JBDS and created/started an instance of JBoss AS server connection

On start-up got errrors:

DEPLOYMENTS MISSING DEPENDENCIES:
  Deployment "VDBDeployer" is missing the following dependencies:
    Dependency "SystemVDBDeployer" (should be in state "Create", but is actually in state "**ERROR**")

DEPLOYMENTS IN ERROR:
  Deployment "SystemVDBDeployer" is in error due to the following reason(s): java.net.URISyntaxException: Illegal character in path at index 23: file:/home/blafond/Test Designer Folder/ServerInstalls/jboss-soa-p-5/jboss-as/server/default/deployers/teiid.deployer/teiid-metadata-7.1.1.jar/System.vdb, **ERROR**

I changed the containing folder and removed the spaces, restarted everything and did NOT receiver the error.

See attached file for Stack Trace.

Comment 1 Barry LaFond 2010-10-26 17:31:22 UTC
Stack Trace

Comment 2 Barry LaFond 2010-10-26 17:31:22 UTC
Attachment: Added: server_error.log


Comment 3 Anne-Louise Tangring 2010-10-28 16:12:42 UTC
Candidate for SOA 5.1.0

Comment 4 Van Halbert 2010-10-28 18:58:13 UTC
Link: Added: This issue depends TEIID-1334


Comment 5 Van Halbert 2010-10-29 14:27:28 UTC
Teiid applied a fix to spaces issue and should be in ER4 release.

Comment 6 Len DiMaggio 2011-02-08 15:40:30 UTC
This is still an issue in ER9 - see attached server.log

2011-02-08 10:34:59,435 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/juddiv3]] (main) Servlet /juddiv3 threw load() exception
java.net.URISyntaxException: Illegal character in path at index 33: vfszip:/jboss/local/JIRA2482/Test Designer Folder/jboss-soa-p-5/jboss-as/server/production/deploy/juddiv3.war/WEB-INF/lib/XMLCatalog.jar/META-INF/xml.xsd


Comment 7 Len DiMaggio 2011-02-08 15:43:50 UTC
Attachment: Added: server.log.SOA2482.Reopen


Comment 8 Len DiMaggio 2011-02-08 15:54:07 UTC
Comment on the JIRA being re-opened - now, it looks like a juddi issue too.

Comment 9 Kevin Conner 2011-02-08 16:00:47 UTC
jUDDIv3 comes from ESB and not juddi.  I do not think this issue should be reopened but, rather, a new one created to cover a different issue (albeit similar).

Comment 10 Kevin Conner 2011-02-08 16:03:00 UTC
This is an issue with the CXF integration, please create a new issue to cover the bug.

Comment 11 Len DiMaggio 2011-02-08 17:08:43 UTC
Link: Added: This issue related SOA-2884


Comment 12 Len DiMaggio 2011-02-08 17:15:32 UTC
Verified fixed in ER9.


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