January 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNPORTAL-2798) Nothing happen when click Save button in Change password form

by Son Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2798?page=com.atlassian.jira.pl... ] Son Tran commented on GTNPORTAL-2798: ------------------------------------- This bug caused by the UIFrom.js haven't already loaded on the ResetPassword form > Nothing happen when click Save button in Change password form > -------------------------------------------------------------- > > Key: GTNPORTAL-2798 > URL: https://issues.jboss.org/browse/GTNPORTAL-2798 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Hang Nguyen > Labels: portal-s70 > > Click Sign In link > Click check box forgot user name/password to recovery it > Open mail and click link to change new password > Input new password -> Click Save => Nothing happen. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2801) Add eviction to indexer-config.xml

by Toshiya Kobayashi (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2801?page=com.atlassian.jira.pl... ] Toshiya Kobayashi updated GTNPORTAL-2801: ----------------------------------------- Description: gatein.ear/portal.war/WEB-INF/conf/jcr/jbosscache/cluster/indexer-config.xml doesn't have eviction configuration. It may cause a memory leak in slave nodes. {code:xml} <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> <locking useLockStriping="false" concurrencyLevel="64" lockParentForChildInsertRemove="false" lockAcquisitionTimeout="20000"/>  <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup"/> <clustering mode="replication" clusterName="${jboss.partition.name:DefaultPartition}-${jbosscache-cluster-name}"> <stateRetrieval timeout="20000" fetchInMemoryState="false"/> <jgroupsConfig configFile="jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml"/> <sync/> </clustering> </jbosscache> {code} was: gatein.ear/portal.war/WEB-INF/conf/jcr/jbosscache/cluster/indexer-config.xml doesn't have eviction configuration. It may cause a memory leak. {code:xml} <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> <locking useLockStriping="false" concurrencyLevel="64" lockParentForChildInsertRemove="false" lockAcquisitionTimeout="20000"/>  <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup"/> <clustering mode="replication" clusterName="${jboss.partition.name:DefaultPartition}-${jbosscache-cluster-name}"> <stateRetrieval timeout="20000" fetchInMemoryState="false"/> <jgroupsConfig configFile="jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml"/> <sync/> </clustering> </jbosscache> {code} > Add eviction to indexer-config.xml > ---------------------------------- > > Key: GTNPORTAL-2801 > URL: https://issues.jboss.org/browse/GTNPORTAL-2801 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCR integration > Affects Versions: 3.5.0.Final > Reporter: Toshiya Kobayashi > > gatein.ear/portal.war/WEB-INF/conf/jcr/jbosscache/cluster/indexer-config.xml doesn't have eviction configuration. It may cause a memory leak in slave nodes. > {code:xml} > <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> > <locking useLockStriping="false" concurrencyLevel="64" lockParentForChildInsertRemove="false" > lockAcquisitionTimeout="20000"/> >  > <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup"/> > <clustering mode="replication" clusterName="${jboss.partition.name:DefaultPartition}-${jbosscache-cluster-name}"> > <stateRetrieval timeout="20000" fetchInMemoryState="false"/> > <jgroupsConfig configFile="jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml"/> > <sync/> > </clustering> > </jbosscache> > {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2801) Add eviction to indexer-config.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2801?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated GTNPORTAL-2801: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=896393 > Add eviction to indexer-config.xml > ---------------------------------- > > Key: GTNPORTAL-2801 > URL: https://issues.jboss.org/browse/GTNPORTAL-2801 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCR integration > Affects Versions: 3.5.0.Final > Reporter: Toshiya Kobayashi > > gatein.ear/portal.war/WEB-INF/conf/jcr/jbosscache/cluster/indexer-config.xml doesn't have eviction configuration. It may cause a memory leak. > {code:xml} > <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> > <locking useLockStriping="false" concurrencyLevel="64" lockParentForChildInsertRemove="false" > lockAcquisitionTimeout="20000"/> >  > <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup"/> > <clustering mode="replication" clusterName="${jboss.partition.name:DefaultPartition}-${jbosscache-cluster-name}"> > <stateRetrieval timeout="20000" fetchInMemoryState="false"/> > <jgroupsConfig configFile="jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml"/> > <sync/> > </clustering> > </jbosscache> > {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2801) Add eviction to indexer-config.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2801?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2801: ---------------------------------------------------- Toshiya Kobayashi <tkobayas(a)redhat.com> made a comment on [bug 896393|https://bugzilla.redhat.com/show_bug.cgi?id=896393] Description of problem: Platform BZ for https://issues.jboss.org/browse/GTNPORTAL-2801 Steps to Reproduce: 1. Add many portals via MOP import in clustered EPP Actual results: Heap usage of slave node will go up and never be released (occupied by indexer cache) Expected results: indexer cache is evicted as configured in indexer-config.xml so no memory leak > Add eviction to indexer-config.xml > ---------------------------------- > > Key: GTNPORTAL-2801 > URL: https://issues.jboss.org/browse/GTNPORTAL-2801 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCR integration > Affects Versions: 3.5.0.Final > Reporter: Toshiya Kobayashi > > gatein.ear/portal.war/WEB-INF/conf/jcr/jbosscache/cluster/indexer-config.xml doesn't have eviction configuration. It may cause a memory leak. > {code:xml} > <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> > <locking useLockStriping="false" concurrencyLevel="64" lockParentForChildInsertRemove="false" > lockAcquisitionTimeout="20000"/> >  > <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup"/> > <clustering mode="replication" clusterName="${jboss.partition.name:DefaultPartition}-${jbosscache-cluster-name}"> > <stateRetrieval timeout="20000" fetchInMemoryState="false"/> > <jgroupsConfig configFile="jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml"/> > <sync/> > </clustering> > </jbosscache> > {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2801) Add eviction to indexer-config.xml

by Toshiya Kobayashi (JIRA)

Toshiya Kobayashi created GTNPORTAL-2801: -------------------------------------------- Summary: Add eviction to indexer-config.xml Key: GTNPORTAL-2801 URL: https://issues.jboss.org/browse/GTNPORTAL-2801 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: JCR integration Affects Versions: 3.5.0.Final Reporter: Toshiya Kobayashi gatein.ear/portal.war/WEB-INF/conf/jcr/jbosscache/cluster/indexer-config.xml doesn't have eviction configuration. It may cause a memory leak. {code:xml} <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> <locking useLockStriping="false" concurrencyLevel="64" lockParentForChildInsertRemove="false" lockAcquisitionTimeout="20000"/>  <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup"/> <clustering mode="replication" clusterName="${jboss.partition.name:DefaultPartition}-${jbosscache-cluster-name}"> <stateRetrieval timeout="20000" fetchInMemoryState="false"/> <jgroupsConfig configFile="jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml"/> <sync/> </clustering> </jbosscache> {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2799) Changing Portlet Icon doesn't work

by Son Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2799?page=com.atlassian.jira.pl... ] Son Tran commented on GTNPORTAL-2799: ------------------------------------- Link internal pull request: https://github.com/exoportal/gatein-portal/pull/18 > Changing Portlet Icon doesn't work > ---------------------------------- > > Key: GTNPORTAL-2799 > URL: https://issues.jboss.org/browse/GTNPORTAL-2799 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebUI > Affects Versions: 3.5.0.Final > Reporter: Trong Tran > Priority: Trivial > Labels: portal-s70 > Attachments: Portal Navigation_1358312135866, Portal Navigation_1358312135866.png, Screen Shot 2013-01-16 at 11.56.05 AM.png > > > Go to the Portlet Edit form to change the Icon, then save ==> it doesn't work (see attached images) -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2800) Cannot add new user into a group if configuring user name as email.

by Tran Trung Thanh (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2800?page=com.atlassian.jira.pl... ] Tran Trung Thanh commented on GTNPORTAL-2800: --------------------------------------------- [pull/318|https://github.com/gatein/gatein-portal/pull/318] removes proper group membership validator in Group Management portlet. Because in this portlet, group membership field allows a list of username which is separated by comma. In case we don't make the consistency between Username validator and group membership validator, it causes this issue. > Cannot add new user into a group if configuring user name as email. > ------------------------------------------------------------------- > > Key: GTNPORTAL-2800 > URL: https://issues.jboss.org/browse/GTNPORTAL-2800 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Tran Trung Thanh > Priority: Minor > Labels: portal-s70 > > For several reasons, we configure username as email by *UserConfigurableValidator* but it causes a bug in *Organization Management* portlet. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2800) Cannot add new user into a group if configuring user name as email.

by Trong Tran (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2800?page=com.atlassian.jira.pl... ] Trong Tran updated GTNPORTAL-2800: ---------------------------------- Labels: portal-s70 (was: ) > Cannot add new user into a group if configuring user name as email. > ------------------------------------------------------------------- > > Key: GTNPORTAL-2800 > URL: https://issues.jboss.org/browse/GTNPORTAL-2800 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Tran Trung Thanh > Priority: Minor > Labels: portal-s70 > > For several reasons, we configure username as email by *UserConfigurableValidator* but it causes a bug in *Organization Management* portlet. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2800) Cannot add new user into a group if configuring user name as email.

by Tran Trung Thanh (JIRA)

Tran Trung Thanh created GTNPORTAL-2800: ------------------------------------------- Summary: Cannot add new user into a group if configuring user name as email. Key: GTNPORTAL-2800 URL: https://issues.jboss.org/browse/GTNPORTAL-2800 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.5.0.Final Reporter: Tran Trung Thanh Priority: Minor For several reasons, we configure username as email by *UserConfigurableValidator* but it causes a bug in *Organization Management* portlet. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-346) Multipart requests are not handeled if there is no attached file

by Chris Laprun (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-346?page=com.atlassian.jira.plugi... ] Chris Laprun updated GTNWSRP-346: --------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Multipart requests are not handeled if there is no attached file > ---------------------------------------------------------------- > > Key: GTNWSRP-346 > URL: https://issues.jboss.org/browse/GTNWSRP-346 > Project: GateIn WSRP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.1.7-GA, 2.2.2.Final > Reporter: Martin Weiler > Assignee: Chris Laprun > Fix For: 2.1.8-GA, 2.2.3.Final > > > We have html multipart form in a wsrp portlet: > {code:xml} > <form enctype="multipart/form-data" method="post" ... > {code} > with an optional input field for an attachment: > {code:xml} > <input type="file" value="org.springframework.web.multipart.commons.CommonsMultipartFile@f3af1" name="attachement"> > {code} > The "org.gatein.wsrp.consumer.handlers.ActionHandler" handles the request correctly and tries to create a UploadContext with the help of the WSRPTypeFactory: > {code} > UploadContext uploadContext = WSRPTypeFactory.createUploadContext(contentType, baos.toByteArray()); > {code} > The problem is, that the createUploadContext throws an exception if the byte array has a content lenght of 0 and so the rest of the parameteres are not handled correctly: > {code} > public static UploadContext createUploadContext(String mimeType, byte[] uploadData) > { > ParameterValidation.throwIllegalArgExceptionIfNullOrEmpty(mimeType, "MIME Type", "UploadContext"); > if (uploadData == null || uploadData.length == 0) > { > throw new IllegalArgumentException("Must pass non-null, non-empty upload data"); > } > > UploadContext uploadContext = new UploadContext(); > uploadContext.setMimeType(mimeType); > uploadContext.setUploadData(uploadData); > return uploadContext; > } > {code} > So currently the post request with WSRP works only if really a file is attached. Without WSRP it runs with and without an attached file. -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues January 2013