9:27 a.m.
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
Reporter: hezimmer
Assigned To: Jesper Pedersen
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying jdbc-driver
is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:31 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=comments#action_12418916 ]
Adrian Brock commented on JBAS-5678:
------------------------------------
"because oracle jdbc commits on close."
That's madness. What's the point of setAutocommit(false)
if the jdbc driver is going to commit silently anyway? :-)
Anyway, after some research I found this addition to the javadocs in JDK6 (JDBC 4)
http://java.sun.com/javase/6/docs/api/java/sql/Connection.html#close()
"
It is strongly recommended that an application explicitly commits or rolls back an active
transaction prior to calling the close method. If the close method is called and there is
an active transaction, the results are implementation-defined.
"
NOTE: JBoss4 actually implements JDBC 3, but the comment is obviously meant to be
retrospective.
The JavaEE semantics are much better defined. If you don't commit or rollback
after starting a local transaction and close() the connection handle (of any type, not
just a jdbc connection)
you get an error and a rollback is done for you. See JCA-1.5, Section 7.8.1 -
LocalTransactionCleanup
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
Reporter: hezimmer
Assigned To: Jesper Pedersen
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:35 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=comments#action_12418917 ]
Adrian Brock commented on JBAS-5678:
------------------------------------
I'd also question why Oracle is throwing an IllegalArgumentException instead of an
SQLException
but then Oracle are always a law unto themselves.
We treat any RuntimeException as a broken connection,
i.e. the connection is almost certainly no longer in a useable state.
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
Reporter: hezimmer
Assigned To: Jesper Pedersen
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:35 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=all ]
Adrian Brock updated JBAS-5678:
-------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
JBossAS-4.2.3.GA
Assignee: Adrian Brock (was: Jesper Pedersen)
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
Reporter: hezimmer
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:10 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=comments#action_12418920 ]
hezimmer commented on JBAS-5678:
--------------------------------
I fully agree with you, i also don't understand why there's no SQLException
thrown. And as
far as i read different oracle jdbc docs there seems to be no way to disable the
"commit" on close.
As you wrote above about the recommendation in JDK6 (JDBC 4) , so the
implementation will be changed in next JBoss version?
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
Reporter: hezimmer
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:30 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=comments#action_12418922 ]
Adrian Brock commented on JBAS-5678:
------------------------------------
We won't wait until JavaEE6 (JDK4) if JDBC4 says the behaviour was never defined.
Especially if Oracle is doing the "wrong thing".
The patch is as follows if you want to try it.
Index: src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.java
===================================================================
--- src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.java (revision
74899)
+++ src/main/org/jboss/resource/adapter/jdbc/BaseWrapperManagedConnection.java (working
copy)
@@ -222,20 +222,30 @@
public void destroy() throws ResourceException
{
synchronized (stateLock)
{
destroyed = true;
}
cleanup();
try
{
+ // See JBAS-5678
+ if (underlyingAutoCommit == false)
+ con.rollback();
+ }
+ catch (SQLException ignored)
+ {
+ getLog().trace("Ignored error during rollback: ", ignored);
+ }
+ try
+ {
con.close();
}
catch (SQLException ignored)
{
getLog().trace("Ignored error during close: ", ignored);
}
}
public boolean checkValid()
{
I'm ignoring the SQLException because in most cases it WILL fail.
i.e. the connection is really broken during the destroy() attempt.
(and who cares about an error during a close anyway :-)
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
Reporter: hezimmer
Assigned To: Adrian Brock
Fix For: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:32 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=comments#action_12418923 ]
Adrian Brock commented on JBAS-5678:
------------------------------------
- We won't wait until JavaEE6 (JDK4) if JDBC4 says the behaviour was never defined.
+ We won't wait until JavaEE6 (JDBC4) if JDBC4 says the behaviour was never defined.
JDBC4 is part of JDK6 and the future (unfinished) JavaEE6
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
Reporter: hezimmer
Assigned To: Adrian Brock
Fix For: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:13 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=comments#action_12418931 ]
hezimmer commented on JBAS-5678:
--------------------------------
Hi Adrian,
thanks for the code snippet and for your very fast feedback. I will try this tomorrow when
i am back in office. I think this
change solves the problem of commiting data which have to be rolled back and not to be
persisted in database,
so it maybe solve the main problem.
But i think there still will be an problem after that (i have to try it tomorrow), because
the connection will be closed
at jdbc level before the "container" got the exception (i think this behavior
isn't changed with this bugfix or is it?) so before
the exception is propagated up to the local managed transaction. So in my opinion
LocalManagedTransaction
getLocalTransaction().rollback() will fail with an exception. Let me try it tomorrow, i
will send an response as soon as
possible.
Thanks,
Heiko
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
Reporter: hezimmer
Assigned To: Adrian Brock
Fix For: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:16 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=all ]
Adrian Brock closed JBAS-5678.
------------------------------
Resolution: Done
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
Reporter: hezimmer
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:25 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=comments#action_12418935 ]
Adrian Brock commented on JBAS-5678:
------------------------------------
"
But i think there still will be an problem after that (i have to try it tomorrow), because
the connection will be closed
at jdbc level before the "container" got the exception (i think this behavior
isn't changed with this bugfix or is it?) so before
the exception is propagated up to the local managed transaction. So in my opinion
LocalManagedTransaction
getLocalTransaction().rollback() will fail with an exception.
"
So what? The real connection is already closed and that jdbc transaction rolled back.
More likely, is a Tx commit which will lead to getLocalTransaction().commit()
We want that to fail since there's no way we can complete the transaction with
a broken transactional resource.
If there's another related issue, it's providing some kind hack to map
Oracle's incorrect
IllegalArgumentException to a proper SQLException, so we don't close
the connection unnecessarily.
But those are discussions for the forums, not this bug report.
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
Reporter: hezimmer
Assigned To: Adrian Brock
Fix For: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:13 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-5678) closed jdbc connection before transaction rollback is called
[ http://jira.jboss.com/jira/browse/JBAS-5678?page=comments#action_12419043 ]
hezimmer commented on JBAS-5678:
--------------------------------
Ok, i've tested it, works fine as expected.
Thanks !
closed jdbc connection before transaction rollback is called
------------------------------------------------------------
Key: JBAS-5678
URL: http://jira.jboss.com/jira/browse/JBAS-5678
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JCA service
Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.1.GA
Reporter: hezimmer
Assigned To: Adrian Brock
Fix For: JBossAS-5.0.0.CR1, JBossAS-4.2.3.GA
Database connection is closed before the transaction handler is able to initiate an
rollback on this connection.
Please take a look at forum entry:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137613
Inside WrappedPreparedStatement method setDouble the Exception from underlying
jdbc-driver is thrown. In case of this example
with Double.NaN as parameter value, Oracle causes an IllegalArgumentException instead of
an SQLException.
Because of that BaseWrapperManagedConnection method connectionError is called:
Code:
void connectionError(Throwable t)
{
if (t instanceof SQLException == false || mcf.isExceptionFatal((SQLException) t))
broadcastConnectionError(t);
}
This Throwable isn't an instance of SQLException so it seems to be an
connection error and broadcastConnectionError is called which causes
unregisterConnections and so the connection on jdbc level is closed
without rollback. Because of that the insert1 statement is commited
because oracle jdbc commits on close. So the transaction handling is not correct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6604
days inactive
6605
days old
10 comments
2 participants
participants (2)
-
Adrian Brock (JIRA) -
hezimmer (JIRA)