Results 1 to 4 of 4

Thread: connectionpool timeout

  1. #1

    Default connectionpool timeout

    So I'm getting lots of timeout exceptions when using pooling with ldapcontextsource.

    I probably have set the
    com.sun.jndi.ldap.connect.pool.timeout to something but the question goes

    -What is the best place to set that?
    Appserver env config , passing -Dcom.sun.jndi.ldap.connect.pool.timeout ..or?

  2. #2
    Join Date
    Mar 2005
    Location
    Landskrona, Sweden
    Posts
    505

    Default

    The pooling configuration properties need to be set as global System properties. As you suggest, placing them in the app server env configuration could be appropriate.
    Mattias Arthursson
    Jayway AB (www.jayway.se)
    Spring-LDAP project member

  3. #3

    Default

    Allright. What about

    <property name="baseEnvironmentProperties">
    <map>
    <entry key="com.sun.jndi.ldap.connect.pool.timeout" value="300000"/>
    </map>
    </property>

    Defined for org.springframework.ldap.support.LdapContextSource ..

    ?

  4. #4
    Join Date
    Mar 2005
    Location
    Landskrona, Sweden
    Posts
    505

    Default

    Quote Originally Posted by kakoni
    Allright. What about

    <property name="baseEnvironmentProperties">
    <map>
    <entry key="com.sun.jndi.ldap.connect.pool.timeout" value="300000"/>
    </map>
    </property>

    Defined for org.springframework.ldap.support.LdapContextSource ..

    ?
    Nope, that would make the property local to the LdapContext created by the ContextSource - the property needs to be System wide.
    Mattias Arthursson
    Jayway AB (www.jayway.se)
    Spring-LDAP project member

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •