I guess there should be a business logic BEFORE this line and not after? Are you sure your SFSB doesn't use bean managed transaction demarcation and there isn't any active transaction which spans on several business methods?
The EJB version is 2.0. we have not used the @ Remove . but before the finally block all the transactions have been committed . i understand that somewhere its missing , we did not commit the transaction.
This is a large project , so i'm not able to locate the exact transaction .
Is there any way i can stop the exception. This exception creates big problem in the production .
So you did not try to commit the transaction - can you just get the current transaction from within the method (I guess you can get it from the SessionContext?), commit it (or rollback it) and see the results?
Sorry I can't be of any help - maybe someone with better knowledge could help you.
if you think brussel sprouts are yummy, you should try any other food. And this tiny ad: