[JBoss JIRA] (GTNPORTAL-2801) Add eviction to indexer-config.xml
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2801?page=com.atlassian.jira.pl... ]
Marek Posolda commented on GTNPORTAL-2801:
------------------------------------------
So Nicolas confirmed on jbossexo ML that this configuration can't be used by default. It's by design that JBC configuration for indexer doesn't have eviction enabled. Enabling eviction could break the index and cause inconsistencies in JCR query results.
On the other hand, for some people it may be still useful as there are not so many places in GateIn where are JCR queries used (I am aware that queries are used in PageManagementPortlet and WSRP). So for someone, it may be good to save some memory with the disadvantage of broken index, which means that some functionalities (like mentioned PageManagementPortlet and WSRP) may not work correctly.
Maybe it worth to mention this into perf tuning guide? But it seems that it must be properly tested first and all consequences should be documented as well.
> 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"/>
> <!-- Configure the TransactionManager -->
> <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
11 years, 1 month
[JBoss JIRA] (GTNPORTAL-3365) Exception swallow in UserDaoImpl.persistUserInfo()
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3365?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3365:
----------------------------------
Original Estimate: 4 hours
Remaining Estimate: 4 hours
> Exception swallow in UserDaoImpl.persistUserInfo()
> --------------------------------------------------
>
> Key: GTNPORTAL-3365
> URL: https://issues.jboss.org/browse/GTNPORTAL-3365
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.3.Final
> Reporter: Vu Viet Phuong
> Assignee: Vu Viet Phuong
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Under "{{org.exoplatform.services.organization.idm}},
> focus on :
> {code:title=UserDAOImp.java|borderStyle=solid}
> public void persistUserInfo(User user, IdentitySession session) throws Exception
> {
> orgService.flush();
> AttributesManager am = session.getAttributesManager();
> ArrayList attributes = new ArrayList();
> /* ... */
> if (user.getPassword() != null)
> {
> if (orgService.getConfiguration().isPasswordAsAttribute())
> {
> attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword()));
> }
> else
> {
> try
> {
> am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword());
> }
> catch (IdentityException e)
> {
> log.info("Cannot update password: " + user.getUserName() + "; ", e);
> }
> }
> }
> Attribute[] attrs = new Attribute[attributes.size()];
> attrs = (Attribute[])attributes.toArray(attrs);
> try
> {
> am.updateAttributes(user.getUserName(), attrs);
> }
> catch (IdentityException e)
> {
> log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e);
> }
> }
> {code}
>
> The method {{saveUser(User, boolean) _throws Exception_}}
> calls
> {{persistUserInfo(User user, IdentitySession session) _throws Exception_}}.
>
> Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}:
> * first time in the password level
> * second time when updating all of the attributes.
> (!) Users want to be notified when an error occurs during user registration.
> As well as being aware of the type of the caught exception.
--
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
11 years, 1 month
[JBoss JIRA] (GTNPORTAL-3365) Exception swallow in UserDaoImpl.persistUserInfo()
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3365?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3365:
----------------------------------
Sprint: Sprint 91
> Exception swallow in UserDaoImpl.persistUserInfo()
> --------------------------------------------------
>
> Key: GTNPORTAL-3365
> URL: https://issues.jboss.org/browse/GTNPORTAL-3365
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.3.Final
> Reporter: Vu Viet Phuong
> Assignee: Vu Viet Phuong
>
> Under "{{org.exoplatform.services.organization.idm}},
> focus on :
> {code:title=UserDAOImp.java|borderStyle=solid}
> public void persistUserInfo(User user, IdentitySession session) throws Exception
> {
> orgService.flush();
> AttributesManager am = session.getAttributesManager();
> ArrayList attributes = new ArrayList();
> /* ... */
> if (user.getPassword() != null)
> {
> if (orgService.getConfiguration().isPasswordAsAttribute())
> {
> attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword()));
> }
> else
> {
> try
> {
> am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword());
> }
> catch (IdentityException e)
> {
> log.info("Cannot update password: " + user.getUserName() + "; ", e);
> }
> }
> }
> Attribute[] attrs = new Attribute[attributes.size()];
> attrs = (Attribute[])attributes.toArray(attrs);
> try
> {
> am.updateAttributes(user.getUserName(), attrs);
> }
> catch (IdentityException e)
> {
> log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e);
> }
> }
> {code}
>
> The method {{saveUser(User, boolean) _throws Exception_}}
> calls
> {{persistUserInfo(User user, IdentitySession session) _throws Exception_}}.
>
> Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}:
> * first time in the password level
> * second time when updating all of the attributes.
> (!) Users want to be notified when an error occurs during user registration.
> As well as being aware of the type of the caught exception.
--
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
11 years, 1 month
[JBoss JIRA] (GTNPORTAL-3315) Portal setup improvements
by Hai Nguyen (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3315?page=com.atlassian.jira.pl... ]
Hai Nguyen commented on GTNPORTAL-3315:
---------------------------------------
I have updated PR included [~vstorm83] commits. It sounds good when running with CORE Snapshot
> Portal setup improvements
> --------------------------
>
> Key: GTNPORTAL-3315
> URL: https://issues.jboss.org/browse/GTNPORTAL-3315
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Final
> Reporter: Trong Tran
> Assignee: Vu Viet Phuong
> Fix For: 3.7.0.Final
>
> Original Estimate: 2 days
> Time Spent: 3 days
> Remaining Estimate: 0 minutes
>
> The Portal Setup feature was introduced since Gatein 3.6, it is always active by default.
> Today there is a need that it could be able to disable the feature somehow. We also identify there are following needed improvements, potential bug fixes should be done in current implementation:
> - Ability to Enable/Disable the feature
> - Make it work more as an extension, to not forced adding things to core portal
> - Get rid of cloning SetupOrganizationDatabaseInitializer from OrganizationDatabaseInitializer
> - Removing repository/workspace name hard-coding in PortalSetupService
--
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
11 years, 1 month
[JBoss JIRA] (GTNPORTAL-3365) Exception swallow in UserDaoImpl.persistUserInfo()
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3365?page=com.atlassian.jira.pl... ]
Work on GTNPORTAL-3365 started by Vu Viet Phuong.
> Exception swallow in UserDaoImpl.persistUserInfo()
> --------------------------------------------------
>
> Key: GTNPORTAL-3365
> URL: https://issues.jboss.org/browse/GTNPORTAL-3365
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.3.Final
> Reporter: Vu Viet Phuong
> Assignee: Vu Viet Phuong
>
> Under "{{org.exoplatform.services.organization.idm}},
> focus on :
> {code:title=UserDAOImp.java|borderStyle=solid}
> public void persistUserInfo(User user, IdentitySession session) throws Exception
> {
> orgService.flush();
> AttributesManager am = session.getAttributesManager();
> ArrayList attributes = new ArrayList();
> /* ... */
> if (user.getPassword() != null)
> {
> if (orgService.getConfiguration().isPasswordAsAttribute())
> {
> attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword()));
> }
> else
> {
> try
> {
> am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword());
> }
> catch (IdentityException e)
> {
> log.info("Cannot update password: " + user.getUserName() + "; ", e);
> }
> }
> }
> Attribute[] attrs = new Attribute[attributes.size()];
> attrs = (Attribute[])attributes.toArray(attrs);
> try
> {
> am.updateAttributes(user.getUserName(), attrs);
> }
> catch (IdentityException e)
> {
> log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e);
> }
> }
> {code}
>
> The method {{saveUser(User, boolean) _throws Exception_}}
> calls
> {{persistUserInfo(User user, IdentitySession session) _throws Exception_}}.
>
> Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}:
> * first time in the password level
> * second time when updating all of the attributes.
> (!) Users want to be notified when an error occurs during user registration.
> As well as being aware of the type of the caught exception.
--
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
11 years, 1 month
[JBoss JIRA] (GTNPORTAL-3365) Exception swallow in UserDaoImpl.persistUserInfo()
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3365?page=com.atlassian.jira.pl... ]
Vu Viet Phuong reassigned GTNPORTAL-3365:
-----------------------------------------
Assignee: Vu Viet Phuong
> Exception swallow in UserDaoImpl.persistUserInfo()
> --------------------------------------------------
>
> Key: GTNPORTAL-3365
> URL: https://issues.jboss.org/browse/GTNPORTAL-3365
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.3.Final
> Reporter: Vu Viet Phuong
> Assignee: Vu Viet Phuong
>
> Under "{{org.exoplatform.services.organization.idm}},
> focus on :
> {code:title=UserDAOImp.java|borderStyle=solid}
> public void persistUserInfo(User user, IdentitySession session) throws Exception
> {
> orgService.flush();
> AttributesManager am = session.getAttributesManager();
> ArrayList attributes = new ArrayList();
> /* ... */
> if (user.getPassword() != null)
> {
> if (orgService.getConfiguration().isPasswordAsAttribute())
> {
> attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword()));
> }
> else
> {
> try
> {
> am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword());
> }
> catch (IdentityException e)
> {
> log.info("Cannot update password: " + user.getUserName() + "; ", e);
> }
> }
> }
> Attribute[] attrs = new Attribute[attributes.size()];
> attrs = (Attribute[])attributes.toArray(attrs);
> try
> {
> am.updateAttributes(user.getUserName(), attrs);
> }
> catch (IdentityException e)
> {
> log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e);
> }
> }
> {code}
>
> The method {{saveUser(User, boolean) _throws Exception_}}
> calls
> {{persistUserInfo(User user, IdentitySession session) _throws Exception_}}.
>
> Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}:
> * first time in the password level
> * second time when updating all of the attributes.
> (!) Users want to be notified when an error occurs during user registration.
> As well as being aware of the type of the caught exception.
--
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
11 years, 1 month
[JBoss JIRA] (GTNPORTAL-3365) Exception swallow in UserDaoImpl.persistUserInfo()
by Vu Viet Phuong (JIRA)
Vu Viet Phuong created GTNPORTAL-3365:
-----------------------------------------
Summary: Exception swallow in UserDaoImpl.persistUserInfo()
Key: GTNPORTAL-3365
URL: https://issues.jboss.org/browse/GTNPORTAL-3365
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 3.6.3.Final
Reporter: Vu Viet Phuong
Under "{{org.exoplatform.services.organization.idm}},
focus on :
{code:title=UserDAOImp.java|borderStyle=solid}
public void persistUserInfo(User user, IdentitySession session) throws Exception
{
orgService.flush();
AttributesManager am = session.getAttributesManager();
ArrayList attributes = new ArrayList();
/* ... */
if (user.getPassword() != null)
{
if (orgService.getConfiguration().isPasswordAsAttribute())
{
attributes.add(new SimpleAttribute(USER_PASSWORD, user.getPassword()));
}
else
{
try
{
am.updatePassword(session.getPersistenceManager().findUser(user.getUserName()), user.getPassword());
}
catch (IdentityException e)
{
log.info("Cannot update password: " + user.getUserName() + "; ", e);
}
}
}
Attribute[] attrs = new Attribute[attributes.size()];
attrs = (Attribute[])attributes.toArray(attrs);
try
{
am.updateAttributes(user.getUserName(), attrs);
}
catch (IdentityException e)
{
log.info("Cannot update attributes for user: " + user.getUserName() + "; ", e);
}
}
{code}
The method {{saveUser(User, boolean) _throws Exception_}}
calls
{{persistUserInfo(User user, IdentitySession session) _throws Exception_}}.
Whereas, deeper in the code, you can easily notice that exceptions are caught in this level and traced by a {{log.info}}:
* first time in the password level
* second time when updating all of the attributes.
(!) Users want to be notified when an error occurs during user registration.
As well as being aware of the type of the caught exception.
--
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
11 years, 1 month
[JBoss JIRA] (GTNPORTAL-3315) Portal setup improvements
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3315?page=com.atlassian.jira.pl... ]
Trong Tran commented on GTNPORTAL-3315:
---------------------------------------
as COR-317 has been resolved, [~haint] could you please make a final check ?
> Portal setup improvements
> --------------------------
>
> Key: GTNPORTAL-3315
> URL: https://issues.jboss.org/browse/GTNPORTAL-3315
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Final
> Reporter: Trong Tran
> Assignee: Vu Viet Phuong
> Fix For: 3.7.0.Final
>
> Original Estimate: 2 days
> Time Spent: 3 days
> Remaining Estimate: 0 minutes
>
> The Portal Setup feature was introduced since Gatein 3.6, it is always active by default.
> Today there is a need that it could be able to disable the feature somehow. We also identify there are following needed improvements, potential bug fixes should be done in current implementation:
> - Ability to Enable/Disable the feature
> - Make it work more as an extension, to not forced adding things to core portal
> - Get rid of cloning SetupOrganizationDatabaseInitializer from OrganizationDatabaseInitializer
> - Removing repository/workspace name hard-coding in PortalSetupService
--
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
11 years, 1 month