[ https://issues.apache.org/jira/browse/GEODE-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357721#comment-16357721 ]
ASF subversion and git services commented on GEODE-3540: -------------------------------------------------------- Commit bbea69a1e0c153e28f5958a58387b80f70fcdc89 in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bbea69a ] GEODE-3540: unable to gfsh destroy gateway-sender (#1414) GW sender bean is not unregistered during destroy command which is why it appears when you list gateways after destroy. This fix is to unregistered the MX bean from SystemManagementService > unable to gfsh destroy gateway-sender > ------------------------------------- > > Key: GEODE-3540 > URL: https://issues.apache.org/jira/browse/GEODE-3540 > Project: Geode > Issue Type: Bug > Components: gfsh, wan > Reporter: Raphaël Enrici > Assignee: Sai Boorlagadda > Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Dear all, > while playing with wan setup we found that we are unable to destroy a > declared sender configuration. > You can reproduce this in a simple one node setup with apache geode 1.2.0: > * start a locator > * start a server > * create a gateway-sender > * destroy the gateway-sender => messages are ok > * list gateways, the gateway-sender is still here although we just destroyed > it > * if you try to destroy it again, you get "ERROR: GateWaySender with Id > sender not found" > * if you list gateways again, the gateway is still here, you can even start > and stop it although it is not functional anymore. > * restarting the whole cluster does not change anything. > Maybe we missed something concerning this, if the answer to this is a RTFM > one, sorry for the noise. > Keep up the good work. > Best, > Raphaël > Here are shrinked outputs concerning this problem: > {quote} > gfsh> start locator --name=happylocator > gfsh> start server --name=happyserver1 > gfsh>create gateway-sender --id=sender --remote-distributed-system-id=2 > Member | Status > ------------ | ------------------------------------------------ > happyserver1 | GatewaySender "sender" created on "happyserver1" > gfsh>list gateways > Gateways > GatewaySender > GatewaySender Id | Member | Remote Cluster > Id | Type | Status | Queued Events | Receiver Location > ---------------- | --------------------------------------- | > ----------------- | ------ | ------- | ------------- | ----------------- > sender | 192.168.0.6(happyserver1:1689)<v1>:1025 | 2 > | Serial | Running | 0 | null > gfsh>destroy gateway-sender --id sender > Member | Status > ------------ | -------------------------------------------------- > happyserver1 | GatewaySender "sender" destroyed on "happyserver1" > gfsh>list gateways > Gateways > GatewaySender > GatewaySender Id | Member | Remote Cluster > Id | Type | Status | Queued Events | Receiver Location > ---------------- | --------------------------------------- | > ----------------- | ------ | ----------- | ------------- | ----------------- > sender | 192.168.0.6(happyserver1:1689)<v1>:1025 | 2 > | Serial | Not Running | 0 | null > gfsh>destroy gateway-sender --id sender > Member | Status > ------------ | ---------------------------------------------- > happyserver1 | ERROR: GateWaySender with Id sender not found > gfsh>start gateway-sender --id sender > Member | Result | Message > --------------------------------------- | ------ | > ----------------------------------------------------------------- > 192.168.0.6(happyserver1:1689)<v1>:1025 | OK | GatewaySender sender is > started on member 192.168.0.6(happyserv.. > {quote} -- This message was sent by Atlassian JIRA (v7.6.3#76005)