LDAP connections timeout

Alberto Ocaña da Costa May 14, 2012

Hello,

I have a problem with idle connections to LDAP. Support tell me that I have to include "-Dcom.sun.jndi.ldap.connect.pool.timeout=3" in setenv.sh

My problem is that Tomcat seems to avoid this parameter. After restart I always see in System Properties: com.sun.jndi.ldap.connect.pool.timeout 0

I've tried to add also in setenv.sh other ldap parameters: -Dcom.sun.jndi.ldap.connect.pool.maxsize=20 and -Dcom.sun.jndi.ldap.connect.pool.debug=all but in that case I can see it in System Properties.

Am I missing something?

Regards.

Alberto


1 answer

0 votes
Bruna Griebeler
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 27, 2013

Hi there!

If the tomcat is ignoring the parameter, this usually happens when you are running tomcat as a service.

In this case, please change this value on:HKEY_LOCAL_MACHINE -> SOFTWARE -> Apache Software Foundation -> Procrun 2.0 -> Crowd -> Parameters -> Java -> Options

For more information, please check this documentation.

Jonathan Bent March 17, 2014

Hi Guys,

I am having the same problem but on Linux.

I can't find if this has been addressed in later versions of JIRA.

Cheers

Suggest an answer

Log in or Sign up to answer