|
From: <jue...@we...> - 2004-12-09 09:41:39
|
Does someone have experience with using Spring's JTA synchronization, in = particular the Hibernate Session synchronization, in a remote = transaction propagation scenario? That is, one server starts and ends = the transaction but the actual data access happens on other servers that = participate in the transaction. The problem is that the synchronization callbacks get executed on each = server, but in a different thread than the one that performed the data = access (triggered by JTA commit, which sends a remote call to each = participating server to execute the synchronizations). So Spring's = synchronization implementation can't find the thread-bound Hibernate = Session anymore, which leads to an IllegalStateException. Have a look at the corresponding JIRA issue: http://opensource.atlassian.com/projects/spring/browse/SPR-532 Any input is greatly appreciated! =20 Juergen |