db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4 regression ?
Date Sun, 09 Sep 2007 15:26:29 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525999
] 

Kathey Marsden commented on DERBY-3038:
---------------------------------------

I was able to reproduce with Reproduce3038.java on the trunk and verified that the program
passed on 10.2.  Thanks for reporting this issue! I was curious why you  shutdown the database
every time you close a connection.  Normally one shutdown of the database before the application
exits is sufficient.  If I take out the database shutdown on connection close it runs fine.
 Also taking out the database shutdown with every connection close will probably improve the
performance of the application if connections are closed frequently and will prevent the shutdown
of one connection from affecting other connections open on the database.
	
One other note: the Class.forName("org.apache.derby.jdbc.EmbeddedDriver") for each connection
is not necessary before each connect.  You only need one Class.forName("org.apache.derby.jdbc.EmbeddedDriver")
.newInstance() before connecting the first time.






> SYSCS_IMPORT_TABLE FAILS : 10.3.1.4 regression ?
> ------------------------------------------------
>
>                 Key: DERBY-3038
>                 URL: https://issues.apache.org/jira/browse/DERBY-3038
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 10.3.1.4
>         Environment: Linux 2.6.21.1 #2 Tue Jun 26 23:24:34 CEST 2007 i686 AMD Athlon(tm)
XP 2800+ GNU/Linux (Mandriva 2007 Spring)
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build 1.6.0-b105)
> Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
>            Reporter: EDAH-TALLY
>         Attachments: create_table.txt, lst_pays.csv, Reproduce3038.zip, stacktrace.txt,
sysinfo.txt, Test3038.java
>
>
> I used to import data with CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE procedure with 
> success in JAVA and DERBY 10.2.2.0.
> Since 10.3.1.4, the import procedure fails.
> The error message is : 
> The exception 'java.sql.SQLException: No current connection.' was thrown while 
> evaluating an expression.
> I'm sure there is a connection, the same which created the statement : 
> ***************************************************************************************************
>     protected boolean importTableDataCOUNTRIES() {
>         try {
>             java.sql.Statement st = 
> conn.createStatement(java.sql.ResultSet.TYPE_SCROLL_INSENSITIVE, 
> java.sql.ResultSet.CONCUR_UPDATABLE);
>             String sql = "";
>             sql = "CALL 
> SYSCS_UTIL.SYSCS_IMPORT_TABLE('NMSET', 'PAYS', '/tmp/lst_pays.csv', 
> null, null, null, 1)";
>             st.executeUpdate(sql);
>             
>             return true;
>         } catch (SQLException ex) {
>             debug(ex.getMessage());
>         }
>         return false;
>     }
> ***************************************************************************************************
> The database is not being accessed by another application. The table does 
> exist. The CSV file is comma separated and strings are enclosed by ".
> Thank you for considering this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message