On 26.08.2015 06:20, Ryan Cuprak wrote:
> Hello,
> I have a couple of suggested ideas for JMS 2.1 from challenges that I ran into:
>
> 1. Singleton MDB
> Recently I was working on a project where I needed a “singleton" MDB reading off of a queue. It is a long story why this was necessary. In GF I configured the bean so that the pool size was 1. However, the container would create and destroy the bean at random (perhaps a bug). The postConstruct method would take upwards of 30 seconds to initialize which resulted in a performance problem. I felt that configuring an MDB pool to have one instance was a bit of a hack. It would be nice to have a "singleton MDB" construct.
+1
Currently the size of the MDB pool limits the level of parallelism you
can have for MDB processing. However for many use cases a single MDB
processing multiple requests in parallel (like a servlet) is fine. For
example we move all our session beans to singleton beans with EE 6.
Cheers
Philippe