Resolution:
This is not a TIBCO BW issue. It is an IBM MQ JMS behaviour.

The behaviour here is, with IBM MQ JMS even if you open/create a JMS session ( not a JMS CONNECTION) the MQ client JMS implementation creates a TCP connection/socket.
This does not happen with other JMS providers like BEA, TIBCO.

TIBCO BW engine creates sessions based on the activities used in the project and also caches a session per engine worker thread for performance reasons. This means initially there would be an increase in sessions and then once all the engine threads have cached the JMS sessions the session count will stabilize and not increase.

Since in IBM MQ each session physically opens a TCP connection IBM MQ customers think BW is using lots of connections. Infact we are not using many CONNECTIONS. we are only creating *sessions* which would eventually stabilize.

Why do we see more JMS connections( TCP connections/sockets) opened by TIBCO BW engine when using IBM MQ as JMS provider?Keywords :- MQ, JMS, BW, connection, session