i have a problem in my websphere environment.
I set my websphere transaction timeout to : 300 sec.
am locking a record in my data base and try to edit the record from my application(through the browser)
browser is hanging for ever, could you please tell me why ejb is not rolling back the transaction even after crossing 300 seconds?
early reply will be appriciated.
The transaction handling in the EJB is done on the method level, and depending on the transaction attributes you set in the deployment descriptor for that method. If your business method of the EJB is completed its execution before your system hanged, then the changes will be commited to database. otherwise if there is any exception in the execution of the EJB method, then the values are rolled back.
If your session expires in 300 seconds the EJB should be destroyed after that. And there should not be any excetion on that instance after that. check with your deployment descriptors and configurations.