close wem connection
Is there a need to close the wem connection when accessing wem via the api?
We have recently increased the usage of this and heap size is increasing. At this point just guessing the cause, but I am wondering it there is something here we are leaving open.
AuthnBundle authnBundle = buildAuthBundle(config);logger.info("WEM Connection to: " + authnBundle.getHost());try { final LoginMgr loginMgr = new LoginMgr(); loginMgr.login(authnBundle);
Comments
-
If you are doing it in a batch program you just need to call this only once at the beginning.
Please don’t call this in a loop.
Best Regards
Qutub
From: eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com>
Sent: Monday, March 18, 2019 5:18 PM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: close wem connectionPosted bylauren.quintanilla@wellsfargo.com (Quintanilla, Lauren) On 03/18/2019 05:17 PM
Is there a need to close the wem connection when accessing wem via the api?
We have recently increased the usage of this and heap size is increasing. At this point just guessing the cause, but I am wondering it there is something here we are leaving open.
AuthnBundle authnBundle = buildAuthBundle(config);
logger.info("WEM Connection to: " + authnBundle.getHost());
try {
final LoginMgr loginMgr = new LoginMgr();
loginMgr.login(authnBundle);
[To post a comment, use the normal reply function]
Forum:
Content Server:
0
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 153 General Questions
- 148 Thrust Services
- 57 Developer Hackathon
- 37 Thrust Studio
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 32 eDOCS
- 190 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 10 XM Fax
- Follow Categories