db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TomohitoNakayama" <tomon...@basil.ocn.ne.jp>
Subject Re: anyone else seeing T_Diagnosticable test failure ?
Date Tue, 30 Aug 2005 14:18:18 GMT
Sorry.

Mistaken in previous mail .....

> 1:
> I removed all class of  org/apache/derby/iapi/services/diag from derby.jar.
> At this time, there exists DiagnosticUtil class in derby.jar as in 
> http://issues.apache.org/jira/browse/DERBY-496?page=comments#action_12317906
> and the test was passed.

not derby.jar .
I remove all class of diag package from "derbyTesting.jar" and remain "derby.jar ( and add
DiagnosticableGeneric)" ....

I removed all class of  org/apache/derby/iapi/services/diag from derbyTesting.jar.
At this time, there exists DiagnosticUtil class in derby.jar as in
http://issues.apache.org/jira/browse/DERBY-496?page=comments#action_12317906
and the test was passed.


Best regards.

/*

         Tomohito Nakayama
         tomonaka@basil.ocn.ne.jp
         tomohito@rose.zero.ad.jp
         tmnk@apache.org

         Naka
         http://www5.ocn.ne.jp/~tomohito/TopPage.html

*/
----- Original Message ----- 
From: "TomohitoNakayama" <tomonaka@basil.ocn.ne.jp>
To: "Derby Development" <derby-dev@db.apache.org>
Sent: Tuesday, August 30, 2005 11:11 PM
Subject: Re: anyone else seeing T_Diagnosticable test failure ?


> Hello.
> Error happend at my site .
>
>
> I found next Exception in derby.log
>
> java.lang.NoClassDefFoundError: org/apache/derby/iapi/services/diag/DiagnosticUtil
> at org.apache.derbyTesting.unitTests.services.T_Diagnosticable.t_001(T_Diagnosticable.java:100)
> at org.apache.derbyTesting.unitTests.services.T_Diagnosticable.runTestSet(T_Diagnosticable.java:207)
> at org.apache.derbyTesting.unitTests.harness.T_MultiIterations.runTests(T_MultiIterations.java:94)
> at org.apache.derbyTesting.unitTests.harness.T_Generic.Execute(T_Generic.java:117)
> at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runATest(BasicUnitTestManager.java:183)
> at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runTests(BasicUnitTestManager.java:245)
> at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:92)
> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:1996)
> at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:290)
> at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1834)
> at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:966)
> at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:398)
> at org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:57)
> at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:288)
> at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:50)
>
>
> I think what happened was as next ....
>
> 1:
> I removed all class of  org/apache/derby/iapi/services/diag from derby.jar.
> At this time, there exists DiagnosticUtil class in derby.jar as in 
> http://issues.apache.org/jira/browse/DERBY-496?page=comments#action_12317906
> and the test was passed.
>
> 2:
> Next to 1, Some other modifications removed DiagnosticUtil from derby.jar.
> I don't know what exact modification caused it .
> However, it is very likely to happen, because build.xml of derby compile only classes
that are used from modules defined in 
> java/engine/org/apache/derby/modules.properties.
>
> 3:
> At last Exception happened in  T_Diagnosticable test as shown ....
>
>
> Adding DiagnosticUtil explicitly to derby.jar by modifying extraDBMSclasses.properties
would be right way.
> Glancing javadoc of DiagnosticUtil 
> (http://db.apache.org/derby/javadoc/engine/org/apache/derby/iapi/services/diag/DiagnosticUtil.html),
> I think DiagnosticUtil is likely to be neccessary in derby.jar ...
>
>
> Best regards.
>
>
> /*
>
>         Tomohito Nakayama
>         tomonaka@basil.ocn.ne.jp
>         tomohito@rose.zero.ad.jp
>         tmnk@apache.org
>
>         Naka
>         http://www5.ocn.ne.jp/~tomohito/TopPage.html
>
> */
> ----- Original Message ----- 
> From: "Ole Solberg" <Ole.Solberg@Sun.COM>
> To: "Derby Development" <derby-dev@db.apache.org>
> Sent: Tuesday, August 30, 2005 9:49 PM
> Subject: Re: anyone else seeing T_Diagnosticable test failure ?
>
>
>> TomohitoNakayama wrote:
>>> Hello.
>>>
>>> Patch for DERBY-496 was commited as 234472.
>>> http://issues.apache.org/jira/browse/DERBY-496#action_12319578
>>>
>>> 234472 is both between 234454 and 234486 ,
>>> and  between  234099and 235761 .....
>>> It is very doughtful that this phenomena is caused by the patch for DERBY-496
...
>>>
>>> Can you show me the value of CLASSPATH where the problem happens now ?
>>> This phenomena seems to happen depending on the value of CLASSPATH .
>>
>> ------------------ Java Information ------------------
>> Java Version:    1.5.0_03
>> Java Vendor:     Sun Microsystems Inc.
>> Java home:       /usr/local/java/jdk1.5.0_03/jre
>> Java classpath: 
>> /home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derby.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyclient.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbytools.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbynet.jar:/usr/local/share/java/db2jcc/lib/db2jcc.jar:/usr/local/share/java/db2jcc/lib/db2jcc_license_c.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyTesting.jar:/home/os136789/Apache/TinderBox_Derby/trunk/tools/java/jakarta-oro-2.0.8.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyLocale_de_DE.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyLocale_es.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyLocale_fr.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyLocale_it.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyLocale_ja_JP.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyLocale_ko_KR.jar:/h
 o
> me
>> /os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyLocale_pt_BR.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyLocale_zh_CN.jar:/home/os136789/Apache/TinderBox_Derby/trunk/jars/insane/derbyLocale_zh_TW.jar
>>
>>
>>>
>>> I will try at my site using that value.
>>>
>>> Best regards.
>>>
>>> /*
>>>
>>>         Tomohito Nakayama
>>>         tomonaka@basil.ocn.ne.jp
>>>         tomohito@rose.zero.ad.jp
>>>         tmnk@apache.org
>>>
>>>         Naka
>>>         http://www5.ocn.ne.jp/~tomohito/TopPage.html
>>>
>>> */
>>> ----- Original Message ----- From: "Ole Solberg" <Ole.Solberg@Sun.COM>
>>> To: "Derby Development" <derby-dev@db.apache.org>
>>> Sent: Tuesday, August 30, 2005 8:27 PM
>>> Subject: Re: anyone else seeing T_Diagnosticable test failure ?
>>>
>>>
>>>> Looking at our test results at
>>>> http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/Limited/index.html
>>>> I see that derbyall (and unit) has failed with this diff since an update
to 234486 on 2005-08-22 15:26:10 CEST.
>>>> (Similar for
>>>> http://www.multinet.no/~solberg/public/Apache/Derby/Limited/index.html
>>>> since an update to 235761 on 2005-08-22 19:46:01 CEST)
>> .
>> .
>>>>
>>>>
>>>> -- 
>>>> No virus found in this incoming message.
>>>> Checked by AVG Anti-Virus.
>>>> Version: 7.0.344 / Virus Database: 267.10.17/84 - Release Date: 2005/08/29
>>>>
>>>>
>>>
>>>
>>
>>
>> -- 
>> Ole Solberg, Database Technology Group,
>> Sun Microsystems, Trondheim, Norway
>>
>>
>>
>> -- 
>> No virus found in this incoming message.
>> Checked by AVG Anti-Virus.
>> Version: 7.0.344 / Virus Database: 267.10.17/84 - Release Date: 2005/08/29
>>
>
>
>
> -- 
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.344 / Virus Database: 267.10.17/84 - Release Date: 2005/08/29
>
>
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.344 / Virus Database: 267.10.17/84 - Release Date: 2005/08/29
> 



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.17/84 - Release Date: 2005/08/29


Mime
View raw message