You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jinmei Liao (Jira)" <ji...@apache.org> on 2021/02/02 21:42:00 UTC
[jira] [Resolved] (GEODE-8893) GFSH deploy command fails with
java.rmi.NoSuchObjectException: no such object in table
[ https://issues.apache.org/jira/browse/GEODE-8893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jinmei Liao resolved GEODE-8893.
--------------------------------
Fix Version/s: 1.14.0
Resolution: Fixed
> GFSH deploy command fails with java.rmi.NoSuchObjectException: no such object in table
> --------------------------------------------------------------------------------------
>
> Key: GEODE-8893
> URL: https://issues.apache.org/jira/browse/GEODE-8893
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Affects Versions: 1.12.1, 1.13.2, 1.14.0
> Reporter: Donal Evans
> Priority: Major
> Labels: blocks-1.14.0, pull-request-available
> Fix For: 1.14.0
>
>
> MicrometerBinderTest fails with the below stack trace:
> {noformat}
> org.apache.geode.metrics.MicrometerBinderTest > jvmMemoryMetricsBinderExists FAILED
> org.junit.ComparisonFailure: [Exit value from process started by [9ead38795d00b100: gfsh -e connect --jmx-manager=localhost[25533] -e deploy --jar=/tmp/junit909471762194553718/function.jar]] expected:<[0]> but was:<[1]>
> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:137)
> at org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:128)
> at org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:114)
> at org.apache.geode.metrics.MicrometerBinderTest.startServer(MicrometerBinderTest.java:95)
> {noformat}
> Test output shows that the connect command succeeds, but the deploy command fails:
> {noformat}
> [info 2021/01/29 10:05:28.790 GMT <pool-10-thread-1> tid=0x2e] (1) Executing - connect --jmx-manager=localhost[25533]
>
> [info 2021/01/29 10:05:28.791 GMT <pool-10-thread-1> tid=0x2e]
>
> [info 2021/01/29 10:05:28.807 GMT <pool-10-thread-1> tid=0x2e] Connecting to Manager at [host=localhost, port=25533] ..
>
> [info 2021/01/29 10:05:29.046 GMT <pool-10-thread-1> tid=0x2e] Successfully connected to: [host=localhost, port=25533]
>
> [info 2021/01/29 10:05:29.046 GMT <pool-10-thread-1> tid=0x2e]
>
> [info 2021/01/29 10:05:29.046 GMT <pool-10-thread-1> tid=0x2e] You are connected to a cluster of version: 1.12.1-build.0
>
> [info 2021/01/29 10:05:29.047 GMT <pool-10-thread-1> tid=0x2e]
>
> [info 2021/01/29 10:05:29.048 GMT <pool-10-thread-1> tid=0x2e]
>
> [info 2021/01/29 10:05:29.048 GMT <pool-10-thread-1> tid=0x2e] (2) Executing - deploy --jar=/tmp/junit909471762194553718/function.jar
>
> [info 2021/01/29 10:05:29.048 GMT <pool-10-thread-1> tid=0x2e]
>
> [error 2021/01/29 10:05:39.404 GMT <pool-11-thread-1> tid=0x2f] Member | Deployed JAR | Deployed JAR Location
>
> [error 2021/01/29 10:05:39.404 GMT <pool-11-thread-1> tid=0x2f] ------ | ------------ | --------------------------------------------------------------
>
> [error 2021/01/29 10:05:39.405 GMT <pool-11-thread-1> tid=0x2f] server | | ERROR: java.rmi.NoSuchObjectException: no such object in table
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)