thanks norman and amitev for your replies. norman, when double-clicking i can see (using firebug) that two requests are being sent to the application server before any response is received. furthermore, i don't see any errors in the server log that would suggest a double insert/optimistic locking. yet i still get the same "the conversation ended, timed out, or was processing another request" error message. in this particular case, i'm posting back to the same page in the context of a long-running conversation (simple "save" functonality that does not navigate away). i had been setting no-cache http headers to force refresh of pages (via a JSF phase listener), but i disabled these headers thinking that perhaps they are complicating things. the one other thing that's odd is that i can see that even with single-click requests, action methods are being called twice. however, this has been the case for a while and we haven't had any other problems (e.g. optimistic locking) as a result. we are using keep-alive connections, but i wouldn't think that should have any impact. just as a sanity check, if i am seeing multiple requests from the browser before any response, would you expect the error message i'm seeing? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4081110#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...