Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
How does Livelink manage the database connection?
Thomas_Weng
I see from database that there are multiple database connections when Livelink starts up. Is there a database connection pool in the oscript code? I see there are StartTransaction and EndTransaction method in all the requesthandlers. But they are not used frequently even in the opentext modules. Why?How does Livelink manage the transaction? In rare cases, code that inserts one row in database works fine in llbuilder fails in LLserver. It inserts multiple rows in database. It seems that more than one database connection flush the transaction to database.
Find more posts tagged with
Comments
John Underhill
I can't answer all your questions re: transactions, but a database connection is created for each thread started on LLServer. Typically, 3 to 7. Configured in opentext.ini. When you start the service each logs in, irrespective of any database traffic at that stage. They are not pooled but fixed to the thread that created them.An incoming request is routed to a free thread and processed to it's conclusion on that thread.Of course, Builder only has 1 thread, so it should only have a single connection.If you set debug to it's highest level you can see all the database traffic. This might help diagnose your problem on LLServer.