Hi,
I have a simple method in an EJB which does (or more correctly: would do)
the following:
1. delete a table named aux0_tmp
2. create a table named aux0_tmp
3. delete a table named aux0
4. rename aux0_tmp to aux0
The problem is that step 1 will almost always throw an SQL exception, since
that table will not exist normally. As a consequence, the whole thing does
not commit. (I put step 1. in a separate try-catch, to be able to ignore it,
so steps 2-4 are executed, but they have no result).
On SunRI I changed the transaction attribute from "required" to "supports"
and it worked afterwards. I deployed the same thing on JBoss (2.4.1) and to
my surprise it did not work, I mean the changes did not commit. Shouldn't
such a basic feature (as transaction attributes) have the same effect on two
J2EE servers? Or is there anything I miss here?
/*I do it like this:
// this is in a separate try-catch to be able to ignore it
// I even tried recreating the statement object, and the connection in the
catch branch, but nothing helped
stmt.execute("drop table...");
stmt.execute("create table aux0_tmp as select...");
*/
Cheers,
Janos
--
Jarecsni János
PGP Key Fingerprint: 846A C0CB 7F7D 28FD C82B 0F28 73BA 88DE 2BE7 31AD
Boycott Amazon: http://www.gnu.org/philosophy/amazon.html
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
