Hello,
I am trying to run the Kaon Open Source application on JBoss 4.0. Deployement
is correct but fails to run correctly.
After more investigation, it happens that the problem comes from JDBC
transactions that are never commited.
I was wondering what changes in JDBC managed transaction
[EMAIL PROTECTED] wrote : This is not JBoss-specific behaviour, this is the
spec. auto-commit is set to false in a managed environment. I think, you should
be able to reproduce this with pure JDBC standalone app and find out what's
wrong.
I know.
Something in the application prevent it from
Hello,
I have the same problem with JBoss 4.0.1 latest Release Candidate and
PostgreSQL 8.0. If I do a select after the insert, I see the content of the
table. However, the content is never commited. I was wondering what have change
between Jboss 3.2 and Jboss 4.0 that could require some
[EMAIL PROTECTED] wrote : You should not touch auto-commit in a managed
environment. Application server will commit local transaction when the global
one is committed.
Ok. That what I thought. JBoss is acting as a wrapper regarding JDBC activity
and transactions.
Now, what I would like to
I am encountering the same problem. Insert of data (used with prepared
statement) do not end up in the database.
Do you have found any answer on your problem ?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3858848#3858848
Reply to the post :
I was wondering if JBoss 4.0 was not doing things in by back with some kind of
optimisation-related interceptors. Could the problem be related to prepared
statement pooling ? Has the behaviour regarding prepared statement changed
between JBoss 3.x and JBoss 4 ?
View the original post :
