7 Replies Latest reply on Mar 20, 2009 10:00 AM by Andy Taylor

    caching the initial session created

    Andy Taylor Master

      Currently when we create a new jms connection we only actually create a session if we are authenticating and then we close it once authentication has taken place.

      I'm changing this so that firstly we always authorize and secondly caching the initial session and reusing it for the first actual session created. The only issue is that the initial core session is created with xa, autoCommitSends, autoCommitAcks and preAcknowledge set to false and ackBatchSize set to 0. O though the best thing was to add an extra method to core session to allow these values to be reset.