| The simplest possible implementation of the ServerSessionFactory SPI:
creating a new ServerSession with a new JMS Session every time.
This is the default used by ServerSessionMessageListenerContainer.
The execution of a ServerSession (and its MessageListener) gets delegated
to a TaskExecutor. By default, a SimpleAsyncTaskExecutor will be used,
creating a new Thread for every execution attempt. Alternatives are a
TimerTaskExecutor, sharing a single Thread for the execution of all
ServerSessions, or a TaskExecutor implementation backed by a thread pool.
To reuse JMS Sessions and/or to limit the number of concurrent
ServerSession executions, consider using a pooling ServerSessionFactory:
for example, CommonsPoolServerSessionFactory.
author: Juergen Hoeller since: 2.0 See Also: org.springframework.core.task.TaskExecutor See Also: org.springframework.core.task.SimpleAsyncTaskExecutor See Also: org.springframework.scheduling.timer.TimerTaskExecutor See Also: CommonsPoolServerSessionFactory See Also: ServerSessionMessageListenerContainer |