When should I use server session pools and connection consumers?
Ans) WebLogic JMS executes an optional JMS facility for defining a server-managed pool of server sessions. This facility enables an application to process messages simultaneously. A ConnectionConsumer object uses a server session to process received messages. If message traffic is heavy, the connection consumer can load every server session with multiple messages to minimize thread context switching. Multiple connection consumers can share server sessions in a server session pool.