geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Barry Oglesby (JIRA)" <>
Subject [jira] [Created] (GEODE-387) GatewayReceivers configured using cache xml should be started after the regions are created
Date Wed, 07 Oct 2015 17:34:26 GMT
Barry Oglesby created GEODE-387:

             Summary: GatewayReceivers configured using cache xml should be started after
the regions are created
                 Key: GEODE-387
             Project: Geode
          Issue Type: Bug
          Components: core
            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:
[info 2015/04/29 16:30:38.644 PDT host1 <main> tid=0x1] The GatewayReceiver started
on port : 1,575
Then, events start being received and dropped:
[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:<v6>:3298
	at com.gemstone.gemfire.internal.cache.tier.sockets.command.GatewayReceiverCommand.cmdExecute(
	at com.gemstone.gemfire.internal.cache.tier.sockets.BaseCommand.execute(
	at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doNormalMsg(
	at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doOneMessage(
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$
	at com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$1$
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(
	... 8 more
Finally, the region is created:
[info 2015/04/29 16:30:39.203 PDT host1 <main> tid=0x1] Partitioned Region /trade is
born with prId=21 ident:#trade
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

View raw message