It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,877
×7,469
×6,111
×4,317
×3,954

question asked: Dec 12 '13, 4:17 a.m.
question was seen: 5,852 times
last updated: Dec 12 '13, 8:21 a.m.

Related questions

CLM 4.0.4 and LDAP Configuration - Idle connection timeouts

0
Adrian Daniels (63●1●21●20) | asked Dec 12 '13, 4:17 a.m.
edited Dec 12 '13, 8:13 a.m. by Paul Slauenwhite (8.4k●1●2)
 Hi,
This has been successfully configured using WAS 8.5 to a corporate LDAP server and is working well.

However the LDAP team is looking for evidence that the WAS servers timeout idle LDAP connections.
Apparently they are not seeing any evidence of LDAP connections timing out.

With CLM would we expect to see them timeout ?
Is this solely a function of WAS and not the CLM applications ?

The customer that I am working with tried to set this parameter
-Dcom.sun.jndi.ldap.connect.pool.timeout=20000
but this assumes that LDAP Connection Pools are in use and I do not think that they are.

Any one else experienced this request before ?

Cheers
Adrian
 


One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
sam detweiler (12.5k●6●195●201) | answered Dec 12 '13, 8:21 a.m.
 I think this documents how to configure the LDAP connection timeout in Websphere

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.