Why LIOP is missing when iiop_ts is used as the default server engine?

Problem:

Why LIOP is not generated in an IOR when thread-per-session (TSession) is used as the thread policy by the Server?

Resolution:

LIOP not being generated in an IOR when thread_per_session policy is used, is a legacy since the VBC 3.x release.

It would be a significant effort to allow LIOP to be also generated for TSession. The logic for not implementing LIOP with thread_per_session policy is as follows:

The property "vbroker.se.default" is used to specify the default server engine that the orb should be using. When using the ThreadSession as the dispatcher type, you must set the Server Engine to iiop_ts (vbroker.se.default=iiop_ts). By specifying it to the value "iiop_ts", it means that the ORB should be using only the IIOP protocol and so the generation of the LIOP profile in the object reference is omitted.