You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "EDAH-TALLY (JIRA)" <ji...@apache.org> on 2007/09/02 10:07:19 UTC
[jira] Created: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
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: JDBC, Regression Test Failure, Services, 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
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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
EDAH-TALLY updated DERBY-3038:
------------------------------
Attachment: (was: stacktrace.txt)
> 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: stacktrace.txt, sysinfo.txt
>
>
> 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.
[jira] Reopened: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
EDAH-TALLY reopened DERBY-3038:
-------------------------------
The exception can now be reproduced as per the archive Reproduce3038.zip, which represents more closely my app design.
Thank you for considering.
> 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3038:
---------------------------------
Component/s: (was: Tools)
SQL
> 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, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524739 ]
Kathey Marsden commented on DERBY-3038:
---------------------------------------
I'd like to try to get this issue in the form of a reproducible case. Can you please post the schema for the table and a sample data file, so we can reproduce and verify it as a regression?
Thanks
Kathey
> 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: stacktrace.txt, sysinfo.txt
>
>
> 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.
[jira] Resolved: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik resolved DERBY-3038.
----------------------------------
Resolution: Fixed
Merged patch to 10.3 branch, ran all regression tests
with no errors. Committed as svn 574917, resolving now.
> 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, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526769 ]
Dag H. Wanvik commented on DERBY-3038:
--------------------------------------
Thanks to EDAH-TALLY for and Kathey for uncovering this and pinning it down!
> 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, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539888 ]
EDAH-TALLY commented on DERBY-3038:
-----------------------------------
Sorry,
Don't know where theis mail comes from. Didn't post it today.
> 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3038:
---------------------------------
Derby Info: [Patch Available, Regression] (was: [Regression])
> 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: 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
> Assignee: Dag H. Wanvik
> Priority: Critical
> Attachments: create_table.txt, DERBY-3038.diff, DERBY-3038.stat, 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3038:
---------------------------------
Derby Info: [Regression] (was: [Regression, Patch Available])
> 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: 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
> Assignee: Dag H. Wanvik
> Priority: Critical
> Attachments: create_table.txt, DERBY-3038-2.diff, DERBY-3038-2.stat, DERBY-3038.diff, DERBY-3038.stat, 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-3038:
--------------------------------------
Component/s: (was: JDBC)
(was: Regression Test Failure)
(was: Services)
(was: SQL)
Tools
Description:
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.
was:
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.
Derby Info: [Regression] (was: [Regression, Existing Application Impact])
> 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: sysinfo.txt
>
>
> 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539792 ]
EDAH-TALLY commented on DERBY-3038:
-----------------------------------
Hello,
In fact, in a real application, I do not shutdown the DB at all except when
ending the application.
I wrote Reproduce3038 this way because during development, I usually create
the DB and the table, checks that the objects are here from OpenOffice Base,
then in a distinct run(which may be on some other day) I would import the
data. That's why I closed the DB between each step in Reproduce3038, to mimic
real time development steps. Any way, in production, a user would import a
file on existing objects.
As I commented in Main.java, if the data is imported in a distinct run on
existing objects, it fails. If in one same run, the DB and the table are
created AND the data is imported, then import succeeds.
Thank you for the 'Class.forName' comment.
One more note, I get the same result with 10.2.
Thank you.
> 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.
[jira] Issue Comment Edited: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS
with No current connection after shutdown/reconnect to encrypted database
: 10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526321 ]
dagw edited comment on DERBY-3038 at 9/11/07 5:14 PM:
---------------------------------------------------------------
Uploading a patch for this (a one liner).
In the repro, Derby thinks it is doing encryption reboot, since
"dataEncryption=true" is supplied when reconnecting. This
leads Derby to do a two-phase boot for authentication purposes before
doing encryption (DERBY-2264). (The attribute is redundant here,
though, since encryption is done at creation time, but that is not relevant.)
The issue is that the second boot of the two-phase boot lacked proper
setup of the EmbedConnectionContext in the second boot, leading to
failure when establishing a nested connection in
SystemProcedures.getDefaultConn. This would also impact other
uses of nested connections, I presume. [Update: It does]
Running regression tests now.
was (Author: dagw):
Uploading a patch for this (a one liner).
In the repro, Derby thinks it is doing encryption reboot, since
"dataEncryption=true" is supplied when reconnecting. This
leads Derby to do a two-phase boot for authentication purposes before
doing encryption (DERBY-2264). (The attribute is redundant here,
though, since encryption is done at creation time, but that is not relevant.)
The issue is that the second boot of the two-phase boot lacked proper
setup of the EmbedConnectionContext in the second boot, leading to
failure when establishing a nested connection in
SystemProcedures.getDefaultConn. This would also impact other
uses of nested connections, I presume.
Running regression tests now.
> 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, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526525 ]
Kathey Marsden commented on DERBY-3038:
---------------------------------------
I didn't try it but on visual inspection the patch looks good.
Kathey
> 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: 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
> Assignee: Dag H. Wanvik
> Priority: Critical
> Attachments: create_table.txt, DERBY-3038-2.diff, DERBY-3038-2.stat, DERBY-3038.diff, DERBY-3038.stat, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526856 ]
EDAH-TALLY commented on DERBY-3038:
-----------------------------------
I understand that the fix would be available as from 10.3.1.5 or in SVN. 10.1.3.4 has only been released so I think there's a delay of a few months before .5 would be available.
Thanks and congratulations for the community's reactivity.
> 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, 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3038:
----------------------------------
Priority: Critical (was: Major)
Summary: SYSCS_IMPORT_TABLE FAILS with No current connection after shutdown/reconnect to encrypted database : 10.3.1.4 regression (was: SYSCS_IMPORT_TABLE FAILS : 10.3.1.4 regression ?)
> 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: 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
> Priority: Critical
> 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
EDAH-TALLY updated DERBY-3038:
------------------------------
Attachment: sysinfo.txt
> 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: JDBC, Regression Test Failure, Services, 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
> Attachments: sysinfo.txt
>
>
> 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
EDAH-TALLY updated DERBY-3038:
------------------------------
Attachment: stacktrace.txt
Posted.
Thanks.
> 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: stacktrace.txt, stacktrace.txt, sysinfo.txt
>
>
> 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526457 ]
Kathey Marsden commented on DERBY-3038:
---------------------------------------
Thanks Dag for looking at this issue. Could you add a regression test for it so we don't reregress?
Kathey
> 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: 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
> Assignee: Dag H. Wanvik
> Priority: Critical
> Attachments: create_table.txt, DERBY-3038.diff, DERBY-3038.stat, 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3038:
---------------------------------
Attachment: DERBY-3038.stat
DERBY-3038.diff
Uploading a patch for this (a one liner).
In the repro, Derby thinks it is doing encryption reboot, since
"dataEncryption=true" is supplied when reconnecting. This
leads Derby to do a two-phase boot for authentication purposes before
doing encryption (DERBY-2264). (The attribute is redundant here,
though, since encryption is done at creation time, but that is not relevant.)
The issue is that the second boot of the two-phase boot lacked proper
setup of the EmbedConnectionContext in the second boot, leading to
failure when establishing a nested connection in
SystemProcedures.getDefaultConn. This would also impact other
uses of nested connections, I presume.
Running regression tests now.
> 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: 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
> Assignee: Dag H. Wanvik
> Priority: Critical
> Attachments: create_table.txt, DERBY-3038.diff, DERBY-3038.stat, 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3038:
---------------------------------
Fix Version/s: 10.4.0.0
10.3.1.5
> 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, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524326 ]
Knut Anders Hatlen commented on DERBY-3038:
-------------------------------------------
Could you also post the complete stack trace? Thanks.
> 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: JDBC, Regression Test Failure, Services, 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
> Attachments: sysinfo.txt
>
>
> 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.
Re: [jira] Resolved: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by Kathey Marsden <km...@sbcglobal.net>.
Kristian Waagan wrote:
> Kathey Marsden (JIRA) skrev:
>> [
>> https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Kathey Marsden resolved DERBY-3038.
>> -----------------------------------
>>
>> Resolution: Cannot Reproduce
>>
>> Closing this issue Cannot Reproduce. Please reopen if you get a
>> reproduction for this problem.
> Hello Kathey,
>
> You say you are closing the issue, but it is only marked as resolved.
> Is this intentional, or can the issue be marked as closed as well?
>
> As a general note, I believe one can specify the resolution from the
> "Close" screen/dialog. Saves one message and a few clicks :)
> I am aware that mostly marking an issue resolved and closed will be
> carried out by different persons and thus done in two steps.
>
I think I will leave to the reporter EDAH-TALLY to close it especially
since it was filed as a regression. Perhaps EDAH will be able to reopen
it with a repro or perhaps is satisfied with the Cannot Reproduce
status. I think it would be too presumptuous of me to close it. Thanks
for the tip on the single step resolve/close. I will certainly use that
on issues that I file myself.
Kathey
Re: [jira] Resolved: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by Kristian Waagan <Kr...@Sun.COM>.
Kathey Marsden (JIRA) skrev:
> [ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Kathey Marsden resolved DERBY-3038.
> -----------------------------------
>
> Resolution: Cannot Reproduce
>
> Closing this issue Cannot Reproduce. Please reopen if you get a reproduction for this problem.
>
Hello Kathey,
You say you are closing the issue, but it is only marked as resolved.
Is this intentional, or can the issue be marked as closed as well?
As a general note, I believe one can specify the resolution from the
"Close" screen/dialog. Saves one message and a few clicks :)
I am aware that mostly marking an issue resolved and closed will be
carried out by different persons and thus done in two steps.
regards,
--
Kristian
>
>> 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, 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.
>>
>
>
[jira] Resolved: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-3038.
-----------------------------------
Resolution: Cannot Reproduce
Closing this issue Cannot Reproduce. Please reopen if you get a reproduction for this problem.
> 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, 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
EDAH-TALLY updated DERBY-3038:
------------------------------
Attachment: lst_pays.csv
create_table.txt
Here they are.
> 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, stacktrace.txt, sysinfo.txt
>
>
> 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526022 ]
EDAH-TALLY commented on DERBY-3038:
-----------------------------------
Hello,
In fact, in a real application, I do not shutdown the DB at all except when
ending the application.
I wrote Reproduce3038 this way because during development, I usually create
the DB and the table, checks that the objects are here from OpenOffice Base,
then in a distinct run(which may be on some other day) I would import the
data. That's why I closed the DB between each step in Reproduce3038, to mimic
real time development steps. Any way, in production, a user would import a
file on existing objects.
As I commented in Main.java, if the data is imported in a distinct run on
existing objects, it fails. If in one same run, the DB and the table are
created AND the data is imported, then import succeeds.
I also removed the shutdown database instruction and failure persists in the same circumstances.
Thank you for the 'Class.forName' comment.
One more note, I get the same result with 10.2.
Thank you.
> 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3038:
----------------------------------
Attachment: Test3038.java
I combined the table creation and import into a small java program and cannot reproduce with 10.3.1.4. Can you modify this program to reproduce the error?
> 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, 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
EDAH-TALLY updated DERBY-3038:
------------------------------
Attachment: Reproduce3038.zip
> 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.
[jira] Closed: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
EDAH-TALLY closed DERBY-3038.
-----------------------------
> 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, 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3038:
---------------------------------
Attachment: DERBY-3038-2.stat
DERBY-3038-2.diff
Sure, Kathey! Uploading a new version DERBY-3038-2.*, which replaces
the previous patch. This includes a a new regression test which
exposes the error prior to the fix contained in this patch.
> 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: 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
> Assignee: Dag H. Wanvik
> Priority: Critical
> Attachments: create_table.txt, DERBY-3038-2.diff, DERBY-3038-2.stat, DERBY-3038.diff, DERBY-3038.stat, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524896 ]
Kathey Marsden commented on DERBY-3038:
---------------------------------------
Please let us know if you make any further progress toward getting a reproducible case for this issue. Since your code works for you with 10.2, I fear there is still something amiss. One thing to check is the derby.log to see if there is an exception that explains the loss of connection.
> 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, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524865 ]
Kathey Marsden commented on DERBY-3038:
---------------------------------------
The result I get with Test3038.java with the .csv file in the working directory is:
[C:/kmarsden/repro/derby-3038] java Test3038
243 rows imported
The error message "No current connection.' no current connection seems to indicate that perhaps some prior action has caused loss of connection. Perhaps the issue is not the import but whatever came just before it.
> 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, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524879 ]
EDAH-TALLY commented on DERBY-3038:
-----------------------------------
You're right, the import procedure went fine in Test3038 !!!
I tried with an disk encrypted Db also and Test3038 did it.
I can't see what can close the connection between two lines in the SAME
procedure. and there is no other action going on. If there were no
connection , the statement wouldn't have been created.
I'll try to workaround this.
Thank you for your help.
> 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, 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.
[jira] Commented: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526644 ]
Dag H. Wanvik commented on DERBY-3038:
--------------------------------------
Thanks for checking it, Kathey! Ran regression tests over again
and committed as svn 574733. Will backport to 10.3
before I resolve.
> 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: 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
> Assignee: Dag H. Wanvik
> Priority: Critical
> Attachments: create_table.txt, DERBY-3038-2.diff, DERBY-3038-2.stat, DERBY-3038.diff, DERBY-3038.stat, 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.
[jira] Assigned: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS with No
current connection after shutdown/reconnect to encrypted database :
10.3.1.4 regression
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik reassigned DERBY-3038:
------------------------------------
Assignee: Dag H. Wanvik
> 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: 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
> Assignee: Dag H. Wanvik
> Priority: Critical
> 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.
[jira] Updated: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by "EDAH-TALLY (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
EDAH-TALLY updated DERBY-3038:
------------------------------
Attachment: stacktrace.txt
> 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: stacktrace.txt, sysinfo.txt
>
>
> 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.