LDAP connections timeout


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?



1 answer

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.

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.


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,308 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot