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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/12/17 19:35:44 UTC

[jira] Created: (DERBY-3993) With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K

With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K
--------------------------------------------------------------------------------------------------------------

                 Key: DERBY-3993
                 URL: https://issues.apache.org/jira/browse/DERBY-3993
             Project: Derby
          Issue Type: Bug
    Affects Versions: 10.5.0.0
         Environment: java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
J9VM - 20081105_025433_lHdSMr
JIT  - r9_20081031_1330
GC   - 20081027_AB)
JCL  - 20081106_01

            Reporter: Kathey Marsden
            Priority: Minor


On Win2K T_RawStoreFactory fails consistently with 
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
J9VM - 20081105_025433_lHdSMr
JIT  - r9_20081031_1330
GC   - 20081027_AB)
JCL  - 20081106_01

 *** Start: T_RawStoreFactory jdk1.6.0 2008-12-17 09:37:49 ***
2 del
< -- Unit Test T_RawStoreFactory finished
2 add
> There should be 0 observers, but we still have 1 observers.
> Shutting down due to unit test failure.
Test Failed.

I have seen the same failure on Linux and Windows XP intermittently with IBM 1.6.




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (DERBY-3993) With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658800#action_12658800 ] 

Knut Anders Hatlen commented on DERBY-3993:
-------------------------------------------

Committed assert.diff with revision 728907.

> With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3993
>                 URL: https://issues.apache.org/jira/browse/DERBY-3993
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.5.0.0
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: assert.diff
>
>
> On Win2K T_RawStoreFactory fails consistently with 
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>  *** Start: T_RawStoreFactory jdk1.6.0 2008-12-17 09:37:49 ***
> 2 del
> < -- Unit Test T_RawStoreFactory finished
> 2 add
> > There should be 0 observers, but we still have 1 observers.
> > Shutting down due to unit test failure.
> Test Failed.
> I have seen the same failure on Linux and Windows XP intermittently with IBM 1.6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (DERBY-3993) With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K

Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661739#action_12661739 ] 

Myrna van Lunteren commented on DERBY-3993:
-------------------------------------------

It appears with sane builds (jars or classes).

> With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3993
>                 URL: https://issues.apache.org/jira/browse/DERBY-3993
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.5.0.0
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: assert.diff
>
>
> On Win2K T_RawStoreFactory fails consistently with 
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>  *** Start: T_RawStoreFactory jdk1.6.0 2008-12-17 09:37:49 ***
> 2 del
> < -- Unit Test T_RawStoreFactory finished
> 2 add
> > There should be 0 observers, but we still have 1 observers.
> > Shutting down due to unit test failure.
> Test Failed.
> I have seen the same failure on Linux and Windows XP intermittently with IBM 1.6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (DERBY-3993) With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K

Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658668#action_12658668 ] 

Myrna van Lunteren commented on DERBY-3993:
-------------------------------------------

That sounds good to me. It's pretty rare, but we've now seen it with ibm16 and ibm's weme6.1 (see DERBY-654). More info would be better.

> With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3993
>                 URL: https://issues.apache.org/jira/browse/DERBY-3993
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.5.0.0
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: assert.diff
>
>
> On Win2K T_RawStoreFactory fails consistently with 
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>  *** Start: T_RawStoreFactory jdk1.6.0 2008-12-17 09:37:49 ***
> 2 del
> < -- Unit Test T_RawStoreFactory finished
> 2 add
> > There should be 0 observers, but we still have 1 observers.
> > Shutting down due to unit test failure.
> Test Failed.
> I have seen the same failure on Linux and Windows XP intermittently with IBM 1.6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (DERBY-3993) With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-3993:
----------------------------------

    Component/s: Regression Test Failure

> With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3993
>                 URL: https://issues.apache.org/jira/browse/DERBY-3993
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.5.0.0
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: assert.diff
>
>
> On Win2K T_RawStoreFactory fails consistently with 
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>  *** Start: T_RawStoreFactory jdk1.6.0 2008-12-17 09:37:49 ***
> 2 del
> < -- Unit Test T_RawStoreFactory finished
> 2 add
> > There should be 0 observers, but we still have 1 observers.
> > Shutting down due to unit test failure.
> Test Failed.
> I have seen the same failure on Linux and Windows XP intermittently with IBM 1.6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (DERBY-3993) With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658644#action_12658644 ] 

Knut Anders Hatlen commented on DERBY-3993:
-------------------------------------------

The message is printed by debug code in Xact.doComplete():

		if (SanityManager.DEBUG) 
        {
			if (countObservers() != 0)
            {
				System.out.println(
                    "There should be 0 observers, but we still have "
					+ countObservers() + " observers.");
				notifyObservers(null);
            }
		}

> With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3993
>                 URL: https://issues.apache.org/jira/browse/DERBY-3993
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.5.0.0
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>            Reporter: Kathey Marsden
>            Priority: Minor
>
> On Win2K T_RawStoreFactory fails consistently with 
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>  *** Start: T_RawStoreFactory jdk1.6.0 2008-12-17 09:37:49 ***
> 2 del
> < -- Unit Test T_RawStoreFactory finished
> 2 add
> > There should be 0 observers, but we still have 1 observers.
> > Shutting down due to unit test failure.
> Test Failed.
> I have seen the same failure on Linux and Windows XP intermittently with IBM 1.6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (DERBY-3993) With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen updated DERBY-3993:
--------------------------------------

    Attachment: assert.diff

Perhaps we should apply this patch to get the stack trace when this happens? It replaces the call to System.out.println() with a call to SanityManager.THROWASSERT().

> With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3993
>                 URL: https://issues.apache.org/jira/browse/DERBY-3993
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.5.0.0
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: assert.diff
>
>
> On Win2K T_RawStoreFactory fails consistently with 
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>  *** Start: T_RawStoreFactory jdk1.6.0 2008-12-17 09:37:49 ***
> 2 del
> < -- Unit Test T_RawStoreFactory finished
> 2 add
> > There should be 0 observers, but we still have 1 observers.
> > Shutting down due to unit test failure.
> Test Failed.
> I have seen the same failure on Linux and Windows XP intermittently with IBM 1.6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (DERBY-3993) With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K

Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661652#action_12661652 ] 

Myrna van Lunteren commented on DERBY-3993:
-------------------------------------------

I should add the stack trace from derby.log:
....
[main]     P706 : update to null true - col 14
[main] Pass - RawStoreFactory P706: multiPortion true segment = -1
[main] Pass - RawStoreFactory P707: segment = -1
[main] FAIL - org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED There should be 0 observers, but we still have 1 observers.
org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED There should be 0 observers, but we still have 1 observers.
	at org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:162)
	at org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:147)
	at org.apache.derby.impl.store.raw.xact.Xact.doComplete(Xact.java:1969)
	at org.apache.derby.impl.store.raw.xact.Xact.preComplete(Xact.java:1925)
	at org.apache.derby.impl.store.raw.xact.Xact.prepareCommit(Xact.java:769)
	at org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:882)
	at org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:679)
	at org.apache.derbyTesting.unitTests.store.T_Util.t_commit(T_Util.java:840)
	at org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.TC001(T_RawStoreFactory.java:7311)
	at org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTempTests(T_RawStoreFactory.java:417)
	at org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTestSet(T_RawStoreFactory.java:248)
	at org.apache.derbyTesting.unitTests.harness.T_MultiIterations.runTests(T_MultiIterations.java:95)
	at org.apache.derbyTesting.unitTests.harness.T_MultiThreadedIterations.runTests(T_MultiThreadedIterations.java:92)
	at org.apache.derbyTesting.unitTests.harness.T_Generic.Execute(T_Generic.java:118)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runATest(BasicUnitTestManager.java:184)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runTests(BasicUnitTestManager.java:246)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:93)
	at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:2019)
	at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:291)
	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1856)
	at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:997)
	at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:429)
	at org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:60)
	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:289)
	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:51)
---------------
Stack traces for all live threads:
Thread name=derby.rawStoreDaemon id=13 priority=5 state=TIMED_WAITING isdaemon=true
	java.lang.Object.wait(Native Method)
	java.lang.Object.wait(Object.java:196)
	org.apache.derby.impl.services.daemon.BasicDaemon.rest(BasicDaemon.java:571)
	org.apache.derby.impl.services.daemon.BasicDaemon.run(BasicDaemon.java:388)
	java.lang.Thread.run(Thread.java:735)

Thread name=Signal Dispatcher id=2 priority=5 state=RUNNABLE isdaemon=true
	com.ibm.misc.SignalDispatcher.waitForSignal(Native Method)
	com.ibm.misc.SignalDispatcher.run(SignalDispatcher.java:54)

Thread name=main id=1 priority=5 state=RUNNABLE isdaemon=false
	java.lang.Thread.getStackTraceImpl(Native Method)
	java.lang.Thread.getStackTrace(Thread.java:1039)
	java.lang.Thread.getAllStackTraces(Thread.java:1067)
	org.apache.derby.shared.common.sanity.ThreadDump.getStackDumpString(ThreadDump.java:34)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	java.lang.reflect.Method.invoke(Method.java:599)
	org.apache.derby.shared.common.sanity.AssertFailure$1.run(AssertFailure.java:165)
	java.security.AccessController.doPrivileged(AccessController.java:251)
	org.apache.derby.shared.common.sanity.AssertFailure.dumpThreads(AssertFailure.java:159)
	org.apache.derby.shared.common.sanity.AssertFailure.<init>(AssertFailure.java:72)
	org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:162)
	org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:147)
	org.apache.derby.impl.store.raw.xact.Xact.doComplete(Xact.java:1969)
	org.apache.derby.impl.store.raw.xact.Xact.preComplete(Xact.java:1925)
	org.apache.derby.impl.store.raw.xact.Xact.prepareCommit(Xact.java:769)
	org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:882)
	org.apache.derby.impl.store.raw.xact.Xact.commit(Xact.java:679)
	org.apache.derbyTesting.unitTests.store.T_Util.t_commit(T_Util.java:840)
	org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.TC001(T_RawStoreFactory.java:7311)
	org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTempTests(T_RawStoreFactory.java:417)
	org.apache.derbyTesting.unitTests.store.T_RawStoreFactory.runTestSet(T_RawStoreFactory.java:248)
	org.apache.derbyTesting.unitTests.harness.T_MultiIterations.runTests(T_MultiIterations.java:95)
	org.apache.derbyTesting.unitTests.harness.T_MultiThreadedIterations.runTests(T_MultiThreadedIterations.java:92)
	org.apache.derbyTesting.unitTests.harness.T_Generic.Execute(T_Generic.java:118)
	org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runATest(BasicUnitTestManager.java:184)
	org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.runTests(BasicUnitTestManager.java:246)
	org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:93)
	org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:2019)
	org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:291)
	org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1856)
	org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:997)
	org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:429)
	org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:60)
	org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:289)
	org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:51)

Thread name=MemoryPoolMXBean notification dispatcher id=10 priority=6 state=RUNNABLE isdaemon=true
	com.ibm.lang.management.MemoryNotificationThread.processNotificationLoop(Native Method)
	com.ibm.lang.management.MemoryNotificationThread.run(MemoryNotificationThread.java:55)

Thread name=Thread-6 id=12 priority=5 state=TIMED_WAITING isdaemon=true
	java.lang.Thread.sleep(Native Method)
	java.lang.Thread.sleep(Thread.java:850)
	org.apache.derbyTesting.unitTests.harness.T_Bomb.run(T_Bomb.java:105)
	java.lang.Thread.run(Thread.java:735)

Thread name=Gc Slave Thread id=5 priority=5 state=RUNNABLE isdaemon=true

Thread name=derby.antiGC id=6 priority=1 state=WAITING isdaemon=true
	java.lang.Object.wait(Native Method)
	java.lang.Object.wait(Object.java:167)
	org.apache.derby.impl.services.monitor.AntiGC.run(BaseMonitor.java:2217)
	java.lang.Thread.run(Thread.java:735)

Thread name=JIT Compilation Thread id=4 priority=10 state=RUNNABLE isdaemon=true

Thread name=Finalizer thread id=7 priority=5 state=RUNNABLE isdaemon=true

Thread name=Thread-2 id=8 priority=5 state=WAITING isdaemon=true
	java.lang.Object.wait(Native Method)
	java.lang.Object.wait(Object.java:167)
	java.util.Timer$TimerImpl.run(Timer.java:210)


---------------

2009-01-05 21:19:50.210 GMT Thread[main,5,main] Test 'org.apache.derbyTesting.unitTests.store.T_RawStoreFactory' failed
2009-01-05 21:19:50.210 GMT Thread[main,5,main] Test Summary - Run 1, Passed 0, Failed 1, Skipped 0.
2009-01-05 21:19:50.210 GMT Thread[main,5,main] Shutting down due to unit test failure, see log for more information.

2009-01-05 21:19:50.492 GMT:
Shutting down instance a816c00e-011e-a8aa-306c-ffffbe84b931
----------------------------------------------------------------
2009-01-05 21:19:50.570 GMT Thread[main,5,main] Cleanup action starting
ERROR XBM01: Startup failed due to an exception. See next exception for details. 
	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:279)
	at org.apache.derby.iapi.services.monitor.Monitor.exceptionStartingModule(Monitor.java:677)
	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1875)
	at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:997)
	at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:429)
	at org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:60)
	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:289)
	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:51)
Caused by: java.lang.NullPointerException
	at org.apache.derby.impl.services.monitor.TopService.getService(TopService.java:130)
	at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(BaseMonitor.java:205)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:103)
	at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:2019)
	at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:291)
	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1856)
	... 5 more
============= begin nested exception, level (1) ===========
java.lang.NullPointerException
	at org.apache.derby.impl.services.monitor.TopService.getService(TopService.java:130)
	at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(BaseMonitor.java:205)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:103)
	at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:2019)
	at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:291)
	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1856)
	at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:997)
	at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:429)
	at org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:60)
	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:289)
	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:51)
============= end nested exception, level (1) ===========
Cleanup action completed
2009-01-05 21:19:50.585 GMT Thread[main,5,main] 2009-01-05 21:19:50.585 GMT Thread[main,5,main] Startup failed due to an exception. See next exception for details. 
ERROR XBM01: Startup failed due to an exception. See next exception for details. 
	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:279)
	at org.apache.derby.iapi.services.monitor.Monitor.exceptionStartingModule(Monitor.java:677)
	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1875)
	at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:997)
	at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:429)
	at org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:60)
	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:289)
	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:51)
Caused by: java.lang.NullPointerException
	at org.apache.derby.impl.services.monitor.TopService.getService(TopService.java:130)
	at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(BaseMonitor.java:205)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:103)
	at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:2019)
	at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:291)
	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1856)
	... 5 more
============= begin nested exception, level (1) ===========
java.lang.NullPointerException
	at org.apache.derby.impl.services.monitor.TopService.getService(TopService.java:130)
	at org.apache.derby.impl.services.monitor.BaseMonitor.shutdown(BaseMonitor.java:205)
	at org.apache.derbyTesting.unitTests.harness.BasicUnitTestManager.boot(BasicUnitTestManager.java:103)
	at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:2019)
	at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:291)
	at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1856)
	at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(BaseMonitor.java:997)
	at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(BaseMonitor.java:429)
	at org.apache.derby.impl.services.monitor.FileMonitor.<init>(FileMonitor.java:60)
	at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Monitor.java:289)
	at org.apache.derbyTesting.unitTests.harness.UnitTestMain.main(UnitTestMain.java:51)
============= end nested exception, level (1) ===========



> With IBM 1.6 T_RawStoreFactory fails with There should be 0 observers, but we still have 1 observers on Win 2K
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3993
>                 URL: https://issues.apache.org/jira/browse/DERBY-3993
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.5.0.0
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>            Reporter: Kathey Marsden
>            Priority: Minor
>         Attachments: assert.diff
>
>
> On Win2K T_RawStoreFactory fails consistently with 
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433 (JIT enabled, AOT enabled)
> J9VM - 20081105_025433_lHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
>  *** Start: T_RawStoreFactory jdk1.6.0 2008-12-17 09:37:49 ***
> 2 del
> < -- Unit Test T_RawStoreFactory finished
> 2 add
> > There should be 0 observers, but we still have 1 observers.
> > Shutting down due to unit test failure.
> Test Failed.
> I have seen the same failure on Linux and Windows XP intermittently with IBM 1.6.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.