anonymous wrote : P.S. I don't follow your point about table 1 in the JTA spec.
|
| Maybe I read it differently?
|
| Be careful with the "Associated"/"Association Suspended" and note
| where it says XAResource.end rather than XAResource.end(SUCCESS)
Within the EJB method:
1) Connec
You are probably right, but I have not seen it yet at least not completely.
JTA section 3.4.6 fails to specify the flag setting - it simply says xares.end(xid1);
additionally, it does not talk about transaction associations. I am concerned with
the responsibilities of the RA. Again, from sec
First the apology:
anonymous wrote : Configuration/deployment of the connection manager/pool isn't even
in the jca spec so how can it be a compliance issue?
The deployment/configuration of a connection manager/pool was never an issue, I simply
misunderstood what the track-connection-by-tx attri
My concerned is with the XAResource being involved in more than one transaction since
the MC is placed into the connection pool before the XAResource.end(TMSUCCESS) call.
For example, using the following settings for the -service.xml file:
MinSize = 1
MaxSize = 1
BlockingTimeoutMi
IÂm seeing the following XA behavior running our RA in JBOSS 3.2.2:
xa.start()
Connection.close();
xa.end(TMSUSPEND);
ManagedConnection.cleanup()
xa.end(TMSUCCESS);
I wouldnÂt expect to see the xa.end(TMSUCCESS) call after the
ManagedConnection.cleanup. In effect, the cleanup call places the M
