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 "A B (JIRA)" <de...@db.apache.org> on 2005/05/26 19:51:52 UTC
[jira] Created: (DERBY-318) SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
--------------------------------------------------------------------------
Key: DERBY-318
URL: http://issues.apache.org/jira/browse/DERBY-318
Project: Derby
Type: Bug
Components: Network Server
Versions: 10.1.0.0
Environment: Derby in Network Server mode with either JCC or Derby Net Client.
Reporter: A B
When connected to the Derby Network Server, if one has a table with a column defined as "GENERATED BY DEFAULT" and then one tries to select the "COLUMNDEFAULT" field from SYS.SYSCOLUMNS, the result is an NPE in the server code that leads to connection deallocation.
I don't know if this is a problem with the "GENERATED BY DEFAULT" feature or if it's a problem with Network Server--more investigation is required.
To reproduce, use ij to connect to a database using Network Server, and then:
ij> create table t1 (i int generated by default as identity);
0 rows inserted/updated/deleted
ij> select columndefault from sys.syscolumns;
COLUMNDEFAULT
----------------------------------------------------------------------------------------------------
----------------------------
null
java.lang.NullPointerException
at org.apache.derby.impl.drda.DRDAConnThread.writeFdocaVal(DRDAConnThread.java:6550)
at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(DRDAConnThread.java:5973)
at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(DRDAConnThread.java:5796)
at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:595)
at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:226)
agentThread[DRDAConnThread_2,5,main]
ERROR 58009: Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x3
--
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-318) SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
Posted by "Samuel Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-318?page=all ]
Samuel Andrew McIntyre updated DERBY-318:
-----------------------------------------
Fix Version: 10.1.0.0
> SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
> --------------------------------------------------------------------------
>
> Key: DERBY-318
> URL: http://issues.apache.org/jira/browse/DERBY-318
> Project: Derby
> Type: Bug
> Components: Network Server
> Versions: 10.1.0.0
> Environment: Derby in Network Server mode with either JCC or Derby Net Client.
> Reporter: A B
> Fix For: 10.1.0.0
> Attachments: DERBY-318.patch, derbyall_diff.txt
>
> When connected to the Derby Network Server, if one has a table with a column defined as "GENERATED BY DEFAULT" and then one tries to select the "COLUMNDEFAULT" field from SYS.SYSCOLUMNS, the result is an NPE in the server code that leads to connection deallocation.
> I don't know if this is a problem with the "GENERATED BY DEFAULT" feature or if it's a problem with Network Server--more investigation is required.
> To reproduce, use ij to connect to a database using Network Server, and then:
> ij> create table t1 (i int generated by default as identity);
> 0 rows inserted/updated/deleted
> ij> select columndefault from sys.syscolumns;
> COLUMNDEFAULT
> ----------------------------------------------------------------------------------------------------
> ----------------------------
> null
> java.lang.NullPointerException
> at org.apache.derby.impl.drda.DRDAConnThread.writeFdocaVal(DRDAConnThread.java:6550)
> at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(DRDAConnThread.java:5973)
> at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(DRDAConnThread.java:5796)
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:595)
> at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:226)
> agentThread[DRDAConnThread_2,5,main]
> ERROR 58009: Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x3
--
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-318) SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-318?page=all ]
Tomohito Nakayama updated DERBY-318:
------------------------------------
Attachment: derbyall_diff.txt
Test result of previous uploaded patch.
> SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
> --------------------------------------------------------------------------
>
> Key: DERBY-318
> URL: http://issues.apache.org/jira/browse/DERBY-318
> Project: Derby
> Type: Bug
> Components: Network Server
> Versions: 10.1.0.0
> Environment: Derby in Network Server mode with either JCC or Derby Net Client.
> Reporter: A B
> Attachments: DERBY-318.patch, derbyall_diff.txt
>
> When connected to the Derby Network Server, if one has a table with a column defined as "GENERATED BY DEFAULT" and then one tries to select the "COLUMNDEFAULT" field from SYS.SYSCOLUMNS, the result is an NPE in the server code that leads to connection deallocation.
> I don't know if this is a problem with the "GENERATED BY DEFAULT" feature or if it's a problem with Network Server--more investigation is required.
> To reproduce, use ij to connect to a database using Network Server, and then:
> ij> create table t1 (i int generated by default as identity);
> 0 rows inserted/updated/deleted
> ij> select columndefault from sys.syscolumns;
> COLUMNDEFAULT
> ----------------------------------------------------------------------------------------------------
> ----------------------------
> null
> java.lang.NullPointerException
> at org.apache.derby.impl.drda.DRDAConnThread.writeFdocaVal(DRDAConnThread.java:6550)
> at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(DRDAConnThread.java:5973)
> at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(DRDAConnThread.java:5796)
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:595)
> at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:226)
> agentThread[DRDAConnThread_2,5,main]
> ERROR 58009: Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x3
--
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] Resolved: (DERBY-318) SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
Posted by "A B (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-318?page=all ]
A B resolved DERBY-318:
-----------------------
Resolution: Fixed
Assign To: Tomohito Nakayama
Patched committed with svn revision 179674 and I have verified that the repro given in the description for this issue has been fixed. Assigning to Tomohito since he was the one who wrote the fix, and then resolving and closing this issue.
> SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
> --------------------------------------------------------------------------
>
> Key: DERBY-318
> URL: http://issues.apache.org/jira/browse/DERBY-318
> Project: Derby
> Type: Bug
> Components: Network Server
> Versions: 10.1.0.0
> Environment: Derby in Network Server mode with either JCC or Derby Net Client.
> Reporter: A B
> Assignee: Tomohito Nakayama
> Fix For: 10.1.0.0
> Attachments: DERBY-318.patch, derbyall_diff.txt
>
> When connected to the Derby Network Server, if one has a table with a column defined as "GENERATED BY DEFAULT" and then one tries to select the "COLUMNDEFAULT" field from SYS.SYSCOLUMNS, the result is an NPE in the server code that leads to connection deallocation.
> I don't know if this is a problem with the "GENERATED BY DEFAULT" feature or if it's a problem with Network Server--more investigation is required.
> To reproduce, use ij to connect to a database using Network Server, and then:
> ij> create table t1 (i int generated by default as identity);
> 0 rows inserted/updated/deleted
> ij> select columndefault from sys.syscolumns;
> COLUMNDEFAULT
> ----------------------------------------------------------------------------------------------------
> ----------------------------
> null
> java.lang.NullPointerException
> at org.apache.derby.impl.drda.DRDAConnThread.writeFdocaVal(DRDAConnThread.java:6550)
> at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(DRDAConnThread.java:5973)
> at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(DRDAConnThread.java:5796)
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:595)
> at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:226)
> agentThread[DRDAConnThread_2,5,main]
> ERROR 58009: Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x3
--
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] Updated: (DERBY-318) SYS.SYSCOLUMN problem with "GENERATED
BY DEFAULT" column w/ Network Server
Posted by Satheesh Bandaram <sa...@Sourcery.Org>.
syscat.sql was added to derbynetmats probably just after David submitted
his patch. So, David couldn't have seen this diff in his test runs. I
will update the masters in DerbyNet and DerbyNetClient frameworks.
Satheesh
Andrew McIntyre wrote:
>
> On Jun 3, 2005, at 7:08 AM, Myrna van Lunteren wrote:
>
>> It looks like David didn't run derbynetmats or derbynetclientmats
>> when he ran the tests...at least, the canons for those two
>> frameworks haven't been updated for this test...
>> (files ...functionTests/master/derbynet/syscat.out and
>> functionTests/master/derbynetclient/syscat.out).
>
>
> Hmm. I ran derbyall as well, including the derbynet and
> derbynetclient suites, on XP and Mac, and not only didn't see this
> failure, but didn't get a skip message in the sum file either. It
> just didn't run in the frameworks tests...?
>
> Ah well, I'll figure it out and check in new masters for these in the
> meantime.
>
> andrew
>
>
>
Re: [jira] Updated: (DERBY-318) SYS.SYSCOLUMN problem with "GENERATED
BY DEFAULT" column w/ Network Server
Posted by Satheesh Bandaram <sa...@Sourcery.Org>.
I have updated both DerbyNet and DerbyNetClient masters for syscat.out.
The test passes in all frameworks now.
Satheesh
Andrew McIntyre wrote:
>
> On Jun 3, 2005, at 7:08 AM, Myrna van Lunteren wrote:
>
>> It looks like David didn't run derbynetmats or derbynetclientmats
>> when he ran the tests...at least, the canons for those two
>> frameworks haven't been updated for this test...
>> (files ...functionTests/master/derbynet/syscat.out and
>> functionTests/master/derbynetclient/syscat.out).
>
>
> Hmm. I ran derbyall as well, including the derbynet and
> derbynetclient suites, on XP and Mac, and not only didn't see this
> failure, but didn't get a skip message in the sum file either. It
> just didn't run in the frameworks tests...?
>
> Ah well, I'll figure it out and check in new masters for these in the
> meantime.
>
> andrew
>
>
>
Re: [jira] Updated: (DERBY-318) SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
Posted by Andrew McIntyre <mc...@gmail.com>.
On Jun 3, 2005, at 7:08 AM, Myrna van Lunteren wrote:
> It looks like David didn't run derbynetmats or derbynetclientmats
> when he ran the tests...at least, the canons for those two
> frameworks haven't been updated for this test...
> (files ...functionTests/master/derbynet/syscat.out and
> functionTests/master/derbynetclient/syscat.out).
Hmm. I ran derbyall as well, including the derbynet and
derbynetclient suites, on XP and Mac, and not only didn't see this
failure, but didn't get a skip message in the sum file either. It
just didn't run in the frameworks tests...?
Ah well, I'll figure it out and check in new masters for these in the
meantime.
andrew
Re: [jira] Updated: (DERBY-318) SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
Posted by Myrna van Lunteren <m....@gmail.com>.
I get a little confused over what has gone in or not, but I think this is
more related to the error message changes.
Note that the new line has a 'in this type' rather than 'on this type'.
ERROR 42Y90: FOR UPDATE is not permitted on this type of statement
It looks like David didn't run derbynetmats or derbynetclientmats when he
ran the tests...at least, the canons for those two frameworks haven't been
updated for this test...
(files ...functionTests/master/derbynet/syscat.out and
functionTests/master/derbynetclient/syscat.out).
Myrna
On 6/3/05, Øystein Grøvlen <Oy...@sun.com> wrote:
>
> >>>>> "TN(" == Tomohito Nakayama (JIRA) <de...@db.apache.org> writes:
>
> TN(> [ http://issues.apache.org/jira/browse/DERBY-318?page=all ]
> TN(> Tomohito Nakayama updated DERBY-318:
> TN(> ------------------------------------
>
> TN(> Attachment: DERBY-318.patch
>
> This bug seems to a introduced a test failure. In the networks test I
> now get:
>
> *** Start: syscat jdk1.4.2_05 DerbyNet derbynetmats:derbynetmats
> 2005-06-03 10:31:15 ***
> 29 del
> < ERROR 42Y90: FOR UPDATE is not permitted on this type of statement.
> 29a29
> > ERROR 42Y90: FOR UPDATE is not permitted in this type of statement.
> Test Failed.
> *** End: syscat jdk1.4.2_05 DerbyNet derbynetmats:derbynetmats 2005-06-03
> 10:31:35 ***
>
>
> Some extra spaces seems to have been added at the end of the failing
> line in the master file.
>
> --
> Øystein
>
>
Re: [jira] Updated: (DERBY-318) SYS.SYSCOLUMN problem with
"GENERATED BY DEFAULT" column w/ Network Server
Posted by Øystein Grøvlen <Oy...@Sun.COM>.
>>>>> "TN(" == Tomohito Nakayama (JIRA) <de...@db.apache.org> writes:
TN(> [ http://issues.apache.org/jira/browse/DERBY-318?page=all ]
TN(> Tomohito Nakayama updated DERBY-318:
TN(> ------------------------------------
TN(> Attachment: DERBY-318.patch
This bug seems to a introduced a test failure. In the networks test I
now get:
*** Start: syscat jdk1.4.2_05 DerbyNet derbynetmats:derbynetmats 2005-06-03 10:31:15 ***
29 del
< ERROR 42Y90: FOR UPDATE is not permitted on this type of statement.
29a29
> ERROR 42Y90: FOR UPDATE is not permitted in this type of statement.
Test Failed.
*** End: syscat jdk1.4.2_05 DerbyNet derbynetmats:derbynetmats 2005-06-03 10:31:35 ***
Some extra spaces seems to have been added at the end of the failing
line in the master file.
--
Øystein
[jira] Updated: (DERBY-318) SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
Posted by "Tomohito Nakayama (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-318?page=all ]
Tomohito Nakayama updated DERBY-318:
------------------------------------
Attachment: DERBY-318.patch
Modified:
1:
SYSCOLUMNS.COLUMNDEFAULT have "GENERATED_BY_DEFAULT",
if the SYSCOLUMNS record stands for default autoinc column.
2:
Test for 1: was added to lang/syscat.sql.
3:
lang/syscat.sql became to executed in derbynetmats.runall.
This results addition of syscat.sql to both of derbynet and derbynetclient.
Testing:
Executed derbyall and found three error.
They seems to be same error as next.
http://www.multinet.no/~solberg/public/Apache/Derby/testlog/SunOS-5.10_i86pc-i386/179247-derbynetclientmats_diff.txt
http://www.multinet.no/~solberg/public/Apache/Derby/testlog/Linux-2.4.20-31.9_i686-i686/179247-storeall_diff.txt
Test result will be uploaded next to this patch.
> SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
> --------------------------------------------------------------------------
>
> Key: DERBY-318
> URL: http://issues.apache.org/jira/browse/DERBY-318
> Project: Derby
> Type: Bug
> Components: Network Server
> Versions: 10.1.0.0
> Environment: Derby in Network Server mode with either JCC or Derby Net Client.
> Reporter: A B
> Attachments: DERBY-318.patch, derbyall_diff.txt
>
> When connected to the Derby Network Server, if one has a table with a column defined as "GENERATED BY DEFAULT" and then one tries to select the "COLUMNDEFAULT" field from SYS.SYSCOLUMNS, the result is an NPE in the server code that leads to connection deallocation.
> I don't know if this is a problem with the "GENERATED BY DEFAULT" feature or if it's a problem with Network Server--more investigation is required.
> To reproduce, use ij to connect to a database using Network Server, and then:
> ij> create table t1 (i int generated by default as identity);
> 0 rows inserted/updated/deleted
> ij> select columndefault from sys.syscolumns;
> COLUMNDEFAULT
> ----------------------------------------------------------------------------------------------------
> ----------------------------
> null
> java.lang.NullPointerException
> at org.apache.derby.impl.drda.DRDAConnThread.writeFdocaVal(DRDAConnThread.java:6550)
> at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(DRDAConnThread.java:5973)
> at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(DRDAConnThread.java:5796)
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:595)
> at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:226)
> agentThread[DRDAConnThread_2,5,main]
> ERROR 58009: Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x3
--
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-318) SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
Posted by "A B (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-318?page=all ]
A B closed DERBY-318:
---------------------
> SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
> --------------------------------------------------------------------------
>
> Key: DERBY-318
> URL: http://issues.apache.org/jira/browse/DERBY-318
> Project: Derby
> Type: Bug
> Components: Network Server
> Versions: 10.1.0.0
> Environment: Derby in Network Server mode with either JCC or Derby Net Client.
> Reporter: A B
> Assignee: Tomohito Nakayama
> Fix For: 10.1.0.0
> Attachments: DERBY-318.patch, derbyall_diff.txt
>
> When connected to the Derby Network Server, if one has a table with a column defined as "GENERATED BY DEFAULT" and then one tries to select the "COLUMNDEFAULT" field from SYS.SYSCOLUMNS, the result is an NPE in the server code that leads to connection deallocation.
> I don't know if this is a problem with the "GENERATED BY DEFAULT" feature or if it's a problem with Network Server--more investigation is required.
> To reproduce, use ij to connect to a database using Network Server, and then:
> ij> create table t1 (i int generated by default as identity);
> 0 rows inserted/updated/deleted
> ij> select columndefault from sys.syscolumns;
> COLUMNDEFAULT
> ----------------------------------------------------------------------------------------------------
> ----------------------------
> null
> java.lang.NullPointerException
> at org.apache.derby.impl.drda.DRDAConnThread.writeFdocaVal(DRDAConnThread.java:6550)
> at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(DRDAConnThread.java:5973)
> at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(DRDAConnThread.java:5796)
> at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:595)
> at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:226)
> agentThread[DRDAConnThread_2,5,main]
> ERROR 58009: Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x3
--
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