, but unfortunately has not find some difference
> yet...
>
> Thanks a lot
> xuhongbo
>
>
> -----origin-----
> sender: Jack Cai [mailto:greensi...@gmail.com]
> date: 2009/12/30 11:45
> receiver: user@geronimo.apache.org
> subject: Re: Reply: Cannot using Geronimo to
@gmail.com]
date: 2009/12/30 11:45
receiver: user@geronimo.apache.org
subject: Re: Reply: Cannot using Geronimo to execute bean-managed
transaction with oracle transaction more than once, but Glassfish does
Can you try to use the tranql-connector-oracle-xa or
tranql-connector-oracle-local to do the te
it failure; but
> maybe it would give some other useful things help to find out the reason.
>
> Thanks a lot
> xuhongbo
>
> -origin -
> sender: David Jencks [mailto:david_jen...@yahoo.com]
> date: 2009/12/30 1:43
> receiver: user@geronimo.apache.org
> subject:
t would give some other useful things help to find out the reason.
Thanks a lot
xuhongbo
-origin -----
sender: David Jencks [mailto:david_jen...@yahoo.com]
date: 2009/12/30 1:43
receiver: user@geronimo.apache.org
subject: Re: Reply: Cannot using Geronimo to execute bean-managed
transaction w
In the future it would be great if you could only post to one mailing
list.
I'm not sure what is wrong yet, however you should never try to set
the autocommit state of a connection that is enlisted in a jta
transaction. Enlisting and delisting the XAConnection will result in
the autocomm
Hi:
Yet I haven't find the real reason , I have noticed another thing
about the problem;
The original test program will throw exception while transaction
commit; but if I comment the statement "connection.setAutoCommit(false); ".
the exception will throws while execute prepare sta
