Conversationの並行性制御

SeamではConversationへのリクエストはシリアライズされますし、キューイングのタイムアウトを設定できます。Seam 2.0.2リファレンスマニュアルの該当部分を引用します。

4.1.10. Concurrency model

(中略)

The Seam session and application contexts are multithreaded. Seam will allow concurrent requests in a context to be processed concurrently. The event and page contexts are by nature single threaded. The business process context is strictly speaking multi-threaded, but in practice concurrency is sufficiently rare that this fact may be disregarded most of the time. Finally, Seam enforces a single thread per conversation per process model for the conversation context by serializing concurrent requests in the same long-running conversation context.

7.11. Concurrent calls to conversational components

(中略)

Therefore Seam queues the action event for a period of time (the concurrent request timeout); if it can't process the event in time, it creates a temporary conversation and prints out a message to the user to let them know what's going on. It's therefore very important not to flood the server with AJAX events!

We can set a sensible default for the concurrent request timeout (in ms) in components.xml: