Are you keeping the session ID and reconnecting by session ID? This does work and we did it for a long time, but it wastes a lot of resources. If you just keep the Application object held in memory and disconnect it only when the user is done with your application you will get a lot better performance, especially if you have a large number of document types and/or keywords. Document types, keywords, and other information are cached in the Application object, and if you keep throwing it away and recreating it this cache has to be rebuilt every time.Even if you do hold the application object in memory, you may still experience a lost connection occasionally, such as the case already mentioned of an app pool recycle.We have the process of acquiring a connection (Application object) isolated in a separate method. Within this method, we get a new Application if we don't have one in memory already. Even if we do have one in memory, we give it a quick check by asking for the Document object by ID of a fixed document ID. In our case, we just use document ID 1. Even if the document ID that you ask for doesn't exist, it won't throw an error. You are just checking to see if the app server is still willing to talk to your Application object. If this fails, you can detect it and establish a new connection (and cache it in memory for the next call) before passing the Application object out to the calling method.
