Back to bug 793816
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Thomas Heute | 2012-01-13 13:29:11 UTC | Assignee | theute+bot | mposolda |
| hfnukal | 2012-01-26 11:50:35 UTC | Target Release | 5.2.x | |
| Thomas Heute | 2012-06-06 08:48:06 UTC | Status | NEW | ON_QA |
| Target Release | 5.2.x | 5.2.2.ER01 | ||
| CC | theute | |||
| Michal Vanco | 2012-07-17 17:32:24 UTC | Status | ON_QA | ASSIGNED |
| Target Release | 5.2.2.ER01 | 5.2.2.CR01 | ||
| CC | mvanco | |||
| hfnukal | 2012-07-24 11:38:31 UTC | Target Release | 5.2.2.CR01 | 5.2.x |
| CC | hfnukal | |||
| hfnukal | 2012-07-24 11:41:41 UTC | Target Release | 5.2.x | 5.2.2.ER02 |
| Boleslaw Dawidowicz | 2012-07-27 11:21:27 UTC | Target Release | 5.2.2.ER02 | 5.2.2.CR01 |
| CC | bdawidow | |||
| Trang Vu | 2012-07-29 16:23:06 UTC | CC | trangvh | |
| Boleslaw Dawidowicz | 2012-07-31 13:50:21 UTC | Target Release | 5.2.2.CR01 | 5.2.x |
| Jared MORGAN | 2012-09-02 22:35:06 UTC | Depends On | 841320, 840917 | |
| Blocks | 834635 | |||
| CC | vramik | |||
| Doc Text | CAUSE: EPP didn't support JTA in previous releases. There are some problems related to it, especially the fact that without JTA support, there is need to obtain DB connection for IDM database for each HTTP request of logged user. In some environments this may cause problems related to lack of DB connections and worse performance. FIX: It's possible to configure EPP for JTA support which can be useful especially for reduce number of DB connections opened against IDM database. JTA is not enabled by default so customer need to do couple of steps to enable it. These steps are described in wiki page https://community.jboss.org/wiki/JTAIntegrationWithGateIn NOTE: Described steps on wiki page are related to GateIn. In EPP some steps are slightly different.Especially: - In EPP there are different names of datasources "gatein-idm" and "gatein-jcr" instead of the names "jdbcidm" and "jdbcjcr" which are used in GateIn and are used on wiki page. - Step 2 (JCR configuration of DataSourceProvider) is not needed because it's enabled by default in EPP. | The platform did not support JTA in previous releases. There were some problems related to it, particularly the fact that without JTA support there was a need to obtain DB connection for IDM database for each HTTP request of logged user. In some environments, this requirement may cause problems related to lack of DB connections and, introduce performance issues. To work around the issue it is possible to configure the platform for JTA support. Configuring JTA support may reduce the number of DB connections opened against an IDM database. JTA is disabled by default. To enable JTA support follow the procedure in https://community.jboss.org/wiki/JTAIntegrationWithGateIn, while observing the following caveats to the procedure: when reading the process replace "gatein-idm" and "gatein-jcr" with "jdbcidm" and "jdbcjcr"; step 2 (JCR configuration of DataSourceProvider) is not needed because it's enabled by default in EPP. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Martin Weiler | 2013-04-23 13:56:02 UTC | Target Release | 5.2.x | --- |
| CC | epp-bugs | |||
| Component | Portal | Portal | ||
| Version | 5.1.0.GA | 6.0.0 | ||
| Assignee | mposolda | jbpapp-maint | ||
| Product | JBoss Enterprise Portal Platform 5 | JBoss Enterprise Portal Platform 6 | ||
| Simon Green | 2013-04-30 23:36:50 UTC | CC | mvanco | mvecera |
| Boleslaw Dawidowicz | 2013-07-26 09:38:30 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2013-07-26 05:38:30 UTC |
Back to bug 793816