April 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-3451) Infinispan transport clusterName property not properly defined

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3451?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3451: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1085927 > Infinispan transport clusterName property not properly defined > -------------------------------------------------------------- > > Key: GTNPORTAL-3451 > URL: https://issues.jboss.org/browse/GTNPORTAL-3451 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Lucas Ponce > Assignee: Lucas Ponce > > clusterName attribute is not well defined for infinispan transport defined in HA configurations. > This bug shows followings warnings: > [...] > 14:47:59,283 WARN [org.infinispan.util.StringPropertyReplacer] (MSC service thread 1-2) ISPN000003: Property infinispan-cluster-name could not be replaced as intended! > [...] > And this bug is root cause for other cascading errors in cluster setup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3451) Infinispan transport clusterName property not properly defined

by Lucas Ponce (JIRA)

Lucas Ponce created GTNPORTAL-3451: -------------------------------------- Summary: Infinispan transport clusterName property not properly defined Key: GTNPORTAL-3451 URL: https://issues.jboss.org/browse/GTNPORTAL-3451 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Lucas Ponce -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3450) Impossible to upload file in Content Explorer when tmpdir does not exist

by Tran Trung Thanh (JIRA)

Tran Trung Thanh created GTNPORTAL-3450: ------------------------------------------- Summary: Impossible to upload file in Content Explorer when tmpdir does not exist Key: GTNPORTAL-3450 URL: https://issues.jboss.org/browse/GTNPORTAL-3450 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.5.8.Final Reporter: Tran Trung Thanh We have a problem when trying to upload files. We noticed that the "org.exoplatform.upload.UploadService" Service uses java.io.tmpdir (System Properties) to create the portal/eXoUpload directory needed to upload files. If the directory does not exist (ie, deleted : custermer's case deleted by tmpwatch command). << we can view the file tree but nothing happens, it stays at 0 % (blocking). *Error log:* {code}DEBUG [org.exoplatform.upload.UploadService] (ajp-10.11.2.212-8009-42) IOException while upload resource org.apache.commons.fileupload.FileUploadBase$IOFileUploadException: Processing of multipart/form-data request failed. /tmp/portal/eXoUpload/upload__175985d8_14550fb3b24_d1a_00000003.tmp (Aucun fichier ou dossier de ce type) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:367) at org.apache.commons.fileupload.servlet.ServletFileUpload.parseRequest(ServletFileUpload.java:126) at org.exoplatform.upload.UploadService.createUploadResource(UploadService.java:120) at org.exoplatform.upload.UploadService.createUploadResource(UploadService.java:96) at org.exoplatform.web.handler.UploadHandler.execute(UploadHandler.java:123) at org.exoplatform.web.handler.UploadHandler.execute(UploadHandler.java:60) at org.exoplatform.web.WebAppController.service(WebAppController.java:358) at org.exoplatform.portal.application.PortalController.onService(PortalController.java:125) at org.exoplatform.container.web.AbstractHttpServlet.service(AbstractHttpServlet.java:132) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:84) at org.exoplatform.web.login.RememberMeFilter.doFilter(RememberMeFilter.java:54) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:114) at com.filhetallard.dis.extranet.adp.portlet.common.SitesAccessFilter.doFilter(SitesAccessFilter.java:195) at com.filhetallard.dis.extranet.fac.exo.web.FilterAdapter.doFilter(FilterAdapter.java:23) at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:110) at org.exoplatform.platform.common.admin.TermsAndConditionsFilter.doFilter(TermsAndConditionsFilter.java:77) at org.exoplatform.web.filter.ExtensibleFilter$ExtensibleFilterChain.doFilter(ExtensibleFilter.java:110) at org.exoplatform.web.filter.ExtensibleFilter.doFilter(ExtensibleFilter.java:84) at org.exoplatform.web.filter.GenericFilter.doFilter(GenericFilter.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.exoplatform.web.CacheUserProfileFilter.doFilter(CacheUserProfileFilter.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter.doFilter(ThreadLocalSessionProviderInitializedFilter.java:116) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.exoplatform.services.security.web.SetCurrentIdentityFilter.doFilter(SetCurrentIdentityFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.exoplatform.web.login.ClusteredSSOFilter.doFilter(ClusteredSSOFilter.java:62) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.exoplatform.container.web.PortalContainerFilter.doFilter(PortalContainerFilter.java:69) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) at org.jboss.web.tomcat.service.session.ClusteredSessionValve.handleRequest(ClusteredSessionValve.java:135) at org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:94) at org.jboss.web.tomcat.service.session.JvmRouteValve.invoke(JvmRouteValve.java:88) at org.jboss.web.tomcat.service.session.LockingValve.invoke(LockingValve.java:62) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:402) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.internalProcess(ActiveRequestResponseCacheValve.java:74) at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:47) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:436) at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:385) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451) at java.lang.Thread.run(Thread.java:701) Caused by: java.io.FileNotFoundException: /tmp/portal/eXoUpload/upload__175985d8_14550fb3b24_d1a_00000003.tmp (Aucun fichier ou dossier de ce type) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:212) at java.io.FileOutputStream.<init>(FileOutputStream.java:160) at org.apache.commons.io.output.DeferredFileOutputStream.thresholdReached(DeferredFileOutputStream.java:165) at org.apache.commons.io.output.ThresholdingOutputStream.checkThreshold(ThresholdingOutputStream.java:221) at org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:127) at org.apache.commons.fileupload.util.Streams.copy(Streams.java:101) at org.apache.commons.fileupload.util.Streams.copy(Streams.java:64) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:362) ... 65 more{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3449) Adding new node in group navigation doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3449?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3449: ---------------------------------------------------- Lucas Ponce <lponce(a)redhat.com> changed the Status of [bug 1089460|https://bugzilla.redhat.com/show_bug.cgi?id=1089460] from ASSIGNED to POST > Adding new node in group navigation doesn't work > ------------------------------------------------ > > Key: GTNPORTAL-3449 > URL: https://issues.jboss.org/browse/GTNPORTAL-3449 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebUI > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.0.Final > > > New pages added under group navigation are not visible in UIUserToolBarGroupPortlet menu. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3449) Adding new node in group navigation doesn't work

by Lucas Ponce (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3449?page=com.atlassian.jira.pl... ] Lucas Ponce updated GTNPORTAL-3449: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-portal/pull/830 > Adding new node in group navigation doesn't work > ------------------------------------------------ > > Key: GTNPORTAL-3449 > URL: https://issues.jboss.org/browse/GTNPORTAL-3449 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebUI > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.0.Final > > > New pages added under group navigation are not visible in UIUserToolBarGroupPortlet menu. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3449) Adding new node in group navigation doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3449?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-3449: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1089460 > Adding new node in group navigation doesn't work > ------------------------------------------------ > > Key: GTNPORTAL-3449 > URL: https://issues.jboss.org/browse/GTNPORTAL-3449 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebUI > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.0.Final > > > New pages added under group navigation are not visible in UIUserToolBarGroupPortlet menu. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3449) Adding new node in group navigation doesn't work

by Lucas Ponce (JIRA)

Lucas Ponce created GTNPORTAL-3449: -------------------------------------- Summary: Adding new node in group navigation doesn't work Key: GTNPORTAL-3449 URL: https://issues.jboss.org/browse/GTNPORTAL-3449 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: WebUI Reporter: Lucas Ponce Assignee: Lucas Ponce Fix For: 3.8.0.Final New pages added under group navigation are not visible in UIUserToolBarGroupPortlet menu. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3417) Disable users icons look like inverse

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3417?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3417: ---------------------------------------------------- Boleslaw Dawidowicz <bdawidow(a)redhat.com> changed the Status of [bug 1076175|https://bugzilla.redhat.com/show_bug.cgi?id=1076175] from NEW to ASSIGNED > Disable users icons look like inverse > ------------------------------------- > > Key: GTNPORTAL-3417 > URL: https://issues.jboss.org/browse/GTNPORTAL-3417 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: 3.8.0.Beta01-SNAPSHOT > Reporter: Vlastislav Ramik > Labels: RHJP62 > Fix For: 3.8.0.Final > > > Icons in users and group managements looks that all users are disabled while they are enabled. The icon is grey and the tag is: <img title="Disabled User" alt="Disabled User" ... /> While disabled user icons is green and the tag is: <img title="Enabled User" alt="Enabled User" ... /> All functionality works as expected but both the icon and the title is very confusing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3448) Failed authentication on service REST after a session timeout

by Tuyen Nguyen The (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3448?page=com.atlassian.jira.pl... ] Tuyen Nguyen The updated GTNPORTAL-3448: ---------------------------------------- Attachment: authenticate-successfully.png reauthenticated-failure.png > Failed authentication on service REST after a session timeout > ------------------------------------------------------------- > > Key: GTNPORTAL-3448 > URL: https://issues.jboss.org/browse/GTNPORTAL-3448 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > Attachments: authenticate-successfully.png, reauthenticated-failure.png > > > Case to reproduce: > - Access to api > {code} > http://localhost:8080/rest/private/managed-components/api/sites/classic/p... > {code} > - Authentication with user root and now we can list all page of classic site (include Group Navitation and Portal Navigation page) > - Wait until session timeout (about ~30 minute) > - Access to list all page api again, now we only see public pages (see attachments) and has error in log: > {code} > [http-bio-8080-exec-10] ERROR exo.core.component.security.core.SetCurrentIdentityFilter - Not found identity in IdentityRegistry for user root, check Login Module. > {code} > This error is unusually occured. > Maybe identity was removed from IdentityRegistry after session timeout and it throw this error. > So, we should set restoreIdentity=true of the filter "SetCurrentIdentityFilter" into web.xml of rest.war (like in portal.war) to reinject the identity when it is lost -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3448) Failed authentication on service REST after a session timeout

by Tuyen Nguyen The (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3448?page=com.atlassian.jira.pl... ] Tuyen Nguyen The updated GTNPORTAL-3448: ---------------------------------------- Description: Case to reproduce: - Access to api {code} http://localhost:8080/rest/private/managed-components/api/sites/classic/p... {code} - Authentication with user root and now we can list all page of classic site (include Group Navitation and Portal Navigation page) - Wait until session timeout (about ~30 minute) - Access to list all page api again, now we only see public pages (see attachments) and has error in log: {code} [http-bio-8080-exec-10] ERROR exo.core.component.security.core.SetCurrentIdentityFilter - Not found identity in IdentityRegistry for user root, check Login Module. {code} This error is unusually occured. Maybe identity was removed from IdentityRegistry after session timeout and it throw this error. So, we should set restoreIdentity=true of the filter "SetCurrentIdentityFilter" into web.xml of rest.war (like in portal.war) to reinject the identity when it is lost was: Customer does not sometimes use /rest after session timeout. He also propose a workaround which adds "restoreIdentity" of the filter "SetCurrentIdentityFilter" into web.xml of rest.war, this parameter is added to almost war files but this param is not available in rest.war. So, we should add this param into web.xml of rest.war > Failed authentication on service REST after a session timeout > ------------------------------------------------------------- > > Key: GTNPORTAL-3448 > URL: https://issues.jboss.org/browse/GTNPORTAL-3448 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tuyen Nguyen The > Assignee: Tuyen Nguyen The > Attachments: authenticate-successfully.png, reauthenticated-failure.png > > > Case to reproduce: > - Access to api > {code} > http://localhost:8080/rest/private/managed-components/api/sites/classic/p... > {code} > - Authentication with user root and now we can list all page of classic site (include Group Navitation and Portal Navigation page) > - Wait until session timeout (about ~30 minute) > - Access to list all page api again, now we only see public pages (see attachments) and has error in log: > {code} > [http-bio-8080-exec-10] ERROR exo.core.component.security.core.SetCurrentIdentityFilter - Not found identity in IdentityRegistry for user root, check Login Module. > {code} > This error is unusually occured. > Maybe identity was removed from IdentityRegistry after session timeout and it throw this error. > So, we should set restoreIdentity=true of the filter "SetCurrentIdentityFilter" into web.xml of rest.war (like in portal.war) to reinject the identity when it is lost -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues April 2014