ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 50484] New: Multiple calls to Ant script <sql> task fail with ojdbc5.jar
Date Thu, 16 Dec 2010 12:34:56 GMT

           Summary: Multiple calls to Ant script <sql> task fail with
           Product: Ant
           Version: 1.7.1
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core tasks

We are using an Ant script to apply SQL scripts to a database.  This is done
using the core <sql> task within a macro passing the script as a parameter, ie

<sql driver="oracle.jdbc.driver.OracleDriver" url="@{url}" userid="@{user}"
password="@{password}" classpathref="database.drivers" >
                                <transaction src="@{script}" />

A controlling shell script calls several Ant targets (each with a new instance
of Ant).  We have reproduced the problem just calling Ant several times from
the shell.

The first call works fine but subsequent calls report

.../build.xml:106: The following error occurred while executing this line:
.../build.xml:29: java.sql.SQLException: IO Error: Connection reset

After some delay (several minutes) running the same script works fine.

This does not seem related to the content of the SQL script - even simple
select statements show this problem.

We have recently updated to use the newer Oracle ojdbc5.jar reverting back to
the ojdbc14.jar fixes the problem.

We are using Ant 1.7.1 (but have reproduced the problem with 1.8.1)

Running on an Ubuntu server:
2.6.24-28-generic #1 SMP Wed Nov 24 09:30:14 UTC 2010 i686 GNU/Linux

Java version:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)

The Oracle ojdbc5.jar reports its version as:
Oracle JDBC 3.0 compiled with JDK5 on Sat_Aug_14_12:16:40_PDT_2010

The Oracle ojdbc14.jar fails to report its version - ie there is no manifest in
that jar file.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message