We ran into the same problem until we did the following: 1. Upgrade Tapestry to 3.0.3 (there is reported bug recovering from errors) 2. Take off all transaction stuff (open/commit/rollback) from queries. Only use transactions when you modify the database. 3. Tune parameteres in containers (JBoss/Tomcat) specially for transactions. There are some defaults that cause problems.
Hope this help, JAVIER SANCHEZ. On 5/6/05, Patrick Yip <[EMAIL PROTECTED]> wrote: > I keep getting this error: JTATransaction Could not register > Synchronization. > > And I can't find the cause of it. > Question: will this cause the problem? > > I created an object from a hibernate session and then set it as a > property on the next page > The hibernate session is closed immediately in the current page before > activating the next page. > When I continue on the next page and start using the object reference I > set earlier, would this cause the above error? > > Any comment is greatly appreciated. > -Patrick > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
