On Tue, May 5, 2009 at 5:19 PM, Raymond Feng <[email protected]> wrote:
> > 1) The JMS message listener registered by the Tuscany/SCA JMS binding > provider > 1 is controlled by the behavior of JMS message listener. By the JMS spec, > the session used to create the message consumer serializes the execution of > all message listeners registered with the session. At any time, only one of > the session's message listeners is running. Each session must insure that it > passes messages serially to the listener. This means that a listener > assigned to one or more consumers of the same session can assume that the > onMessage method is not called with the next message until the session has > completed the last call. > The spec questions aside the current Tuscany implementation uses the Tuscany work manager thread pool to read messages off the JMS queue on one thread and dispatch the messages into Tuscany to invoke the service implementation on other threads, so i would have expected the messages get processed concurrently. Is there any chance you could create a small testcase or sample the demonstrates the problem to help debug whats going on? ...ant
