Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1942

Investigate AD Connectivity issues


    • Icon: Suggestion Suggestion
    • Resolution: Not a bug
    • None
    • None
    • None
    • AD 2003
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      After our 2.0 release, the javax.naming.ServiceUnavailableException has become more common.

      As a workaround we've been suggesting the following configuration in the Crowd JAVA_OPTS (apache-tomcat/bin/setenv.sh).


      The fact that it has been working, points that the problem may be in the connection pool (or connections individually).

      Another workaround that solved the problem was to start 'TCPMon' on AD-Server and listens on port 390 and pass the data to port 389 (use x.x.x.x:390 as URL in the Crowd-Directory Setup).

      Unfortunately, I couldn't reproduce the problem locally.

            Unassigned Unassigned
            rbattaglin Renan Battaglin
            2 Vote for this issue
            5 Start watching this issue