Bug 779276 (SOA-1665)

Summary: jUDDI fails to start if installation directory contains <space> character
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Julian Coleman <jcoleman>
Component: jUDDI - within SOAAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER4   
Target Milestone: ---   
Target Release: 5.0.0 GA, 5.0.0 ER6   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1665
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Windows and unix
Last Closed: 2010-01-28 11:00:14 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:
Attachments:
Description Flags
server.log.gz none

Description Julian Coleman 2009-12-03 12:48:46 UTC
Date of First Response: 2009-12-07 05:13:56
project_key: SOA

If the SOA server is installed in a directory name containing a <space> character, jUDDI will fail to start:

  INFO  [org.apache.juddi.config.Install] (main) Loading the content of file: vfsfile:/tmp/SOA%20Platform/jboss-soa-p.5.0.0/jboss-as/server/default/deploy/jbossesb-registry.sar/juddi_custom_install_data/root_Publisher.xml
  ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=jboss.esb:service=JuddiRMI state=Create mode=Manual requiredState=Installed
org.apache.commons.configuration.ConfigurationException: java.lang.IllegalArgumentException: URI is not absolute
	at org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:111)
	at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:88)
	at org.apache.juddi.config.AppConfig.<init>(AppConfig.java:62)

Comment 1 Kevin Conner 2009-12-07 10:13:56 UTC
Tried reproducing this over the weekend but was not able to.

Can you please attach a log file showing the error?

Thanks

Comment 2 Julian Coleman 2009-12-07 10:52:53 UTC
Complete log file from ER4 embedded default server start up.

Comment 3 Julian Coleman 2009-12-07 10:52:53 UTC
Attachment: Added: server.log.gz


Comment 4 Kevin Conner 2009-12-07 14:44:07 UTC
Thanks J, that is very useful.

It is the first time configuration of the database which fails, but I wasn't starting from a clean deployment.

It should be relatively straight forward to address.

Comment 5 Kevin Conner 2009-12-07 14:45:13 UTC
Link: Added: This issue depends JBESB-3042


Comment 6 Kevin Conner 2009-12-08 19:36:22 UTC
Updated in the project, will be in the next merge.

Comment 7 Martin Vecera 2010-01-28 11:00:14 UTC
Verified in ER7.