[jira] [Updated] (GEODE-4827) Cq should not be added to the cq map if cq's base region is null

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-4827:
--
Labels: pull-request-available  (was: )

> Cq should not be added to the cq map if cq's base region is null
> 
>
> Key: GEODE-4827
> URL: https://issues.apache.org/jira/browse/GEODE-4827
> Project: Geode
>  Issue Type: Bug
>  Components: cq
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>
> Currently while registering a cq if the cache is closing down , it throws an 
> exception. but we ignore the exception and continue adding the cq to the map.
> While processing the closing of cq it will ask for the cq's base region which 
> will be null. Thus ends with NPE because we end up calling methods on null 
> region.
> Solution:
> put the addition of the cq to the cqMap inside a if check for base region 
> {code:java}
>  void processRegisterCq(String serverCqName, ServerCQ ServerCQ, boolean 
> addToCqMap,
>   GemFireCacheImpl cache) {
> ServerCQ cq = (ServerCQ) ServerCQ;
> try {
>   CqService cqService = cache.getCqService();
>   cqService.start();
>   cq.setCqService(cqService);
>   CqStateImpl cqState = (CqStateImpl) cq.getState();
>   cq.setName(generateCqName(serverCqName));
>   cq.registerCq(null, null, cqState.getState());
> } catch (Exception ex) {
>   // Change it to Info level.
>   logger.info("Error while initializing the CQs with FilterProfile for CQ 
> {}, Error : {}",
>   serverCqName, ex.getMessage(), ex);
> }
> if (logger.isDebugEnabled()) {
>   logger.debug("Adding CQ to remote members FilterProfile using name: 
> {}", serverCqName);
> }
> // The region's FilterProfile is accessed through CQ reference as the
> // region is not set on the FilterProfile created for the peer nodes.
> if (cq.getCqBaseRegion() != null) {
>   if (addToCqMap) {
> this.cqs.put(serverCqName, cq);
>   }
>   FilterProfile pf = cq.getCqBaseRegion().getFilterProfile();
>   if (pf != null) {
> pf.incCqCount();
>   }
> }
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4427) Cleanup function pointer types in Serializable.hpp

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4427:


Commit 7b32fed6e75c67b145718d9cf76fc6c7f45d1918 in geode-native's branch 
refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=7b32fed ]

GEODE-4427: Moving CliCallbackMethod to DistributedSystemImpl (#233)



Signed-off-by: Blake Bender 


> Cleanup function pointer types in Serializable.hpp
> --
>
> Key: GEODE-4427
> URL: https://issues.apache.org/jira/browse/GEODE-4427
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> This callback should not be in Serializable.hpp or it might not be needed.  
> At the very least, this should be removed from the public API.
> {code:java}
> typedef void (*CliCallbackMethod)(Cache );{code}
> Modernize the below header to used std::function.
> This should implement {{std::function}}.
> {code:java}
> typedef PdxSerializable* (*TypeFactoryMethodPdx)();{code}
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4381) TcrMessage::readCacheableString incorrectly deserializes Java Modified UTF-8 strings.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4381:


Commit e1c75ded5c07e3039bff5b41501d4d30aa6c4076 in geode-native's branch 
refs/heads/develop from [~mcmellawatt]
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=e1c75de ]

GEODE-4381: Refactoring readCacheableString() decoding (#234)



Signed-off-by: Blake Bender 


> TcrMessage::readCacheableString incorrectly deserializes Java Modified UTF-8 
> strings.
> -
>
> Key: GEODE-4381
> URL: https://issues.apache.org/jira/browse/GEODE-4381
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> This method should be replaced with one that just decodes the bytes as Java 
> Modified UTF-8 up to the given length into a UTF-8 std::string and return a 
> CacheableString from that.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-4827) Cq should not be added to the cq map if cq's base region is null

[nabarun (JIRA)]

nabarun created GEODE-4827:
--

 Summary: Cq should not be added to the cq map if cq's base region 
is null
 Key: GEODE-4827
 URL: https://issues.apache.org/jira/browse/GEODE-4827
 Project: Geode
  Issue Type: Bug
  Components: cq
Reporter: nabarun


Currently while registering a cq if the cache is closing down , it throws an 
exception. but we ignore the exception and continue adding the cq to the map.
While processing the closing of cq it will ask for the cq's base region which 
will be null. Thus ends with NPE because we end up calling methods on null 
region.

Solution:
put the addition of the cq to the cqMap inside a if check for base region 


{code:java}
 void processRegisterCq(String serverCqName, ServerCQ ServerCQ, boolean 
addToCqMap,
  GemFireCacheImpl cache) {
ServerCQ cq = (ServerCQ) ServerCQ;
try {
  CqService cqService = cache.getCqService();
  cqService.start();
  cq.setCqService(cqService);
  CqStateImpl cqState = (CqStateImpl) cq.getState();
  cq.setName(generateCqName(serverCqName));
  cq.registerCq(null, null, cqState.getState());
} catch (Exception ex) {
  // Change it to Info level.
  logger.info("Error while initializing the CQs with FilterProfile for CQ 
{}, Error : {}",
  serverCqName, ex.getMessage(), ex);

}
if (logger.isDebugEnabled()) {
  logger.debug("Adding CQ to remote members FilterProfile using name: {}", 
serverCqName);
}

// The region's FilterProfile is accessed through CQ reference as the
// region is not set on the FilterProfile created for the peer nodes.
if (cq.getCqBaseRegion() != null) {
  if (addToCqMap) {
this.cqs.put(serverCqName, cq);
  }

  FilterProfile pf = cq.getCqBaseRegion().getFilterProfile();
  if (pf != null) {
pf.incCqCount();
  }
}
  }
{code}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4807) Pulse UI tests using locator/cluster rule.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4807:


Commit 94586e1945d4e48313e60a39b91077450bf8525b in geode's branch 
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=94586e1 ]

GEODE-4807: Pulse UI tests using locator/cluster rule. (#1584)

These UI tests uses locator and cluster rules to setup VMs with integrated 
security.

   * Added selenium based pulse UI tests to setup using locator and cluster 
rules
   * Added pulse as a test dependency to geode-assembly
   * Added selenium and chrome driver dependency to geode-assembly
   * Added uiTest task to geode-assembly gradle

> Pulse UI tests using locator/cluster rule.
> --
>
> Key: GEODE-4807
> URL: https://issues.apache.org/jira/browse/GEODE-4807
> Project: Geode
>  Issue Type: Test
>  Components: pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig

[Vlad Ermolaev (JIRA)]

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

Vlad Ermolaev commented on GEODE-4822:
--

I have just tested it with ReflectionBasedAutoSerializer - everything works 
fine. Another option is to not configure any serializer and make region 
entities PdxSerializable.

> The second server instance startup error: Could not create an instance of 
> PartitionRegionConfig
> ---
>
> Key: GEODE-4822
> URL: https://issues.apache.org/jira/browse/GEODE-4822
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Vlad Ermolaev
>Priority: Major
>
> I have a simple configuration containing a partitioned persistent region and 
> an async queue:
> {code:xml} 
>  dispatcher-threads="1" enable-batch-conflation="true" batch-size="10" 
> batch-time-interval="10">
>  
>  test.geode.UserQueueListener
>  
> 
> 
>  
>  test.geode.util.PdxSerializerWrapper
>  
> 
> 
>   async-event-queue-ids="userQueue">
>  java.lang.Long
>  test.geode.domain.User
>  
> 
> {code}
>  
> The first server instance successfully started.
> But the second one in always failing on startup. The problem disappears if I 
> remove the  config or disable PDX serialization.
> Here is the stacktrace of the failed instance:
> {code}
> [info 2018/03/12 11:01:43.880 CET server2  tid=0x1] Initializing region 
> PdxTypes
> [info 2018/03/12 11:01:43.893 CET server2  tid=0x1] Region PdxTypes 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] PdxTypes is done 
> getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Region PdxTypes 
> initialized persistent id: 
> /192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at 
> timestamp 1520848903878 version 0 diskStoreId 
> 9d7c3e96b525418d-ae5b85e1966f3a51 name server2 with data from 
> 192.168.178.159(server1:23330):1025.
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Initialization of 
> region PdxTypes completed
> [info 2018/03/12 11:01:43.901 CET server2  tid=0x1] Recovered disk 
> store mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33
> [info 2018/03/12 11:01:43.902 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.907 CET server2  tid=0x1] Created disk store 
> queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a
> [info 2018/03/12 11:01:43.908 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.929 CET server2  tid=0x1] Initializing region 
> gatewayEventIdIndexMetaData
> [info 2018/03/12 11:01:43.933 CET server2  tid=0x1] Region 
> gatewayEventIdIndexMetaData requesting initial image from 
> 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] 
> gatewayEventIdIndexMetaData is done getting image from 
> 192.168.178.159(server1:23330):1025. isDeltaGII is false
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] Initialization of 
> region gatewayEventIdIndexMetaData completed
> [info 2018/03/12 11:01:43.944 CET server2  tid=0x1] 
> ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1
> [info 2018/03/12 11:01:43.953 CET server2  tid=0x1] Started  
> ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning 
> =true}
> [info 2018/03/12 11:01:43.985 CET server2  tid=0x1] Initializing region 
> __PR
> [info 2018/03/12 11:01:43.989 CET server2  tid=0x1] Region __PR 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:44.001 CET server2  Processor 2> tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
>   name=java.util.Collections$UnmodifiableSet
>   fields=[
>   c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
>   empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]
> [info 2018/03/12 11:01:44.005 CET server2  tid=0x1] __PR failed to get 
> image from 192.168.178.159(server1:23330):1025
> [warning 2018/03/12 11:01:44.006 CET server2  tid=0x1] Initialization 
> failed for Region /__PR
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.internal.cache.PartitionRegionConfig .
>   at Remote Member '192.168.178.159(server2:24615):1026' in 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2474)
>   at Remote Member '192.168.178.159(server2:24615):1026' in 
> org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:990)
>   at Remote Member '192.168.178.159(server2:24615):1026' in 
> 

[jira] [Updated] (GEODE-4266) JMX manager should not deserialize exceptions from server

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-4266:
--
Labels: jdbc pull-request-available  (was: jdbc)

> JMX manager should not deserialize exceptions from server
> -
>
> Key: GEODE-4266
> URL: https://issues.apache.org/jira/browse/GEODE-4266
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Fred Krone
>Assignee: Nick Reich
>Priority: Major
>  Labels: jdbc, pull-request-available
>
> Steps
> Created a jdbc-connection, jdbc-mapping, region in gfsh
> Tried a .get from the region which attempted to read through with the 
> JdbcLoader
> However it could not connect to the endpoint and threw an exception (fine).  
> But the exception wasn't handled in gfsh -- gfsh appeared hung.
> [info 2018/01/09 13:42:41.338 PST s1  
> tid=0x4b] Exception occurred:
> java.lang.IllegalStateException: Could not connect ...
>   at 
> org.apache.geode.connectors.jdbc.internal.SqlHandler.getConnection(SqlHandler.java:59)
>   at 
> org.apache.geode.connectors.jdbc.internal.SqlHandler.read(SqlHandler.java:73)
>   at org.apache.geode.connectors.jdbc.JdbcLoader.load(JdbcLoader.java:52)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.doLocalLoad(SearchLoadAndWriteProcessor.java:791)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.load(SearchLoadAndWriteProcessor.java:602)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.searchAndLoad(SearchLoadAndWriteProcessor.java:461)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.doSearchAndLoad(SearchLoadAndWriteProcessor.java:177)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.findUsingSearchLoad(DistributedRegion.java:2338)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.findObjectInSystem(DistributedRegion.java:2208)
>   at 
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1477)
>   at 
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1366)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1300)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1285)
>   at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:320)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.get(DataCommandFunction.java:443)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.get(DataCommandFunction.java:151)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.execute(DataCommandFunction.java:116)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:187)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   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.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$9$1.run(ClusterDistributionManager.java:987)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: 
> Communications link failure
> The last packet sent successfully to the server was 0 milliseconds ago. The 
> driver has not received any packets from the server.
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>   at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
>   at 
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990)
>   at com.mysql.jdbc.MysqlIO.(MysqlIO.java:341)
>   at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2186)
>   at 
> 

[jira] [Commented] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig

[Darrel Schneider (JIRA)]

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

Darrel Schneider commented on GEODE-4822:
-

This: 
Caused by: java.lang.ClassCastException: 
org.apache.geode.pdx.internal.PdxInstanceImpl cannot be cast to java.util.Set
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.cache.PartitionRegionConfig.fromData(PartitionRegionConfig.java:320)
indicates that we thought we were deserializing a set of gatewayIds but instead 
deserialized a PdxInstance.

Setting read serialized to true can cause objects serialized with pdx to 
deserialize as a PdxInstance.

But I think you must also have the ReflectionBasedAutoSerializer configured and 
it is serializing

java.util.concurrent.CopyOnWriteArraySet.CopyOnWriteArraySet as a pdx. My 
understanding of the ReflectionBasedAutoSerializer is that it should ignore any 
java.util.** classes.

I've reassigned this to the serialization team and hope that they can provide 
more information.

> The second server instance startup error: Could not create an instance of 
> PartitionRegionConfig
> ---
>
> Key: GEODE-4822
> URL: https://issues.apache.org/jira/browse/GEODE-4822
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Vlad Ermolaev
>Priority: Major
>
> I have a simple configuration containing a partitioned persistent region and 
> an async queue:
> {code:xml} 
>  dispatcher-threads="1" enable-batch-conflation="true" batch-size="10" 
> batch-time-interval="10">
>  
>  test.geode.UserQueueListener
>  
> 
> 
>  
>  test.geode.util.PdxSerializerWrapper
>  
> 
> 
>   async-event-queue-ids="userQueue">
>  java.lang.Long
>  test.geode.domain.User
>  
> 
> {code}
>  
> The first server instance successfully started.
> But the second one in always failing on startup. The problem disappears if I 
> remove the  config or disable PDX serialization.
> Here is the stacktrace of the failed instance:
> {code}
> [info 2018/03/12 11:01:43.880 CET server2  tid=0x1] Initializing region 
> PdxTypes
> [info 2018/03/12 11:01:43.893 CET server2  tid=0x1] Region PdxTypes 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] PdxTypes is done 
> getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Region PdxTypes 
> initialized persistent id: 
> /192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at 
> timestamp 1520848903878 version 0 diskStoreId 
> 9d7c3e96b525418d-ae5b85e1966f3a51 name server2 with data from 
> 192.168.178.159(server1:23330):1025.
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Initialization of 
> region PdxTypes completed
> [info 2018/03/12 11:01:43.901 CET server2  tid=0x1] Recovered disk 
> store mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33
> [info 2018/03/12 11:01:43.902 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.907 CET server2  tid=0x1] Created disk store 
> queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a
> [info 2018/03/12 11:01:43.908 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.929 CET server2  tid=0x1] Initializing region 
> gatewayEventIdIndexMetaData
> [info 2018/03/12 11:01:43.933 CET server2  tid=0x1] Region 
> gatewayEventIdIndexMetaData requesting initial image from 
> 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] 
> gatewayEventIdIndexMetaData is done getting image from 
> 192.168.178.159(server1:23330):1025. isDeltaGII is false
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] Initialization of 
> region gatewayEventIdIndexMetaData completed
> [info 2018/03/12 11:01:43.944 CET server2  tid=0x1] 
> ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1
> [info 2018/03/12 11:01:43.953 CET server2  tid=0x1] Started  
> ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning 
> =true}
> [info 2018/03/12 11:01:43.985 CET server2  tid=0x1] Initializing region 
> __PR
> [info 2018/03/12 11:01:43.989 CET server2  tid=0x1] Region __PR 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:44.001 CET server2  Processor 2> tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
>   name=java.util.Collections$UnmodifiableSet
>   fields=[
>   c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
>   empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]
> [info 2018/03/12 11:01:44.005 CET server2  tid=0x1] __PR failed to get 
> image from 

[jira] [Resolved] (GEODE-4684) Replace setPdxReadSerialized and getPdxReadSerialized in org.apache.geode.internal.cache

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer resolved GEODE-4684.
--
   Resolution: Fixed
 Assignee: Udo Kohlmeyer
Fix Version/s: 1.6.0

> Replace setPdxReadSerialized and getPdxReadSerialized in 
> org.apache.geode.internal.cache
> 
>
> Key: GEODE-4684
> URL: https://issues.apache.org/jira/browse/GEODE-4684
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
> Fix For: 1.6.0
>
>
> Replace with the solution from GEODE-4679



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4682) Remove setPdxReadSerialized and getPdxReadSerialized from org.apache.geode.cache.query.internal.index

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer resolved GEODE-4682.
--
   Resolution: Fixed
 Assignee: Udo Kohlmeyer
Fix Version/s: 1.6.0

> Remove setPdxReadSerialized and getPdxReadSerialized  from 
> org.apache.geode.cache.query.internal.index
> --
>
> Key: GEODE-4682
> URL: https://issues.apache.org/jira/browse/GEODE-4682
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
> Fix For: 1.6.0
>
>
> The solution / outcome of GEODE-4682 must be used as the replacement for 
> org.apache.geode.cache.query.internal.index



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4681) Remove all static methods involving pdxReadSerialized

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer resolved GEODE-4681.
--
   Resolution: Fixed
 Assignee: Udo Kohlmeyer
Fix Version/s: 1.6.0

> Remove all static methods involving pdxReadSerialized 
> --
>
> Key: GEODE-4681
> URL: https://issues.apache.org/jira/browse/GEODE-4681
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
> Fix For: 1.6.0
>
>
> Remove the following static methods after GEODE-4679 is completed.
>  * setPdxReadSerialized()
>  * getPdxReadSerialized()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer resolved GEODE-4685.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

> Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
> --
>
> Key: GEODE-4685
> URL: https://issues.apache.org/jira/browse/GEODE-4685
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 5h 20m
>  Remaining Estimate: 0h
>
> Replace with the solution from GEODE-4679



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig

[Darrel Schneider (JIRA)]

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

Darrel Schneider updated GEODE-4822:

Component/s: (was: regions)
 serialization

> The second server instance startup error: Could not create an instance of 
> PartitionRegionConfig
> ---
>
> Key: GEODE-4822
> URL: https://issues.apache.org/jira/browse/GEODE-4822
> Project: Geode
>  Issue Type: Bug
>  Components: serialization
>Reporter: Vlad Ermolaev
>Priority: Major
>
> I have a simple configuration containing a partitioned persistent region and 
> an async queue:
> {code:xml} 
>  dispatcher-threads="1" enable-batch-conflation="true" batch-size="10" 
> batch-time-interval="10">
>  
>  test.geode.UserQueueListener
>  
> 
> 
>  
>  test.geode.util.PdxSerializerWrapper
>  
> 
> 
>   async-event-queue-ids="userQueue">
>  java.lang.Long
>  test.geode.domain.User
>  
> 
> {code}
>  
> The first server instance successfully started.
> But the second one in always failing on startup. The problem disappears if I 
> remove the  config or disable PDX serialization.
> Here is the stacktrace of the failed instance:
> {code}
> [info 2018/03/12 11:01:43.880 CET server2  tid=0x1] Initializing region 
> PdxTypes
> [info 2018/03/12 11:01:43.893 CET server2  tid=0x1] Region PdxTypes 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] PdxTypes is done 
> getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Region PdxTypes 
> initialized persistent id: 
> /192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at 
> timestamp 1520848903878 version 0 diskStoreId 
> 9d7c3e96b525418d-ae5b85e1966f3a51 name server2 with data from 
> 192.168.178.159(server1:23330):1025.
> [info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Initialization of 
> region PdxTypes completed
> [info 2018/03/12 11:01:43.901 CET server2  tid=0x1] Recovered disk 
> store mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33
> [info 2018/03/12 11:01:43.902 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.907 CET server2  tid=0x1] Created disk store 
> queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a
> [info 2018/03/12 11:01:43.908 CET server2  tid=0x1] recovery region 
> initialization took 0 ms
> [info 2018/03/12 11:01:43.929 CET server2  tid=0x1] Initializing region 
> gatewayEventIdIndexMetaData
> [info 2018/03/12 11:01:43.933 CET server2  tid=0x1] Region 
> gatewayEventIdIndexMetaData requesting initial image from 
> 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] 
> gatewayEventIdIndexMetaData is done getting image from 
> 192.168.178.159(server1:23330):1025. isDeltaGII is false
> [info 2018/03/12 11:01:43.935 CET server2  tid=0x1] Initialization of 
> region gatewayEventIdIndexMetaData completed
> [info 2018/03/12 11:01:43.944 CET server2  tid=0x1] 
> ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1
> [info 2018/03/12 11:01:43.953 CET server2  tid=0x1] Started  
> ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning 
> =true}
> [info 2018/03/12 11:01:43.985 CET server2  tid=0x1] Initializing region 
> __PR
> [info 2018/03/12 11:01:43.989 CET server2  tid=0x1] Region __PR 
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:44.001 CET server2  Processor 2> tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
>   name=java.util.Collections$UnmodifiableSet
>   fields=[
>   c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
>   empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]
> [info 2018/03/12 11:01:44.005 CET server2  tid=0x1] __PR failed to get 
> image from 192.168.178.159(server1:23330):1025
> [warning 2018/03/12 11:01:44.006 CET server2  tid=0x1] Initialization 
> failed for Region /__PR
> org.apache.geode.SerializationException: Could not create an instance of  
> org.apache.geode.internal.cache.PartitionRegionConfig .
>   at Remote Member '192.168.178.159(server2:24615):1026' in 
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2474)
>   at Remote Member '192.168.178.159(server2:24615):1026' in 
> org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:990)
>   at Remote Member '192.168.178.159(server2:24615):1026' in 
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2784)
>   at Remote Member '192.168.178.159(server2:24615):1026' in 
> 

[jira] [Resolved] (GEODE-4679) pdxReadSerialized accessors must be present in some product level component like Cache

[Udo Kohlmeyer (JIRA)]

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

Udo Kohlmeyer resolved GEODE-4679.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

> pdxReadSerialized accessors must be present in some product level component 
> like Cache
> --
>
> Key: GEODE-4679
> URL: https://issues.apache.org/jira/browse/GEODE-4679
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
> Fix For: 1.6.0
>
>
> +*Current situation:*+
> The getters/setters for pdxReadSerialized thread is present in DefaultQuery 
> as static calls. 
>  * DefaultQuery # getPdxReadSerialized()
>  * DefaultQuery # setPdxReadSerialized()
>  
> +*Solution:*+
> These getters/setters need to move to a more logical part of the code like 
> cache and not be present in DeafaultQuery
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4716) The Gateway Sender MBean needs to monitor events overflowed to disk

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4716:


Commit 307982682d405e26fd94f0bdec856bac2726f695 in geode's branch 
refs/heads/develop from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3079826 ]

GEODE-4716: Added overflow attributes to gateway mbeans



> The Gateway Sender MBean needs to monitor events overflowed to disk
> ---
>
> Key: GEODE-4716
> URL: https://issues.apache.org/jira/browse/GEODE-4716
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, wan
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The Gateway Sender MBean needs to monitor events overflowed to disk.
> These stats provide that info:
> * DiskRegionStatistics entriesOnlyOnDisk and bytesOnlyOnDisk stats for the 
> sender queue (e.g. /ny_PARALLEL_GATEWAY_SENDER_QUEUE)
> * MemLRUStatistics lruEvictions stat for the sender queue (e.g. 
> MemLRUStatistics-/ny_PARALLEL_GATEWAY_SENDER_QUEUE)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4772) Protobuf: add region clear message/operation

[Michael Dodge (JIRA)]

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

Michael Dodge resolved GEODE-4772.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

> Protobuf: add region clear message/operation
> 
>
> Key: GEODE-4772
> URL: https://issues.apache.org/jira/browse/GEODE-4772
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> As a dev using the new protocol, I want to be able to clear a region 
> completely.
> Add a region clear message/operation that clears a replicated region.
> GEODE-788 will implement .clear for partitioned regions - when that is 
> complete we can add support for clearing PRs.
>  
> Client should receive error if the region does not exist or the client does 
> not have authorization on the region.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4772) Protobuf: add region clear message/operation

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4772:


Commit 393959526f50e235787f1b726fa1bf9b9ee17378 in geode's branch 
refs/heads/develop from [~PivotalSarge]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3939595 ]

GEODE-4772: Enhance new protocol with ability to clear region of all entries. 
(#1590)

* GEODE-4772: Enhance region with ability to clear.

* GEODE-4772: Address review comments.

* GEODE-4772: Spotless!


> Protobuf: add region clear message/operation
> 
>
> Key: GEODE-4772
> URL: https://issues.apache.org/jira/browse/GEODE-4772
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> As a dev using the new protocol, I want to be able to clear a region 
> completely.
> Add a region clear message/operation that clears a replicated region.
> GEODE-788 will implement .clear for partitioned regions - when that is 
> complete we can add support for clearing PRs.
>  
> Client should receive error if the region does not exist or the client does 
> not have authorization on the region.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4772) Protobuf: add region clear message/operation

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4772:


Commit 393959526f50e235787f1b726fa1bf9b9ee17378 in geode's branch 
refs/heads/develop from [~PivotalSarge]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3939595 ]

GEODE-4772: Enhance new protocol with ability to clear region of all entries. 
(#1590)

* GEODE-4772: Enhance region with ability to clear.

* GEODE-4772: Address review comments.

* GEODE-4772: Spotless!


> Protobuf: add region clear message/operation
> 
>
> Key: GEODE-4772
> URL: https://issues.apache.org/jira/browse/GEODE-4772
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> As a dev using the new protocol, I want to be able to clear a region 
> completely.
> Add a region clear message/operation that clears a replicated region.
> GEODE-788 will implement .clear for partitioned regions - when that is 
> complete we can add support for clearing PRs.
>  
> Client should receive error if the region does not exist or the client does 
> not have authorization on the region.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4772) Protobuf: add region clear message/operation

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4772:


Commit 393959526f50e235787f1b726fa1bf9b9ee17378 in geode's branch 
refs/heads/develop from [~PivotalSarge]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3939595 ]

GEODE-4772: Enhance new protocol with ability to clear region of all entries. 
(#1590)

* GEODE-4772: Enhance region with ability to clear.

* GEODE-4772: Address review comments.

* GEODE-4772: Spotless!


> Protobuf: add region clear message/operation
> 
>
> Key: GEODE-4772
> URL: https://issues.apache.org/jira/browse/GEODE-4772
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> As a dev using the new protocol, I want to be able to clear a region 
> completely.
> Add a region clear message/operation that clears a replicated region.
> GEODE-788 will implement .clear for partitioned regions - when that is 
> complete we can add support for clearing PRs.
>  
> Client should receive error if the region does not exist or the client does 
> not have authorization on the region.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4772) Protobuf: add region clear message/operation

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4772:


Commit 393959526f50e235787f1b726fa1bf9b9ee17378 in geode's branch 
refs/heads/develop from [~PivotalSarge]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3939595 ]

GEODE-4772: Enhance new protocol with ability to clear region of all entries. 
(#1590)

* GEODE-4772: Enhance region with ability to clear.

* GEODE-4772: Address review comments.

* GEODE-4772: Spotless!


> Protobuf: add region clear message/operation
> 
>
> Key: GEODE-4772
> URL: https://issues.apache.org/jira/browse/GEODE-4772
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> As a dev using the new protocol, I want to be able to clear a region 
> completely.
> Add a region clear message/operation that clears a replicated region.
> GEODE-788 will implement .clear for partitioned regions - when that is 
> complete we can add support for clearing PRs.
>  
> Client should receive error if the region does not exist or the client does 
> not have authorization on the region.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4796) jdbc-1.0.xsd should exist at http://geode.apache.org/schema/jdbc

[Kirk Lund (JIRA)]

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

Kirk Lund resolved GEODE-4796.
--
   Resolution: Fixed
Fix Version/s: 1.5.0

> jdbc-1.0.xsd should exist at http://geode.apache.org/schema/jdbc
> 
>
> Key: GEODE-4796
> URL: https://issues.apache.org/jira/browse/GEODE-4796
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Affects Versions: 1.4.0, 1.5.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Fix For: 1.5.0
>
>
> jdbc-1.0.xsd should added it to the geode-site repo on the asf-site branch:
> {noformat}
> ~/code/geode-site (asf-site)$ find . -name *.xsd
> ./schema/lucene/lucene-1.0.xsd
> ./schema/cache/cache-1.0.xsd
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEODE-4266) JMX manager should not deserialize exceptions from server

[Nick Reich (JIRA)]

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

Nick Reich reassigned GEODE-4266:
-

Assignee: Nick Reich

> JMX manager should not deserialize exceptions from server
> -
>
> Key: GEODE-4266
> URL: https://issues.apache.org/jira/browse/GEODE-4266
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Fred Krone
>Assignee: Nick Reich
>Priority: Major
>  Labels: jdbc
>
> Steps
> Created a jdbc-connection, jdbc-mapping, region in gfsh
> Tried a .get from the region which attempted to read through with the 
> JdbcLoader
> However it could not connect to the endpoint and threw an exception (fine).  
> But the exception wasn't handled in gfsh -- gfsh appeared hung.
> [info 2018/01/09 13:42:41.338 PST s1  
> tid=0x4b] Exception occurred:
> java.lang.IllegalStateException: Could not connect ...
>   at 
> org.apache.geode.connectors.jdbc.internal.SqlHandler.getConnection(SqlHandler.java:59)
>   at 
> org.apache.geode.connectors.jdbc.internal.SqlHandler.read(SqlHandler.java:73)
>   at org.apache.geode.connectors.jdbc.JdbcLoader.load(JdbcLoader.java:52)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.doLocalLoad(SearchLoadAndWriteProcessor.java:791)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.load(SearchLoadAndWriteProcessor.java:602)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.searchAndLoad(SearchLoadAndWriteProcessor.java:461)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.doSearchAndLoad(SearchLoadAndWriteProcessor.java:177)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.findUsingSearchLoad(DistributedRegion.java:2338)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.findObjectInSystem(DistributedRegion.java:2208)
>   at 
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1477)
>   at 
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1366)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1300)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1285)
>   at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:320)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.get(DataCommandFunction.java:443)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.get(DataCommandFunction.java:151)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.execute(DataCommandFunction.java:116)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:187)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   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.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$9$1.run(ClusterDistributionManager.java:987)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: 
> Communications link failure
> The last packet sent successfully to the server was 0 milliseconds ago. The 
> driver has not received any packets from the server.
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>   at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
>   at 
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990)
>   at com.mysql.jdbc.MysqlIO.(MysqlIO.java:341)
>   at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2186)
>   at 
> com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2219)
>   at 

[jira] [Resolved] (GEODE-4798) JdbcConnectorException can not be deserialized

[Nick Reich (JIRA)]

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

Nick Reich resolved GEODE-4798.
---
   Resolution: Fixed
Fix Version/s: 1.6.0

> JdbcConnectorException can not be deserialized
> --
>
> Key: GEODE-4798
> URL: https://issues.apache.org/jira/browse/GEODE-4798
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.5.0
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
> Fix For: 1.6.0
>
>
> The JdbcConnectorException cannot be deserialized because it is not a 
> "trusted" class. Also the SQLException it usually wraps will also fail 
> deserialization so it might be better to not create JdbcConnectorException 
> instances whose cause is a SQLException. Instead do some type of conversion 
> of the SQLException.
> The following is some information about how to get JdbcConnectorException to 
> be trusted by the serialization code:
> Create a new DistributionService like this lucene one:
> LuceneDistributedSystemService
> geode-lucene/src/main/resources/META-INF/services/org.apache.geode.distributed.internal.DistributedSystemService
> It returns a text file with a whitelist.
> Add a test like 
> org.apache.geode.codeAnalysis.AnalyzeLuceneSerializablesJUnitTest



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4796) jdbc-1.0.xsd should exist at http://geode.apache.org/schema/jdbc

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4796:


Commit 961ad24d6f9fbdd8415305f386c1b9e421ac3802 in geode-site's branch 
refs/heads/asf-site from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode-site.git;h=961ad24 ]

GEODE-4796: add schema/jdbc/jdbc-1.0.xsd


> jdbc-1.0.xsd should exist at http://geode.apache.org/schema/jdbc
> 
>
> Key: GEODE-4796
> URL: https://issues.apache.org/jira/browse/GEODE-4796
> Project: Geode
>  Issue Type: Bug
>  Components: extensions
>Affects Versions: 1.4.0, 1.5.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> jdbc-1.0.xsd should added it to the geode-site repo on the asf-site branch:
> {noformat}
> ~/code/geode-site (asf-site)$ find . -name *.xsd
> ./schema/lucene/lucene-1.0.xsd
> ./schema/cache/cache-1.0.xsd
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4658) Expose how much time it takes to write to disk and what is the disk store size

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller updated GEODE-4658:
---
Component/s: docs

> Expose how much time it takes to write to disk and what is the disk store size
> --
>
> Key: GEODE-4658
> URL: https://issues.apache.org/jira/browse/GEODE-4658
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, regions
>Reporter: Fred Krone
>Priority: Major
>  Labels: starter++
>
> *Given* I have a persistent region with a default disk store
>  *When* I write data on the region
>  *Then* I can see  2 new metrics {{average write time to disk}} ns time and 
> {{size of disk store}} in bytes
> h3. Documentation
> Add this new metric to the docs
>  
> This should be a matter of altering the ShowMetricsCommand.java 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEODE-4816) Enhance experimental driver with authentication

[Michael Dodge (JIRA)]

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

Michael Dodge reassigned GEODE-4816:


Assignee: Michael Dodge

> Enhance experimental driver with authentication
> ---
>
> Key: GEODE-4816
> URL: https://issues.apache.org/jira/browse/GEODE-4816
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Michael Dodge
>Assignee: Michael Dodge
>Priority: Major
>
> The experimental driver does not experiment with authentication. It ought.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4233) Create new geode-example about transactions

[Michael Dodge (JIRA)]

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

Michael Dodge resolved GEODE-4233.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

> Create new geode-example about transactions
> ---
>
> Key: GEODE-4233
> URL: https://issues.apache.org/jira/browse/GEODE-4233
> Project: Geode
>  Issue Type: New Feature
>  Components: examples
>Reporter: Michael Dodge
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Create a new example that demonstrates transactions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4801) Readme should link to "how to contribute" on wiki

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4801:


Commit 386b92bc8f4a05b77047e1af681ed863b8d2d005 in geode's branch 
refs/heads/develop from [~amurmann]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=386b92b ]

GEODE-4801 Readme links to "how to contribute"

To encourage contributions by new community members this adds a link
from the readme to the "how to contribute" page in the wiki.

This also changes a few `http://` links to `https://`.


> Readme should link to "how to contribute" on wiki
> -
>
> Key: GEODE-4801
> URL: https://issues.apache.org/jira/browse/GEODE-4801
> Project: Geode
>  Issue Type: Improvement
>  Components: website
>Reporter: Alexander Murmann
>Assignee: Alexander Murmann
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4801) Readme should link to "how to contribute" on wiki

[Anthony Baker (JIRA)]

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

Anthony Baker resolved GEODE-4801.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

> Readme should link to "how to contribute" on wiki
> -
>
> Key: GEODE-4801
> URL: https://issues.apache.org/jira/browse/GEODE-4801
> Project: Geode
>  Issue Type: Improvement
>  Components: website
>Reporter: Alexander Murmann
>Assignee: Alexander Murmann
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4801) Readme should link to "how to contribute" on wiki

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-4801:
--
Labels: pull-request-available  (was: )

> Readme should link to "how to contribute" on wiki
> -
>
> Key: GEODE-4801
> URL: https://issues.apache.org/jira/browse/GEODE-4801
> Project: Geode
>  Issue Type: Improvement
>  Components: website
>Reporter: Alexander Murmann
>Assignee: Alexander Murmann
>Priority: Major
>  Labels: pull-request-available
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-4826) Fail fast with Spotless and rat checks

[Michael Dodge (JIRA)]

Michael Dodge created GEODE-4826:


 Summary: Fail fast with Spotless and rat checks
 Key: GEODE-4826
 URL: https://issues.apache.org/jira/browse/GEODE-4826
 Project: Geode
  Issue Type: New Feature
Reporter: Michael Dodge


The Spotless and rat checks happened at the *end* of the build, which makes 
them fail as slowly as possible. Enhance developer productivity by putting 
those checks (and the potential for concomitant failures) at the *beginning* of 
the build. Also, investigate automatically applying the Spotless rules to 
prevent any possibility of a failed Spotless check.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEODE-4826) Fail fast with Spotless and rat checks

[Michael Dodge (JIRA)]

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

Michael Dodge reassigned GEODE-4826:


Assignee: Patrick Rhomberg

> Fail fast with Spotless and rat checks
> --
>
> Key: GEODE-4826
> URL: https://issues.apache.org/jira/browse/GEODE-4826
> Project: Geode
>  Issue Type: New Feature
>Reporter: Michael Dodge
>Assignee: Patrick Rhomberg
>Priority: Major
>
> The Spotless and rat checks happened at the *end* of the build, which makes 
> them fail as slowly as possible. Enhance developer productivity by putting 
> those checks (and the potential for concomitant failures) at the *beginning* 
> of the build. Also, investigate automatically applying the Spotless rules to 
> prevent any possibility of a failed Spotless check.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-577) CI Failure: QueryMonitorDUnitTest.testQueryExecutionLocally

[Shelley Lynn Hughes-Godfrey (JIRA)]

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

Shelley Lynn Hughes-Godfrey commented on GEODE-577:
---

Reproduced in CI (Flaky Tests):
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/294

```
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest > 
testQueryExecutionLocally FAILED
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.test.dunit.NamedRunnable.run in VM 1 running on Host 
d090c941-f8b7-4e1d-4618-0043584ad8ae with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
at org.apache.geode.test.dunit.VM.invoke(VM.java:370)
at org.apache.geode.test.dunit.VM.invoke(VM.java:301)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.testQueryExecutionLocally(QueryMonitorDUnitTest.java:480)

Caused by:
java.lang.AssertionError: The query should have been canceled by the 
QueryMonitor. Query: SELECT ID FROM /root/exampleRegion p WHERE  p.ID > 100
at org.junit.Assert.fail(Assert.java:88)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.executeQuery(QueryMonitorDUnitTest.java:360)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.executeQueriesAgainstQueryService(QueryMonitorDUnitTest.java:351)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.executeQueriesOnServer(QueryMonitorDUnitTest.java:342)
at 
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.lambda$testQueryExecutionLocally$bb17a952$6(QueryMonitorDUnitTest.java:480)
```

> CI Failure: QueryMonitorDUnitTest.testQueryExecutionLocally
> ---
>
> Key: GEODE-577
> URL: https://issues.apache.org/jira/browse/GEODE-577
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Barry Oglesby
>Priority: Major
>  Labels: CI, Flaky
>
> GemFire_develop_DistributedTests
> Private Build #38 (Nov 15, 2015 3:12:12 PM)
> Revision: b7f640cf2e41acb40a531cc7abbee932a9ea093c
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> Error Message
> {noformat}
> dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1 
> running on Host latvia.gemstone.com with 4 VMs
> {noformat}
> Stacktrace
> {noformat}
> dunit.RMIException: While invoking 
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1 
> running on Host latvia.gemstone.com with 4 VMs
>   at dunit.VM.invoke(VM.java:369)
>   at dunit.VM.invoke(VM.java:312)
>   at dunit.VM.invoke(VM.java:266)
>   at 
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest.testQueryExecutionLocally(QueryMonitorDUnitTest.java:493)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at junit.framework.TestCase.runBare(TestCase.java:141)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:252)
>   at junit.framework.TestSuite.run(TestSuite.java:247)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
>   at 
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
>   at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown Source)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
>   at 
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   

[jira] [Closed] (GEODE-4752) create an AnalyzeSerializables unit test for geode-connectors

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt closed GEODE-4752.
---

> create an AnalyzeSerializables unit test for geode-connectors
> -
>
> Key: GEODE-4752
> URL: https://issues.apache.org/jira/browse/GEODE-4752
> Project: Geode
>  Issue Type: Task
>  Components: regions, serialization
>Reporter: Bruce Schuchardt
>Priority: Major
>
> This module has recently been added and contains serializable functions.  
> Someone added these to the serialization whitelist in InternalDataSerializers 
> and this needs to be removed.
> Consider changing the functions to use DataSerializable instead of java 
> Serializable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4824) Categorize all the session tests as SessionTest

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-4824:
--
Labels: pull-request-available  (was: )

> Categorize all the session tests as SessionTest
> ---
>
> Key: GEODE-4824
> URL: https://issues.apache.org/jira/browse/GEODE-4824
> Project: Geode
>  Issue Type: Bug
>  Components: http session
>Reporter: nabarun
>Assignee: nabarun
>Priority: Major
>  Labels: pull-request-available
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4825) Lucene Index sets pdx read serialized to true

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-4825:
--
Labels: pull-request-available  (was: )

> Lucene Index sets pdx read serialized to true
> -
>
> Key: GEODE-4825
> URL: https://issues.apache.org/jira/browse/GEODE-4825
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>
> In IndexRepositoryFactory, there is a call to set the pdx read serialized to 
> true, but it is only unset if the index failed to be created.  Instead it 
> should be pulled out of the if block.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEODE-4825) Lucene Index sets pdx read serialized to true

[Jason Huynh (JIRA)]

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

Jason Huynh reassigned GEODE-4825:
--

Assignee: Jason Huynh

> Lucene Index sets pdx read serialized to true
> -
>
> Key: GEODE-4825
> URL: https://issues.apache.org/jira/browse/GEODE-4825
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>
> In IndexRepositoryFactory, there is a call to set the pdx read serialized to 
> true, but it is only unset if the index failed to be created.  Instead it 
> should be pulled out of the if block.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4266) JMX manager should not deserialize exceptions from server

[Fred Krone (JIRA)]

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

Fred Krone updated GEODE-4266:
--
Labels: jdbc  (was: )

> JMX manager should not deserialize exceptions from server
> -
>
> Key: GEODE-4266
> URL: https://issues.apache.org/jira/browse/GEODE-4266
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Fred Krone
>Priority: Major
>  Labels: jdbc
>
> Steps
> Created a jdbc-connection, jdbc-mapping, region in gfsh
> Tried a .get from the region which attempted to read through with the 
> JdbcLoader
> However it could not connect to the endpoint and threw an exception (fine).  
> But the exception wasn't handled in gfsh -- gfsh appeared hung.
> [info 2018/01/09 13:42:41.338 PST s1  
> tid=0x4b] Exception occurred:
> java.lang.IllegalStateException: Could not connect ...
>   at 
> org.apache.geode.connectors.jdbc.internal.SqlHandler.getConnection(SqlHandler.java:59)
>   at 
> org.apache.geode.connectors.jdbc.internal.SqlHandler.read(SqlHandler.java:73)
>   at org.apache.geode.connectors.jdbc.JdbcLoader.load(JdbcLoader.java:52)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.doLocalLoad(SearchLoadAndWriteProcessor.java:791)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.load(SearchLoadAndWriteProcessor.java:602)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.searchAndLoad(SearchLoadAndWriteProcessor.java:461)
>   at 
> org.apache.geode.internal.cache.SearchLoadAndWriteProcessor.doSearchAndLoad(SearchLoadAndWriteProcessor.java:177)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.findUsingSearchLoad(DistributedRegion.java:2338)
>   at 
> org.apache.geode.internal.cache.DistributedRegion.findObjectInSystem(DistributedRegion.java:2208)
>   at 
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1477)
>   at 
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1366)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1300)
>   at 
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1285)
>   at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:320)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.get(DataCommandFunction.java:443)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.get(DataCommandFunction.java:151)
>   at 
> org.apache.geode.management.internal.cli.functions.DataCommandFunction.execute(DataCommandFunction.java:116)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:187)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
>   at 
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
>   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.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$9$1.run(ClusterDistributionManager.java:987)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: 
> Communications link failure
> The last packet sent successfully to the server was 0 milliseconds ago. The 
> driver has not received any packets from the server.
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>   at com.mysql.jdbc.Util.handleNewInstance(Util.java:425)
>   at 
> com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990)
>   at com.mysql.jdbc.MysqlIO.(MysqlIO.java:341)
>   at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2186)
>   at 
> com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2219)
>   at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2014)
> 

[jira] [Assigned] (GEODE-4824) Categorize all the session tests as SessionTest

[nabarun (JIRA)]

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

nabarun reassigned GEODE-4824:
--

Assignee: nabarun

> Categorize all the session tests as SessionTest
> ---
>
> Key: GEODE-4824
> URL: https://issues.apache.org/jira/browse/GEODE-4824
> Project: Geode
>  Issue Type: Bug
>  Components: http session
>Reporter: nabarun
>Assignee: nabarun
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (GEODE-4797) Categorize all WAN tests as WANTest

[nabarun (JIRA)]

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

nabarun closed GEODE-4797.
--

> Categorize all WAN tests as WANTest 
> 
>
> Key: GEODE-4797
> URL: https://issues.apache.org/jira/browse/GEODE-4797
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GEODE-4797) Categorize all WAN tests as WANTest

[nabarun (JIRA)]

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

nabarun resolved GEODE-4797.

Resolution: Fixed

> Categorize all WAN tests as WANTest 
> 
>
> Key: GEODE-4797
> URL: https://issues.apache.org/jira/browse/GEODE-4797
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


Commit 4143a736871b53244102d3a48fc73ddea81179a1 in geode's branch 
refs/heads/develop from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4143a73 ]

GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the 
TypeRegistry.
Cleaned up the overriding of readSerialized to reset to previous value.
Added cache to AbstractJdbcCallback.java so that children classes can access it.
Replaced AtomicLong with LongAdder.


> Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
> --
>
> Key: GEODE-4685
> URL: https://issues.apache.org/jira/browse/GEODE-4685
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 5h 20m
>  Remaining Estimate: 0h
>
> Replace with the solution from GEODE-4679



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


Commit ae8356cd87a28f506d66bc5e21baa79ec5ecbb91 in geode's branch 
refs/heads/feature/GEODE-4685 from Udo
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ae8356c ]

GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the 
TypeRegistry.
Cleaned up the overriding of readSerialized to reset to previous value.
Added cache to AbstractJdbcCallback.java so that children classes can access it.
Replaced AtomicLong with LongAdder.


> Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
> --
>
> Key: GEODE-4685
> URL: https://issues.apache.org/jira/browse/GEODE-4685
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Assignee: Udo Kohlmeyer
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> Replace with the solution from GEODE-4679



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4750) Add finer grained security to OQL queries with protobuf

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4750:


Commit 17602ce01f82188b807cae63c65770e33006a26f in geode's branch 
refs/heads/feature/GEODE-4685 from [~WireBaron]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=17602ce ]

GEODE-4750: Allow region level authorization for OQL queries (#1570)



> Add finer grained security to OQL queries with protobuf
> ---
>
> Key: GEODE-4750
> URL: https://issues.apache.org/jira/browse/GEODE-4750
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Dan Smith
>Assignee: Brian Rowe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> After GEODE-3126 and GEODE-4406 are implemented, we should update the 
> OqlOperationHandler to allow queries if the user has access to the individual 
> regions. Currently the changes for GEODE-3126 are validating that the user 
> has DATA:READ access for all regions in order to do a query.
> The QueryCommand class has an example of how to validate the regions involved 
> in the query.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4821) RegisterInterestIntegrationTest should not use ClusterStarterRule

[Jason Huynh (JIRA)]

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

Jason Huynh updated GEODE-4821:
---
Component/s: client queues

> RegisterInterestIntegrationTest should not use ClusterStarterRule
> -
>
> Key: GEODE-4821
> URL: https://issues.apache.org/jira/browse/GEODE-4821
> Project: Geode
>  Issue Type: Bug
>  Components: client queues, tests
>Reporter: Kirk Lund
>Priority: Major
>
> ClusterStarterRule is a DistributedTest rule and launches DUnit child VMs. 
> RegisterInterestIntegrationTest should either change to be a DistributedTest 
> or change to not use ClusterStarterRule.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GEODE-4823) Indexes should not be updated on a destroy if the old value is a TOMBSTONE

[Jason Huynh (JIRA)]

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

Jason Huynh reassigned GEODE-4823:
--

Assignee: Jason Huynh

> Indexes should not be updated on a destroy if the old value is a TOMBSTONE
> --
>
> Key: GEODE-4823
> URL: https://issues.apache.org/jira/browse/GEODE-4823
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>
> If a destroy operation is called but the old value is a TOMBSTONE, the index 
> operation is a no op but certain indexes may spend cycles trying to locate 
> the entry in the index.
>  
> Instead we should short circuit and ignore an operation if the action is 
> DESTROY and the old value is a TOMBSTONE



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GEODE-4823) Indexes should not be updated on a destroy if the old value is a TOMBSTONE

[Jason Huynh (JIRA)]

Jason Huynh created GEODE-4823:
--

 Summary: Indexes should not be updated on a destroy if the old 
value is a TOMBSTONE
 Key: GEODE-4823
 URL: https://issues.apache.org/jira/browse/GEODE-4823
 Project: Geode
  Issue Type: Bug
  Components: querying
Reporter: Jason Huynh


If a destroy operation is called but the old value is a TOMBSTONE, the index 
operation is a no op but certain indexes may spend cycles trying to locate the 
entry in the index.

 

Instead we should short circuit and ignore an operation if the action is 
DESTROY and the old value is a TOMBSTONE



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4716) The Gateway Sender MBean needs to monitor events overflowed to disk

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller updated GEODE-4716:
---
Component/s: docs

> The Gateway Sender MBean needs to monitor events overflowed to disk
> ---
>
> Key: GEODE-4716
> URL: https://issues.apache.org/jira/browse/GEODE-4716
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, wan
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The Gateway Sender MBean needs to monitor events overflowed to disk.
> These stats provide that info:
> * DiskRegionStatistics entriesOnlyOnDisk and bytesOnlyOnDisk stats for the 
> sender queue (e.g. /ny_PARALLEL_GATEWAY_SENDER_QUEUE)
> * MemLRUStatistics lruEvictions stat for the sender queue (e.g. 
> MemLRUStatistics-/ny_PARALLEL_GATEWAY_SENDER_QUEUE)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4814) Categorize FunctionService Tests

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated GEODE-4814:
--
Labels: pull-request-available  (was: )

> Categorize FunctionService Tests
> 
>
> Key: GEODE-4814
> URL: https://issues.apache.org/jira/browse/GEODE-4814
> Project: Geode
>  Issue Type: Task
>  Components: functions
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>
> add a new FunctionServiceTest interface and categorize all relevant dunit and 
> integration tests



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4735) All CliUtils functions should take cache as a parameter if it needs one.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4735:


Commit b53714cf045669bebe0fd78d3692d76f07c2116f in geode's branch 
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b53714c ]

GEODE-4735: get rid of Cache.getInstance call from CliUtils and GfshC… (#1551)

* GEODE-4735: get rid of Cache.getInstance call from CliUtils and GfshCommand

* all functions in CliUtils take cache as a parameter if needs one.
* InternalCache is injected to the command when the command is initialized.

> All CliUtils functions should take cache as a parameter if it needs one. 
> -
>
> Key: GEODE-4735
> URL: https://issues.apache.org/jira/browse/GEODE-4735
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> get rid of Cache.getInstance call from CliUtils and GfshCommand. 
> Commands/functions/tests that use CliUtils should supply its own cache when 
> using these functions.
> Commands's access to cache should be injected when the commands are 
> initialized.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (GEODE-4735) All CliUtils functions should take cache as a parameter if it needs one.

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4735:


Commit b53714cf045669bebe0fd78d3692d76f07c2116f in geode's branch 
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b53714c ]

GEODE-4735: get rid of Cache.getInstance call from CliUtils and GfshC… (#1551)

* GEODE-4735: get rid of Cache.getInstance call from CliUtils and GfshCommand

* all functions in CliUtils take cache as a parameter if needs one.
* InternalCache is injected to the command when the command is initialized.

> All CliUtils functions should take cache as a parameter if it needs one. 
> -
>
> Key: GEODE-4735
> URL: https://issues.apache.org/jira/browse/GEODE-4735
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> get rid of Cache.getInstance call from CliUtils and GfshCommand. 
> Commands/functions/tests that use CliUtils should supply its own cache when 
> using these functions.
> Commands's access to cache should be injected when the commands are 
> initialized.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig

[Vlad Ermolaev (JIRA)]

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

Vlad Ermolaev updated GEODE-4822:
-
Description: 
I have a simple configuration containing a partitioned persistent region and an 
async queue:

{code:xml} 

 
 test.geode.UserQueueListener
 



 
 test.geode.util.PdxSerializerWrapper
 



 
 java.lang.Long
 test.geode.domain.User
 

{code}
 
The first server instance successfully started.
But the second one in always failing on startup. The problem disappears if I 
remove the  config or disable PDX serialization.

Here is the stacktrace of the failed instance:
{code}
[info 2018/03/12 11:01:43.880 CET server2  tid=0x1] Initializing region 
PdxTypes

[info 2018/03/12 11:01:43.893 CET server2  tid=0x1] Region PdxTypes 
requesting initial image from 192.168.178.159(server1:23330):1025

[info 2018/03/12 11:01:43.897 CET server2  tid=0x1] PdxTypes is done 
getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true

[info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Region PdxTypes 
initialized persistent id: 
/192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at 
timestamp 1520848903878 version 0 diskStoreId 9d7c3e96b525418d-ae5b85e1966f3a51 
name server2 with data from 192.168.178.159(server1:23330):1025.

[info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Initialization of 
region PdxTypes completed

[info 2018/03/12 11:01:43.901 CET server2  tid=0x1] Recovered disk store 
mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33

[info 2018/03/12 11:01:43.902 CET server2  tid=0x1] recovery region 
initialization took 0 ms

[info 2018/03/12 11:01:43.907 CET server2  tid=0x1] Created disk store 
queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a

[info 2018/03/12 11:01:43.908 CET server2  tid=0x1] recovery region 
initialization took 0 ms

[info 2018/03/12 11:01:43.929 CET server2  tid=0x1] Initializing region 
gatewayEventIdIndexMetaData

[info 2018/03/12 11:01:43.933 CET server2  tid=0x1] Region 
gatewayEventIdIndexMetaData requesting initial image from 
192.168.178.159(server1:23330):1025

[info 2018/03/12 11:01:43.935 CET server2  tid=0x1] 
gatewayEventIdIndexMetaData is done getting image from 
192.168.178.159(server1:23330):1025. isDeltaGII is false

[info 2018/03/12 11:01:43.935 CET server2  tid=0x1] Initialization of 
region gatewayEventIdIndexMetaData completed

[info 2018/03/12 11:01:43.944 CET server2  tid=0x1] 
ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1

[info 2018/03/12 11:01:43.953 CET server2  tid=0x1] Started  
ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning 
=true}

[info 2018/03/12 11:01:43.985 CET server2  tid=0x1] Initializing region 
__PR

[info 2018/03/12 11:01:43.989 CET server2  tid=0x1] Region __PR 
requesting initial image from 192.168.178.159(server1:23330):1025

[info 2018/03/12 11:01:44.001 CET server2  tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
  name=java.util.Collections$UnmodifiableSet
  fields=[
  c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
  empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]

[info 2018/03/12 11:01:44.005 CET server2  tid=0x1] __PR failed to get 
image from 192.168.178.159(server1:23330):1025

[warning 2018/03/12 11:01:44.006 CET server2  tid=0x1] Initialization 
failed for Region /__PR
org.apache.geode.SerializationException: Could not create an instance of  
org.apache.geode.internal.cache.PartitionRegionConfig .
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2474)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:990)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2784)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:99)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.cache.EntryEventImpl.deserialize(EntryEventImpl.java:1951)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.cache.EntryEventImpl.deserialize(EntryEventImpl.java:1944)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.cache.VMCachedDeserializable.getDeserializedValue(VMCachedDeserializable.java:134)
at Remote Member '192.168.178.159(server2:24615):1026' in 

[jira] [Created] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig

[Vlad Ermolaev (JIRA)]

Vlad Ermolaev created GEODE-4822:


 Summary: The second server instance startup error: Could not 
create an instance of PartitionRegionConfig
 Key: GEODE-4822
 URL: https://issues.apache.org/jira/browse/GEODE-4822
 Project: Geode
  Issue Type: Bug
  Components: regions
Reporter: Vlad Ermolaev


I have a simple configuration containing a partitioned persistent region and an 
async queue:

{code:xml} 

 
 test.geode.UserQueueListener
 



 
 test.geode.util.PdxSerializerWrapper
 



 
 java.lang.Long
 test.geode.domain.User
 

{code}
 
The first server instance successfully started.
But the second one in always failing on startup. The problem disappears if I 
remove the  config.

Here is the stacktrace of the failed instance:
{code}
[info 2018/03/12 11:01:43.880 CET server2  tid=0x1] Initializing region 
PdxTypes

[info 2018/03/12 11:01:43.893 CET server2  tid=0x1] Region PdxTypes 
requesting initial image from 192.168.178.159(server1:23330):1025

[info 2018/03/12 11:01:43.897 CET server2  tid=0x1] PdxTypes is done 
getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true

[info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Region PdxTypes 
initialized persistent id: 
/192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at 
timestamp 1520848903878 version 0 diskStoreId 9d7c3e96b525418d-ae5b85e1966f3a51 
name server2 with data from 192.168.178.159(server1:23330):1025.

[info 2018/03/12 11:01:43.897 CET server2  tid=0x1] Initialization of 
region PdxTypes completed

[info 2018/03/12 11:01:43.901 CET server2  tid=0x1] Recovered disk store 
mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33

[info 2018/03/12 11:01:43.902 CET server2  tid=0x1] recovery region 
initialization took 0 ms

[info 2018/03/12 11:01:43.907 CET server2  tid=0x1] Created disk store 
queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a

[info 2018/03/12 11:01:43.908 CET server2  tid=0x1] recovery region 
initialization took 0 ms

[info 2018/03/12 11:01:43.929 CET server2  tid=0x1] Initializing region 
gatewayEventIdIndexMetaData

[info 2018/03/12 11:01:43.933 CET server2  tid=0x1] Region 
gatewayEventIdIndexMetaData requesting initial image from 
192.168.178.159(server1:23330):1025

[info 2018/03/12 11:01:43.935 CET server2  tid=0x1] 
gatewayEventIdIndexMetaData is done getting image from 
192.168.178.159(server1:23330):1025. isDeltaGII is false

[info 2018/03/12 11:01:43.935 CET server2  tid=0x1] Initialization of 
region gatewayEventIdIndexMetaData completed

[info 2018/03/12 11:01:43.944 CET server2  tid=0x1] 
ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1

[info 2018/03/12 11:01:43.953 CET server2  tid=0x1] Started  
ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning 
=true}

[info 2018/03/12 11:01:43.985 CET server2  tid=0x1] Initializing region 
__PR

[info 2018/03/12 11:01:43.989 CET server2  tid=0x1] Region __PR 
requesting initial image from 192.168.178.159(server1:23330):1025

[info 2018/03/12 11:01:44.001 CET server2  tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
  name=java.util.Collections$UnmodifiableSet
  fields=[
  c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
  empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]

[info 2018/03/12 11:01:44.005 CET server2  tid=0x1] __PR failed to get 
image from 192.168.178.159(server1:23330):1025

[warning 2018/03/12 11:01:44.006 CET server2  tid=0x1] Initialization 
failed for Region /__PR
org.apache.geode.SerializationException: Could not create an instance of  
org.apache.geode.internal.cache.PartitionRegionConfig .
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2474)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:990)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2784)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.DataSerializer.readObject(DataSerializer.java:2961)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:99)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.cache.EntryEventImpl.deserialize(EntryEventImpl.java:1951)
at Remote Member '192.168.178.159(server2:24615):1026' in 
org.apache.geode.internal.cache.EntryEventImpl.deserialize(EntryEventImpl.java:1944)
at Remote Member '192.168.178.159(server2:24615):1026' in