Since the data in Table1 effectively doesn't exist until the COMMIT, this is
not going to work. Transaction isolation levels will prevent this regardless of
whether or not they are in the same transactions.
Do you actually want to implement something like this, or is this just a test
scenario
Sure,
I have two enterprise applications (App1 and App2). All EJBs are Container
Managed Transaction with transction attribute required.
App1 and App2 are connected with the same database across different datasources
(DataSource1 and DataSource2). My problem is:
In the database I have two tab
No, it's not full suppport. The driver doesn't support transaction
interleaving, as well as the stop/resume portions of the protocol. The
developer of the XA functionality remarks on this in a variety of areas in the
driver.
Could you describe a bit more about the behavior you are seeing, as w
I'm using PostgreSQL JDBC 3 Driver with PostgreSQL 8.1. In PostgreSQL site says
that supports XA. Is not full suport? I can't use this database for this Task?
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956310#3956310
Reply to the post :
http://
Sure, is here:
jdbc/SIPACDB
true
org.postgresql.xa.PGXADataSource
sipac.info.ufrn.br
5432
db
user
pass
1
10
5000
12
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3
Postgres SQL does not support 'true' XA behavior. Certain aspects of JTA
interaction with the TM (such as suspend/resume) are not available. Were you
informed of something different? Could you post your ds-xml files?
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
