We have 2 servers1-is hosting a lotus application
2nd one is hosting dom doc
the 1st server access dom doc using API’s
We are using Domino.Doc Api and its method SetHTTPLogin to log on to Domino.Doc. in a lotus agent. This method opens a port on to the server. Even after closing the library and API the port is not getting closed. The network ports associated with the remote database connection are not released until the HTTP task is shutdown. Show Port TCPIP command shows large amount of ports open to the server.
Problem:
Your organization is hosting a web application that opens databases on remote domino servers programmatically. This is accomplished via a LotusScript, Java, or formula language calls to a server other than the one hosting the web application. The network ports associated with the remote database connection are not released until the HTTP task is shutdown. For example issuing a netstat or a show port tcpip command on your Domino server console shows a large amount of connections open to the server where the remote database is hosted. Once the HTTP task has quit issuing these commands again reveals that these connections have been released.
When network resources are allocated as a consequence of opening a remote database, these connections are only released when the thread that allocated them terminates. In the case of web applications, worker threads belonging to the HTTP task will execute web-triggered agents, Java Servlets (using the Domino Java Servlet Manager), or formula language statements in a web application. HTTP utilizes thread pooling, so these threads are persistent and are only terminated once the HTTP task has been shutdown. Therefore resulting in the scenario above.
I would appreciate if you could provide a solution for the same