RollbackException using UserTransaction when calling EJB in separate server

Question

I'm using WL 6.1 on Solaris and am calling a stateless session EJB that
          is running in a separate server. I'm looking up the remote EJB using
          JNDI and calling through it's home interface. This works fine but if
          the client code begins a UserTransaction, then calls the EJB that's in
          the separate server, and then calls commit on the transaction, I get the
          following:
          weblogic.transaction.RollbackException: Aborting prepare because some
          resources could not be assigned - with nested exception:
          [javax.transaction.SystemException: Aborting prepare because some
          resources could not be assigned]
          The code that works looks like:
          rgData =
          HomeHolder.ROUTING_GUIDE_MGR_HOME.create().getResourceOptions(qd);
          whereas the code that fails is:
          UserTransaction transaction = new UserTransaction();
          transaction.begin();
          rgData =
          HomeHolder.ROUTING_GUIDE_MGR_HOME.create().getResourceOptions(qd);
          transaction.commit();
          If I put the EJB in the same server as the client, I don't get the
          exception so it seems to be related to running it in the separate server
          and using the UserTransaction. The deployment descriptor of the EJB
          states that it "Supports" transactions.
          Any ideas?
          Thanks,
          John
          

Answer 1

Yes, actually we are using:
          AppServerTransaction transaction = new AppServerTransaction();
          which is a wrapper which does what you say:
          Context ctx = new InitialContext(...); // connect to another WLS
          UserTransaction tx = (UserTransaction)ctx.lookup("java:comp/UserTransaction");
          and our HomeHolder does what you say as well:
          Homexxx home = ctx.lookup(...);
          Any ideas why surrounding the EJB call by a UserTransaction causes a problem when
          committing?
          Thanks,
          John
          Dimitri Rakitine wrote:
          > John Hanna <[email protected]> wrote:
          > > I'm using WL 6.1 on Solaris and am calling a stateless session EJB that
          > > is running in a separate server. I'm looking up the remote EJB using
          > > JNDI and calling through it's home interface. This works fine but if
          > > the client code begins a UserTransaction, then calls the EJB that's in
          > > the separate server, and then calls commit on the transaction, I get the
          > > following:
          >
          > > weblogic.transaction.RollbackException: Aborting prepare because some
          > > resources could not be assigned - with nested exception:
          > > [javax.transaction.SystemException: Aborting prepare because some
          > > resources could not be assigned]
          >
          > > The code that works looks like:
          >
          > > rgData =
          > > HomeHolder.ROUTING_GUIDE_MGR_HOME.create().getResourceOptions(qd);
          >
          > > whereas the code that fails is:
          >
          > > UserTransaction transaction = new UserTransaction();
          >
          > It's an interface, how did this work? Assuming that you do not want
          > distributed tx, does this work:
          >
          > Context ctx = new InitialContext(...); // connect to another WLS
          > UserTransaction tx = (UserTransaction)ctx.lookup("java:comp/UserTransaction");
          > Homexxx home = ctx.lookup(...);
          > tx.begin();
          > home.create().getResourceOptions(qd);
          > tx.commit();
          >
          > ?
          >
          > > transaction.begin();
          > > rgData =
          > > HomeHolder.ROUTING_GUIDE_MGR_HOME.create().getResourceOptions(qd);
          > > transaction.commit();
          >
          > > If I put the EJB in the same server as the client, I don't get the
          > > exception so it seems to be related to running it in the separate server
          > > and using the UserTransaction. The deployment descriptor of the EJB
          > > states that it "Supports" transactions.
          >
          > > Any ideas?
          >
          > > Thanks,
          >
          > > John
          >
          > --
          > Dimitri