4 a.m.
Nicolas Filotto created GTNPORTAL-2463:
------------------------------------------
Summary: 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
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.
Please find more details (and the related patch) in the linked JIRA issue
The link to the patch
https://jira.exoplatform.org/secure/attachment/58267/LAZY-OPEN-TX-IDM.patch
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
4:02 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
Nicolas Filotto updated GTNPORTAL-2463:
---------------------------------------
Description:
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.
Please find more details (and the related patch) in the linked JIRA issue of the original
issue
The link to the patch
https://jira.exoplatform.org/secure/attachment/58267/LAZY-OPEN-TX-IDM.patch
Original Issue: https://jira.exoplatform.org/browse/EXOGTN-1162
was:
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.
Please find more details (and the related patch) in the linked JIRA issue
The link to the patch
https://jira.exoplatform.org/secure/attachment/58267/LAZY-OPEN-TX-IDM.patch
Original Issue: https://jira.exoplatform.org/browse/EXOGTN-1162
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
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.
Please find more details (and the related patch) in the linked JIRA issue of the original
issue
The link to the patch
https://jira.exoplatform.org/secure/attachment/58267/LAZY-OPEN-TX-IDM.patch
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
4:14 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
Boleslaw Dawidowicz commented on GTNPORTAL-2463:
------------------------------------------------
Hi,
I cannot check the patch (access denied), could you attach it here also?
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
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.
Please find more details (and the related patch) in the linked JIRA issue of the original
issue
The link to the patch
https://jira.exoplatform.org/secure/attachment/58267/LAZY-OPEN-TX-IDM.patch
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
4:18 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
Nicolas Filotto updated GTNPORTAL-2463:
---------------------------------------
Attachment: LAZY-OPEN-TX-IDM.patch
Here it is
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.
Please find more details (and the related patch) in the linked JIRA issue of the original
issue
The link to the patch
https://jira.exoplatform.org/secure/attachment/58267/LAZY-OPEN-TX-IDM.patch
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
4:18 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
Nicolas Filotto updated GTNPORTAL-2463:
---------------------------------------
Description:
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
was:
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.
Please find more details (and the related patch) in the linked JIRA issue of the original
issue
The link to the patch
https://jira.exoplatform.org/secure/attachment/58267/LAZY-OPEN-TX-IDM.patch
Original Issue: https://jira.exoplatform.org/browse/EXOGTN-1162
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
8:31 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
Boleslaw Dawidowicz commented on GTNPORTAL-2463:
------------------------------------------------
Please check https://github.com/picketlink/picketlink-idm/pull/2
We believe this will be more proper way to address the problem. It introduces the fix
deeper inside of PLIDM which will in fact let all caches above be used more efficiently.
New version of PLIDM including this fix will be released this week.
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
9:12 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
Marek Posolda updated GTNPORTAL-2463:
-------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/58
Pull request https://github.com/gatein/gatein-portal/pull/58 is adding new option to
picketlink IDM configuration. This new option specifies if Hibernate transaction should be
started lazily or not-lazily (old behaviour) at the beginning of RequestLifeCycle. For
GateIn, it will be enabled by default. Changes will be available after Picketlink IDM of
version 1.3.2.CR1 will be released and GateIn dependencies upgraded to this version.
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
9:22 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
RH Bugzilla Integration updated GTNPORTAL-2463:
-----------------------------------------------
Git Pull Request: https://github.com/gatein/gatein-portal/pull/58 (was:
https://github.com/gatein/gatein-portal/pull/58)
Bugzilla Update: Perform
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
9:22 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
RH Bugzilla Integration updated GTNPORTAL-2463:
-----------------------------------------------
Git Pull Request: https://github.com/gatein/gatein-portal/pull/58 (was:
https://github.com/gatein/gatein-portal/pull/58)
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=835578
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
9:35 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
RH Bugzilla Integration commented on GTNPORTAL-2463:
----------------------------------------------------
mposolda(a)redhat.com changed the Status of [bug
835578|https://bugzilla.redhat.com/show_bug.cgi?id=835578] from ASSIGNED to ON_QA
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
9:35 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
RH Bugzilla Integration commented on GTNPORTAL-2463:
----------------------------------------------------
mposolda(a)redhat.com made a comment on [bug
835578|https://bugzilla.redhat.com/show_bug.cgi?id=835578]
Technical note added. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
New Contents:
CAUSE: Currently hibernate transaction needs to be started for every HTTP request of
anonymous or logged user to EPP. This always needs obtain new DB connection from
connection pool, which is quite expensive operation.
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:
<option>
<name>lazyStartOfHibernateTransaction</name>
<value>false</value>
</option>
We can see that default value is false, so behaviour is same like before (because of
backward compatibility and avoiding of risk).
But for customers, who have problem with performance and DB connection is critical for
them, it would be good to switch this option to "true".
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
9:34 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
Boleslaw Dawidowicz updated GTNPORTAL-2463:
-------------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
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
7:05 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
RH Bugzilla Integration commented on GTNPORTAL-2463:
----------------------------------------------------
Michal Vanco <mvanco(a)redhat.com> changed the Status of [bug
835578|https://bugzilla.redhat.com/show_bug.cgi?id=835578] from ON_QA to VERIFIED
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
7:05 a.m.
[
https://issues.jboss.org/browse/GTNPORTAL-2463?page=com.atlassian.jira.pl...
]
RH Bugzilla Integration commented on GTNPORTAL-2463:
----------------------------------------------------
Michal Vanco <mvanco(a)redhat.com> made a comment on [bug
835578|https://bugzilla.redhat.com/show_bug.cgi?id=835578]
Verified with few performance tests with updated lazyStartOfHibernateTransaction (set to
true), minimum number of idm connections are present during the tests.
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
8:45 p.m.
[
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:
@@ -2,12 +2,12 @@
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:
- <option>
+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>
<name>lazyStartOfHibernateTransaction</name>
<value>false</value>
- </option>
+ </option>]]</programlisting
-We can see that default value is false, so behaviour is same like before (because of
backward compatibility and avoiding of risk).
+<para>We can see that default value is false, so behaviour is same like before
(because of backward compatibility and avoiding of risk).
But for customers, who have problem with performance and DB connection is critical for
them, it would be good to switch this option to "true".
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
8:51 p.m.
[
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
9:06 p.m.
[
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
11:19 p.m.
[
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><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
11:47 p.m.
[
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:
@@ -1,13 +1,9 @@
-CAUSE: Currently hibernate transaction needs to be started for every HTTP request of
anonymous or logged user to EPP. This always needs obtain new DB connection from
connection pool, which is quite expensive operation.
+Hibernate transactions had to be started for each HTTP request from an anonymous or
authenticated user, which in turn required a new database connection from the connection
pool (an expensive operation if it is not required for the request). The fix enables a new
option, "lazyStartOfHibernateTransaction", which is set in
gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml.
-
+</para>
-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)
+<programlisting>
-
+ <option>
-RESULT: In configuration file
gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml
is new option added:</para>
+ <name>lazyStartOfHibernateTransaction</name>
- <programlisting><option>
+ <value>false</value>
- <name>lazyStartOfHibernateTransaction</name>
+ </option>
- <value>false</value>
+</programlisting>
- </option></programlisting>
+<para>If the value is set to true, the Hibernate transaction is started only when
required, and not for every request. The default value is false for
backwards-compatibility.-
-<para>We can see that default value is false, so behaviour is same like before
(because of backward compatibility and avoiding of risk).
-
-But for customers, who have problem with performance and DB connection is critical for
them, it would be good to switch this option to "true".
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
1:22 a.m.
[
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:
@@ -1,9 +1,9 @@
Hibernate transactions had to be started for each HTTP request from an anonymous or
authenticated user, which in turn required a new database connection from the connection
pool (an expensive operation if it is not required for the request). The fix enables a new
option, "lazyStartOfHibernateTransaction", which is set in
gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml.
</para>
<programlisting>
- <option>
- <name>lazyStartOfHibernateTransaction</name>
- <value>false</value>
- </option>
+<option>
+ <name>lazyStartOfHibernateTransaction</name>
+ <value>false</value>
+ </option>
</programlisting>
<para>If the value is set to true, the Hibernate transaction is started only when
required, and not for every request. The default value is false for
backwards-compatibility.
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
4429
days inactive
4506
days old
22 comments
4 participants
participants (4)
-
Boleslaw Dawidowicz (JIRA) -
Marek Posolda (JIRA)
-
Nicolas Filotto (JIRA)
-
RH Bugzilla Integration (JIRA)