Description:
Symptom
=======
This behaviour can be seen when using Adapter version 5.0.1 and 5.1.0 on all the supported platforms. Even if the adapter configuration contains a session (E.g: DefaultTopicSession) with no services (publication, subscription, Request Response Invocation and Request Response Service), adapter creates as many dispatcher threads and siebel connections as the threads configured for the session. Default is 1.

Impact
======
Other
Un-necessary connections to Siebel Object Manager.

Workaround
==========
Explicitly set the No. of threads to '0' (zero) for the session


Resolution
==========
This issue will be addressed in a future release/Hotfix.
Symptoms:

Cause:

The adapter creates dispatcher threads and siebel connections to the Server for a session even if the session does not contain any adapter services.