A few months ago, I coded a Domino application (R 5.0.6a) using LEI (R3.1a) for a batch agent and integrated DECS for Domino agents on Oracle 7 connection. While I attempted to optimize connect/disconnect process (using lxslc), I saw that a new feature was implemented: "ConnectionPooling". This new property was set at LCSession level (+ some settings in .INI). I checked the behavior of the connection poll and it seemed not to be working at all. On the Oracle side, we did not see any persistent connection.
Did I miss something in the configuration? Does DECS inherit this feature? Is there any enhancement in LEI R3.2 or LEI RNext?
Connection Pooling works for the life of your agent, but does not work for multiple runs/instances of an agent. That means from the time your agent starts and Uselsx "*lsxlc" is called until the agent terminates. If you are expecting the Connections to remain pooled from one agent call to another it will not. Also, a Connection in the Pool is only reused if the same credentials are used for authentication (same userid, password, db and table/view). DECS manages connections in the same manner and with its activities you can specify the number of Concurrent Connections for each. Please see my previous reply for comments on LEInext.
Dig Deeper on Domino Resources - Part 3
Related Q&A from Scott Lemieux
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.