Jms : accessing sessions through pools

Question

Quite new to jms
I have configured WAS5.1 for accessing MQ queues through jms api
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "corbaloc:iiop:127.0.0.1:2809");
InitialContext ic = new InitialContext(env);
setQcf((QueueConnectionFactory) ic.lookup(qcfName));
setRequestQ((Queue) ic.lookup(requestQName));
setResponseQ((Queue) ic.lookup(responseQName));
setTimeOut(timeOut);
ic.close();
jmsCon = (qcf.createQueueConnection());
jmsCon.start();
session = jmsCon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
Confused if, above code fetching sessions from session pool which i suppose WAS have prepared, as I hav configured the qcf with 250,300 (min,max) no. of sessions through console
Please suggest any corrections to the above code

Answer 1

valon,
This is indeed a tricky one. You are correct that a transaction is started whenever you do any selects that touch a remote object. The problem that I see is that even if you were somehow able to execute a commit after every SELECT statement, the transaction always executes in the context of an application module - if you committed the transaction, you'd also commit any outstanding transaction going on in the AM at the time. In general, this would be a bad thing, although you may be able to ensure that it is OK for your specific use case. I did a quick scan of the APIs to see if I could locate any method that you could possibly override, but didn't locate anything that looked promising.
John