Hello,

I have a problem with a transaction and particularly the transaction mode
when i open a transaction with those instructions to make an insert operation

session = sessionFactory.openSession();
transaction = session.beginTransaction();

I have this message about the transaction mode which said we should be in an unchained transaction mode.
What can i do with the connection to resolve this kind of problem?

- could not insert: [com.reuters.kplus.ssdb.entities.Country#130632]
com.sybase.jdbc2.jdbc.SybSQLException: Stored procedure 'DataMvts_insert' may be run only in unchained transaction mode. The 'SET CHAINED OFF' command will cause the current session to use unchained transaction mode.

Ooops, i forgot to indicate that this only happens with Sybase ASE (12.5).
It works fine with MySQL.

I will welcome any suggestions.
Alexis

This is very DB specific,
Did you try to add SET CHAINED OFF in your stored proc ?

I would probably agree with your proposition and i thank you but
the problem remains because i cannot change the stored proc for a few reason there are too many stored proc and we can't do it because of our product taht does not give enough flexibility.

Well, if your stored procedures can't run inside of a plain jdbc transaction provided by the JDBC driver for your database, this can't be hibernates problem. Either change your stored procedures or make your db vendor remove that restriction.

We made a plain JDBC sample and it works fine.
Playing with it, we managed to figure out that the previous error to occured if our insertion operation was done within a transaction. The transaction is started by calling setAutoCommit(false) before doing the insertion (the insertion operation trigger a stored procedure).

Going back to our hibernate sample, we managed to remove the error by removing call to session.beginTransaction() & session.commit().

While this works, it does not allows transaction. We found the following tips that provides another solutions (changing the stored procedure execution mode constraint):

http://swssun00.isbe.ch/docs/java/jConn ... EADING5-89

Any other solutions is welcome.

Alexis

Transaction boundaries are probably set in your stored proc boundaries.
Hum, that's sucks.

Any scripting adding 'SET CHAINED OFF' automaticaly in your SP ?