But if it gets the synchronization callbacks in a different thread, how should it find the Sessions it bound to the thread earlier? I’m not sure how to get around this. I have noticed that Spring will not close sessions when running an XA transaction between separate weblogic domain instances. Glad to see that things work out. Object; Unknown Sour ce at org. I’ve added a check whether there is a SessionHolder bound to the current thread, only invoking “unbindResource” if found.
|Date Added:||3 March 2008|
|File Size:||39.62 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I’ve added a check whether there is a SessionHolder bound to the current thread, psr532 invoking “unbindResource” if found. Glad to see that things work out. We can close this SPR now as resolved.
After a few days of testing, I have not seen any more errors like the ones described in this SCR. I’m not sure where to go with this, so any suggestions would be greatly appreaciated.
My original post can be found here showing more details: I guess this happens in a new thread, which will break Spring’s Session cleanup. You’ve helped me have Spring live another day!
Sp532 if it gets the synchronization callbacks in a different thread, how should it find the Sessions it bound to the thread earlier?
Please double-check that you Hibernate jars from a single Hibernate sr532 in your classpath, on all your servers. I’m glad that it works for you now, Lou!
Else, the SessionHolder is simply left bound to the thread: So this problem only arises in with remote transaction propagation: Here’s the stack trace: Yes, I agree on the other classpath issues. Juergen, again thank you very much for your support. Upon completion, we see the transaction commit, but in the log we see an IllegalStateException saying it can’t find the session see below.
Index of /download/SmartCardReader/SCM/driver/SPR532
The next data access operation on that thread will simply reuse the same SessionHolder, adding a new Hibernate Session to it. Spring will bind a Hibernate Session to the thread during the data access operations within that transaction, on each participating server. Replace the corresponding file spr523 your Spring 1. Thanks Juergen for looking into this so promptly.
Finally, I see one more type of exception as follows below note: Let me do some more testing especially from the UI and I can let you know for certain, but this certainly looks very, very promising!!
We still got the chance to make the official 1. There has to be a solution for this!
And supporting Hibernate Session synchronization in a remote transaction scenario too is a nice improvement, after all Juergen. I’ll do some research on WebLogic’s remote transaction propagation. It’s empty anyway, as the synchronization code will have removed and closed the transactional Session. My management has been very impressed with your response time and visibilty placed on this critical sp5r32 for us.
SCM SPR – SMART card reader – USB / RS Overview – CNET
It would be great if you could give this a try ASAP, as we’re just about to release 1. It then makes a remote call to an EJB in a separate process in another domain.
How does the WebLogic transaction spr53 actually execute those synchronizations callbacks? This in turn causes all sorts of unexplainable problems like NoSuchElementExceptions, etc.
Actually, there seems to be a pretty straightforward solution: I had to move all the JOS jars to the server’s classpath and this has resolved those issues.