Looks to me like this is going to be more efficient in an environment where you have a connection pool and are possibly using a different connection from the pool for each message. Ideal for a J2EE environment yes?
I think so.
If the app doesn't want to close(disconnect) their Qmgr connection for each message(or atleast for every couple of msgs) due to performance implications, the CCDT is not a good solution for load balancing. It can be used for high availability.
Joined: 05 Jan 2008 Posts: 9475 Location: US: west coast, almost. Otherwise, enroute.
It is also possible for a client application to MQCONNect to two qmgrs; then the app could decide which queue the message should next go. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum