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] Updated: (DERBY-1637) OutBufferedStream.java fails on ibm131/jdk131 jvms.
Date Fri, 04 Aug 2006 17:20:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1637?page=all ]

Sunitha Kambhampati updated DERBY-1637:

    Attachment: outbuff_ibm131.jar

This test is hanging on my machine (win2k, T40 laptop, ibm131). with  derby jars
alpha - (428044M)

I did a control/pause break and I am attaching javacore dump files. 
It has the look of DERBY-300. 

With 142 jvms, the test passes OK and comes out in less than a minute.

The tmp file has only one line , start test. I let it run yesterday and the test didnt finish
for more than an hour. Also  I dont think the timeout mechanism is working for this combination
of jvm/test. 

I changed the timeout to 10 for derbynetclientmats, but the test does not timeout .

I am posting the test directory outbuff_ibm131.jar.

Is anyone else seeing this behavior ? 


> OutBufferedStream.java fails on ibm131/jdk131 jvms.
> ---------------------------------------------------
>                 Key: DERBY-1637
>                 URL: http://issues.apache.org/jira/browse/DERBY-1637
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions:
>         Environment: ibm131, sun jdk131 ,windows. derby jars are alpha - (426734)
>            Reporter: Sunitha Kambhampati
>             Fix For:
>         Attachments: 1637_jcc2.4.zip, javacore.20060804.101637.3308.txt, javacore.20060804.101643.3308.txt,
outbuff_ibm131.jar, outbuffstream_derbyall_report.txt
> OutBufferedStream test fails with ibm131 and jdk131. I'll attach the report file to this

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


View raw message