[jira] Commented: (DERBY-2054) Rewrite 'derbynet/SuicideOfStreaming' to a JUnit test
[ http://issues.apache.org/jira/browse/DERBY-2054?page=comments#action_12448936 ] Tomohito Nakayama commented on DERBY-2054: -- I'm not familiar with newly created test system at all. Then this comment may be missed ... System property of derby.debug.suicideOfLayerBStreaming is effective on code of NetworkServer. Then System property must be set for process of NetworkServer. Reading the code setUp(), I found both of code to call JDBC interface to execute sql which would be at NetworkClient and code to set System property of derby.debug.suicideOfLayerBStreaming in a same method. In newly created test system, does NetworkServer and NetworkClient run on a same process ? I remember that they are different in old test system ... > Rewrite 'derbynet/SuicideOfStreaming' to a JUnit test > - > > Key: DERBY-2054 > URL: http://issues.apache.org/jira/browse/DERBY-2054 > Project: Derby > Issue Type: Test > Components: Test >Affects Versions: 10.3.0.0 >Reporter: Kristian Waagan > Assigned To: Kristian Waagan >Priority: Minor > Attachments: derby-2054-1a.diff, derby-2054-1a.stat, > derby-2054-preview.diff > > > The test 'derbynet/SuicideOfStreaming' should be rewritten to a JUnit test > more in line with our newly created test system. > It is one of the last tests still being run from the deprecated > 'tests/junitTests/' directory, through a wrapper class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0
Hello. Thank you for your comment :) I think you understood what the issue is. I understand your idea as using module of Engine where JDBC4.0 feature is implemented directly rather than via JDBC interface from NetworkServer. I take the idea in consideration. Best regards. Oystein Grovlen - Sun Norway wrote: TomohitoNakayama wrote: > Hello. > > Thank you for your kindness :) > > What is needed is calling method which was introduced in JDBC 4.0 > from NetworkServer to utilize JDBC 4.0 feature in Engine. > Concretely,the method is PreparedStatement#setBinaryStream(int, > java.io.InputStream). > http://download.java.net/jdk6/docs/api/java/sql/PreparedStatement.html#setBinaryStream(int,%20java.io.InputStream) > > > What is important is that JDBC 4.0 is optional and > implementation to utilize the feature of it should be appropriately > placed in code of NetworkServer > in order to keep compatibility for previous spec in NetworkServer. > If I understand you correctly the issue is: - When using Layer B streaming, you want the Network Server to be able to use the new JDBC 4 methods for lengthless streaming. - The problem is that the JDBC 4 methods is not directly available to the NetworkServer if using older run-time libraries (e.g., Java SE 5). Since the implementation of the JDBC 4 methods will be part of derby.jar regardless of which JVM you are running on, I would guess it is just a question of how to make them available to the network server. -- /* Tomohito Nakayama [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Naka http://www5.ocn.ne.jp/~tomohito/TopPage.html */
Regression Test Report - tinderbox_trunk15 473603 - Sun DBTG
[Auto-generated mail] *tinderbox_trunk15* 473603/2006-11-11 01:52:19 CET Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 1516515 2 120.57% derbyall 020402040 0 111.44% org.apache.derbyTesting.functionTests.suites.All Details in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/testing/Limited/testSummary-473603.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/FailReports/473603.html --- Changes in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/UpdateInfo/473603.txt ( All results in http://dbtg.thresher.com/derby/test/ )
[jira] Resolved: (DERBY-2018) NullPointerException in CREATE VIEW ... VALUES NULL;
[ http://issues.apache.org/jira/browse/DERBY-2018?page=all ] Bryan Pendleton resolved DERBY-2018. Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) > NullPointerException in CREATE VIEW ... VALUES NULL; > > > Key: DERBY-2018 > URL: http://issues.apache.org/jira/browse/DERBY-2018 > Project: Derby > Issue Type: Bug > Components: SQL >Affects Versions: 10.2.1.6 > Environment: Java 1.5.0_06-b05 >Reporter: Christian d'Heureuse > Assigned To: Yip Ng >Priority: Minor > Fix For: 10.3.0.0 > > Attachments: derby2018-trunk-diff01.txt, derby2018-trunk-stat01.txt > > > The following statement produces a NullPointerException: >CREATE VIEW v1 (f1) AS VALUES NULL; > Stack trace: > > 2006-10-30 12:39:31.750 GMT: > Booting Derby version The Apache Software Foundation - Apache Derby - > 10.2.1.6 - (452058): instance c013800d-010e-993b-512f-0012f418 > on database directory C:\temp_sys\temp_Derby_TestErr_db > Database Class Loader started - derby.database.classpath='' > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Cleanup > action starting > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Failed > Statement is: CREATE VIEW v1 (f1) AS VALUES NULL > java.lang.NullPointerException > at > org.apache.derby.impl.sql.catalog.SYSCOLUMNSRowFactory.makeRow(Unknown Source) > at > org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorArray(Unknown > Source) > at > org.apache.derby.impl.sql.execute.CreateViewConstantAction.executeConstantAction(Unknown > Source) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.tools.ij.ij.executeImmediate(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.doCatch(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.mainCore(Unknown Source) > at org.apache.derby.impl.tools.ij.Main14.main(Unknown Source) > at org.apache.derby.tools.ij.main(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2018) NullPointerException in CREATE VIEW ... VALUES NULL;
[ http://issues.apache.org/jira/browse/DERBY-2018?page=comments#action_12448913 ] Bryan Pendleton commented on DERBY-2018: The rest of my testing was uneventful. Committed the patch to subversion as revision 473603. > NullPointerException in CREATE VIEW ... VALUES NULL; > > > Key: DERBY-2018 > URL: http://issues.apache.org/jira/browse/DERBY-2018 > Project: Derby > Issue Type: Bug > Components: SQL >Affects Versions: 10.2.1.6 > Environment: Java 1.5.0_06-b05 >Reporter: Christian d'Heureuse > Assigned To: Yip Ng >Priority: Minor > Attachments: derby2018-trunk-diff01.txt, derby2018-trunk-stat01.txt > > > The following statement produces a NullPointerException: >CREATE VIEW v1 (f1) AS VALUES NULL; > Stack trace: > > 2006-10-30 12:39:31.750 GMT: > Booting Derby version The Apache Software Foundation - Apache Derby - > 10.2.1.6 - (452058): instance c013800d-010e-993b-512f-0012f418 > on database directory C:\temp_sys\temp_Derby_TestErr_db > Database Class Loader started - derby.database.classpath='' > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Cleanup > action starting > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Failed > Statement is: CREATE VIEW v1 (f1) AS VALUES NULL > java.lang.NullPointerException > at > org.apache.derby.impl.sql.catalog.SYSCOLUMNSRowFactory.makeRow(Unknown Source) > at > org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorArray(Unknown > Source) > at > org.apache.derby.impl.sql.execute.CreateViewConstantAction.executeConstantAction(Unknown > Source) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.tools.ij.ij.executeImmediate(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.doCatch(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.mainCore(Unknown Source) > at org.apache.derby.impl.tools.ij.Main14.main(Unknown Source) > at org.apache.derby.tools.ij.main(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Regression Test Report - tinderbox_trunk15 473483 - Sun DBTG
[Auto-generated mail] *tinderbox_trunk15* 473483/2006-11-10 22:12:51 CET Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 1516515 2 121.37% derbyall 020402040 0 115.56% org.apache.derbyTesting.functionTests.suites.All Details in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/testing/Limited/testSummary-473483.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/FailReports/473483.html --- Changes in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/UpdateInfo/473483.txt ( All results in http://dbtg.thresher.com/derby/test/ )
Re: [VOTE] Laura Stewart as committer
Jean T. Anderson wrote: Please vote +1 if you approve of Laura as a committer. +1 Army
Re: [VOTE] Laura Stewart as committer
Deepa Remesh wrote: On 11/10/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: Please vote +1 if you approve of Laura as a committer. +1 Deepa +1 Manjula
Re: [VOTE] Laura Stewart as committer
On 11/10/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: Please vote +1 if you approve of Laura as a committer. +1 Deepa
[jira] Commented: (DERBY-2018) NullPointerException in CREATE VIEW ... VALUES NULL;
[ http://issues.apache.org/jira/browse/DERBY-2018?page=comments#action_12448870 ] Bryan Pendleton commented on DERBY-2018: Thank you very much, Yip, that was exactly it! Now I get the results I expect: the new test fails without your code patch, and passes with your code patch. Excellent! I will proceed with my review/commit. > NullPointerException in CREATE VIEW ... VALUES NULL; > > > Key: DERBY-2018 > URL: http://issues.apache.org/jira/browse/DERBY-2018 > Project: Derby > Issue Type: Bug > Components: SQL >Affects Versions: 10.2.1.6 > Environment: Java 1.5.0_06-b05 >Reporter: Christian d'Heureuse > Assigned To: Yip Ng >Priority: Minor > Attachments: derby2018-trunk-diff01.txt, derby2018-trunk-stat01.txt > > > The following statement produces a NullPointerException: >CREATE VIEW v1 (f1) AS VALUES NULL; > Stack trace: > > 2006-10-30 12:39:31.750 GMT: > Booting Derby version The Apache Software Foundation - Apache Derby - > 10.2.1.6 - (452058): instance c013800d-010e-993b-512f-0012f418 > on database directory C:\temp_sys\temp_Derby_TestErr_db > Database Class Loader started - derby.database.classpath='' > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Cleanup > action starting > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Failed > Statement is: CREATE VIEW v1 (f1) AS VALUES NULL > java.lang.NullPointerException > at > org.apache.derby.impl.sql.catalog.SYSCOLUMNSRowFactory.makeRow(Unknown Source) > at > org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorArray(Unknown > Source) > at > org.apache.derby.impl.sql.execute.CreateViewConstantAction.executeConstantAction(Unknown > Source) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.tools.ij.ij.executeImmediate(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.doCatch(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.mainCore(Unknown Source) > at org.apache.derby.impl.tools.ij.Main14.main(Unknown Source) > at org.apache.derby.tools.ij.main(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Laura Stewart as committer
Jean T. Anderson wrote: I propose that we add Laura Stewart as a committer for Derby. +1
[jira] Commented: (DERBY-2018) NullPointerException in CREATE VIEW ... VALUES NULL;
[ http://issues.apache.org/jira/browse/DERBY-2018?page=comments#action_12448865 ] Yip Ng commented on DERBY-2018: --- Hi Bryan. It appears that the view.sql test has been moved to JUnit. Try: java org.apache.derbyTesting.functionTests.tests.lang.LangScripts views I discovered this when trying to fix DERBY-2048. > NullPointerException in CREATE VIEW ... VALUES NULL; > > > Key: DERBY-2018 > URL: http://issues.apache.org/jira/browse/DERBY-2018 > Project: Derby > Issue Type: Bug > Components: SQL >Affects Versions: 10.2.1.6 > Environment: Java 1.5.0_06-b05 >Reporter: Christian d'Heureuse > Assigned To: Yip Ng >Priority: Minor > Attachments: derby2018-trunk-diff01.txt, derby2018-trunk-stat01.txt > > > The following statement produces a NullPointerException: >CREATE VIEW v1 (f1) AS VALUES NULL; > Stack trace: > > 2006-10-30 12:39:31.750 GMT: > Booting Derby version The Apache Software Foundation - Apache Derby - > 10.2.1.6 - (452058): instance c013800d-010e-993b-512f-0012f418 > on database directory C:\temp_sys\temp_Derby_TestErr_db > Database Class Loader started - derby.database.classpath='' > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Cleanup > action starting > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Failed > Statement is: CREATE VIEW v1 (f1) AS VALUES NULL > java.lang.NullPointerException > at > org.apache.derby.impl.sql.catalog.SYSCOLUMNSRowFactory.makeRow(Unknown Source) > at > org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorArray(Unknown > Source) > at > org.apache.derby.impl.sql.execute.CreateViewConstantAction.executeConstantAction(Unknown > Source) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.tools.ij.ij.executeImmediate(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.doCatch(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.mainCore(Unknown Source) > at org.apache.derby.impl.tools.ij.Main14.main(Unknown Source) > at org.apache.derby.tools.ij.main(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--
Derby Info: [Patch Available]
> Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional
> -
>
> Key: DERBY-1953
> URL: http://issues.apache.org/jira/browse/DERBY-1953
> Project: Derby
> Issue Type: Improvement
> Components: SQL, Documentation
>Affects Versions: 10.2.1.6, 10.3.0.0
> Environment: Any
>Reporter: Yip Ng
> Assigned To: Yip Ng
>Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-1770-tests-v2.diff, derby-1770-tests-v2.stat,
> derby-1770-tests.diff, derby-1770-tests.stat, derby1953-trunk-diff01.txt,
> derby1953-trunk-diff02.txt, derby1953-trunk-diff03.txt,
> derby1953-trunk-diff04.txt, derby1953-trunk-dita-diff01.txt,
> derby1953-trunk-dita-stat01.txt, derby1953-trunk-stat01.txt,
> derby1953-trunk-stat02.txt, derby1953-trunk-stat03.txt,
> derby1953-trunk-stat04.txt
>
>
> According to SQL:2003 standard, section 11.39 , under
> Syntax Rules item 8:
> If neither FOR EACH ROW nor FOR EACH STATEMENT is specified, then FOR EACH
> STATEMENT is implicit.
> [ FOR EACH { ROW | STATEMENT } ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--
Attachment: derby1953-trunk-dita-stat01.txt
derby1953-trunk-dita-diff01.txt
Attaching documentation patch derby1953-trunk-dita-diff01.txt for this jira.
The patch updates the ref manual - CREATE TRIGGER syntax and examples. Please
review.
> Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional
> -
>
> Key: DERBY-1953
> URL: http://issues.apache.org/jira/browse/DERBY-1953
> Project: Derby
> Issue Type: Improvement
> Components: SQL, Documentation
>Affects Versions: 10.2.1.6, 10.3.0.0
> Environment: Any
>Reporter: Yip Ng
> Assigned To: Yip Ng
>Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-1770-tests-v2.diff, derby-1770-tests-v2.stat,
> derby-1770-tests.diff, derby-1770-tests.stat, derby1953-trunk-diff01.txt,
> derby1953-trunk-diff02.txt, derby1953-trunk-diff03.txt,
> derby1953-trunk-diff04.txt, derby1953-trunk-dita-diff01.txt,
> derby1953-trunk-dita-stat01.txt, derby1953-trunk-stat01.txt,
> derby1953-trunk-stat02.txt, derby1953-trunk-stat03.txt,
> derby1953-trunk-stat04.txt
>
>
> According to SQL:2003 standard, section 11.39 , under
> Syntax Rules item 8:
> If neither FOR EACH ROW nor FOR EACH STATEMENT is specified, then FOR EACH
> STATEMENT is implicit.
> [ FOR EACH { ROW | STATEMENT } ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Laura Stewart as committer
"Jean T. Anderson" <[EMAIL PROTECTED]> writes: > I propose that we add Laura Stewart as a committer for Derby. +1 -- Knut Anders
[jira] Commented: (DERBY-2018) NullPointerException in CREATE VIEW ... VALUES NULL;
[ http://issues.apache.org/jira/browse/DERBY-2018?page=comments#action_12448855 ] Bryan Pendleton commented on DERBY-2018: I get this diff with or without the patch, so it's not a problem with the patch. Must be something odd in my environment. > NullPointerException in CREATE VIEW ... VALUES NULL; > > > Key: DERBY-2018 > URL: http://issues.apache.org/jira/browse/DERBY-2018 > Project: Derby > Issue Type: Bug > Components: SQL >Affects Versions: 10.2.1.6 > Environment: Java 1.5.0_06-b05 >Reporter: Christian d'Heureuse > Assigned To: Yip Ng >Priority: Minor > Attachments: derby2018-trunk-diff01.txt, derby2018-trunk-stat01.txt > > > The following statement produces a NullPointerException: >CREATE VIEW v1 (f1) AS VALUES NULL; > Stack trace: > > 2006-10-30 12:39:31.750 GMT: > Booting Derby version The Apache Software Foundation - Apache Derby - > 10.2.1.6 - (452058): instance c013800d-010e-993b-512f-0012f418 > on database directory C:\temp_sys\temp_Derby_TestErr_db > Database Class Loader started - derby.database.classpath='' > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Cleanup > action starting > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Failed > Statement is: CREATE VIEW v1 (f1) AS VALUES NULL > java.lang.NullPointerException > at > org.apache.derby.impl.sql.catalog.SYSCOLUMNSRowFactory.makeRow(Unknown Source) > at > org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorArray(Unknown > Source) > at > org.apache.derby.impl.sql.execute.CreateViewConstantAction.executeConstantAction(Unknown > Source) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.tools.ij.ij.executeImmediate(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.doCatch(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.mainCore(Unknown Source) > at org.apache.derby.impl.tools.ij.Main14.main(Unknown Source) > at org.apache.derby.tools.ij.main(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Regression Test Report - tinderbox_trunk15 473410 - Sun DBTG
[Auto-generated mail] *tinderbox_trunk15* 473410/2006-11-10 19:22:37 CET Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 1516515 2 121.37% derbyall 020402040 0 118.99% org.apache.derbyTesting.functionTests.suites.All Details in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/testing/Limited/testSummary-473410.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/FailReports/473410.html --- Changes in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/UpdateInfo/473410.txt ( All results in http://dbtg.thresher.com/derby/test/ )
[jira] Commented: (DERBY-2018) NullPointerException in CREATE VIEW ... VALUES NULL;
[ http://issues.apache.org/jira/browse/DERBY-2018?page=comments#action_12448852 ] Bryan Pendleton commented on DERBY-2018: I get the following diff on lang/views.sql. I wonder if this is somehow an issue with carriage-return/line-feed issues? I think the patch was generated on Windows and I am trying to apply it on Linux. java org.apache.derbyTesting.functionTests.harness.RunTest lang/views.sql *** Start: views jdk1.4.2_11 2006-11-10 12:58:17 *** 18d17 < 74d72 < Test Failed. *** End: views jdk1.4.2_11 2006-11-10 12:58:23 *** > NullPointerException in CREATE VIEW ... VALUES NULL; > > > Key: DERBY-2018 > URL: http://issues.apache.org/jira/browse/DERBY-2018 > Project: Derby > Issue Type: Bug > Components: SQL >Affects Versions: 10.2.1.6 > Environment: Java 1.5.0_06-b05 >Reporter: Christian d'Heureuse > Assigned To: Yip Ng >Priority: Minor > Attachments: derby2018-trunk-diff01.txt, derby2018-trunk-stat01.txt > > > The following statement produces a NullPointerException: >CREATE VIEW v1 (f1) AS VALUES NULL; > Stack trace: > > 2006-10-30 12:39:31.750 GMT: > Booting Derby version The Apache Software Foundation - Apache Derby - > 10.2.1.6 - (452058): instance c013800d-010e-993b-512f-0012f418 > on database directory C:\temp_sys\temp_Derby_TestErr_db > Database Class Loader started - derby.database.classpath='' > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Cleanup > action starting > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Failed > Statement is: CREATE VIEW v1 (f1) AS VALUES NULL > java.lang.NullPointerException > at > org.apache.derby.impl.sql.catalog.SYSCOLUMNSRowFactory.makeRow(Unknown Source) > at > org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorArray(Unknown > Source) > at > org.apache.derby.impl.sql.execute.CreateViewConstantAction.executeConstantAction(Unknown > Source) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.tools.ij.ij.executeImmediate(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.doCatch(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.mainCore(Unknown Source) > at org.apache.derby.impl.tools.ij.Main14.main(Unknown Source) > at org.apache.derby.tools.ij.main(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Laura Stewart as committer
Jean T. Anderson wrote: I propose that we add Laura Stewart as a committer for Derby. +1 -suresh
Re: [VOTE] Laura Stewart as committer
+1 Henri Jean T. Anderson wrote: I propose that we add Laura Stewart as a committer for Derby.
Re: [VOTE] Laura Stewart as committer
Jean T. Anderson wrote: I propose that we add Laura Stewart as a committer for Derby. +1
Re: [VOTE] Laura Stewart as committer
+1 Jean T. Anderson wrote: I propose that we add Laura Stewart as a committer for Derby. At last count, Laura has contributed patches for over 30 documentation issues and she has also been driving the development of writing guidelines for the Derby web site. She has been contributing so many patches, it's getting difficult to keep up with her! Please vote +1 if you approve of Laura as a committer. I'll close the vote at noon PST on Wednesday, November 15th. -jean -- /* Tomohito Nakayama [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Naka http://www5.ocn.ne.jp/~tomohito/TopPage.html */
Re: Contribution of System tests for Derby
Daniel John Debrunner wrote: Manjula G Kutty wrote: Hello, As a continued effort towards improving Derby quality, I wish to contribute some long running system tests for Derby. Here is a brief description of each: [snip - four test descriptions] Sounds good, look forward to have this additional testing ability. I don't think these tests can be run as functional tests on a nightly basis. Some of these could be run for weeks and would be useful to test release candidates. It might be useful to run some form as functional tests, this at least ensures the test is not broken by some change. That of course could be done subsequent to the contribution. Possibly it's useful to think of these as test toolkits and not just their potential use to a long running test. For example with the OE I imagine there is a functional test that could be written to ensure the schema scripts work, data can be loaded etc. I suggest org.apache.derbyTesting.system.tests. as a location for these tests. I put the OE test, which is similar in concept to what you describe, directly under org.apache.derbyTesting.system. I don't think there's any benefit to that extra 'tests'. So I would propose: org.apache.derbyTesting.system. to match oe. I would also suggest a new ant target to build these classes. So that the simple ant command do not have to compile these test classes everytime. If any one wants them, they could run it as ant . Probably should be included in the all target, probably depends on how much extra time is involved. Thanks, Dan. Thanks Dan for your valuable suggestions. Thanks Dan for your valuable suggestions. I will open individual jira entries for each test to contribute them one by one. I agree the package name can be org.apache.derbyTesting.system., similar to the order entry tests. The time taken to compile them is very minimal hence we can include these tests in the ant all target. A readme file that tells how to run and check the results will be included in each of the tests. Also note that these tests can be run for few hours since there is no explicit exit conditions, so anyone can choose to run them for the desired duration by using some sort of utility wrappers around them Please let me know if you have any further questions. Thanks Manjula
Re: build failure (Re: svn commit: r473416 - .../JarUtil.java)
Andrew McIntyre wrote: On 11/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Author: djd Date: Fri Nov 10 10:30:50 2006 New Revision: 473416 URL: http://svn.apache.org/viewvc?view=rev&rev=473416 Log: DERBY-537 (partial) Cleanup JarUtil removing code that is never called and making class package private. Seeing this build failure after this change: Fixed, missed a file on the commit. Sorry, Dan.
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional
[
http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12448830 ]
Yip Ng commented on DERBY-1953:
---
I think this issue can be marked as resolved once the ref manual
documentation's CREATE TRIGGER syntax is updated.
::=
[ FOR EACH { ROW | STATEMENT } ]
[ MODE DB2SQL ]
> Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional
> -
>
> Key: DERBY-1953
> URL: http://issues.apache.org/jira/browse/DERBY-1953
> Project: Derby
> Issue Type: Improvement
> Components: SQL, Documentation
>Affects Versions: 10.2.1.6, 10.3.0.0
> Environment: Any
>Reporter: Yip Ng
> Assigned To: Yip Ng
>Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-1770-tests-v2.diff, derby-1770-tests-v2.stat,
> derby-1770-tests.diff, derby-1770-tests.stat, derby1953-trunk-diff01.txt,
> derby1953-trunk-diff02.txt, derby1953-trunk-diff03.txt,
> derby1953-trunk-diff04.txt, derby1953-trunk-stat01.txt,
> derby1953-trunk-stat02.txt, derby1953-trunk-stat03.txt,
> derby1953-trunk-stat04.txt
>
>
> According to SQL:2003 standard, section 11.39 , under
> Syntax Rules item 8:
> If neither FOR EACH ROW nor FOR EACH STATEMENT is specified, then FOR EACH
> STATEMENT is implicit.
> [ FOR EACH { ROW | STATEMENT } ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r473416 - /db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/execute/JarUtil.java
On 11/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: djd
Date: Fri Nov 10 10:30:50 2006
New Revision: 473416
URL: http://svn.apache.org/viewvc?view=rev&rev=473416
Log:
DERBY-537 (partial) Cleanup JarUtil removing code that is never called and
making class package private.
Modified:
db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/execute/JarUtil.java
Modified:
db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/execute/JarUtil.java
URL:
http://svn.apache.org/viewvc/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/execute/JarUtil.java?view=diff&rev=473416&r1=473415&r2=473416
==
---
db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/execute/JarUtil.java
(original)
+++
db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/execute/JarUtil.java
Fri Nov 10 10:30:50 2006
@@ -48,12 +48,8 @@
import java.sql.Connection;
import java.sql.SQLException;
-public class JarUtil
+class JarUtil
{
- public static final String ADD_JAR_DDL = "ADD JAR";
- public static final String DROP_JAR_DDL = "DROP JAR";
- public static final String REPLACE_JAR_DDL = "REPLACE JAR";
- public static final String READ_JAR = "READ JAR";
//
//State passed in by the caller
private UUID id; //For add null means create a new id.
@@ -68,7 +64,7 @@
//
//State derived from the caller's context
- public JarUtil(UUID id, String schemaName, String sqlName)
+ private JarUtil(UUID id, String schemaName, String sqlName)
throws StandardException
{
this.id = id;
@@ -93,7 +89,7 @@
@exception StandardException Opps
*/
- static public long
+ static long
add(UUID id, String schemaName, String sqlName, String externalPath)
throws StandardException
{
@@ -121,7 +117,7 @@
@param is A stream for reading the content of the file to add.
@exception StandardException Opps
*/
- public long add(InputStream is) throws StandardException
+ private long add(InputStream is) throws StandardException
{
//
//Like create table we say we are writing before we read the dd
@@ -160,7 +156,7 @@
@exception StandardException Opps
*/
- static public void
+ static void
drop(UUID id, String schemaName, String sqlName,boolean purgeOnCommit)
throws StandardException
{
@@ -179,7 +175,7 @@
@exception StandardException Opps
*/
- public void drop(boolean purgeOnCommit) throws StandardException
+ private void drop(boolean purgeOnCommit) throws StandardException
{
//
//Like create table we say we are writing before we read the dd
@@ -249,7 +245,7 @@
@exception StandardException Opps
*/
- static public long
+ static long
replace(UUID id,String schemaName, String sqlName,
String externalPath,boolean purgeOnCommit)
throws StandardException
@@ -283,7 +279,7 @@
means leave it around for use by replication.
@exception StandardException Opps
*/
- public long replace(InputStream is,boolean purgeOnCommit) throws
StandardException
+ private long replace(InputStream is,boolean purgeOnCommit) throws
StandardException
{
//
//Like create table we say we are writing before we read the dd
@@ -333,22 +329,6 @@
}
/**
- Get the FileInfoDescriptor for a jar file from the current
connection's database or
- null if it does not exist.
-
- @param schemaName the name for the schema that holds the jar file.
- @param sqlName the sql name for the jar file.
- @return The FileInfoDescriptor.
- @exception StandardException Opps
- */
- public static FileInfoDescriptor getInfo(String schemaName, String
sqlName, String statementType)
-throws StandardException
- {
- JarUtil jUtil = new JarUtil(null,schemaName,sqlName);
- return jUtil.getInfo();
- }
-
- /**
Get the FileInfoDescriptor for the Jar file or null if it does not
exist.
@exception StandardException Ooops
*/
@@ -357,44 +337,6 @@
{
SchemaDescriptor sd = dd.getSchemaDescriptor(schemaName, null,
true);
return dd.getFileInfoDescriptor(sd,sqlName);
- }
-
- // get the current version of the jar file as a File or InputStream
- public static Object getAsObject(String schemaName, String sqlName)
-throws StandardException
- {
- JarUtil jUtil = new JarUtil(null,schemaName,sqlName);
-
- FileInfoDescriptor fid = jUtil.getInfo();
- if (fid == n
Re: [VOTE] Laura Stewart as committer
Jean T. Anderson wrote: I propose that we add Laura Stewart as a committer for Derby. +1 Sunitha.
[jira] Resolved: (DERBY-2048) LangScripts JUnit test fails in views.sql
[ http://issues.apache.org/jira/browse/DERBY-2048?page=all ] Yip Ng resolved DERBY-2048. --- Fix Version/s: 10.3.0.0 Resolution: Fixed I think this jira is resolved since I haven't seen the ordering diff again after this patch was applied to the trunk. > LangScripts JUnit test fails in views.sql > - > > Key: DERBY-2048 > URL: http://issues.apache.org/jira/browse/DERBY-2048 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.3.0.0 > Environment: Windows XP >Reporter: Yip Ng > Assigned To: Yip Ng > Fix For: 10.3.0.0 > > Attachments: derby2048-trunk-diff01.txt, derby2048-trunk-diff02.txt, > derby2048-trunk-stat01.txt > > > LangScripts JUnit test fails in views.sql > There was 1 failure: > 1) views(org.apache.derbyTesting.functionTests.tests.lang.LangScripts > )junit.fram > ework.ComparisonFailure: Output at line 104 expected:<...T1' because VIEW > 'SV[1]' is dependent on th...> but was:<...T1' because VIEW 'SV[2]' is > dependent on th...> > at > org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon(CanonTestCase.java:100) > at > org.apache.derbyTesting.functionTests.util.ScriptTestCase.runTest(ScriptTestCase.java:117) > at > org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:76) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) > at junit.extensions.TestSetup$1.protect(TestSetup.java:21) > at junit.extensions.TestSetup.run(TestSetup.java:25) > FAILURES!!! > Tests run: 2016, Failures: 1, Errors: 0 > Some observations: > If org.apache.derbyTesting.functionTests.tests.lang.LangScripts is used to > run views.sql as a single test, then it ran smoothly without a problem. > . > Time: 7.109 > OK (1 test) > But if views.sql is run as part of a suite, then the ordering diff occurs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Laura Stewart as committer
On 11/10/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: Please vote +1 if you approve of Laura as a committer. +1 Myrna
build failure (Re: svn commit: r473416 - .../JarUtil.java)
On 11/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Author: djd Date: Fri Nov 10 10:30:50 2006 New Revision: 473416 URL: http://svn.apache.org/viewvc?view=rev&rev=473416 Log: DERBY-537 (partial) Cleanup JarUtil removing code that is never called and making class package private. Seeing this build failure after this change: compile_impl_services_169: [javac] Compiling 52 source files to /Users/andrewm/derby/classes [javac] /Users/andrewm/derby/java/engine/org/apache/derby/impl/services/reflect/JarLoader.java:24: org.apache.derby.impl.sql.execute.JarUtil is not public in org.apache.derby.impl.sql.execute; cannot be accessed from outside package [javac] import org.apache.derby.impl.sql.execute.JarUtil; [javac] ^ [javac] 1 error andrew
Re: [VOTE] Laura Stewart as committer
Jean T. Anderson wrote: I propose that we add Laura Stewart as a committer for Derby. At last count, Laura has contributed patches for over 30 documentation issues and she has also been driving the development of writing guidelines for the Derby web site. She has been contributing so many patches, it's getting difficult to keep up with her! Please vote +1 if you approve of Laura as a committer. I'll close the vote at noon PST on Wednesday, November 15th. -jean +1. -Rajesh
Re: [VOTE] Laura Stewart as committer
+1 Jean T. Anderson wrote: I propose that we add Laura Stewart as a committer for Derby. At last count, Laura has contributed patches for over 30 documentation issues and she has also been driving the development of writing guidelines for the Derby web site. She has been contributing so many patches, it's getting difficult to keep up with her! Please vote +1 if you approve of Laura as a committer. I'll close the vote at noon PST on Wednesday, November 15th. -jean
Re: [VOTE] Laura Stewart as committer
I propose that we add Laura Stewart as a committer for Derby. Laura has been doing a great job on the docs. +1 thanks, bryan
Re: [VOTE] Laura Stewart as committer
On 11/10/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: I propose that we add Laura Stewart as a committer for Derby.+1Yip Ng
Re: [VOTE] Laura Stewart as committer
Jean T. Anderson wrote: I propose that we add Laura Stewart as a committer for Derby. +1 Olav
Re: [VOTE] Laura Stewart as committer
On 11/10/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: I propose that we add Laura Stewart as a committer for Derby. +1 andrew
Re: [VOTE] Laura Stewart as committer
Jean T. Anderson wrote: > I propose that we add Laura Stewart as a committer for Derby. +1 -jean
[VOTE] Laura Stewart as committer
I propose that we add Laura Stewart as a committer for Derby. At last count, Laura has contributed patches for over 30 documentation issues and she has also been driving the development of writing guidelines for the Derby web site. She has been contributing so many patches, it's getting difficult to keep up with her! Please vote +1 if you approve of Laura as a committer. I'll close the vote at noon PST on Wednesday, November 15th. -jean
[jira] Updated: (DERBY-2055) Add execution of the schema scripts for order entry
[ http://issues.apache.org/jira/browse/DERBY-2055?page=all ] Daniel John Debrunner updated DERBY-2055: - Derby Info: (was: [Patch Available]) Committed revision 473413 - Thanks Sunitha > Add execution of the schema scripts for order entry > --- > > Key: DERBY-2055 > URL: http://issues.apache.org/jira/browse/DERBY-2055 > Project: Derby > Issue Type: Sub-task > Components: Test >Reporter: Sunitha Kambhampati > Assigned To: Sunitha Kambhampati >Priority: Minor > Fix For: 10.3.0.0 > > Attachments: derby2055.diff.txt > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Regression Test Report - tinderbox_trunk15 473368 - Sun DBTG
[Auto-generated mail] *tinderbox_trunk15* 473368/2006-11-10 16:32:32 CET Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 1516515 2 122.51% derbyall 020402040 0 119.90% org.apache.derbyTesting.functionTests.suites.All Details in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/testing/Limited/testSummary-473368.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/FailReports/473368.html --- Changes in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/UpdateInfo/473368.txt ( All results in http://dbtg.thresher.com/derby/test/ )
[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mike Matrigali updated DERBY-606: - Do you know how you are going to fix this issue, definitely consider upgrade implications of any change made. I think any change to allow CompressedNumber to write a negative number is likely not going to be backward compatible - now maybe that does not matter as any attempt to write a negative number with it, is already a bug. The bit patterns for the compressed number representation are pretty carefully chosen assuming non-negative numbers. This code is used extensively in every row/column on disk in the database, so requiring a hard upgrade of the format is a large issue. a few easier paths: 1) rewrite the log format for the record to not compress the numbers. The space doesn't really matter as it doesn't happen very much. As this would be a new log format it should be handled under hard upgrade. The bug would not be fixed under soft upgrade. Probably should throw an error earlier if you see a negative number under soft upgrade. If we could set back time on the db this would seem the natural fix. Or maybe if you are soft upgrade you change the -1 to be the last page in the conglomerate, which would mean in this special case the code would think there was a free page when we know there aren't any, but this is only a hint anyway. If you go this route look at the upgrade tests and add a case for both soft and hard upgrade in 10.3. 2) change the conglomerate code to not generate negative numbers, maybe use something like maxint or maxlong. This will of course require looking at all the code that currently checks for -1. > SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables > > > Key: DERBY-606 > URL: http://issues.apache.org/jira/browse/DERBY-606 > Project: Derby > Issue Type: Bug > Components: Store >Affects Versions: 10.1.1.0 > Environment: Java 1.5.0_04 on Windows Server 2003 Web Edition >Reporter: Jeffrey Aguilera > Assigned To: Mayuresh Nirhali > Attachments: A606Test.java > > > SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails with one of the following error > messages when applied to a very large table (>2GB): > Log operation null encounters error writing itself out to the log stream, > this could be caused by an errant log operation or internal log buffer full > due to excessively large log operation. SQLSTATE: XJ001: Java exception: ': > java.io.IOException'. > or > The exception 'java.lang.ArrayIndexOutOfBoundsException' was thrown while > evaluating an expression. SQLSTATE: XJ001: Java exception: ': > java.lang.ArrayIndexOutOfBoundsException'. > In either case, no entry is written to the console log or to derby.log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-2042) Provide documentation for new RENAME COLUMN statement
[ http://issues.apache.org/jira/browse/DERBY-2042?page=all ] Bryan Pendleton closed DERBY-2042. -- Verified that doc is visible on the main apache site. > Provide documentation for new RENAME COLUMN statement > - > > Key: DERBY-2042 > URL: http://issues.apache.org/jira/browse/DERBY-2042 > Project: Derby > Issue Type: Improvement > Components: Documentation >Affects Versions: 10.3.0.0 >Reporter: Bryan Pendleton > Assigned To: Bryan Pendleton >Priority: Minor > Fix For: 10.3.0.0 > > Attachments: renameColumnDoc_v1.diff, renameColumnDoc_v2.diff, > renameColumnDoc_v3_changedSyntaxRefs.diff, > rrefsqljrenamecolumnstatement.html, rrefsqljrenamecolumnstatement.html, > rrefsqljrenamecolumnstatement.html > > > DERBY-1490 proposes to add a new RENAME COLUMN statement. Assuming that such > a statement is added, we need to update the documentation to describe this > new statement. DERBY-1490 describes the behavior of the statement in detail; > this issue is just to track the documentation, which I intend to address > separately after the DERBY-1490 changes are committed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali updated DERBY-606: --- Attachment: A606Test.java Attaching a repro for this issue. The idea for reproduction is to create a table with large number of records and delete most of them so that atleast the last AllocExtent is empty and then attempt to do a inplace_compress. This demonstrates the scenario of compressing AllocExtent with new_highest_page = -1. I would like to add this testcase to the existing suite. Any thoughts on which suite would be the most appropriate for such case and if there is any existing test which I can extend to include this case instead ?? > SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables > > > Key: DERBY-606 > URL: http://issues.apache.org/jira/browse/DERBY-606 > Project: Derby > Issue Type: Bug > Components: Store >Affects Versions: 10.1.1.0 > Environment: Java 1.5.0_04 on Windows Server 2003 Web Edition >Reporter: Jeffrey Aguilera > Assigned To: Mayuresh Nirhali > Attachments: A606Test.java > > > SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails with one of the following error > messages when applied to a very large table (>2GB): > Log operation null encounters error writing itself out to the log stream, > this could be caused by an errant log operation or internal log buffer full > due to excessively large log operation. SQLSTATE: XJ001: Java exception: ': > java.io.IOException'. > or > The exception 'java.lang.ArrayIndexOutOfBoundsException' was thrown while > evaluating an expression. SQLSTATE: XJ001: Java exception: ': > java.lang.ArrayIndexOutOfBoundsException'. > In either case, no entry is written to the console log or to derby.log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables
[ http://issues.apache.org/jira/browse/DERBY-606?page=all ] Mayuresh Nirhali reassigned DERBY-606: -- Assignee: Mayuresh Nirhali > SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables > > > Key: DERBY-606 > URL: http://issues.apache.org/jira/browse/DERBY-606 > Project: Derby > Issue Type: Bug > Components: Store >Affects Versions: 10.1.1.0 > Environment: Java 1.5.0_04 on Windows Server 2003 Web Edition >Reporter: Jeffrey Aguilera > Assigned To: Mayuresh Nirhali > > SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails with one of the following error > messages when applied to a very large table (>2GB): > Log operation null encounters error writing itself out to the log stream, > this could be caused by an errant log operation or internal log buffer full > due to excessively large log operation. SQLSTATE: XJ001: Java exception: ': > java.io.IOException'. > or > The exception 'java.lang.ArrayIndexOutOfBoundsException' was thrown while > evaluating an expression. SQLSTATE: XJ001: Java exception: ': > java.lang.ArrayIndexOutOfBoundsException'. > In either case, no entry is written to the console log or to derby.log. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Regression Test Report - Daily 472979 - Sun DBTG
[Auto-generated mail] *Daily* 472979/2006-11-09 18:00:09 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 5527522 099.72% derbyall 062796279 0 101.10% org.apache.derbyTesting.functionTests.suites.All sol NA NA NANA derbyall NA NA NANA org.apache.derbyTesting.functionTests.suites.All solN+1 5527522 0 115.46% derbyall 062796279 0 114.49% org.apache.derbyTesting.functionTests.suites.All sparc 5527522 099.55% derbyall 062796279 0 107.17% org.apache.derbyTesting.functionTests.suites.All win 5527522 0 149.20% derbyall F:0,E:5562796224 0 100.00% org.apache.derbyTesting.functionTests.suites.All Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-472979.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/472979.html *Jvm: 1.5* lin 3519516 299.59% derbyall 020322032 0 106.08% org.apache.derbyTesting.functionTests.suites.All sol 3519516 2 107.19% derbyall 020322032 0 105.82% org.apache.derbyTesting.functionTests.suites.All solN+1 3519516 2 120.53% derbyall 020322032 0 109.20% org.apache.derbyTesting.functionTests.suites.All sparc 3519516 2 100.16% derbyall 020322032 0 101.70% org.apache.derbyTesting.functionTests.suites.All win 3519516 2 159.02% derbyall 020322032 0 100.00% org.apache.derbyTesting.functionTests.suites.All Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-472979.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/472979.html *Jvm: 1.4* lin 3513510 499.60% derbyall 020302030 096.22% org.apache.derbyTesting.functionTests.suites.All sol 3513510 4 103.44% derbyall 020302030 088.69% org.apache.derbyTesting.functionTests.suites.All solN+1 3513510 4 121.26% derbyall 020302030 0 103.16% org.apache.derbyTesting.functionTests.suites.All sparc 3513510 499.83% derbyall 020302030 0 117.21% org.apache.derbyTesting.functionTests.suites.All win NA NA NANA derbyall NA NA NANA org.apache.derbyTesting.functionTests.suites.All Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-472979.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/472979.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/472979.txt ( All results in http://dbtg.thresher.com/derby/test/ )
[jira] Commented: (DERBY-2040) Setting derby.database.classpath to contain installed jars causes the database to be unbootable when a Securitymanager is installed.
[ http://issues.apache.org/jira/browse/DERBY-2040?page=comments#action_12448794 ] Daniel John Debrunner commented on DERBY-2040: -- Committed revision 473387. Create the class loaders (JarLoader instances) for database class loading within a privileged block. Solves the described problem but still unable to load classes from the jar files due to security exceptions. Need to ensure accessing the jar files from JarLoader is in a privileged block, but fix might be different is DERBY-538 is addressed. > Setting derby.database.classpath to contain installed jars causes the > database to be unbootable when a Securitymanager is installed. > > > Key: DERBY-2040 > URL: http://issues.apache.org/jira/browse/DERBY-2040 > Project: Derby > Issue Type: Bug > Components: Security, Services >Affects Versions: 10.2.1.6 >Reporter: Daniel John Debrunner > Assigned To: Daniel John Debrunner > Fix For: 10.3.0.0 > > > If the jars are sucessfully installed (without a security manager see > DERBY-537) and the class path set then subsequent boots with a security > manager fail with a SecurityException due to trying to install a class loader. > Related to DERBY-537 but not the same. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2018) NullPointerException in CREATE VIEW ... VALUES NULL;
[ http://issues.apache.org/jira/browse/DERBY-2018?page=comments#action_12448788 ] Bryan Pendleton commented on DERBY-2018: This patch looks good to me. I intend to commit it this weekend. > NullPointerException in CREATE VIEW ... VALUES NULL; > > > Key: DERBY-2018 > URL: http://issues.apache.org/jira/browse/DERBY-2018 > Project: Derby > Issue Type: Bug > Components: SQL >Affects Versions: 10.2.1.6 > Environment: Java 1.5.0_06-b05 >Reporter: Christian d'Heureuse > Assigned To: Yip Ng >Priority: Minor > Attachments: derby2018-trunk-diff01.txt, derby2018-trunk-stat01.txt > > > The following statement produces a NullPointerException: >CREATE VIEW v1 (f1) AS VALUES NULL; > Stack trace: > > 2006-10-30 12:39:31.750 GMT: > Booting Derby version The Apache Software Foundation - Apache Derby - > 10.2.1.6 - (452058): instance c013800d-010e-993b-512f-0012f418 > on database directory C:\temp_sys\temp_Derby_TestErr_db > Database Class Loader started - derby.database.classpath='' > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Cleanup > action starting > 2006-10-30 12:39:38.484 GMT Thread[main,5,main] (XID = 122), (SESSIONID = 0), > (DATABASE = c:\temp_sys\temp_Derby_TestErr_db), (DRDAID = null), Failed > Statement is: CREATE VIEW v1 (f1) AS VALUES NULL > java.lang.NullPointerException > at > org.apache.derby.impl.sql.catalog.SYSCOLUMNSRowFactory.makeRow(Unknown Source) > at > org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorArray(Unknown > Source) > at > org.apache.derby.impl.sql.execute.CreateViewConstantAction.executeConstantAction(Unknown > Source) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown > Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > at org.apache.derby.impl.tools.ij.ij.executeImmediate(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.doCatch(Unknown Source) > at org.apache.derby.impl.tools.ij.utilMain.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.go(Unknown Source) > at org.apache.derby.impl.tools.ij.Main.mainCore(Unknown Source) > at org.apache.derby.impl.tools.ij.Main14.main(Unknown Source) > at org.apache.derby.tools.ij.main(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Subscription: Derby: JIRA issues with patch available
Issue Subscription Filter: Derby: JIRA issues with patch available (14 issues) Subscriber: derby-dev Key Summary DERBY-638 Network driver setTransactionIsolation() causes a commit, but does not complete it locally http://issues.apache.org/jira/browse/DERBY-638 DERBY-2054 Rewrite 'derbynet/SuicideOfStreaming' to a JUnit test http://issues.apache.org/jira/browse/DERBY-2054 DERBY-2067 Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java http://issues.apache.org/jira/browse/DERBY-2067 DERBY-2001 Add DITA templates for the 3 topic types into the trunk http://issues.apache.org/jira/browse/DERBY-2001 DERBY-2018 NullPointerException in CREATE VIEW ... VALUES NULL; http://issues.apache.org/jira/browse/DERBY-2018 DERBY-2055 Add execution of the schema scripts for order entry http://issues.apache.org/jira/browse/DERBY-2055 DERBY-1972 Working With Derby needs some formatting fixes and other minor cleanup http://issues.apache.org/jira/browse/DERBY-1972 DERBY-2030 'set schema sys' followed by 'show tables' does not show tables in sys schema http://issues.apache.org/jira/browse/DERBY-2030 DERBY-1693 Out of Memory Error with derby.language.logStatementText=true http://issues.apache.org/jira/browse/DERBY-1693 DERBY-1808 [PATCH] Inbuilt functions SIGN, SQRT, RAND, RANDOM, COSH, SINH and TANH http://issues.apache.org/jira/browse/DERBY-1808 DERBY-2009 Modify links to reflect that Sun DBTG test reports have moved to dbtg.thresher.com http://issues.apache.org/jira/browse/DERBY-2009 DERBY-1938 Add support for setObject(, null) http://issues.apache.org/jira/browse/DERBY-1938 DERBY-963 Allow user friendly string values for security mechanism in client connection url. http://issues.apache.org/jira/browse/DERBY-963 DERBY-646 In-memory backend storage support http://issues.apache.org/jira/browse/DERBY-646
[jira] Resolved: (DERBY-2047) TestDataSourceFactory doesn't work correctly outside the old harness
[ http://issues.apache.org/jira/browse/DERBY-2047?page=all ] Daniel John Debrunner resolved DERBY-2047. -- Fix Version/s: 10.3.0.0 Resolution: Fixed Committed revision 473366. TestDataSourceFactory removed and replaced with J2EEDataSourrce and JDBCDataSource which are independent of the old harness. > TestDataSourceFactory doesn't work correctly outside the old harness > > > Key: DERBY-2047 > URL: http://issues.apache.org/jira/browse/DERBY-2047 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.3.0.0 >Reporter: Knut Anders Hatlen > Assigned To: Daniel John Debrunner > Fix For: 10.3.0.0 > > Attachments: DataSource.java, derby-2047.diff, derby-2047.stat > > > TestDataSourceFactory uses TestUtil to create DataSource, > ConnectionPoolDataSource and XADataSource objects. TestUtil needs to run in > the old harness in order to detect which framework it is running under, so it > will create embedded data sources for all JUnit tests that are run outside > the old harness. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2071) How to initialise BLOB in Derby.
[ http://issues.apache.org/jira/browse/DERBY-2071?page=comments#action_12448769 ] Daniel John Debrunner commented on DERBY-2071: -- JDBC 4 provides createBlob and createClob methods on Connection. Derby 10.2 supports these methods when running in a JDK 6 environment. With non-JDBC 4 implementations there is no corresponding feature, one can insert into a BLOB column using a byte[] or an InputStream. > How to initialise BLOB in Derby. > > > Key: DERBY-2071 > URL: http://issues.apache.org/jira/browse/DERBY-2071 > Project: Derby > Issue Type: Bug >Reporter: kishorevodnala > > In oracle there is empty_blob function to initialise a BLOB.Is there any way > to initialise BLOB in Derby . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-638) Network driver setTransactionIsolation() causes a commit, but does not complete it locally
[ http://issues.apache.org/jira/browse/DERBY-638?page=all ]
Bernt M. Johnsen updated DERBY-638:
---
Attachment: DERBY-638-v3.diff
DERBY-638-v3.stat
Uploaded new patch (V3) whith test change that will catch changes in wether
setTransactionIsolation commits or not.
> Network driver setTransactionIsolation() causes a commit, but does not
> complete it locally
> --
>
> Key: DERBY-638
> URL: http://issues.apache.org/jira/browse/DERBY-638
> Project: Derby
> Issue Type: Bug
> Components: Network Client
>Affects Versions: 10.2.1.6
>Reporter: Deepa Remesh
> Assigned To: Bernt M. Johnsen
> Attachments: d638.java, d638_repro2.java, d638_repro3.java,
> DERBY-638-v2.diff, DERBY-638-v3.diff, DERBY-638-v3.stat, DERBY-638.diff
>
>
> When autocommit is set to false, a call to setTransactionIsolation using
> client driver does not end the transaction when the method exits. When a
> close() is called on the conection, it throws an exception.
> Running the code below:
>conn.setAutoCommit(false);
>conn.setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED);
>try{
>conn.close();
>}catch(SQLException se){
>System.out.println("Got exception when closing the
> connection");
>se.printStackTrace();
>}
> with client driver gives:
> Got exception when closing the connection
> org.apache.derby.client.am.SqlException: java.sql.Connection.close()
> requested while a transaction is in progress on the connection.The
> transaction remains active, and the connection cannot be closed.
> with embedded driver, it works okay and does not throw any exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1971) Make TestConfiguration set descriptive names for TestSuite objects it instantiates
[ http://issues.apache.org/jira/browse/DERBY-1971?page=all ] Kristian Waagan closed DERBY-1971. -- > Make TestConfiguration set descriptive names for TestSuite objects it > instantiates > -- > > Key: DERBY-1971 > URL: http://issues.apache.org/jira/browse/DERBY-1971 > Project: Derby > Issue Type: Improvement > Components: Test >Affects Versions: 10.3.0.0 >Reporter: Kristian Waagan > Assigned To: Daniel John Debrunner >Priority: Minor > Fix For: 10.3.0.0 > > > Several JUnit tools make use of TestSuite.getName() to display test > hierarchies and other information. An example is junit.swingui.TestRunner. > Currently, the TestSuite objects generated by TestConfiguration are not given > names. > To improve readability and the level of information, descriptive named should > be set. At a minimum, the associated framework should be indicated. Another > point is whether the user set name (if any) of the "root test suite" should > be propagated or not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-2027) JUnit suite All crashes with OutOfMemoryError when running LobLengthTest
[ http://issues.apache.org/jira/browse/DERBY-2027?page=all ] Kristian Waagan closed DERBY-2027. -- > JUnit suite All crashes with OutOfMemoryError when running LobLengthTest > > > Key: DERBY-2027 > URL: http://issues.apache.org/jira/browse/DERBY-2027 > Project: Derby > Issue Type: Bug > Components: Test >Affects Versions: 10.3.0.0 > Environment: General, but default heap space size for the VM used > matters. >Reporter: Kristian Waagan > Assigned To: Kristian Waagan > Fix For: 10.3.0.0 > > Attachments: derby-2027-1a.diff > > > The All suite crashes when running jdbcapi/LobLengthTest. > It is reasonable to believe the memory usage accumulates and that this test > makes the memory usage too high. > Looking at the test, it uses a ~16 MB byte array. > This problem was reported on derby-dev: > http://www.nabble.com/Out-of-memory-error-when-running-JUnit-suite-t2549103.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2054) Rewrite 'derbynet/SuicideOfStreaming' to a JUnit test
[ http://issues.apache.org/jira/browse/DERBY-2054?page=all ] Kristian Waagan updated DERBY-2054: --- Derby Info: [Patch Available] > Rewrite 'derbynet/SuicideOfStreaming' to a JUnit test > - > > Key: DERBY-2054 > URL: http://issues.apache.org/jira/browse/DERBY-2054 > Project: Derby > Issue Type: Test > Components: Test >Affects Versions: 10.3.0.0 >Reporter: Kristian Waagan > Assigned To: Kristian Waagan >Priority: Minor > Attachments: derby-2054-1a.diff, derby-2054-1a.stat, > derby-2054-preview.diff > > > The test 'derbynet/SuicideOfStreaming' should be rewritten to a JUnit test > more in line with our newly created test system. > It is one of the last tests still being run from the deprecated > 'tests/junitTests/' directory, through a wrapper class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2054) Rewrite 'derbynet/SuicideOfStreaming' to a JUnit test
[ http://issues.apache.org/jira/browse/DERBY-2054?page=all ] Kristian Waagan updated DERBY-2054: --- Attachment: derby-2054-1a.diff derby-2054-1a.stat Thanks Tomohito. My patch removes several files. 'derby-2054-1a.diff' rewrites the SuicideOfStreaming tests to a JUnit test and: Deletes files no longer needed, adds SqlException and ByteArrayCombinerStreamTest to derbynet/_Suite, update suite files for the old harness, rewrite DDMWriter so that it requires the debug property to be true (not only set). Patch ready for review/commit. > Rewrite 'derbynet/SuicideOfStreaming' to a JUnit test > - > > Key: DERBY-2054 > URL: http://issues.apache.org/jira/browse/DERBY-2054 > Project: Derby > Issue Type: Test > Components: Test >Affects Versions: 10.3.0.0 >Reporter: Kristian Waagan > Assigned To: Kristian Waagan >Priority: Minor > Attachments: derby-2054-1a.diff, derby-2054-1a.stat, > derby-2054-preview.diff > > > The test 'derbynet/SuicideOfStreaming' should be rewritten to a JUnit test > more in line with our newly created test system. > It is one of the last tests still being run from the deprecated > 'tests/junitTests/' directory, through a wrapper class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DERBY-2071) How to initialise BLOB in Derby.
How to initialise BLOB in Derby. Key: DERBY-2071 URL: http://issues.apache.org/jira/browse/DERBY-2071 Project: Derby Issue Type: Bug Reporter: kishorevodnala In oracle there is empty_blob function to initialise a BLOB.Is there any way to initialise BLOB in Derby . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2070) Is there a way to initialise a BLOB in derby, and how to insert a document object in Derby
[
http://issues.apache.org/jira/browse/DERBY-2070?page=comments#action_12448705 ]
Anurag Shekhar commented on DERBY-2070:
---
org.w3c.dom.Document doesn't extends from Serializable so it can't be written
into stream unless the implementation class is extending from the same. In case
of Crimson the implementation doesn't appears to be be extending from it
either. Hence the java.io.NotSerializableException.
So you may have to either insert the XML file as text stream into blob or clob
fields. If you are using derby 10.2 you can look into XML data type and
functions related to that to see if it meets your requirements.
here is the link of ref. manual if you want to know more about XML functions
available in derby
http://db.apache.org/derby/docs/10.2/ref/
> Is there a way to initialise a BLOB in derby, and how to insert a document
> object in Derby
> --
>
> Key: DERBY-2070
> URL: http://issues.apache.org/jira/browse/DERBY-2070
> Project: Derby
> Issue Type: Bug
> Environment: Windows 98,Derby ,JAVA.
>Reporter: kishorevodnala
>
> I have a problem while inserting an XML document object into a BLOB column in
> Derby database.
> Could you please help me out in resolving this problem.
> Note:there is empty_blob function in oracle for initialising a BLOB.Is there
> anything in derby for initialising a BLOB like in oracle.
> Following is the sample code.
> //creating a DOM object for a xml file and storing this object into the BLOB
> column in the database using streams.
> class exdom
> {
> public static void main(String ss[])
> {
> Document pdxDOM =buildDocument();//creating a DOM object for
> xml file
> serializePDXDOMToDB(pdxDOM); //storing this object into the
> BLOB column in the database using streams
> }
> public static Document buildDocument() {
> Document document = null;
> try {
> DocumentBuilderFactory builderFactory =
> DocumentBuilderFactory.newInstance();
> DocumentBuilder documentBuilder =
> builderFactory.newDocumentBuilder();
> document = documentBuilder.parse(new File("d:\\sample.xml"));
> } catch (Exception e) {e.printStackTrace();}
>
> return document;
> }
>public static void serializePDXDOMToDB(Document obj) {
> Connection conn = null;
> PreparedStatement ps = null;
> ResultSet rs = null;
> String query = "insert into ex9(bl) values(?) " ;
>
> try {
> Class.forName("org.apache.derby.jdbc.ClientDriver");
> String
> url="jdbc:derby://s104f50:1527/example;create=true";
>conn=DriverManager.getConnection(url);
>
> ps = conn.prepareStatement(query);
> ByteArrayOutputStream baos = new ByteArrayOutputStream();
> ObjectOutputStream oout = new ObjectOutputStream(baos);
> oout.writeObject(obj);
> oout.close();
>
> ps.setBytes(1, baos.toByteArray());
> ps.execute();
>
>
>
> }catch(Exception e){e.printStackTrace();}
>}
> }
>
> Following is the exception that occured while execution:
> java.io.NotSerializableException: org.apache.crimson.tree.XmlDocument
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
> at
> java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
> :1330)
> at
> java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
> 02)
> at
> java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
> a:1245)
> at
> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
> at exdom.serializePDXDOMToDB(exdom.java:42)
> at exdom.main(exdom.java:11)
> //this code is working fine for String and Integer objects but getting an
> Exception while trying to insert an XML Document object.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0
TomohitoNakayama wrote: > Hello. > > Thank you for your kindness :) > > What is needed is calling method which was introduced in JDBC 4.0 > from NetworkServer to utilize JDBC 4.0 feature in Engine. > Concretely,the method is PreparedStatement#setBinaryStream(int, > java.io.InputStream). > http://download.java.net/jdk6/docs/api/java/sql/PreparedStatement.html#setBinaryStream(int,%20java.io.InputStream) > > > What is important is that JDBC 4.0 is optional and > implementation to utilize the feature of it should be appropriately > placed in code of NetworkServer > in order to keep compatibility for previous spec in NetworkServer. > If I understand you correctly the issue is: - When using Layer B streaming, you want the Network Server to be able to use the new JDBC 4 methods for lengthless streaming. - The problem is that the JDBC 4 methods is not directly available to the NetworkServer if using older run-time libraries (e.g., Java SE 5). Since the implementation of the JDBC 4 methods will be part of derby.jar regardless of which JVM you are running on, I would guess it is just a question of how to make them available to the network server. -- Øystein
Re: Derby causes appserver hang with "maxthreads"
Hi, Posted a reply to this on derby-user. On second thought, I think there might be some technical discussion on this, so maybe we should continue the thread here anyway. Just wanted to let other users aware of the issue. -- Kristian Jagadish Prasath Ramu wrote: Hi, I am investigating an issue where Sun Application server hangs "temporarily"/"permanently" while talking to Derby Server. I could not reproduce the temporary hang. However I could make the hang permanent. Permanent Hang Steps : derby.properties will have the following settings: derby.drda.maxThreads=32 derby.drda.timeslice=2000 In appserver connection-pool, steady-pool-size is 34 (when the pool is initialized 34 connections will be created). When the pool is being initialized, derby.log prints that 31 or 32 or 33 connections had been created and appserver is trying to make another connection. Appserver hangs waiting for the response from derby. JStack output below : Thread 9782: (state = IN_NATIVE) - java.net.SocketInputStream.socketRead0(java.io.FileDescriptor, byte[], int, int, int) @bci=0 (Interpreted frame) - java.net.SocketInputStream.read(byte[], int, int) @bci=84, line=129 (Interpreted frame) - org.apache.derby.client.net.Reply.fill(int) @bci=34 (Interpreted frame) - org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(int) @bci=21 (Interpreted frame) - org.apache.derby.client.net.Reply.readDssHeader() @bci=7 (Interpreted frame) - org.apache.derby.client.net.Reply.startSameIdChainParse() @bci=1 (Interpreted frame) - org.apache.derby.client.net.NetConnectionReply.readExchangeServerAttributes(org.apache.derby.client.am.Connection) @bci=1 (Interpreted frame) - org.apache.derby.client.net.NetConnection.readServerAttributesAndKeyExchange(int) @bci=8 (Interpreted frame) - org.apache.derby.client.net.NetConnection.flowServerAttributesAndKeyExchange(int, byte[]) @bci=22 (Interpreted frame) - org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(java.lang.String) @bci=3 (Interpreted frame) - org.apache.derby.client.net.NetConnection.flowConnect(java.lang.String, int) @bci=163 (Interpreted frame) - org.apache.derby.client.net.NetConnection.initialize(java.lang.String, java.lang.String, org.apache.derby.jdbc.ClientDataSource, int, boolean) @bci=40 (Interpreted frame) - org.apache.derby.client.net.NetConnection.(org.apache.derby.client.net.NetLogWriter, java.lang.String, java.lang.String, org.apache.derby.jdbc.ClientDataSource, int, boolean) @bci=135 (Interpreted frame) - org.apache.derby.jdbc.ClientDataSource.getConnection(java.lang.String, java.lang.String) @bci=32 (Interpreted frame) - com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(javax.security.auth.Subject, javax.resource.spi.ConnectionRequestInfo) @bci=77, line=96 (Interpreted frame) - com.sun.enterprise.resource.LocalTxConnectorAllocator.createResource() @bci=12, line=56 (Interpreted frame) - com.sun.enterprise.resource.AbstractResourcePool.createSingleResource(com.sun.enterprise.resource.ResourceAllocator) @bci=8, line=756 (Interpreted frame) - com.sun.enterprise.resource.AbstractResourcePool.createResourceAndAddToPool(com.sun.enterprise.resource.ResourceAllocator) @bci=2, line=1515 (Interpreted frame) - com.sun.enterprise.resource.AbstractResourcePool.createResources(com.sun.enterprise.resource.ResourceAllocator, int) @bci=9, line=780 (Interpreted frame) - com.sun.enterprise.resource.AbstractResourcePool.initPool(com.sun.enterprise.resource.ResourceSpec, com.sun.enterprise.resource.ResourceAllocator) @bci=27, line=209 (Interpreted frame) - com.sun.enterprise.resource.AbstractResourcePool.internalGetResource(com.sun.enterprise.resource.ResourceSpec, com.sun.enterprise.resource.ResourceAllocator, javax.transaction.Transaction) @bci=10, line=501 (Interpreted frame) - com.sun.enterprise.resource.AbstractResourcePool.getResource(com.sun.enterprise.resource.ResourceSpec, com.sun.enterprise.resource.ResourceAllocator, javax.transaction.Transaction) @bci=37, line=428 (Interpreted frame) - com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(com.sun.enterprise.resource.ResourceSpec, com.sun.enterprise.resource.ResourceAllocator, com.sun.enterprise.resource.ClientSecurityInfo, javax.transaction.Transaction) @bci=16, line=248 (Interpreted frame) - com.sun.enterprise.resource.PoolManagerImpl.getResource(com.sun.enterprise.resource.ResourceSpec, com.sun.enterprise.resource.ResourceAllocator, com.sun.enterprise.resource.ClientSecurityInfo) @bci=34, line=174 (Interpreted frame) - com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(javax.resource.spi.ManagedConnectionFactory, com.sun.enterprise.deployment.ResourcePrincipal, javax.resource.spi.ConnectionRequestInfo, boolean, java.lang.String, java.lang.Object, boolean) @bci=388, line=312 (Interpreted frame) - com.sun.enterprise.c
Regression Test Report - tinderbox_trunk15 473205 - Sun DBTG
[Auto-generated mail] *tinderbox_trunk15* 473205/2006-11-10 07:32:22 CET Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 1516515 2 121.02% derbyall 020402040 0 106.63% org.apache.derbyTesting.functionTests.suites.All Details in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/testing/Limited/testSummary-473205.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/jvm1.5/FailReports/473205.html --- Changes in http://dbtg.thresher.com/derby/test/tinderbox_trunk15/UpdateInfo/473205.txt ( All results in http://dbtg.thresher.com/derby/test/ )
