JDBC LDAP Timeout

While connecting to our LDAP source using packaged LDAP JDBC driver we receive a timeout error:
7000 : null : com.sunopsis.sql.k: Oracle Data Integrator TimeOut
Re-executing the job helps in most cases, but sometimes timeout problem persists. Any ideas on how can we increase the connection timeout ?
We are still on ODI 10.1.3.2.0
Connection details:
JDBC Driver: com.sunopsis.ldap.jdbc.driver.SnpsLdapDriver
JDBC URL: jdbc:snps:ldap?ldap_url=ldap://server:389/&ldap_password=ENCODEDPASSWORD&ldap_basedn=OU=one,OU=two,OU=three,OU=four,OU=five,DC=SIX,DC=COM&ab=\\fileserver\alias_ldap.txt

Go to odi studio menu-->odi--->user parameters
There you can find to increase the time out time
Oracle Data Integrator Timeout     1000     Timeout used by Oracle Data Integrator for the database connections.

Similar Messages

  • JDBC-LDAP bridge

    We use a directory server to store data. So I tried to add the JDBC-LDAP bridge driver from OpenLDAP/Octetstring as data source. That is working. Testing the connection is successful. The problem is: no tables are retrieved from the data source. With no tables there is no data binding to JSF components.
    Is Sun working on a solution for this?

    thanks.
    i'll first try to get the jdbc:ldap bridge running.
    in the last two weeks i also tried to build the jndi connection on the basis of the jndi tutorial. unsuccessfully.
    maybe i'll get the ldap bridge working.

  • JDBC Wait timeout in WL 7.0

    Hi All,
    We are using the JDBC connection pool in the application and I have
    coinfigured the max connections as 100. Its been observed that, when
    the 101st user request for the connection, pool throws
    ResourceException immediately without waiting any time. Is it possible
    to coinfigure pool in WL 7.0 with wait timeout? if possible how?
    Thank you all,
    Santhosh.

    Joseph Weinstein" <[email protected]> wrote in message
    news:[email protected]..
    Currently there is no way to make the pool waiting. But you can
    easily fix the problem by increasing size of the connection
    pool.So if he increases to 200, and his 201st user logs in and gets the same
    problem?Aparently, if you can not set up a pool to satisfy all requests,
    there is a problem with code/design. We can hardly fight
    programming/design mistakes except may be giving good
    advices.
    The fundamental problem is that the design of his application is retaining
    a pooled JDBC connection indefinitely, spanning multiple interactionsbetween
    a given user and the server. If this is necessary the customer must either
    have a pool with as many connections as he will have concurrent users,I meant exactly that.
    or he should write his application to use direct non-pooled connectionswhich
    he gets from the DBMS driver.Than application will get screwed up using direct driver calls.
    As for me, it doesn' t make big difference. At least using
    pool helped to identify the fact of the problem presence
    quickly.
    < Ideally, the customer can design the application
    like EJBs or good servlets, that get a connection, use it, and return itto the pool,
    all with a single user-server message/response.Sure.
    Regards,
    Slava Imeshev

  • Synchronous JDBC - message timeout

    Hi,
    I have a scenario RFC-XI-JDBC synch. I am getting a message timeout error while trying to post large data volume. Apparently the sync message is geting expired after timeout (default 180 sec).
    I found SAP note 730870 (question 14) suggests to increase the property xiadapter.inbound.timeout.default. However, SAP note 791379 says you should never change this value.
    Is anyone has chaged this value in oreder to optimize performance ? Pls suggest.
    Also pls let me know if you have any other suggestion.

    As per the documentation
    http://help.sap.com/saphelp_nw04s/helpdata/en/29/22ee41c334c717e10000000a155106/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
    You should increase the timeout from 180000(default) to 240000.
    or 240 sec.
    please visit
    Re: MessageExpired because of large amount of data

  • Urgent: Please help: Trusted recon - Sun LDAP - timeout

    Hi Experts,
    I am doing trusted reconciliation with sun ldap using oim 11.1.1.5 bp4.
    LDAP system has around 3 lakh users. so i am planned to do trusted recon in 5 or 6 intervals to get around 50K records each time.
    i tested for 1000 users - no timeout is happening and all users are created perfectly using trusted recon
    when i run for 25K users, i am getting timeout excception below,
    1. It is searching and listing the users, (please chck time)
    recon.schedule.tasks.tcTskIPlanetUserReconciliation : countRecord() : Before search time: Tue Oct 09 13:24:41 KST 2012
    recon.schedule.tasks.tcTskIPlanetUserReconciliation : countRecord() : TotalRecords from LDAP: 22882
    recon.schedule.tasks.tcTskIPlanetUserReconciliation : countRecord() : After search time: Tue Oct 09 15:54:42 KST 2012
    2. Timeout exception
    recon.schedule.tasks.tcTskIPlanetUserReconciliation : pagingBatchingReconciliation() : The searchBase is: ou=XX,ou=XX,o=XX
    pagingBatchingReconciliation() : Problem searching directory: javax.naming.TimeLimitExceededException: [LDAP: error code 3 - Timelimit Exceeded]; Remaining name: ou=XX,ou=XX,o=XX
    In iPlanet User Truseted Recon I gave,
    Abandoned connection timeout - 108000 (seconds)
    Connection pooling supported - false
    Connection wait timeout - 60 (seconds)
    LDAP Connection TimeOut - 3000 (seconds)
    Inactive connection timeout - 60 (seconds)
    Above parameters are good for more than 25K users?
    Please help me...
    Thanks..

    They look good...
    Try to use Connection pooling too if possible...
    Abandoned connection timeout - 108000 (seconds)
    Connection pooling supported - true
    Connection wait timeout - 60 (seconds) --> Increase it to say 90 (seconds)
    LDAP Connection TimeOut - 3000 (seconds) --->
    Inactive connection timeout - 60 (seconds) --> Increase it to 600 (As the default value in the LDAP Server IT Resource Type Definition)
    Alternatively You can rather break your chunks in 20000 records because you are able to fetch 22882 records successfully....

  • OAS 10.1 3.1 0 OC4J JDBC Connection/Timeout settings

    I am fairly new to OAS, and am trying to resolve a intermitent issue,
    I have an OAS 10.1.3.1.0 with a deployed EAR file I was provided by a supplier containing mainly PL/SQL based logic, which configured the OAS to ask a middle tier for a an external to pass data to it via Stored Procedure and then usiing the deployed package connect to an external Oracle DB and insert the data.
    Oas is running on a Windows 2003 platform that has no problems or connectivity problems, how ever intermittenlt the OAS stops uploading data to the external Oracle DB. Some custom external logging details this as a communication at the time it occurs, how ever there are no comms issues. A quick restart of the OAS windows service resolves the issue.
    Apart from upgrading OAS to patch set 5, the only other thing I considered could be causing the issue is how OAS is handling the session timeout or connection pool.
    I can see the following settings for the JDBC connection I am using, I wondered if anyone could advise anything that could be changed? I am not sure the implications on setting the validate connection to True and also not sure why maximum number of connections is set to -1?
    Connections
    Initial size of Connection Cache
    Minimum Number of Connections
    Maximum Number of Connections
    Connection Retry Interval (seconds)
    Maximum Connection Attempts
    Maximum Number of Statements Cached
    Lower Threshold Limit On Pool (%)
    Defaults to 20% of max connections.
    Validate Connection FalseTrue
    Timeouts
    Inactivity Timeout (seconds)
    Time that an unused connection is inactive before it is removed from the pool.
    Wait For Used Connection Timeout (seconds)
    Maximum time to wait for a used connection to be released.
    Max Active Time for a Used Connection (seconds)
    Maximum time a used connection may be active.
    Abandoned Connection Timeout (seconds)
    Enforce Timeout Limits Interval (seconds)
    Any help would be appreciated

    Hi,
    Along with Priya's suggestions, please refer the link below for the details on the parameters.
    http://download.oracle.com/docs/cd/B32110_01/web.1013/b28958/datasrc.htm#CHDCFCHB
    Hope this will help understand all the parameters.
    Also refer,
    What Should Be My Maximum Connection Pool Size? [ID 1061155.1]
    http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html
    Regards,
    Mithun

  • Timestem and jdbc Query Timeout

    hi all,
    i have install timesten on one computer and configure there Query Timeout like This:
    SQLQueryTimeout = 80
    and i have JBoss Application Server on another computer and timesten client.
    i've timesten-xa-ds.xml configuration file configured like this :
    <set-tx-query-timeout>
    <query-timeout>50000</query-timeout>
    <set-tx-query-timeout>
    and when i tryed to execute sql command i get an error:
    14:19:13,342 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: S1000
    14:19:13,344 ERROR [JDBCExceptionReporter] [TimesTen][TimesTen 6.0.4 CLIENT]Query Timeout must be numeric, greater than or equal to 0, and less than the Network Timeout
    14:19:13,346 ERROR [STDERR] javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute query
    14:19:13,346 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:567)
    14:19:13,346 ERROR [STDERR] at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:56)
    14:19:13,347 ERROR [STDERR] at com.magti.businesslayer.ejb3Fasade.srvprov.MobileServiceFasadeBean.simChange(MobileServiceFasadeBean.java:1381)
    can anybody help me ? :(

    We are execute some tests and we got this mistake
    java.sql.SQLException: [TimesTen][TimesTen 7.0.1.0.0 CLIENT]Query Timeout must be numeric; if the Network Timeout is non-zero, the Query Timeout must be greater than zero and less than the Network Timeout, else if the Network Timeout is zero, the Query Timeout must be greater than or equal to zero.
    at com.timesten.jdbc.JdbcOdbc.createSQLException(JdbcOdbc.java:3186)
    at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3320)
    at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3285)
    at com.timesten.jdbc.JdbcOdbc.SQLSetStmtOption(JdbcOdbc.java:2555)
    at com.timesten.jdbc.JdbcOdbcStatement.setStmtOption(JdbcOdbcStatement.java:1889)
    at com.timesten.jdbc.JdbcOdbcStatement.setQueryTimeout (JdbcOdbcStatement.java:714)
    at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:226)
    at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:162)
    at org.hibernate.loader.Loader.doQuery(Loader.java:714)
    at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
    at org.hibernate.loader.Loader.loadCollection(Loader.java:1919)
    at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71)
    at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520)
    at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
    at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1627)
    at org.hibernate.collection.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:454)
    at org.hibernate.engine.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java :827)
    at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:229)
    at org.hibernate.loader.Loader.doList(Loader.java:2150)
    at org.hibernate.loader.Loader.listIgnoreQueryCache (Loader.java:2029)
    at org.hibernate.loader.Loader.list(Loader.java:2024)
    at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:369)
    at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java :300)
    at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:146)
    at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1093)
    at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
    at org.springframework.orm.hibernate3.HibernateTemplate$31.doInHibernate(HibernateTemplate.java:853)
    at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:366)
    at org.springframework.orm.hibernate3.HibernateTemplate.find (HibernateTemplate.java:844)
    at org.springframework.orm.hibernate3.HibernateTemplate.find(HibernateTemplate.java:836)
    at com.bursatec.bmv.selectividad.persistence.dao.impl.FedCenlacesDaoImpl.findEnlaces(FedCenlacesDaoImpl.java :119)
    at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.getEnlaces(RetransmisorImpl.java:229)
    at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.getInfoEnlace (RetransmisorImpl.java:242)
    at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.efectuarReTx(RetransmisorImpl.java:122)
    at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.atenderSolicitud (RetransmisorImpl.java:103)
    at com.bursatec.bmv.retransmision.middleware.configura.SubscriptorListener.onMessage(SubscriptorListener.java:22)
    at progress.message.jimpl.Session.deliver(Unknown Source)
    at progress.message.jimpl.Session.run(Unknown Source)
    at progress.message.jimpl.Session$SessionThread.run(Unknown Source)
    I wish some one could help me
    Thanks a lot.

  • AEX JDBC Synchronous Timeout

    Hi everyone!
    I have a synchronous scenario Proxy->JDBC On PI 7.4 Java Only.
    I have imported this scenario from another server dual stack, there it works.
    I following this thread
    SOAP Receiver adapter on 7.4 AEX exeeds synchronous timeout
    , but it´s not answered.
    do i forgot something?

    Hi guys,
    I found a solution.
    Applying the SAPnote 0001493502.
    Our problem was the paralelism, this wasn´t set.

  • JDBC / JTA Timeouts : How to set a timeout on the fetching of a query ?

    Hi !
    I'm working on an Application running on Weblogic Server 11g. This app executes a query on an Oracle 11g database ...
    The problem is that this query returns millions of records ... and the app fetches the results during tens of minutes.
    We would like to set a timeout, wich will abandon the transaction, hang the database connection, destroy the socket ... or anything else ...
    This timeout will prevent the thread to become in STUCK state and stucking the weblogic managed server.
    Is this possible ?
    Thank's for your answers.
    Steve.
    Edited by: 966918 on 10 avr. 2013 07:18

    Abandon timeout will not help. That is only used if a database crashes during the second phase of commit. It specifies how long the transaction manager should keep trying to complete the transaction.
    JTA timeout will only work if you are using XA datasources and two-phase commit transactions. When the timeout occurs, it guarantees that the transaction cannot be committed. Eventually, all of the participant resources will be notified and will not allow any more work to take place on the transaction. It does not stop the threads and the application must be written to handle exceptions appropriately.
    Edited by: Steve Felts on Apr 17, 2013 8:32 AM

  • JDBC Tx timeout

    Nedd help!
    We are runing Weblogic6.1 with Oracle 8.
    During our Tx transaction processes, flollowing SQL Error happens:
    "[java.sql.SQLException: Transaction 14:7aaa0978f11df335 not active anymore. tx
    status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 31 seconds
    Name=[EJB com.processingnew.NewProcessBean.(java.util.Vector,com.eduction.pay.PayCalendar,long,boolean)],Xid=14:7aaa0978f11df335(5400402),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=31,seconds left=30,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[eductionprod+biz01]=(state=active),properties=({weblogic.transaction.name=[EJB
    com.processingnew.NewProcessBean.process(java.util.Vector,com.eduction.pay.PayCalendar,long,boolean)],
    weblogic.jdbc=t3://122.122.23.23:9001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=biz01+122.122.23.23:9001+eductionprod+,
    Resources={})],CoordinatorURL=biz01+122.122.23.23:9001+eductionprod+)]]
    But we know whole process runs much less than 30 seconds, only about 5 seconds,
    it must be some bug errors.

    Hi Jining,
    Transaction timemout is calculated since the transaction
    started. Is it possible that method NewProcessBean.process
    is called within another transaction?
    Regards,
    Slava Imeshev
    "Jining Qi" <[email protected]> wrote in message
    news:3da72c75$[email protected]..
    >
    Nedd help!
    We are runing Weblogic6.1 with Oracle 8.
    During our Tx transaction processes, flollowing SQL Error happens:
    "[java.sql.SQLException: Transaction 14:7aaa0978f11df335 not active
    anymore. tx> status = Marked rollback.[Reason=weblogic.transaction.internal.TimedOutException:> Transaction timed out after 31 seconds> Name=[EJBcom.processingnew.NewProcessBean.(java.util.Vector,com.eduction.pay.PayCalendar,long,boolean),Xid=14:7aaa0978f11df335(5400402),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=31,secondsleft=30,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assi
    gned=none),SCInfo[eductionprod+biz01]=(state=active),properties=({weblogic.t
    ransaction.name=[EJB
    >
    com.processingnew.NewProcessBean.process(java.util.Vector,com.eduction.pay.P
    ayCalendar,long,boolean)],
    >
    weblogic.jdbc=t3://122.122.23.23:9001}),OwnerTransactionManager=ServerTM[Ser
    verCoordinatorDescriptor=(CoordinatorURL=biz01+122.122.23.23:9001+eductionpr
    od+,
    Resources={})],CoordinatorURL=biz01+122.122.23.23:9001+eductionprod+)]]
    But we know whole process runs much less than 30 seconds, only about 5seconds,
    it must be some bug errors.

  • LDAP Timeout parameter

    Hello,
    I have a huge directory (120K users) with dynamic groups on Novell Edirectory.
    Unfortunately it's seems that for Ldap search,  there is a timer of 10 secondes for request answers and if you are not in this time slot you have an Ldap search failed.Do you know if we could change this behavior and change default value parameter ?
    Thanks
    Philippe

    My Thoughts -
    When 'Sleep For' parameter is set, the Identity/Access Server tries to establish a connection to the secondary Directory server if the primary is down. Again, once the Primary Directory Server is up, the Identity/Access Server 'fails back (re-establishes connection)' to the the primary DS. During this 'fail back', the 'Sleep For' parameter is again used. i.e, even if the Primary DS is up after 3 secs, the Identity/Access Server establishes connection back to primary DS only after 'Sleep For' seconds.
    -- Pramod Aravind

  • JDBC Exception while calling a web-service

    Hi all,
    We are getting the following JDBC Driver Timeout Exception while calling an external web-service..
    An exception occurred while executing a transaction. Details: An error occurred while accesing the database. Detail:SQL statement: ' SELECT INSTANCEDATA, PROCESSID, INSTID, THREADID, NAME, PARENTTHREAD, PRIORITY, CREATIONTIME, AUTHOR, PARTICIPANT, NEXTPARTICIPANT, PROCESSDEADLINE, ACTIVITYDEADLINE, RECEIVETIME, ACTIVITYNAME, NTHREADS, CTHREADS, FCTHREAD, TOTALTHREADS, STATE, SOURCEACTIVITYNAME, ROLEIN, PENDINGITEMID, LASTRESULT, ITEMDEADLINE, NCHANGES , NREMARKS, NATTACHMENTS, HASPARTFORROLE,MICROACTIVITYNAME FROM PPROCINSTANCE WHERE PROCESSID = 11AND INSTID = 10 AND THREADID = 0 FOR UPDATE' Caused by: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock fuego.transaction.DatabaseException:
    How do we resolve this exception?
    We have increased the JTA timeout to 120 seconds.. in the engine..
    Our process is deployed on Weblogic Server

    Looks like specific record for the Instance id 10 is locked in the Engine table. I am not quite sure, what kind of Business scenraio you executed to end up in this issue.
    But you can try restarting the BPM engine or check with the Oracle DBA to see any lock on the rows in Engine database and perform required unlocking operations.
    -Lovin.V

  • Deleting a Entry in LDAP Server through JNDI

    I have modified and created enteries in LDAP Server.But have no idea how to remove or delete a entry(a subcontext).
    can anyone help ne out
    thanks
    murali

    Thank you mike.its working.I just missed that method.
    I have one more problem.
    i am using the octetstring's jdbc-ldap bridge to connect to Eudora LDAP server, but when ever i try to connect to the server we are getting the following error...
    javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'o=Siquell,c=IN'
    even though we have the root dsn i.e "o=Siquell,c=IN". this we can say cause we were able to connect to the same server using JNDI.
    Is this because octetstring's jdbc-ldap bridge is not supported by Eudora LDAP server.
    Thanks
    Murali

  • BEST_EFFORT_QUERY Timeout - inconsistent behavior

    I'm seeing inconsistent results with the Best Effort Query/Timeout combination using the Jena Adaptor. Sometimes it appears that the timeout is working exactly as expected, after X amount of time (5 seconds in our case), the query returns with a subset of the specified data. Other times, it seems that the query ignores the fact that a timeout has been specified and it churns much longer than I would expect. Is there some reason for this that I'm missing?
    Jena v 2.6.2
    11g r2.0.2
    I provided these numbers for a different thread (Binding string values in SPARQL but they apply here as well. The query starts like so:
    PREFIX ORACLE_SEM_FS_NS:<http://oracle.com/semtech#timeout=5,BEST_EFFORT_QUERY=t,DEGREE=8>
    DEBUG[2011-08-05 09:05:49,498] - [service:debugQuery:202] - ( 0 processed in 0:00:32.578)
    DEBUG[2011-08-05 09:08:30,872] - [service:debugQuery:202] - ( 532 processed in 0:00:04.265)
    DEBUG[2011-08-05 09:09:23,262] - [service:debugQuery:202] - ( 532 processed in 0:00:01.250)
    Second Test: Search for "Juvenile"
    DEBUG[2011-08-05 09:16:22,588] - [service:debugQuery:202] - ( 0 processed in 0:00:06.078)
    DEBUG[2011-08-05 09:18:01,072] - [service:debugQuery:202] - ( 1 processed in 0:00:52.172)
    DEBUG[2011-08-05 09:19:21,602] - [service:debugQuery:202] - ( 1001 processed in 0:00:57.999)
    DEBUG[2011-08-05 09:20:03,477] - [service:debugQuery:202] - ( 1001 processed in 0:00:07.031)
    Any suggestions you can offer would be very helpful.
    Regards,
    J.P.
    Edited by: 877356 on Aug 5, 2011 8:00 AM

    Hi,
    Could you please send me (alan dot wu at oracle dot com) a reproducible test case?
    The time out logic in Jena Adapter depends on JDBC's timeout and also row fetching from a result set.
    Thanks,
    Zhe Wu

  • LDAPConnection timeout problem

    Hello,
    LDAPConnection(int M_timeout) timeout seems not work.
    I expect the exception will be thrown if the connection to LDAP server
    is not alive for M_timeout seconds.
    But it doesn't work, no matter what is the value of M_timeout, the
    connection timeout is same.
    Can anyone know that how the LDAPConnection timeout can be setup at
    program?
    Thanks.
    mscat
    mscat's Profile: http://forums.novell.com/member.php?userid=42629
    View this thread: http://forums.novell.com/showthread.php?t=377742

    Sorry, I could not download your code.
    (Redirect loop)
    Anyhow, this works:
    LDAPConstraints cons = new LDAPConstraints();
    cons.setTimeLimit(1);
    Setting to 1 milliseconds. No server will bind in 10 milliseconds.
    (Use bad credentials to make sure)
    Then Bind with constraints
    lc.bind(LDAPConnection.LDAP_V3, loginDN, password.getBytes("UTF8"), cons);
    Yields:
    Error: LDAPException: Client request timed out (85) LDAP Timeout
    -jim
    mscat wrote:
    > Attached is sample application you can reproduce.
    > I am using LDAPConnection(int timeout) construtor.
    > Total time taken for timeout of the socket which server cannot be
    > response: 22334ms (even the LDAPConnection(int timeout = 5000))
    >
    >
    > palaniappan1;1815685 Wrote:
    >> The setSocketTimeout() API has to be used, if you want to change the
    >> timeout value after you do the connection. And the constructor
    >> LDAPConnection(int timeout) has to be used, in case you want to set it
    >> before the connect.
    >>
    >> These timeout values specify the time your socket can be open when the
    >> server becomes unresponsive.
    >>
    >> Not sure, why the issue is there. If you are very sure that this is the
    >> requirement and you use the APIs, properly, send me your sample
    >> application to reproduce.
    >>
    >> I'll raise a bug and shall work on that.
    >
    >
    > +----------------------------------------------------------------------+
    > |Filename: TestOnConnection.txt |
    > |Download: http://forums.novell.com/attachment....achmentid=3037 |
    > +----------------------------------------------------------------------+
    >

Maybe you are looking for