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

ASF GitHub Bot commented on GEODE-3987:
---------------------------------------

jujoramos commented on a change in pull request #1086: GEODE-3987: enforce 
GatewayReceiver uniqueness per member.
URL: https://github.com/apache/geode/pull/1086#discussion_r153346493
 
 

 ##########
 File path: 
geode-core/src/main/resources/org/apache/geode/cache/doc-files/cache8_0.dtd
 ##########
 @@ -144,7 +144,7 @@ contains, if any.
     dynamic-region-factory?,
     gateway-hub*,
     gateway-sender*,
-    gateway-receiver*,
+    gateway-receiver?,
 
 Review comment:
   Hello @boglesby,
   
   As you said, I don't think anybody is actually trying to configure more than 
one `gateway-receiver` per node, the member will just throw an exception and 
shutdown when trying to register the `MBean`. That's why I added the validation 
int he DTD/XSD as well, primarily to fail fast and allow earlier detection of 
the issue for people using XML modeling tools and/or editors.
   Just for the record, I was also concerned about "breaking the backward 
compatibility" by modifying these files, so I had a discussion with @jhuynh1 / 
@nabarunnag and they agreed with the change. Bottom line, even if we don't 
change the DTD/XSD the member will fail when configuring more than one 
`gateway-receiver` so we're not actually breaking the backward compatibility, 
but just making sure the product is configured as it should.
   Just my two cents, let me know what you think.
   Cheers.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Enforce the uniqueness of a single gateway-receiver per member
> --------------------------------------------------------------
>
>                 Key: GEODE-3987
>                 URL: https://issues.apache.org/jira/browse/GEODE-3987
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Juan José Ramos Cassella
>            Assignee: Juan José Ramos Cassella
>
> Within the documentation, both in [Configure Gateway 
> Receivers|http://geode.apache.org/docs/guide/13/topologies_and_comm/multi_site_configuration/setting_up_a_multisite_system.html#setting_up_a_multisite_system__section_E3A44F85359046C7ADD12861D261637B]
>  and [gfsh create 
> gateway-receiver|http://geode.apache.org/docs/guide/13/tools_modules/gfsh/command-pages/create.html#topic_a4x_pb1_dk],
>  we state that only one {{gateway-receiver}} is allowed per member. However, 
> there is no enforcement of this rule within the code nor within the schema 
> for the {{cache.xml}} file, so the user might end up having more than one 
> {{gateway-receiver}} per host.
> It's unknown which {{gateway-receiver}} is going to be used after a restart, 
> making it hard to configure firewall rules between clusters, if any. The 
> following exception is also printed in the logs whenever we try to register 
> (only the first one is succesfull) the MBean for the {{gateway-receiver}}:
> {noformat}
> [warning 2017/11/16 15:27:46.156 PST host1-server1 <Function Execution 
> Processor1> tid=0x44] javax.management.InstanceAlreadyExistsException: 
> GemFire:service=GatewayReceiver,type=Member,member=host1-server1
> org.apache.geode.management.ManagementException: 
> javax.management.InstanceAlreadyExistsException: 
> GemFire:service=GatewayReceiver,type=Member,member=host1-server1
>       at 
> org.apache.geode.management.internal.MBeanJMXAdapter.registerMBean(MBeanJMXAdapter.java:110)
>       at 
> org.apache.geode.management.internal.SystemManagementService.registerInternalMBean(SystemManagementService.java:368)
>       at 
> org.apache.geode.management.internal.beans.ManagementAdapter.createGatewayReceiverMBean(ManagementAdapter.java:471)
>       at 
> org.apache.geode.management.internal.beans.ManagementAdapter.handleGatewayReceiverStart(ManagementAdapter.java:493)
>       at 
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:134)
>       at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2175)
>       at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:562)
>       at 
> org.apache.geode.internal.cache.wan.GatewayReceiverImpl.start(GatewayReceiverImpl.java:194)
>       at 
> org.apache.geode.internal.cache.wan.GatewayReceiverFactoryImpl.create(GatewayReceiverFactoryImpl.java:141)
>       at 
> org.apache.geode.management.internal.cli.functions.GatewayReceiverCreateFunction.createGatewayReceiver(GatewayReceiverCreateFunction.java:164)
>       at 
> org.apache.geode.management.internal.cli.functions.GatewayReceiverCreateFunction.execute(GatewayReceiverCreateFunction.java:63)
>       at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
>       at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:374)
>       at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:440)
>       at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>       at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:668)
>       at 
> org.apache.geode.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1114)
>       at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.management.InstanceAlreadyExistsException: 
> GemFire:service=GatewayReceiver,type=Member,member=host1-server1
>       at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
>       at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
>       at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
>       at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
>       at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
>       at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
>       at 
> org.apache.geode.management.internal.MBeanJMXAdapter.registerMBean(MBeanJMXAdapter.java:105)
>       ... 18 more
> {noformat}
> The fix implies:
> . Change the {{maxOccurs}} attribute from {{unbounded}} to {{1}} in the 
> {{cache-1.0.xsd}} file.
> . Add the validation to the {{GatewayReceiverFactoryImpl.create()}} method, 
> as this is the single entry point for {{GatewayReceiver}} instance creations.



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

Reply via email to