We have the business requirement to process messages in the exact order they are coming from the queue. The only way we found to achieve this for MDB is to set the pool size to 1.
But logging in the @PostConstruct method revealed that the MDB is re-created on every message processed. If the MDB contains a couple of injected references, this may incur a performance penalty.
Is this behaviour a bug? IMHO, it is.
Is this planned to be changed with GF v3 singletons?
Cheers, Jörg
[Message sent by forum member 'jthoennes' (jthoennes)]
http://forums.java.net/jive/thread.jspa?messageID=359994