[JBoss JIRA] Updated: (GTNPORTAL-2080) Remove embbeded logger configuration
by Julien Viet (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2080?page=com.atlassian.jira.pl... ]
Julien Viet updated GTNPORTAL-2080:
-----------------------------------
Summary: Remove embbeded logger configuration (was: Remove embbeded logger configuration from exojcr)
> Remove embbeded logger configuration
> ------------------------------------
>
> Key: GTNPORTAL-2080
> URL: https://issues.jboss.org/browse/GTNPORTAL-2080
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Henri Gomez
> Fix For: 3.2.0-M02
>
>
> Activating JRMP configuration in JBoss EPP 5.1.x (or EPP based products) produce a large quantity of JMX/RMI logs in stdout/stderr :
> {code:title=bin/run.conf}
> JMX_REMOTE_IP=1.2.3.4
> JMX_REMOTE_PORT=1234
> JRMP_OPTS="-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl -Djboss.platform.mbeanserver -Djava.rmi.server.hostname=$JMX_REMOTE_IP -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=$JMX_REMOTE_PORT -DclientConnectAddress=$JMX_REMOTE_IP -Dcom.sun.management.jmxremote.authenticate=false"
> JAVA_OPTS="$JAVA_OPTS $JRMP_OPTS"
> {code}
> As soon as a JRMP agent is connected to instance (ie: VisualVM or JMXTrans), you'll see stdout/stderr log filled with messages like :
> {code}
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,789 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,791 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,791 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,794 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,794 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,796 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,796 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,818 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,818 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,900 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,900 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,933 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,933 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,935 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,935 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,950 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,950 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,969 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,969 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(6)-192.168.0.165: (port 52851) connection closed
> 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) connection closed
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(2)-192.168.0.165: (port 52851) connection closed
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(1)-192.168.0.165: (port 8004) connection closed
> 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPConnection close
> FIN: RMI TCP Connection(2)-192.168.0.165: close connection
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(5)-192.168.0.165: (port 52851) connection closed
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPConnection close
> FIN: RMI TCP Connection(6)-192.168.0.165: close connection
> {code}
> Digging into Gatein ear, I notice the following in log-configuration.xml :
> {code:title=server/default/deploy/gatein.ear/02portal.war/WEB-INF/conf/common/logs-configuration.xml}
> <!-- end Commons Simple -->
> <!-- JDK -->
> <value-param>
> <name>logger</name>
> <value>org.exoplatform.services.log.impl.BufferedJdk14Logger</value>
> </value-param>
> <value-param>
> <name>configurator</name>
> <value>org.exoplatform.services.log.impl.Jdk14Configurator</value>
> </value-param>
> <properties-param>
> <name>properties</name>
> <description>jdk1.4 Logger properties</description>
> <property name="handlers" value="java.util.logging.ConsoleHandler"/>
> <property name=".level" value="FINE"/>
> <property name="java.util.logging.ConsoleHandler.level" value="FINE"/>
> </properties-param>
> <!-- end JDK -->
> <!-- Log4J -->
> <!--
> <value-param>
> <name>logger</name>
> <value>org.exoplatform.services.log.impl.BufferedLog4JLogger</value>
> </value-param>
> <value-param>
> <name>configurator</name>
> <value>org.exoplatform.services.log.impl.Log4JConfigurator</value>
> </value-param>
> <properties-param>
> <name>properties</name>
> <description>Log4J properties</description>
> <property name="log4j.rootLogger" value="DEBUG, stdout, file"/>
> <property name="log4j.appender.stdout" value="org.apache.log4j.ConsoleAppender"/>
> <property name="log4j.appender.stdout.layout" value="org.apache.log4j.PatternLayout"/>
> <property name="log4j.appender.stdout.layout.ConversionPattern" value="%d {dd.MM.yyyy HH:mm:ss} %c {1}: %m (%F, line %L) %n"/>
> <property name="log4j.appender.file" value="org.apache.log4j.FileAppender"/>
> <property name="log4j.appender.file.File" value="jcr.log"/>
> <property name="log4j.appender.file.layout" value="org.apache.log4j.PatternLayout"/>
> <property name="log4j.appender.file.layout.ConversionPattern" value="%d{dd.MM.yyyy HH:mm:ss} %m (%F, line %L) %n"/>
> </properties-param>
> -->
> <!-- end Log4J-->
> {code}
> JDK logger level is set to FINE, overriding default log configuration (OPS/ADM tasks)
> It's what activate so many messages in logs.
> I recommand to restore this configuration to INFO or better remove this logger configuration to let it done by OPS/ADM teams, these will use App Server engine logging capability as they use to (ie: log4j.xml in JBoss AS)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Moved: (GTNPORTAL-2080) Remove embbeded logger configuration from exojcr
by Nicolas Filotto (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2080?page=com.atlassian.jira.pl... ]
Nicolas Filotto moved EXOJCR-1517 to GTNPORTAL-2080:
----------------------------------------------------
Project: GateIn Portal (was: eXo-JCR)
Key: GTNPORTAL-2080 (was: EXOJCR-1517)
Assignee: (was: Anatoliy Bazko)
> Remove embbeded logger configuration from exojcr
> ------------------------------------------------
>
> Key: GTNPORTAL-2080
> URL: https://issues.jboss.org/browse/GTNPORTAL-2080
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Henri Gomez
>
> Activating JRMP configuration in JBoss EPP 5.1.x (or EPP based products) produce a large quantity of JMX/RMI logs in stdout/stderr :
> {code:title=bin/run.conf}
> JMX_REMOTE_IP=1.2.3.4
> JMX_REMOTE_PORT=1234
> JRMP_OPTS="-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl -Djboss.platform.mbeanserver -Djava.rmi.server.hostname=$JMX_REMOTE_IP -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.port=$JMX_REMOTE_PORT -DclientConnectAddress=$JMX_REMOTE_IP -Dcom.sun.management.jmxremote.authenticate=false"
> JAVA_OPTS="$JAVA_OPTS $JRMP_OPTS"
> {code}
> As soon as a JRMP agent is connected to instance (ie: VisualVM or JMXTrans), you'll see stdout/stderr log filled with messages like :
> {code}
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,789 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,791 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,791 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,794 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,794 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,796 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,796 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,818 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,818 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,900 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,900 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,933 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,933 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,935 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,935 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,950 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,950 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:14,969 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) op = 80
> 09:55:14,969 ERROR [STDERR] 6 sept. 2011 09:55:14 sun.rmi.server.LoaderHandler loadClass
> FIN: RMI TCP Connection(4)-192.168.0.165: name = "javax.management.ObjectName", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@7a9664a1
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(6)-192.168.0.165: (port 52851) connection closed
> 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(4)-192.168.0.165: (port 52851) connection closed
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(2)-192.168.0.165: (port 52851) connection closed
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(1)-192.168.0.165: (port 8004) connection closed
> 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPConnection close
> FIN: RMI TCP Connection(2)-192.168.0.165: close connection
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPTransport handleMessages
> FIN: RMI TCP Connection(5)-192.168.0.165: (port 52851) connection closed
> 09:55:15,407 ERROR [STDERR] 6 sept. 2011 09:55:15 sun.rmi.transport.tcp.TCPConnection close
> FIN: RMI TCP Connection(6)-192.168.0.165: close connection
> {code}
> Digging into Gatein ear, I notice the following in log-configuration.xml :
> {code:title=server/default/deploy/gatein.ear/02portal.war/WEB-INF/conf/common/logs-configuration.xml}
> <!-- end Commons Simple -->
> <!-- JDK -->
> <value-param>
> <name>logger</name>
> <value>org.exoplatform.services.log.impl.BufferedJdk14Logger</value>
> </value-param>
> <value-param>
> <name>configurator</name>
> <value>org.exoplatform.services.log.impl.Jdk14Configurator</value>
> </value-param>
> <properties-param>
> <name>properties</name>
> <description>jdk1.4 Logger properties</description>
> <property name="handlers" value="java.util.logging.ConsoleHandler"/>
> <property name=".level" value="FINE"/>
> <property name="java.util.logging.ConsoleHandler.level" value="FINE"/>
> </properties-param>
> <!-- end JDK -->
> <!-- Log4J -->
> <!--
> <value-param>
> <name>logger</name>
> <value>org.exoplatform.services.log.impl.BufferedLog4JLogger</value>
> </value-param>
> <value-param>
> <name>configurator</name>
> <value>org.exoplatform.services.log.impl.Log4JConfigurator</value>
> </value-param>
> <properties-param>
> <name>properties</name>
> <description>Log4J properties</description>
> <property name="log4j.rootLogger" value="DEBUG, stdout, file"/>
> <property name="log4j.appender.stdout" value="org.apache.log4j.ConsoleAppender"/>
> <property name="log4j.appender.stdout.layout" value="org.apache.log4j.PatternLayout"/>
> <property name="log4j.appender.stdout.layout.ConversionPattern" value="%d {dd.MM.yyyy HH:mm:ss} %c {1}: %m (%F, line %L) %n"/>
> <property name="log4j.appender.file" value="org.apache.log4j.FileAppender"/>
> <property name="log4j.appender.file.File" value="jcr.log"/>
> <property name="log4j.appender.file.layout" value="org.apache.log4j.PatternLayout"/>
> <property name="log4j.appender.file.layout.ConversionPattern" value="%d{dd.MM.yyyy HH:mm:ss} %m (%F, line %L) %n"/>
> </properties-param>
> -->
> <!-- end Log4J-->
> {code}
> JDK logger level is set to FINE, overriding default log configuration (OPS/ADM tasks)
> It's what activate so many messages in logs.
> I recommand to restore this configuration to INFO or better remove this logger configuration to let it done by OPS/ADM teams, these will use App Server engine logging capability as they use to (ie: log4j.xml in JBoss AS)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (GTNPORTAL-2050) NPE at startup
by Chris Laprun (JIRA)
NPE at startup
--------------
Key: GTNPORTAL-2050
URL: https://issues.jboss.org/browse/GTNPORTAL-2050
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: PC integration
Affects Versions: 3.2.0-M01
Reporter: Chris Laprun
Assignee: Matt Wringe
Fix For: 3.2.0-M02
java.lang.NullPointerException
14:17:19,631 ERROR [STDERR] at org.gatein.pc.portlet.impl.info.ContainerInfoBuilder.fixMetaData(ContainerInfoBuilder.java:281)
14:17:19,631 ERROR [STDERR] at org.gatein.pc.portlet.impl.info.ContainerInfoBuilder.build(ContainerInfoBuilder.java:610)
14:17:19,631 ERROR [STDERR] at org.gatein.pc.portlet.impl.info.ContainerInfoBuilder.build(ContainerInfoBuilder.java:375)
14:17:19,631 ERROR [STDERR] at org.gatein.pc.portlet.impl.deployment.PortletApplicationDeployment.install(PortletApplicationDeployment.java:91)
14:17:19,631 ERROR [STDERR] at org.gatein.pc.portlet.impl.deployment.PortletApplicationDeployer.add(PortletApplicationDeployer.java:187)
14:17:19,631 ERROR [STDERR] at org.gatein.pc.portlet.impl.deployment.PortletApplicationDeployer.onEvent(PortletApplicationDeployer.java:156)
14:17:19,631 ERROR [STDERR] at org.gatein.wci.impl.DefaultServletContainer.safeFireEvent(DefaultServletContainer.java:200)
14:17:19,631 ERROR [STDERR] at org.gatein.wci.impl.DefaultServletContainer.addWebAppListener(DefaultServletContainer.java:166)
14:17:19,631 ERROR [STDERR] at org.gatein.pc.portlet.impl.deployment.PortletApplicationDeployer.start(PortletApplicationDeployer.java:229)
14:17:19,631 ERROR [STDERR] at org.exoplatform.portal.pc.ExoKernelIntegration.start(ExoKernelIntegration.java:154)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (GTNPORTAL-2076) Portal navigation doesn't show some nodes in the first time access to portal
by Vu Viet Phuong (JIRA)
Portal navigation doesn't show some nodes in the first time access to portal
----------------------------------------------------------------------------
Key: GTNPORTAL-2076
URL: https://issues.jboss.org/browse/GTNPORTAL-2076
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0-M01
Reporter: Vu Viet Phuong
Assignee: Vu Viet Phuong
Priority: Minor
- Login and create some node : below "Home" node. For example we have :
/home/test1/test2/test3 (with access permission: everyone)
- Now close firefox browser or clear browser's cache and cookie
- Open browser again and access to "home" node
--> The portal navigation menu only shows /home/test1
--> Expected: show all nodes : /home/test1/test2/test3
Only after refresh browser, portal navigation can show all nodes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (GTNPORTAL-2034) Navigation portlet doesn't render correctly in non-default layout
by Matt Wringe (JIRA)
Navigation portlet doesn't render correctly in non-default layout
-----------------------------------------------------------------
Key: GTNPORTAL-2034
URL: https://issues.jboss.org/browse/GTNPORTAL-2034
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface
Reporter: Matt Wringe
If the navigation portlet is placed in a column container, the links will be render in the wrong location and can't be accessed.
- Log into portal
- Create a new page under home
- Edit the layout of the portal, place a 3 column layout at the top of the page, drag the navigation portlet to the middle column
- Save the changes and now try and use the navigation portlet to get to the new page created under home
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months