September 2011 - gatein-issues - Jboss List Archives

[JBoss JIRA] Created: (GTNPORTAL-2058) Group Management does not display newly created users

by Matt Wringe (JIRA)

Group Management does not display newly created users ----------------------------------------------------- Key: GTNPORTAL-2058 URL: https://issues.jboss.org/browse/GTNPORTAL-2058 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe When creating a new user via Groups->Organization->New Staff that new user does not appear within the groups management page (but you can search for the user and they will be displayed). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
10
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-2070) Edit Layout on Dashboard removes the dashboard layout

by Matt Wringe (JIRA)

Edit Layout on Dashboard removes the dashboard layout ----------------------------------------------------- Key: GTNPORTAL-2070 URL: https://issues.jboss.org/browse/GTNPORTAL-2070 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Matt Wringe Its not possible to edit the layout of specific types of pages, like dashboard or group. If you click edit layout on a dashboard page, then click save (even though nothing was saved), the page will no longer be in the default dashboard layout. See JBEPP-1138 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-2085) Proper serialization for description cache

by Julien Viet (JIRA)

Proper serialization for description cache ------------------------------------------ Key: GTNPORTAL-2085 URL: https://issues.jboss.org/browse/GTNPORTAL-2085 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Assignee: Julien Viet Fix For: 3.2.0-M02 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-2086) Proper serialization for navigation cache

by Julien Viet (JIRA)

Proper serialization for navigation cache ----------------------------------------- Key: GTNPORTAL-2086 URL: https://issues.jboss.org/browse/GTNPORTAL-2086 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Assignee: Julien Viet Fix For: 3.2.0-M02 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-2087) Simple MarshalledObject to contain an marshalled object into bytes

by Julien Viet (JIRA)

Simple MarshalledObject to contain an marshalled object into bytes ------------------------------------------------------------------ Key: GTNPORTAL-2087 URL: https://issues.jboss.org/browse/GTNPORTAL-2087 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Assignee: Julien Viet Fix For: 3.2.0-M02 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-2084) Allow for emtpy zip file for import.

by Nick Scavelli (JIRA)

Allow for emtpy zip file for import. ------------------------------------ Key: GTNPORTAL-2084 URL: https://issues.jboss.org/browse/GTNPORTAL-2084 Project: GateIn Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Management Reporter: Nick Scavelli Assignee: Nick Scavelli Priority: Minor gatein-management now allows empty zip files during export. Do not error out when empty zip file is imported. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-2083) A site should not be overwritten when the workspace import marker is not present

by Julien Viet (JIRA)

A site should not be overwritten when the workspace import marker is not present -------------------------------------------------------------------------------- Key: GTNPORTAL-2083 URL: https://issues.jboss.org/browse/GTNPORTAL-2083 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Environment: 1/ boot with gatein 2/ modify classic layout 3/ connect with crash and remove gtn:imported mixin 4/ reboot the layout will be the same as the initial layout Reporter: Julien Viet Assignee: Julien Viet Fix For: 3.2.0-M02 Currently when the workspace import marker is not present, the sites configured by XML will be overwritten (layout, pages). This raise an issue when migrating from an older version (gatein 3.1 for instance). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-2027) Upgrade eXo JCR to 1.14.0-CR4-CP01 (and dependencies)

by Thomas Heute (JIRA)

Upgrade eXo JCR to 1.14.0-CR4-CP01 (and dependencies) ----------------------------------------------------- Key: GTNPORTAL-2027 URL: https://issues.jboss.org/browse/GTNPORTAL-2027 Project: GateIn Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Heute Assignee: Thomas Heute Fix For: 3.2.0-M02 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (GTNPORTAL-2082) j_security_check request is sent as GET method.

by Takayuki Konishi (JIRA)

j_security_check request is sent as GET method. ----------------------------------------------- Key: GTNPORTAL-2082 URL: https://issues.jboss.org/browse/GTNPORTAL-2082 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 3.2.0-M01 Reporter: Takayuki Konishi j_sequrity_check request is sent like: http://localhost:8080/portal/private/j_security_check?j_username=root&j_p... The "root" value is user typed value and recorded in a browser history and server side logs like access_log of apache that not expected to record such sensitive information. It causes some problems of security like a shoulder hacking in client side and it put an unnecessary burden to server administrators because they have to manage sensitive information in logs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] Resolved: (GTNPORTAL-2080) Remove embbeded logger configuration

by Julien Viet (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2080?page=com.atlassian.jira.pl... ] Julien Viet resolved GTNPORTAL-2080. ------------------------------------ Assignee: Julien Viet Fix Version/s: 3.2.0-M02 Resolution: Done > 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 > Assignee: Julien Viet > 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} >  >  > <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> >  >  >  >  > {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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues September 2011