[gatein-issues] [JBoss JIRA] Commented: (GTNPORTAL-1201) GateIn fails to start up when there are spaces in JBOSS_HOME path

[Marko Strukelj (JIRA)]

    [ https://jira.jboss.org/jira/browse/GTNPORTAL-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12530333#action_12530333 ] 

Marko Strukelj commented on GTNPORTAL-1201:
-------------------------------------------

At first this seemed like a VFS bug - as the symptom is that the resource is being looked up, but isn't found (gatein.ear/lib/exo.kernel.component.common-2.2.1-CR1.jar/conf/configuration.properties).

It's actually an exo-kernel bug - see related issue.


> GateIn fails to start up when there are spaces in JBOSS_HOME path
> -----------------------------------------------------------------
>
>                 Key: GTNPORTAL-1201
>                 URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1201
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0-GA
>         Environment: Windows, Linux
>            Reporter: Marko Strukelj
>
> Exception during start up:
> 01:12:02,137 ERROR [ContainerUtil] Cannot load property file null
> java.io.IOException: Child not found gatein.ear/lib/exo.kernel.component.common-2.2.1-CR1.jar/conf/configuration.properties/ for FileHandler at 8344029[path= context=file:/C:/development/test/jboss%20epp%205.0/jboss-as/server/default/deploy/ real=file:/C:/development/test/jboss%20ep
> p%205.0/jboss-as/server/default/deploy/], 
> ...
> ...
>         at org.jboss.virtual.plugins.registry.DefaultVFSRegistry.findHandler(DefaultVFSRegistry.java:128)
>         at org.jboss.virtual.plugins.registry.DefaultVFSRegistry.getFile(DefaultVFSRegistry.java:107)
>         at org.jboss.virtual.plugins.registry.DefaultVFSRegistry.getFile(DefaultVFSRegistry.java:140)
>         at org.jboss.virtual.protocol.AbstractVFSHandler.openConnection(AbstractVFSHandler.java:71)
>         at java.net.URL.openConnection(URL.java:945)
>         at java.net.URL.openStream(URL.java:1010)
>         at org.exoplatform.container.util.ContainerUtil.loadProperties(ContainerUtil.java:230)
>         at org.exoplatform.container.util.ContainerUtil.loadProperties(ContainerUtil.java:211)
>         at org.exoplatform.container.PropertyConfigurator.<init>(PropertyConfigurator.java:105)
> The symptom is the same as if exo.conf.dir.name system property has not been set through JBOSS_HOME/bin/run.conf (run.conf.bat) or via JBOSS_HOME/server/default/deploy/properties-service.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira