UnitOfWork is not committing in JBOSS

Question

Hi All,
     I'm using Toplink in Jboss 4.0.5 and getting the JDBC connection as:
uow = session.acquireUnitOfWork();
DatabaseLogin login = session.getLogin();
conn = (java.sql.Connection)login.connectToDatasource(null);
After performing the transactions its not commiting to the database, instead it gets committed as soon as I stop Jboss server.
Please help me to fix this issue..
Thanks

Answer 1

You should first make sure your session.login is completed before starting to use the session. I am unsure why you are accessing the connection. The connection returned will not necessarily be the one used by TopLink. You should just use the UnitOfWork and then rely on TopLink to properly access the configured data source during the transactional write.
The real issues surrounding TopLink's UnitOfWork and integration with the container is the type of transaction control and the type of data source being used.
JTA: Ensure you have a managed data source where the container controls the transactions. Then ensure you configure TopLink to use external transaction control. The UnitOfwork will be registered with the active JTA transaction and will write its SQL during the JTA call-backs and not on UnitOfWork.commit()
RESOURCE_LOCAL (JDBC): Ensure the data source is not managed (i.e. no JTA). Here the UnitfWork.commit() will cause Toplink to begin the transaction and write your changes.
Doug