Re: Reply: Cannot using Geronimo to execute bean-managed transaction with oracle transaction more than once, but Glassfish does

2009-12-30 Thread xuhongbo
, Geronimo do additional things... maybe the difference will be the real reason cause the problem; I have tracked at runtime, 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

Reply: Cannot using Geronimo to execute bean-managed transaction with oracle transaction more than once, but Glassfish does

2009-12-29 Thread xuhongbo
-datasource) is returned? -origin- Sender: xuhongbo [mailto:x...@tongtech.com] Date: 2009/12/29 12:53 Receiver: d...@geronimo.apache.org CC: user@geronimo.apache.org Subject: Cannot using Geronimo to execute bean-managed transaction with oracle transaction more than once, but Glassfish does

Reply: Cannot using Geronimo to execute bean-managed transaction with oracle transaction more than once, but Glassfish does

2009-12-29 Thread xuhongbo
; I thinks this should have no means to the transaction commit 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

Cannot using Geronimo to execute bean-managed transaction with oracle transaction more than once, but Glassfish does

2009-12-28 Thread xuhongbo
Hi: When I using bean managed transaction with oracle-xa , I found that it cannot execute more than once; the first time, things is right and database is update; but if execute once again a oracle- xa-warning and a Geronimo exception occurs; the warning and exception is list at the end

oracle xa datasource cannot commit twice

2009-12-25 Thread xuhongbo
Hi: I am using oracle xa and bean managed transaction in my applicationgeronimo 2.1.4 oracle 9i; In my test ejb, just update a table in a bean-managed user-transaction; The first time , my test ejb works, but if I execute the ejb twice, the oracle-xa-transaction will failed; In the