症状

JIRA is using too many or too few LDAP connections and you need to adjust the connection pool. 

診断

You would normally use a third party monitoring tool to determine how your connection pool is being used over time. 

You can inspect JIRA's current settings at: <BASE URL>/plugins/servlet/embedded-crowd/configure/connection-pool/

 The timeout is not accurately reflected on this page. There are options there to configure it, but they don't work.  Other settings are saved correctly.

原因

The only time we have seen a need to adjust this pool is when scripts are authenticating against JIRA and not using cookies.

回避策

You can use Java system properties found in the setenv.sh or setenv.bat file to configure the LDAP connection pool. From http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html:

Here is an example of a command line that sets the maximum pool size to 20, the preferred pool size to 10, and the idle timeout to 5 minutes for pooled connections.

-Dcom.sun.jndi.ldap.connect.pool.maxsize=20 
-Dcom.sun.jndi.ldap.connect.pool.prefsize=10
-Dcom.sun.jndi.ldap.connect.pool.timeout=300000

Please see the above link for exhaustive documentation on this functionality.

 Check out Setting properties and options on startup for more information on setting Java properties.