Is there a way to figure out which call triggered the event in the first place? i dont have any transactions arround the functionality and if some ajax call triggers a transaction i would rather turn it of or work it out instead of adding a filter to workarround.
The page uses seam remote to update an area of the header of the page. The aera references to values of a session bean which is also marked as transactionamangementtype.bean.
any suggestions on how to find the source for this error?
I also encounter this error on every page load I have. I can't exactly say where it comes from, I didn't always have this error with JBoss 7.1.1 and Seam 3.1.0. It breaks some but not all page functionality, but I still have to debug what it exactly does. Meanwhile, is there any fix for this error already out there?
Edit: I couldn't trace it down in the debugger, unfortunately, but I found out that this problem occurs fare more often in PrimeFaces 3.3-SNAPSHOT than in PrimeFaces 3.2. It does happen in 3.2, too, but only very seldom.
If you want to reproduce this problem, create a simple example project with PrimeFaces 3.3-SNAPSHOT.