|
From: Jon T. <jt...@hy...> - 2007-03-19 17:57:59
|
We currently do get a second error, though it appears that it's benign. Of course we are welcoming any patches to clean these types of things up. -- Jon On Mar 19, 2007, at 10:41 AM, Charles Lee wrote: > Reposting for another forums user: > > SessionManager.cleanupSessionInternal is flushing in the finally > clause. If your transaction has already failed, you may get a > second error. Also you no longer have a Transaction at this > point. As suggested, forgoing CMT for Spring configured > interceptors will ease debugging and development all around. > |