[JBoss JIRA] Created: (GTNPORTAL-1201) GateIn fails to start up when there are spaces in JBOSS_HOME path
by Marko Strukelj (JIRA)
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@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
12 years, 4 months
[JBoss JIRA] Created: (GTNPORTAL-1183) Running tests on windows produces stacktraces and fails to create test log files
by Marko Strukelj (JIRA)
Running tests on windows produces stacktraces and fails to create test log files
--------------------------------------------------------------------------------
Key: GTNPORTAL-1183
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1183
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0-GA
Environment: Windows
Reporter: Marko Strukelj
Priority: Minor
Stacktrace keeps occuring when running tests on windows.
Can't load log handler "java.util.logging.FileHandler"
java.io.IOException: Couldn't get lock for C:javagateincomponenttestcore/target/gateintest-%u.log
java.io.IOException: Couldn't get lock for C:javagateincomponenttestcore/target/gateintest-%u.log
at java.util.logging.FileHandler.openFiles(FileHandler.java:372)
at java.util.logging.FileHandler.<init>(FileHandler.java:208)
It doesn't cause tests to fail, but there is no log file, and it gives an impression that something is terribly wrong.
--
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
12 years, 4 months
[JBoss JIRA] Created: (GTNPORTAL-1141) Problem after logout from a private navigation in a portal
by Esslem GHODBANE (JIRA)
Problem after logout from a private navigation in a portal
----------------------------------------------------------
Key: GTNPORTAL-1141
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-1141
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.0.0-GA
Reporter: Esslem GHODBANE
I found a problem which occurred after logout from a private navigation in a portal.
To reproduce this issue :
* Login to classic portal
*- Here we are under */portal/public/classic/*
* Edit Portal's Properties
*- Make classic portal private for navigation
*- Add permission to *:/platform/users
* Logout from this portal
*- You'll get a warning saying that that page|portal is not found
*- This is due to that there is a filter that redirect all connection request to a public mode however navigation mode under this portal was changed to private
* If you put directly a private URL, like this */portal/private/classic/* you'll got the _login.jsp_ page.
{quote} *So, is it a real bug, or I must have more configuration ?* {quote}
--
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
12 years, 4 months