db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3561) testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError: expected:<2> but was:<5>
Date Thu, 27 Mar 2008 15:21:25 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582686#action_12582686
] 

John H. Embretsen commented on DERBY-3561:
------------------------------------------

I am only able to reproduce this failure when running suites.All, or a subset of it, before
running the ManagementMBeanTest. Running the management suite by itself does not result in
a failure. 

It seems to me that when connecting directly to the platform MBean server in the same JVM,
there is a set of MBeans from a different Derby system available, as indicated by the extra
debugging output I added:

initial: org.apache.derby:type=Management
initial: org.apache.derby:system=c013800d-0118-f0c9-77c9-00004d1fe320,type=Management
initial: org.apache.derby:jar=derby.jar,system=c013800d-0118-f0c9-9143-00004d1fe320,type=Version
initial: org.apache.derby:system=c013800d-0118-f0c9-77c9-00004d1fe320,type=JDBC
initial: org.apache.derby:system=c013800d-0118-f0c9-9143-00004d1fe320,type=JDBC
initial: org.apache.derby:jar=derbynet.jar,system=c013800d-0118-f0c9-9143-00004d1fe320,type=Version
initial: org.apache.derby:jar=derby.jar,system=c013800d-0118-f0c9-77c9-00004d1fe320,type=Version
initial: org.apache.derby:system=c013800d-0118-f0c9-9143-00004d1fe320,type=NetworkServer
initial: org.apache.derby:system=c013800d-0118-f0c9-9143-00004d1fe320,type=Management
DerbyMBeanCount after no-op startMgmt: 9
DerbyMBeanCount after stop: 5
after stop: org.apache.derby:type=Management
after stop: org.apache.derby:jar=derby.jar,system=c013800d-0118-f0c9-77c9-00004d1fe320,type=Version
after stop: org.apache.derby:system=c013800d-0118-f0c9-77c9-00004d1fe320,type=Management
after stop: org.apache.derby:system=c013800d-0118-f0c9-77c9-00004d1fe320,type=JDBC
after stop: org.apache.derby:system=c013800d-0118-f0c9-9143-00004d1fe320,type=Management
testStartStopManagementFromApplication used 24 ms F

I have reduced the number of tests needed to reproduce the failure to a suite consisting of:

suite.addTest(org.apache.derbyTesting.functionTests.tests.derbynet.NSinSameJVMTest.suite());
suite.addTest(org.apache.derbyTesting.functionTests.tests.derbynet.ServerPropertiesTest.suite());
suite.addTest(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest.suite());

in that specific order. Looking closer at those tests might reveal something.


> testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError:
expected:<2> but was:<5>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3561
>                 URL: https://issues.apache.org/jira/browse/DERBY-3561
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.5.0.0
>            Reporter: Mike Matrigali
>
> The following test has been failing consistently in the tinderbox runs since about build
636714, unfortunately the run right before this build  failed so
> it may be from that one. 
> first tinderbox failure I could find:
> http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/636714-org.apache.derbyTesting.functionTests.suites.All_diff.txt
> most recent as of this report:
> http://dbtg.thresher.com/derby/test/tinderbox_trunk16/jvm1.6/testing/testlog/SunOS-5.10_i86pc-i386/639156-org.apache.derbyTesting.functionTests.suites.All_diff.txt
> There was 1 failure:
> 1) testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError:
expected:<2> but was:<5>
> 	at org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest.startStopManagement(ManagementMBeanTest.java:86)
> 	at org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest.testStartStopManagementFromApplication(ManagementMBeanTest.java:56)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:101)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)

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


Mime
View raw message