geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-387) GatewayReceivers configured using cache xml should be started after the regions are created
Date Fri, 05 Feb 2016 23:18:39 GMT

     [ https://issues.apache.org/jira/browse/GEODE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Darrel Schneider updated GEODE-387:
-----------------------------------
    Component/s:     (was: core)
                 wan

> GatewayReceivers configured using cache xml should be started after the regions are created
> -------------------------------------------------------------------------------------------
>
>                 Key: GEODE-387
>                 URL: https://issues.apache.org/jira/browse/GEODE-387
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Barry Oglesby
>            Assignee: Barry Oglesby
>
> Currently, {{GatewayReceivers}} configured using cache xml are started before the {{Regions}}
in that xml. This can cause data loss since a remote {{GatewaySender}} could connect to that
{{GatewayReceiver}} and send batches before the {{Regions}} are created.
> First, the {{GatewayReceiver}} is started:
> {noformat}
> [info 2015/04/29 16:30:38.644 PDT host1 <main> tid=0x1] The GatewayReceiver started
on port : 1,575
> {noformat}
> Then, events start being received and dropped:
> {noformat}
> [warning 2015/04/29 16:30:38.978 PDT host1 <ServerConnection on port 1575 Thread 1>
tid=0x7b] Server connection from [identity(xx.x.xx.xx(host1:6372)<v2>:27373,connection=1;
port=36493]: Wrote batch exception: 
> com.gemstone.gemfire.internal.cache.wan.BatchException70: Exception occurred while processing
a batch on the receiver running on DistributedSystem with Id: 2, DistributedMember on which
the receiver is running: xx.x.xx.xxx(host1:25784)<v6>:3298
> 	at com.gemstone.gemfire.internal.cache.tier.sockets.command.GatewayReceiverCommand.cmdExecute(GatewayReceiverCommand.java:648)
> 	at com.gemstone.gemfire.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:182)
> 	at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:789)
> 	at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:920)
> 	at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1165)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> 	at com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:577)
> 	at java.lang.Thread.run(Thread.java:724)
> Caused by: com.gemstone.gemfire.cache.RegionDestroyedException: Region /trade was not
found during batch create request 0
> 	at com.gemstone.gemfire.internal.cache.tier.sockets.command.GatewayReceiverCommand.cmdExecute(GatewayReceiverCommand.java:288)
> 	... 8 more
> {noformat}
> Finally, the region is created:
> {noformat}
> [info 2015/04/29 16:30:39.203 PDT host1 <main> tid=0x1] Partitioned Region /trade
is born with prId=21 ident:#trade
> {noformat}
> In {{CacheCreation.create}}, the {{GatewayReceiver}} is created and started before the
regions are initialized. For comparison, the {{GatewayHub}} (which is the predecessor to the
{{GatewayReceiver}}) is started after the regions are created. This is the way it should be.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message