Managed JDBC transaction never commited on JBoss 4

[mremond]

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 could have happened from JBoss 3 to JBoss 4 that could cause this behaviour ?

Do you have any idea on something that could need to be changed in the code to fix the problem ? Is there something that could be changed in the configuration file to default to Jboss 3 behaviour regarding JDBC management of transaction ?

Thank you in advance for your help.

--
Mickaël Rémond

[adrian.brock]

Your post makes little very little sense to me.
What does "JDBC transactions that are never commited" mean?
If you mean JTA transactions that can have jdbc local transactions, they either commit/rollback or timeout.

I'm *guessing* you are referring to point 8 on this FAQ?
http://www.jboss.org/wiki/Wiki.jsp?page=JBoss4FAQ

If you expect anybody to look at this further you will need to provide
some more concrete than "IT DOES NOT WORK".