conversation ended unexpectantly

[gothmog]

Hi,

If I click randomly around my application especially before ajax requests have completed, I will consistently get the following:

sourceId=null[severity=(WARN 1), summary=(The conversation ended, timed out or was processing another request), detail=(The conversation ended, timed out or was processing another request)]

After which point my app stops functioning correctly until I move away from the page.

This only happens when I madly click around on a heavy ajax page.

Any ideas?

Troy

[constantin.cash]

If you using ajax4jsf, use queue. If simulate a queue.

Or use stateless beans, you stateful session beans are not thread save.

[gothmog]

ok, I'm using richfaces and simple pojos, no SLSB or SFSB. How does queue work?

[constantin.cash]

http://labs.jboss.com/file-access/default/members/jbossrichfaces/freezone/docs/devguide/en/html/RichFacesComponentsLibrary.html

some of tags have a attribute "eventsQueue"

[gothmog]

I came across that, but it doesn't really make any sense to me

Name of requests queue to avoid send next request before complete other from same event. Can be used to reduce number of requests of frequently events (key press, mouse move etc.)

Are there any examples floating around on how to use this feature?

[pmuir]

I wrote this up in the Seam docs for Seam2. Take a look, it mostly applies to Seam 1 as well.

[pmuir]

http://docs.jboss.org/seam/2.0.0.GA/reference/en/html/conversations.html#d0e5062

[tim_ph]

Now, that explains it. I've been working around this problem for a long time. Finally, figure out eventsQueue is the only thing that helps. Not 100% though. These actions are just update and validate field data, but result has got into timeout almost every time unless you enter a value, sip some tea, then hit the button.
I just read the new document. That definitely will help.
Thanks, Pete.