The transaction attributes are set to Supports, I am running in an user
transaction. And I believe that UserTransaction.getStatus should have
returned STATUS_ROLLBACK if the transaction was marked for rollback. So I
think that it's something that the container does when I call commit.
----- Original Message -----
From: "Santosh Kumar" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Wednesday, December 06, 2000 3:02 PM
Subject: Re: Problems when commiting a transaction.
> Check the return value of EJBContext.getRollbackOnly() before you do a
> commit.
> I believe if it is false then you cannot commit it.
> Also let us know how you have set the transaction attributes in the DD.
>
>
> ----- Original Message -----
> From: Tommy Eriksson <[EMAIL PROTECTED]>
> To: Orion-Interest <[EMAIL PROTECTED]>
> Sent: Wednesday, December 06, 2000 6:56 PM
> Subject: Problems when commiting a transaction.
>
>
> > Hi,
> >
> > I have a problem with some transaction stuff. My transactions sometimes
> roll
> > back when I try to commit them. There is no problem during the
transaction
> > i.e. no exceptions get thrown and the UserTransaction.getStatus returns
> > Status.STATUS_ACTIVE before commit is called, but when I call commit I
get
> > the following stack trace
> >
> > javax.transaction.RollbackException
> > at com.evermind.server.ApplicationServerTransaction.commit(JAX)
> > at com.evermind.server.ApplicationServerTransactionManager.commit(JAX)
> > at
> >
>
knut.ejb.session.RequestHandlerBean.handleRequest(RequestHandlerBean.java:28
> > 4)
> > at
> >
>
RequestHandler_StatelessSessionBeanWrapper0.handleRequest(RequestHandler_Sta
> > telessSessionBeanWrapper0.java:39)
> > at knut.servlet.RequestServlet.doPost(RequestServlet.java:244)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java)
> > at com.evermind.server.http.d3.so(JAX)
> > at com.evermind.server.http.d3.sm(JAX)
> > at com.evermind.server.http.ef.su(JAX)
> > at com.evermind.server.http.ef.dn(JAX)
> > at com.evermind.util.f.run(JAX)
> >
> > The problem seems to occur more often if another transaction has just
> > finished. The database log doesn't show anything unusually, only that
the
> > transaction was rolled back.
> >
> > Does anyone know what the requirements (by Orion) are for committing a
> > transaction successfully.
> >
> > I use:
> > Red Hat Linux 6.2
> > Sun JVM 1.3
> > Orion 1.4.0
> > Postgesql 7.0.2
> >
> > /Tommy
> >
> >
> >
>
