I've been running into sporadic issues with an enterprise app that hits Livelink constantly through LAPI. The following are some articles I found. None of them fixed my issue though because we've actually attempted the resolutions two years ago to fix ANOTHER LAPI connection issue. F%$K!!!
Article Number: 3500936 - Why do I get LAPI connectivity issues intermittently?
- Running massive amounts LAPI transactions result in "Could not access server" error.
Article Number: 15090633 - LAPI - GetObjectAttributesEx Function Executes Increasingly Slowly When Called Repeatedly
- Repetitive usage of the function results in degrading performance.
Article Number: 3496785 - Keep Livelink Socket Backlog In Mind When Creating Multi-Threaded LAPI programs
- LAPI calls randomly fail in Multi-threaded applications if the number of application threads are greater than the number of Livelink server threads
Article Number: 3501616 - Getting sporadic LAPI errors (Pooling LLSession objects)
- There is no apparent advantage to pooling LLSession objects
1 comments:
LAPI is about client-server network communication. You should anticipate overloaded server and other network problems in your design by the proper error handling and/or graceful recovery.
Running multiple threads against a single LL front-end usually doesn't bring much. If you want to run many threads you should consider using more LL front-ends with a load-balancer, for example.
Post a Comment