You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/10 17:52:00 UTC

[jira] [Commented] (GEODE-3175) backward-compatibility tests fail with bad classpath

    [ https://issues.apache.org/jira/browse/GEODE-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080735#comment-16080735 ] 

ASF subversion and git services commented on GEODE-3175:
--------------------------------------------------------

Commit 5c434bc3adb5e329a8bfc809395171d4e1aff524 in geode's branch refs/heads/develop from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=5c434bc ]

GEODE-3175 backward-compatibility tests fail with bad classpath

Added a printout of the versions loaded by VersionManager when it
initializes.  This will help us figure out why the test runs are failing.


> backward-compatibility tests fail with bad classpath
> ----------------------------------------------------
>
>                 Key: GEODE-3175
>                 URL: https://issues.apache.org/jira/browse/GEODE-3175
>             Project: Geode
>          Issue Type: Bug
>          Components: tests
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>
> Some test runs are failing to start up a JVM running an old version of Geode.  RollingUpgradeDUnitTest was trying to boot a VM running 110 and the classpath logged by ProcessManager was for 100 & the VM didn't launch correctly.
> {noformat}
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest > testRollServersOnPersistentRegion_dataserializable[2] FAILED
>     java.lang.RuntimeException: VMs did not start up within 120 seconds
>         at org.apache.geode.test.dunit.standalone.DUnitLauncher$Master.bounce(DUnitLauncher.java:440)
>         at org.apache.geode.test.dunit.standalone.StandAloneDUnitEnv.bounce(StandAloneDUnitEnv.java:64)
>         at org.apache.geode.test.dunit.VM.bounce(VM.java:407)
>         at org.apache.geode.test.dunit.standalone.DUnitLauncher$DUnitHost.getVM(DUnitLauncher.java:495)
>         at org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.doTestRollAll(RollingUpgradeDUnitTest.java:144)
>         at org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest.testRollServersOnPersistentRegion_dataserializable(RollingUpgradeDUnitTest.java:134)
>     org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host a775258ffe87 with 4 VMs
>         Caused by:
>         java.lang.IllegalStateException: VM not available: VM 0 running on Host a775258ffe87 with 4 VMs
> org.apache.geode.internal.cache.rollingupgrade.RollingUpgradeDUnitTest > testRollServersOnReplicatedRegion_dataserializable[2] FAILED
>     org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host a775258ffe87 with 4 VMs
>         Caused by:
>         java.lang.IllegalStateException: VM not available: VM 0 running on Host a775258ffe87 with 4 VMs
>     org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.NamedRunnable.run in VM 0 running on Host a775258ffe87 with 4 VMs
>         Caused by:
>         java.lang.IllegalStateException: VM not available: VM 0 running on Host a775258ffe87 with 4 VMs
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)