Get Data Moving 1
Results 1 to 1 of 1

Thread: JDBC connection timeout

  1. #1
    Costi Zaboura is offline World Wide Support Manager
    Join Date
    Aug 2006
    Posts
    300
    Rep Power
    14

    JDBC connection timeout

    DESCRIPTION


    Customer are running a Java application (StreamFlow) which calls Attunity Connect via JDBC
    The daemon control setting had been set to have connectTimeout as 28800 seconds (8 hours) as follows:-

    serverLogFile='/appl/attunity/navroot/tmp/nav_%i.log' language='/>

    But it seems this connectTimeout does not apply to JDBC clients, in the irpcd.log, the reported connectTimeout is always 60 seconds as follows:-

    <9> Login: (172.19.13.32:58322, 15-May-06 04:01:15)
    <9> Get App Info Navigator
    <9> Return: ConnectTimeout=60, CallTimeout=28800, DebugMode=0x0,
    ServerMode=1
    <9> Get Server Navigator ()
    <9> Started new server process (PID=1835), log file is
    /appl/attunity/navroot/tmp/nav_4.log

    Is there any way to increase the JDBC connectTimeout?

    SOLUTION
    The solution is to specify in the workspace a value of zero to the connectTimeout parameter, then the default value will be taken from the
    same parameter in the daemon configuration.

    Summary:
    case 1: Workspace = 60; IRPCD = 120
    Timeout is 60 (WS setting is used)

    case 2: Workspace = Not Define; IRPCD = 120
    Timeout is 60 (WS default setting is used)

    case 3: Workspace = 0: IRPCD = 120
    Timeout is 120 (IRPCD setting is used)
    Last edited by Costi Zaboura; 09-06-2006 at 08:37 AM.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

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