I've searched for some clear explanation about the difference between connection and session attributes in mts_dispatchers but am still not clear about the differences.
It looks like session means the maximum number of concurrent user processes that can connect to a dispatcher while connection attribute means the maximum number of concurrent connections that can be made to the instance via the dispatcher. Also, connection attribute should be less than the session attribute.
Can someone give me an example to distinguish the differences?
Connections is the number of physical connections to the dispatcher. Sessions is the number of users that can be logged in.
In a regular MTS Setup, you would have one connection for each session. When you used pooling or multiplexing, you could have multiple sessions SHARING one physical connection. This is where you would want more sessions than connections.