Bug 780996 (SOA-3473) - It is not possible to use XA transactions with SOA platform + Postgress 8.4 using implicit Postgress settings
Summary: It is not possible to use XA transactions with SOA platform + Postgress 8.4 u...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3473
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation
Version: 5.2.0.ER4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.2.0 GA
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-11 13:50 UTC by Filip Nguyen
Modified: 2011-11-15 03:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-15 03:45:36 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3473 0 None None None Never

Description Filip Nguyen 2011-10-11 13:50:15 UTC
project_key: SOA

PRD for SOA P 5.2 requires RHEL 5.5/6 PostgreSQL config in version 8.4 to work "(as delivered)". 

In Postgress 8.4 implicit settings of max_prepared_transactions is [changed to 0 | http://www.postgresql.org/docs/8.4/static/runtime-config-resource.html#GUC-MAX-PREPARED-TRANSACTIONS] that means XA transactions are *turned off*.

That means SOA-P is not certifiable with this configuration.

Comment 1 Van Halbert 2011-10-11 14:09:38 UTC
Curious, isn't this a consistent XA issue with every one of our products in this configuration?

Comment 2 tcunning 2011-10-11 18:13:01 UTC
David, I think we need something in the release notes like : 

"In order to use XA transactions with a PostgreSQL 8.4 backing store, you will need to change the default value of max_prepare_transactions in your postgresql.conf file.    As of 8.4, the default setting for this property is 0.     Please choose a number of prepared transactions equal to or greater the maximum number of connections specified in your postgresql.conf - so that there is a transaction available per connection.

Comment 3 David Le Sage 2011-10-20 00:08:29 UTC
Release Notes Docs Status: Added: Documented as Known Issue
Writer: Added: dlesage
Release Notes Text: Added: In order to use XA transactions with a PostgreSQL 8.4 backing store, you will need to change the default value of max_prepare_transactions in your postgresql.conf file. As of 8.4, the default setting for this property is 0. Please choose a number of prepared transactions equal to or greater the maximum number of connections specified in your postgresql.conf - so that there is a transaction available per connection.


Comment 4 David Le Sage 2011-10-20 00:08:56 UTC
Release Notes Text: Removed: In order to use XA transactions with a PostgreSQL 8.4 backing store, you will need to change the default value of max_prepare_transactions in your postgresql.conf file. As of 8.4, the default setting for this property is 0. Please choose a number of prepared transactions equal to or greater the maximum number of connections specified in your postgresql.conf - so that there is a transaction available per connection. Added: https://issues.jboss.org/browse/SOA-3473

In order to use XA transactions with a PostgreSQL 8.4 backing store, you will need to change the default value of max_prepare_transactions in your postgresql.conf file. As of 8.4, the default setting for this property is 0. Please choose a number of prepared transactions equal to or greater the maximum number of connections specified in your postgresql.conf - so that there is a transaction available per connection.


Comment 5 David Le Sage 2011-10-20 00:09:31 UTC
Thanks for that detailed note, Tom.  I have put it in the Release Notes largely verbatim.

Comment 6 Len DiMaggio 2011-11-14 14:10:58 UTC
David - this is not in the release notes here:

http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5/html-single/5.2.0_Release_Notes/index.html

Can you check ASAP??  Thx!



Note You need to log in before you can comment on or make changes to this bug.