Resolution:
Description:
==========
When a JMS Queue Sender activity is located inside a looping group, and it sends a JMS message at every group iteration, does the JMS Queue Sender instantiate a new Session object for each iteration?

Environment:
===========
All versions of BW
All OS

Resolution:
==========
The JMS Queue Sender activity uses the same session object for all iterations. To confirm this,  you can enable EMS server tracing by executing the following command on the EMS admin console::

set server client_trace=true

You will see the following trace in the Designer console. It shows that three messages are sent out using the same connection object and session object.

2010-01-29 14:32:46 [32669556 JobCourier0] [TIBCO EMS]: [J] QueueConnection Create QueueSession conn=14 sess=19 transacted=false ackmode=1
2010-01-29 14:32:46 [32669556 JobCourier0] [TIBCO EMS]: [J] QueueSession Create QueueSender conn=14 sess=19 prod=14 dest={not set} type={not set}
2010-01-29 14:32:46 [32669556 JobCourier0] [TIBCO EMS]: [J] QueueSender Send conn=14 sess=19 prod=14 dest=test.1 msgid=ID:EMS-SERVER.1BD84B63617F13:14 dlvmode=2 pri=4 ttl=0
2010-01-29 14:32:47 [32669556 JobCourier0] [TIBCO EMS]: [J] QueueSender Send conn=14 sess=19 prod=14 dest=test.1 msgid=ID:EMS-SERVER.1BD84B63617F13:15 dlvmode=2 pri=4 ttl=0
2010-01-29 14:32:47 [32669556 JobCourier0] [TIBCO EMS]: [J] QueueSender Send conn=14 sess=19 prod=14 dest=test.1 msgid=ID:EMS-SERVER.1BD84B63617F13:16 dlvmode=2 pri=4 ttl=02