Transaction coordination across different domains

[Jorge Ribeiro]

Hi,

I�m having some problems whenever trying to connect applications residing in different WebLogic domains. I have an MDB, using Required as onMessage�s transaction attribute, trying to access a session bean in a different WLS domain. The lookup of the home object is done successfully, but whenever the create method is invoked there is an exception that is thrown, complaining about the transaction coordination. This problem occurs whenever using WLS 9 as host for the MDB. It does not matter if the Session bean is deployed in a WLS 8.1 or 9. If I deploy the MDB in a WLS 8.1 domain then everything works fine (again both if I have the session bean in a WLS 8.1 or 9 domain).
I would expect that all method invocations done in the Session bean would run within a transaction that is coordinated by the first WLS domain, where the MDB resides. But to be honest I do not know if my assumption is valid. Could you please shed some light about what should be the correct behaviour?

Thanks!
Paulo

[Roger Chung-Wee]

Please post your code and DDs.

[Jorge Ribeiro]

I'll post the code tomorrow as I do not have it here with me. But my question is more generic- let's assume that we have application A running on Application Server X and an application B running on Application Server Y. If a bean's method in B, running within a transaction that is coordinated by X, looks up and uses a bean in B, should X and Y be able to communicate in terms of transaction coordination?

[Roger Chung-Wee]

Bean B should indeed run in bean A's transaction context, assuming that the trans attribute is set to Required or Mandatory. If it isn't happening, then something may be wrong with your code or DDs. Or it may be something WebLogic-specific, eg if the data sources are not set up as tx Data Sources.

[ankush purwar]

Yes ,it should be that Server X and server Y will coordinate same transactions. But at least vendor must provide distributed transaction .