i have seen the issue from jira
http://jira.jboss.org/jira/browse/JBSEAM-183
and it says that
"We need to put some proper thought into handling of concurrent requests in a conversation, and also duplicate form submission (second is probably not an issue, 'cos conversations mainly solve the problem). At least we should catch the standard exception that EJB3 throws from concurrent access to an SFSB."
i am not clear about how and why conversations solve the duplicate form submission. could gavin introduce how seam framework solve it ? beg a description of it , thank you ..
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987310#3987310
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987310
The code you have above, the getSingleCacheLoaderConfig() method generates a block of XML corresponding to a cache loader config (see the chapter on cache loaders in the docs).
Make sure you generate XML that sets __async__ to false. If async is true, flushes will not happen in realtime and will be deferred to a queue and processed by a separate thread. Perhaps you could check the XML that getSingleCacheLoaderConfig() generates?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987308#3987308
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3987308