Ok, so Seam applies the SynchronisationInterceptor to session scoped components always,
and the timeout is set to 1000ms by default. So I would guess you see this exception under
heavy load of some sort... This has been the case since Seam 1.1
Does the component need to be session scoped? If so, increase the timeout.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099384#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...