db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-900) Remove use of String(byte[]) and String(byte[], int, int) constructors in network client leading to non-portable behaviour
Date Thu, 11 May 2006 00:43:05 GMT
    [ http://issues.apache.org/jira/browse/DERBY-900?page=comments#action_12378999 ] 

Sunitha Kambhampati commented on DERBY-900:

Hi Kathey,

I synced up till about  yesterday as svn is down now and applied the p2 cleanup patch and
ran the testSecMec.java with sun 1.4.2_07 and it works OK on my win2000 laptop.  I ran this
test a couple of times and it passes OK.  The tmp file in testsecmec.zip seems to look like
as though the test exited in between - this behavior seems to me like the one seen in DERBY-1114.
 The jvm bug described in DERBY-1114 is fixed in 1.5 and 1.4.2_08 atleast from the entries
in the java bug database.   However, I didnt see windows platforms being mentioned anywhere
in the java bug report. 

can you please try running the test without the patch and see if it passes or not. and if
 the test passes with antoher jvm -jdk1.5. 


> Remove use of String(byte[]) and String(byte[], int, int) constructors in network client
leading to non-portable behaviour
> --------------------------------------------------------------------------------------------------------------------------
>          Key: DERBY-900
>          URL: http://issues.apache.org/jira/browse/DERBY-900
>      Project: Derby
>         Type: Bug

>   Components: Network Client
>     Reporter: Daniel John Debrunner
>     Assignee: Sunitha Kambhampati
>      Fix For:
>  Attachments: Derby900.p2.diff.txt, TestEnc.java, derby900.diff.p1.txt, derby900.p2.stat.txt,
derby900.p2_encodingChange.diff.txt, derby900.stat.p1.txt, derby900.test.diff.txt, derby900.test.stat.txt,
derby900_p2_cleanup.diff.txt, derby900_p2_cleanup.stat.txt, for_10.1_derby900.diff.p1.txt,
for_10.1_derby900.stat.p1.txt, testsecmec.zip
> These constructors use the Java default platform encoding to convert the bytes to a String,
this typically leads to bugs on platforms with different encodings.
> Replace with code using fixed conversion, or alternative mechanisms. 
> If the call is required its use should be commented as to why it is required.
> org.apache.derby.client.am.ClobOutputStream - some existing bug?
> org.apache.derby.client.am.DateTime - see DERBY-877
> org.apache.derby.client.am.sqlca
> I generated this list using the Java search in eclipse for references to the constructors
> String(byte[])
> String(byte[],int,int)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message