db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "EDAH-TALLY (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No current connection after shutdown/reconnect to encrypted database : 10.3.1.4 regression
Date Sat, 03 Nov 2007 05:42:54 GMT

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

EDAH-TALLY updated DERBY-3038:
------------------------------

    Attachment: derby.log

Hello,

There are no exceptions in derby.log.

One thing amazing, when connecting to Derby, it constantly starts an instance, 
closes it and starts a new one. Even if one just connects without doing any 
task. Has it something to do with the reported failure ?

The only way I could import the CSV file was to do everything in one single 
run : create DB, create tables and import data. If these steps are done 
distinctly in different runs, then import fails. This is so in my app, and 
not in Test3038.

I have checked and cross-checked my code, I don't have any explanation of 
this.

I can still workaround, but what if this happens in a distributed app !

When I said before that I didn't have any problems with 10.2, it was with 
another app (Goggle/SourceForge search OpenCIM10 if the source code is 
required)(Sorry if don't have the right to mention any project here). When I 
run the current failed import with 10.2, the failure persists.

I agree that the first thing to think of is an error in my code. With best 
honesty, I can't find any.

I don't have the means and time to dig in the Derby source code.

I'll close this issue in a few days as UNRESOLVED.

Thank you very much.



> SYSCS_IMPORT_TABLE FAILS  with No current connection after shutdown/reconnect to encrypted
database : 10.3.1.4 regression 
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3038
>                 URL: https://issues.apache.org/jira/browse/DERBY-3038
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    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
>            Assignee: Dag H. Wanvik
>            Priority: Critical
>             Fix For: 10.3.1.5, 10.4.0.0
>
>         Attachments: create_table.txt, DERBY-3038-2.diff, DERBY-3038-2.stat, DERBY-3038.diff,
DERBY-3038.stat, derby.log, 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