Connection pooling is enabled by default in JMS 5.2 (see chapters 7
and 14, class MQConnection of csqzaw07.pdf). If it is required to
disable it for some reason, this can be done by calling
MQConnectionFactory.setUseConnectionPooling(false) before creating
the connection.
This parameter is not supported from the JMSAdmin tool. It can be
set at runtime to alter an existing ConnectionFactory.
"
Questions :-
1. Does this means when we use JMS classes (NOT MQ BASE JAVA) the connection pooling is enabled automatically.
2. The readme suggests that call --MQConnectionFactort.set****
We have created QueueConnectionFactory (using JMS calls, MQConnectionFactory is inherited from QueueConnectionFactory).
Is it allowed in a MQ JMS code to make call to MQ Base Java classes ? I understand that the MQ JMS is written on top of MQ Base Java. But, really can I mix these two.
3. If mixing is allowed, I can refer to MQEnvironment class as well to set my own connection pool.
MQEnvironmanet.setDefaultConnectionManager(myConnMgr)
I have struggling to get answer to these questions. Anyone from Hursley Lab...please
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