db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-4266) hang with sane jars with ibm 1.5 on iseries in lang/wisconsin.java
Date Sun, 27 Feb 2011 08:28:58 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren closed DERBY-4266.
-------------------------------------

            Resolution: Not A Problem
    Bug behavior facts:   (was: [Regression Test Failure])

I did do the verification test with 10.5.1.1 debug builds, and although the test with network
server took about 14 mins it did pass (although I did do a NetworkServerControl ping first,
which caused the system to 'attach' derbynet.jar).
I reran with 10.8.alpha and found that there too, the test took about 15 mins, but actually
finished. So there's no hang, no regression after all, running with sane jars & networkserver
on this platform is just a lot slower...

For comparison, with insane builds, both with embedded and with client the wisconsin test
takes about 4 minutes on the test machine; with sane builds, embedded took 6-8 minutes and
client took 14-15 minutes.

> hang with sane jars with ibm 1.5 on iseries in lang/wisconsin.java
> ------------------------------------------------------------------
>
>                 Key: DERBY-4266
>                 URL: https://issues.apache.org/jira/browse/DERBY-4266
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.6.1.0
>         Environment: IBM iseries, OS version: V5R4M0 
>            Reporter: Myrna van Lunteren
>              Labels: derby_triage10_8
>
> Found trying to verify a patch for DERBY-4142. 
> With sane jars of trunk, I see lang/wisconsin.java hang. 
> It seemed that it was dependent on my environment, but then a run with another build
(same revision, different environment, still sane jars) got the hang also - just not right
off the bat; a couple of queries were worked through.
> A run with insane jars did not hang.
> A run with sane jars of 10.5.1.1 is needed to find out whether this is a regression or
not.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message