[gatein-issues] [JBoss JIRA] (GTNPORTAL-2463) Open an "Identity Transaction" only when it is necessary
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
RH Bugzilla Integration commented on GTNPORTAL-2463:
----------------------------------------------------
Jared MORGAN <jmorgan(a)redhat.com> made a comment on [bug
835578|https://bugzilla.redhat.com/show_bug.cgi?id=835578]
Technical note updated. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
Diffed Contents:
@@ -3,10 +3,10 @@
FIX: There is fix available in underlying component Picketlink IDM, which added
possibility to start Hibernate transaction lazily only for case when it's really
needed. It's adding new option "lazyStartOfHibernateTransaction" into
Picketlink IDM configuration file. Value true means that Hibernate transaction will be
started lazily only when needed. Value false is starting transaction non-lazily during
each request (current behaviour)
RESULT: In configuration file
gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml
is new option added:</para>
- <programlisting>&[CDATA[<option>
+ <programlisting><![CDATA[<option>
<name>lazyStartOfHibernateTransaction</name>
<value>false</value>
- </option>]];</programlisting
+ </option>]]></programlisting
<para>We can see that default value is false, so behaviour is same like before
(because of backward compatibility and avoiding of risk).
Open an "Identity Transaction" only when it is necessary
--------------------------------------------------------
Key: GTNPORTAL-2463
URL: https://issues.jboss.org/browse/GTNPORTAL-2463
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Identity integration
Affects Versions: 3.2.0-GA
Reporter: Nicolas Filotto
Assignee: Boleslaw Dawidowicz
Labels: performance
Attachments: LAZY-OPEN-TX-IDM.patch
The component {{PicketLinkIDMOrganizationServiceImpl}} has been defined as a
{{ComponentRequestLifecycle}} to be able to scope an "identity transaction" to
the life time of the request. However depending on the page we try to access, it could be
useless to open a tx in case the organization service is not even accessed which can have
a dramatic impact on performances for nothing especially when we use hibernate because
when we open a tx with hibernate, it does a JDBC call to switch to non auto commit mode.
Original Issue: https://jira.exoplatform.org/browse/EXOGTN-1162
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira