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

This widget could not be displayed.

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 Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

144 views 2 0
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