[jira] [Assigned] (GEODE-4401) Add a CloseConnection protobuf message

[Michael Dodge (JIRA)]

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

Michael Dodge reassigned GEODE-4401:


Assignee: Michael Dodge

> Add a CloseConnection protobuf message
> --
>
> Key: GEODE-4401
> URL: https://issues.apache.org/jira/browse/GEODE-4401
> Project: Geode
>  Issue Type: Task
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Michael Dodge
>Priority: Major
>
> The current API has no way for the client to inform a server of its intent to 
> close its connection.  The server is left thinking the client crashed.  It 
> would be nice to have a graceful shutdown message & have the server log 
> something if the client abnormally closes the connection without sending a 
> Close message.
> See also GEODE-4300 where we added supression of log messages when client 
> connections are found to be closed.



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

[jira] [Assigned] (GEODE-4737) User Guide: Describe addition of JSON specs to gfsh commands

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller reassigned GEODE-4737:
--

Assignee: Karen Smoler Miller

> User Guide: Describe addition of JSON specs to gfsh commands
> 
>
> Key: GEODE-4737
> URL: https://issues.apache.org/jira/browse/GEODE-4737
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Some new gfsh commands can take a JSON spec. Examples include `alter region 
> --entry-idle-time-custom-expiry` and `create region --cache-listener`.
> Add a general description of the syntax to the gfsh section of the manual so 
> individual command-reference entries can point to a centralized explanation, 
> rather than repeating the syntax details each time.
> One developer has requested that we state that the JSON parser recognizes 
> double quotes as well as single quotes. Some JSON parsers accept only single 
> quotes.



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

[jira] [Assigned] (GEODE-1798) Dead code in transaction layer confusing

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg reassigned GEODE-1798:
---

Assignee: (was: Patrick Rhomberg)

> Dead code in transaction layer confusing
> 
>
> Key: GEODE-1798
> URL: https://issues.apache.org/jira/browse/GEODE-1798
> Project: Geode
>  Issue Type: Improvement
>  Components: transactions
>Reporter: Darrel Schneider
>Priority: Major
>
> In geode the transaction code always has a collection of "pendingCallbacks". 
> But the code makes some special calls if this collection is null. This code 
> should be cleaned up to only handle an existing collection.
> Also BucketRegion has an implementation of invokeTXCallbacks that is wrong. 
> If it ever is called it will cause extra events. But it should never be 
> invoked since pendingCallbacks is never null. Instead 
> PartitionedRegion.invokeTXCallbacks will be invoked.
> So the implementation of BucketRegion invokeTXCallbacks should be changed to 
> throw an exception. If tests find any code paths that call it they should be 
> changed to instead call PartitionedRegion.



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

[jira] [Commented] (GEODE-4704) GatewaySender batch conflation can incorrectly conflate events causing out of order processing

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4704:


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

GEODE-4704: Modified ConflationKey to use shadowKey when comparing events



> GatewaySender batch conflation can incorrectly conflate events causing out of 
> order processing
> --
>
> Key: GEODE-4704
> URL: https://issues.apache.org/jira/browse/GEODE-4704
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Barry Oglesby
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In the current implementation of \{{AbstractGatewaySenderEventProcessor 
> conflate}} can incorrectly conflate two create events on the same key.
> The else clause of the conflate method (meaning the event is not conflatable) 
> assumes there isn't already a event with the same region, key and operation 
> in the map. It just does a put:
> {noformat}
> ConflationKey key = new ConflationKey(gsEvent.getRegion().getFullPath(), 
> gsEvent.getKeyToConflate(), gsEvent.getOperation());
> conflatedEventsMap.put(key, gsEvent);
> {noformat}
> In certain cases, there could already be a create event on the same region, 
> key and operation in the batch, so the previous one gets replaced by the 
> later once which causes the events to be processed out of order.
> These 4 events:
> {noformat}
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=100;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_13964;shadowKey=27709]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=101;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_14024;shadowKey=27822]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=102;bucketId=24];operation=DESTROY;region=/dataStoreRegion;key=Object_13964;shadowKey=27935]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=104;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_14024;shadowKey=28161]
> {noformat}
> Become these 3 events:
> {noformat}
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=100;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_13964;shadowKey=27709]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=104;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_14024;shadowKey=28161]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=102;bucketId=24];operation=DESTROY;region=/dataStoreRegion;key=Object_13964;shadowKey=27935]
> {noformat}
> Notice the shadowKeys and sequenceIds are out of order after the conflation.
> The fix will be to include the shadow key in hashCode and equals in the case 
> where the event is not conflatable.



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

[jira] [Created] (GEODE-4743) Code Cleanup: Remove dead classes DebuggerSupport, SingletonCallable, SingletonValue, StackTraceCollector, DebuggerUtils

[Patrick Rhomberg (JIRA)]

Patrick Rhomberg created GEODE-4743:
---

 Summary: Code Cleanup: Remove dead classes DebuggerSupport, 
SingletonCallable, SingletonValue, StackTraceCollector, DebuggerUtils
 Key: GEODE-4743
 URL: https://issues.apache.org/jira/browse/GEODE-4743
 Project: Geode
  Issue Type: Bug
Reporter: Patrick Rhomberg


These classes appear to be remnants of the dark and dreadful time before IDE 
debuggers.



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

[jira] [Updated] (GEODE-4743) Code Cleanup: Remove dead classes DebuggerSupport, SingletonCallable, SingletonValue, StackTraceCollector, DebuggerUtils

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg updated GEODE-4743:

Labels: pull-request-available  (was: )

> Code Cleanup: Remove dead classes DebuggerSupport, SingletonCallable, 
> SingletonValue, StackTraceCollector, DebuggerUtils
> 
>
> Key: GEODE-4743
> URL: https://issues.apache.org/jira/browse/GEODE-4743
> Project: Geode
>  Issue Type: Bug
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>
> These classes appear to be remnants of the dark and dreadful time before IDE 
> debuggers.



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

[jira] [Assigned] (GEODE-1798) Dead code in transaction layer confusing

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg reassigned GEODE-1798:
---

Assignee: Patrick Rhomberg

> Dead code in transaction layer confusing
> 
>
> Key: GEODE-1798
> URL: https://issues.apache.org/jira/browse/GEODE-1798
> Project: Geode
>  Issue Type: Improvement
>  Components: transactions
>Reporter: Darrel Schneider
>Assignee: Patrick Rhomberg
>Priority: Major
>
> In geode the transaction code always has a collection of "pendingCallbacks". 
> But the code makes some special calls if this collection is null. This code 
> should be cleaned up to only handle an existing collection.
> Also BucketRegion has an implementation of invokeTXCallbacks that is wrong. 
> If it ever is called it will cause extra events. But it should never be 
> invoked since pendingCallbacks is never null. Instead 
> PartitionedRegion.invokeTXCallbacks will be invoked.
> So the implementation of BucketRegion invokeTXCallbacks should be changed to 
> throw an exception. If tests find any code paths that call it they should be 
> changed to instead call PartitionedRegion.



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

[jira] [Resolved] (GEODE-4704) GatewaySender batch conflation can incorrectly conflate events causing out of order processing

[Barry Oglesby (JIRA)]

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

Barry Oglesby resolved GEODE-4704.
--
   Resolution: Fixed
Fix Version/s: 1.5.0

> GatewaySender batch conflation can incorrectly conflate events causing out of 
> order processing
> --
>
> Key: GEODE-4704
> URL: https://issues.apache.org/jira/browse/GEODE-4704
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Barry Oglesby
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In the current implementation of \{{AbstractGatewaySenderEventProcessor 
> conflate}} can incorrectly conflate two create events on the same key.
> The else clause of the conflate method (meaning the event is not conflatable) 
> assumes there isn't already a event with the same region, key and operation 
> in the map. It just does a put:
> {noformat}
> ConflationKey key = new ConflationKey(gsEvent.getRegion().getFullPath(), 
> gsEvent.getKeyToConflate(), gsEvent.getOperation());
> conflatedEventsMap.put(key, gsEvent);
> {noformat}
> In certain cases, there could already be a create event on the same region, 
> key and operation in the batch, so the previous one gets replaced by the 
> later once which causes the events to be processed out of order.
> These 4 events:
> {noformat}
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=100;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_13964;shadowKey=27709]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=101;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_14024;shadowKey=27822]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=102;bucketId=24];operation=DESTROY;region=/dataStoreRegion;key=Object_13964;shadowKey=27935]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=104;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_14024;shadowKey=28161]
> {noformat}
> Become these 3 events:
> {noformat}
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=100;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_13964;shadowKey=27709]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=104;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_14024;shadowKey=28161]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=102;bucketId=24];operation=DESTROY;region=/dataStoreRegion;key=Object_13964;shadowKey=27935]
> {noformat}
> Notice the shadowKeys and sequenceIds are out of order after the conflation.
> The fix will be to include the shadow key in hashCode and equals in the case 
> where the event is not conflatable.



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

[jira] [Created] (GEODE-4742) OQL operator '/' without surrounding spaces generates syntax error

[Diane Hardman (JIRA)]

Diane Hardman created GEODE-4742:


 Summary: OQL operator '/' without surrounding spaces generates 
syntax error
 Key: GEODE-4742
 URL: https://issues.apache.org/jira/browse/GEODE-4742
 Project: Geode
  Issue Type: Bug
  Components: querying
Reporter: Diane Hardman


The following query will generate a syntax error:

gfsh>query --query="select * from /example-region x where x.salary/2080 > 30"

Result  : false

Message : Query is invalid due for error : 

If I add surrounding spaces, the query is successful:

gfsh>query --query="select * from /example-region x where x.salary / 2080 > 30"

Result : true

Limit  : 100

Rows   : 11

 

          email            | emplNumber | firstName | hoursPerWeek | lastName | 
salary

-- | -- | - |  |  | 
--

frankie.fo...@example.com  | 10010      | Frankie   | 30           | Forth    | 
10

kris.c...@example.com      | 10003      | Kris      | 40           | Call     | 
75000

bertie.b...@example.com    | 10001      | Bertie    | 40           | Bell     | 
8

morgan.min...@example.com  | 10021      | Morgan    | 40           | Minnow   | 
8

ricky.relia...@example.com | 10036      | Ricky     | 40           | Reliable | 
9

ryan.r...@example.com      | 10078      | Ryan      | 40           | Redo     | 
75000

skyler.s...@example.com    | 10091      | Skyler    | 40           | Skip     | 
9

dale.dri...@example.com    | 10006      | Dale      | 40           | Driver   | 
9

pat.p...@example.com       | 10028      | Pat       | 40           | Puts     | 
75000

jessie@example.com     | 10066      | Jessie    | 20           | Jam      | 
8

taylor.t...@example.com    | 10045      | Taylor    | 40           | Tack     | 
10

I tested the other operators ('+', '-', '*', '%') which all seem to work 
correctly with or without surrounding spaces.

 



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

[jira] [Updated] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized

[ASF GitHub Bot (JIRA)]

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

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

> EventSeqNum and versionVector in a region are accessed when they are not yet 
> initialized
> 
>
> Key: GEODE-4738
> URL: https://issues.apache.org/jira/browse/GEODE-4738
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.4.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>  Labels: pull-request-available
>
> It is possible that eventSeqNum and versionVector are accessed when they are  
> not initialized yet. This could cause transaction to fail on the node just 
> start up.
> {noformat}
> Got unexpected exception org.apache.geode.cache.CommitIncompleteException: 
> Incomplete commit of transaction TXId: 
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
>   Caused by the following exceptions:  From member: 
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
>  java.lang.NullPointerException
>   at 
> org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
>   at 
> org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
>   at 
> org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
>   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:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   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$4$1.run(ClusterDistributionManager.java:788)
>   at java.lang.Thread.run(Thread.java:748).
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
>   at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
>   at 
> org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
>   at 
> org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
>   at 
> org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
>   at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
>   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:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
>

[jira] [Commented] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4738:


Commit 9b60ddcfff29bbc5436fc052ba8edd123ccdf29d in geode's branch 
refs/heads/feature/GEODE-4738 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9b60ddc ]

GEODE-4738: move eventSeqNum and versionVector setting in constructors.


> EventSeqNum and versionVector in a region are accessed when they are not yet 
> initialized
> 
>
> Key: GEODE-4738
> URL: https://issues.apache.org/jira/browse/GEODE-4738
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.4.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>
> It is possible that eventSeqNum and versionVector are accessed when they are  
> not initialized yet. This could cause transaction to fail on the node just 
> start up.
> {noformat}
> Got unexpected exception org.apache.geode.cache.CommitIncompleteException: 
> Incomplete commit of transaction TXId: 
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
>   Caused by the following exceptions:  From member: 
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
>  java.lang.NullPointerException
>   at 
> org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
>   at 
> org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
>   at 
> org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
>   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:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   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$4$1.run(ClusterDistributionManager.java:788)
>   at java.lang.Thread.run(Thread.java:748).
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
>   at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
>   at 
> org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
>   at 
> org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
>   at 
> org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
>   at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
>   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:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> 

[jira] [Commented] (GEODE-4722) Code Improvement: Refactor CliUtil

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4722:


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

GEODE-4722: Refactor CliUtil (#1487)

* Reorder methods, grouped by similar functionality.
* Replace .stackTraceToString and .contains with Apache Commons methods.
* Moved getClientIdFromCacheClientProxy to only class that calls it.
* Move arrayToString from CliUtil to sensible StringUtils.  Moved associated 
test.
* Refactor CliUtil methods.

> Code Improvement: Refactor CliUtil
> --
>
> Key: GEODE-4722
> URL: https://issues.apache.org/jira/browse/GEODE-4722
> Project: Geode
>  Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> This class could use some cleaning.  Many methods are unused, some trivially 
> replaced by Apache Commons libraries.



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

[jira] [Commented] (GEODE-4703) DestroyGatewayReceiver may cause hang if executed during RollingUpgrade

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4703:


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

GEODE-4703: Prevent sending RemoveCacheServerProfileMessage to older members 
(#1468)



> DestroyGatewayReceiver may cause hang if executed during RollingUpgrade
> ---
>
> Key: GEODE-4703
> URL: https://issues.apache.org/jira/browse/GEODE-4703
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> GEODE-2667 introduced the ability to destroy gateway receiver -> destroy 
> cache server. However if executed in a cluster with mixed servers (servers 
> prior to 1.5) the distribution of the message causes a DSFID deserialization 
> failure on the older versions, which causes the sender to wait for replies 
> infinitely.



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

[jira] [Updated] (GEODE-4690) ClusterStartupRule causes System properties to 'disappear'

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4690:
--
Fix Version/s: 1.5.0

> ClusterStartupRule causes System properties to 'disappear'
> --
>
> Key: GEODE-4690
> URL: https://issues.apache.org/jira/browse/GEODE-4690
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> The {{ClusterStartupRule}} uses {{DistributedRestoreSystemProperties}} 
> internally to capture and restore system properties. However, the result is 
> that system properties appear to 'disappear' (they are actually captured as 
> defaults) but Geode does not consider default properties when looking for 
> {{gemfire}} or {{geode}} prefixed properties.



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

[jira] [Resolved] (GEODE-4691) Gfsh command Start Locator shows inconsistent behavior with auto-connecting with a Security Manager

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-4691.
---
Resolution: Fixed

> Gfsh command Start Locator shows inconsistent behavior with auto-connecting 
> with a Security Manager
> ---
>
> Key: GEODE-4691
> URL: https://issues.apache.org/jira/browse/GEODE-4691
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh, security
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When starting a locator in gfsh like this
> {code:java}
> start locator --name=locator1{code}
> the default behavior is to auto-connect gfsh to the locator.
> From the gfsh start locator help:
> {code:java}
> connect
> When connect is set to false , Gfsh does not automatically connect to the 
> locator which is started
> using this command.
> Required: false
> Default (if the parameter is specified without value): true
> Default (if the parameter is not specified): true{code}
> When starting the locator with a Security Manager like this
> {code:java}
> start locator --name=locator1 
> --J=-Dgemfire.security-manager=org.apache.geode.examples.SimpleSecurityManager{code}
> The result is that gfsh does not auto connect to the locator. However this is 
> not listed in the help command and is inconsistent in the user expectation.
>  
> Solution and accceptance criteria:
> Update the output of 
> {code:java}
> start locator 
> --J=-Dgemfire.security-manager=org.apache.geode.examples.SimpleSecurityManager{code}
> to indicate that it is not auto-connected. New output:
> {code:java}
> Security Manager is enabled - unable to auto-connect. Please use connect with 
> --user and --password to connect to locator.{code}
> Update gfsh help to correctly list the behavior when the Security Manager is 
> set via the --J parameter
>  
> gfsh should display correct connect help message for
> {code:java}
> help start locator{code}
> when using Security Manager.
> {code:java}
> connect
> When connect is set to false or when locator is started with a security 
> manager using --J=-Dgemfire.security-manager option, Gfsh does not 
> automatically connect to the locator which is started using this command.
> Required: false
> Default (if the parameter is specified without value): true
> Default (if the parameter is not specified): true{code}
>  



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

[jira] [Updated] (GEODE-4691) Gfsh command Start Locator shows inconsistent behavior with auto-connecting with a Security Manager

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4691:
--
Fix Version/s: 1.5.0

> Gfsh command Start Locator shows inconsistent behavior with auto-connecting 
> with a Security Manager
> ---
>
> Key: GEODE-4691
> URL: https://issues.apache.org/jira/browse/GEODE-4691
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh, security
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When starting a locator in gfsh like this
> {code:java}
> start locator --name=locator1{code}
> the default behavior is to auto-connect gfsh to the locator.
> From the gfsh start locator help:
> {code:java}
> connect
> When connect is set to false , Gfsh does not automatically connect to the 
> locator which is started
> using this command.
> Required: false
> Default (if the parameter is specified without value): true
> Default (if the parameter is not specified): true{code}
> When starting the locator with a Security Manager like this
> {code:java}
> start locator --name=locator1 
> --J=-Dgemfire.security-manager=org.apache.geode.examples.SimpleSecurityManager{code}
> The result is that gfsh does not auto connect to the locator. However this is 
> not listed in the help command and is inconsistent in the user expectation.
>  
> Solution and accceptance criteria:
> Update the output of 
> {code:java}
> start locator 
> --J=-Dgemfire.security-manager=org.apache.geode.examples.SimpleSecurityManager{code}
> to indicate that it is not auto-connected. New output:
> {code:java}
> Security Manager is enabled - unable to auto-connect. Please use connect with 
> --user and --password to connect to locator.{code}
> Update gfsh help to correctly list the behavior when the Security Manager is 
> set via the --J parameter
>  
> gfsh should display correct connect help message for
> {code:java}
> help start locator{code}
> when using Security Manager.
> {code:java}
> connect
> When connect is set to false or when locator is started with a security 
> manager using --J=-Dgemfire.security-manager option, Gfsh does not 
> automatically connect to the locator which is started using this command.
> Required: false
> Default (if the parameter is specified without value): true
> Default (if the parameter is not specified): true{code}
>  



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

[jira] [Resolved] (GEODE-2149) Queries shouldn't allow access to reflection API

[Dan Smith (JIRA)]

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

Dan Smith resolved GEODE-2149.
--
   Resolution: Duplicate
Fix Version/s: 1.3.0

> Queries shouldn't allow access to reflection API
> 
>
> Key: GEODE-2149
> URL: https://issues.apache.org/jira/browse/GEODE-2149
> Project: Geode
>  Issue Type: Bug
>Reporter: Galen O'Sullivan
>Priority: Major
> Fix For: 1.3.0
>
>
> Currently, it is possible to run GFSH queries like:
> {code}
> query --query="select a.class from /region1 a"
> Result : true
> startCount : 0
> endCount   : 20
> Rows   : 1
>   
> protectionDomain  
>  | modifiers | interface | array | primitive |   superclass   
> |  componentType   |   name   | annotation | synthetic |  
>  classLoader|   typeParameters   |   genericSuperclass|   
>   package | interfaces | 
> genericInterfaces  | enclosingMethod  |   enclosingConstructor   |
>   enclosingClass  | simpleName | typeName |  canonicalName   | 
> anonymousClass | localClass | memberClass |  classes   |   fields 
>   |  methods   |constructors|  declaredClasses   |   
> declaredFields   |  declaredMethods   | declaredConstructors | enum  |
> annotations | declaredAnnotations |
> annotatedSuperclass | annotatedInterfaces
> 
>  | - | - | - | - | -- | 
>  |  | -- | - | 
>  | -- | -- | 
> --- | 
> -- | -- |  | 
>  |  | -- | 
>  |  | -- | -- | 
> --- | -- | -- | -- | 
> -- | -- | -- | 
> -- |  | - | -- | 
> --- | 
> -- | 
> ---
> ProtectionDomain  null
>  null
>  
>  java.security.Permissions@2c1fc586 (
>  ("java.security.AllPermission" "" "")
> )
>  | 17| false | false | false | class java.lang.Object | 
> org.json.JSONObject.Null | java.lang.String | false  | false | 
> org.json.JSONObject.Null | org.json.JSONArray | class java.lang.Object | 
> package java.lang, Java Platform API Specification, version 1.8 | 
> org.json.JSONArray | org.json.JSONArray | org.json.JSONObject.Null | 
> org.json.JSONObject.Null | org.json.JSONObject.Null | String | 
> java.lang.String | java.lang.String | false  | false  | false 
>   | org.json.JSONArray | org.json.JSONArray | org.json.JSONArray | 
> org.json.JSONArray | org.json.JSONArray | org.json.JSONArray | 
> org.json.JSONArray | org.json.JSONArray   | false | org.json.JSONArray | 
> org.json.JSONArray  | 
> sun.reflect.annotation.AnnotatedTypeFactory$AnnotatedTypeBaseImpl@7cad0747 | 
> org.json.JSONArray
> NEXT_STEP_NAME : END
> {code}
> Methods and properties can be chained to get queries like the following, 
> which seems to expose information about the running JVM:
> {code}
> query --query="select a.class.interfaces[0].package from /region1 a"
> Result : true
> startCount : 0
> endCount   : 20
> Rows   : 1
>  name   |annotations | declaredAnnotations | sealed |   
> specificationTitle| specificationVersion | specificationVendor |   
> implementationTitle| implementationVersion | implementationVendor
> --- | -- | --- | -- | 
> --- |  | --- 
> |  | - | 
> java.io | org.json.JSONArray | org.json.JSONArray  | false  | Java Platform 
> API Specification | 1.8  | Oracle Corporation  | Java Runtime 
> Environment | 1.8.0_111 | Oracle Corporation
> NEXT_STEP_NAME : END
> {code}
> I haven't found a way to make a real security hole out of this, because as 
> far as I can tell, I can't call functions on objects I can access, and it's 
> generally harder to travel 

[jira] [Commented] (GEODE-4402) Log exceptions to server log

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4402:


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

GEODE-4402: Add logging where exceptions would be thrown or caught. (#1452)

* GEODE-4402: Add logging where exceptions would be thrown or caught.

* GEODE-4402: Address review comments.

* GEODE-4402: Add another ignore exception.

* GEODE-4402: Fix spotless.

* Adding log messages that were lost on the merge commit


> Log exceptions to server log
> 
>
> Key: GEODE-4402
> URL: https://issues.apache.org/jira/browse/GEODE-4402
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When the new protocol handles an exception, it should write the exception to 
> the server log (even if it only sends back an error to the client) -- this 
> will help in debugging efforts.
> All exceptions handled by the new protocol should be logged to the server log.



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

[jira] [Commented] (GEODE-4402) Log exceptions to server log

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4402:


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

GEODE-4402: Add logging where exceptions would be thrown or caught. (#1452)

* GEODE-4402: Add logging where exceptions would be thrown or caught.

* GEODE-4402: Address review comments.

* GEODE-4402: Add another ignore exception.

* GEODE-4402: Fix spotless.

* Adding log messages that were lost on the merge commit


> Log exceptions to server log
> 
>
> Key: GEODE-4402
> URL: https://issues.apache.org/jira/browse/GEODE-4402
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When the new protocol handles an exception, it should write the exception to 
> the server log (even if it only sends back an error to the client) -- this 
> will help in debugging efforts.
> All exceptions handled by the new protocol should be logged to the server log.



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

[jira] [Commented] (GEODE-4402) Log exceptions to server log

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4402:


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

GEODE-4402: Add logging where exceptions would be thrown or caught. (#1452)

* GEODE-4402: Add logging where exceptions would be thrown or caught.

* GEODE-4402: Address review comments.

* GEODE-4402: Add another ignore exception.

* GEODE-4402: Fix spotless.

* Adding log messages that were lost on the merge commit


> Log exceptions to server log
> 
>
> Key: GEODE-4402
> URL: https://issues.apache.org/jira/browse/GEODE-4402
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When the new protocol handles an exception, it should write the exception to 
> the server log (even if it only sends back an error to the client) -- this 
> will help in debugging efforts.
> All exceptions handled by the new protocol should be logged to the server log.



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

[jira] [Commented] (GEODE-4402) Log exceptions to server log

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4402:


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

GEODE-4402: Add logging where exceptions would be thrown or caught. (#1452)

* GEODE-4402: Add logging where exceptions would be thrown or caught.

* GEODE-4402: Address review comments.

* GEODE-4402: Add another ignore exception.

* GEODE-4402: Fix spotless.

* Adding log messages that were lost on the merge commit


> Log exceptions to server log
> 
>
> Key: GEODE-4402
> URL: https://issues.apache.org/jira/browse/GEODE-4402
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> When the new protocol handles an exception, it should write the exception to 
> the server log (even if it only sends back an error to the client) -- this 
> will help in debugging efforts.
> All exceptions handled by the new protocol should be logged to the server log.



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

[jira] [Resolved] (GEODE-4690) ClusterStartupRule causes System properties to 'disappear'

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn resolved GEODE-4690.
---
Resolution: Fixed

> ClusterStartupRule causes System properties to 'disappear'
> --
>
> Key: GEODE-4690
> URL: https://issues.apache.org/jira/browse/GEODE-4690
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> The {{ClusterStartupRule}} uses {{DistributedRestoreSystemProperties}} 
> internally to capture and restore system properties. However, the result is 
> that system properties appear to 'disappear' (they are actually captured as 
> defaults) but Geode does not consider default properties when looking for 
> {{gemfire}} or {{geode}} prefixed properties.



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

[jira] [Commented] (GEODE-3875) gfsh command to create jndi binding

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn commented on GEODE-3875:
---

For the tab auto-complete part to display the options, only one option gets 
displayed (it seems the next one in the option list):
{code:java}
gfsh>create jndi-binding --connection-url=hsqldb:hsql://localhost:1701

required --connection-url: This is the JDBC driver connection URL string, for 
example, jdbc:hsqldb:hsql://localhost:1701.; no default value
gfsh>create jndi-binding --connection-url=hsqldb:hsql://localhost:1701 
--blocking-timeout-seconds{code}
While other commands (create region, start locator) show all options available:
{code:java}
gfsh>start server --name=sse --
--J  --assign-buckets 
--bind-address   --cache-xml-file
--classpath  --critical-heap-percentage   
--critical-off-heap-percentage   --dir
--disable-default-server --disable-exit-when-out-of-memory
--enable-time-statistics --eviction-heap-percentage
--eviction-off-heap-percentage   --force  
--group  --groups
--hostname-for-clients   --http-service-bind-address  
--http-service-port  --include-system-classpath
--initial-heap   --jmx-manager-hostname-for-clients   
--locator-wait-time  --locators
--lock-memory--log-level  
--max-connections--max-heap
--max-message-count  --max-threads
--mcast-address  --mcast-port
--memcached-bind-address --memcached-port 
--memcached-protocol --message-time-to-live
--off-heap-memory-size   --password   
--properties-file--rebalance
--redirect-output--redis-bind-address 
--redis-password --redis-port
--security-properties-file   --server-bind-address
--server-port--socket-buffer-size
--spring-xml-location--start-rest-api 
--statistic-archive-file --use-cluster-configuration
--user
{code}
Please update this command to list all option when hitting tab auto-complete.

> gfsh command to create jndi binding
> ---
>
> Key: GEODE-3875
> URL: https://issues.apache.org/jira/browse/GEODE-3875
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>   
>  jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
>   password="changeme" 
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>   
>   
> {code}
> A user should be able to create a datasource using the gfsh command {{create 
> jndi-binding }}
>  Then a datasource will be created with the supplied options and the binding 
> will be created without the user having to restart the existing server(s)
> Please look at Geode's schema for a list of attributes that can be set: 
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]



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

[jira] [Commented] (GEODE-3875) gfsh command to create jndi binding

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn commented on GEODE-3875:
---

When creating a jndi-binding with only locator running and no servers, please 
update the message to state that the JNDI-binding has been created. Currently 
it displays:
{code:java}
No members found. Cluster configuration is updated.{code}
Please display:
{code:java}
No members found. Cluster configuration is updated with jndi-binding 
"name".{code}

> gfsh command to create jndi binding
> ---
>
> Key: GEODE-3875
> URL: https://issues.apache.org/jira/browse/GEODE-3875
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>   
>  jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
>   password="changeme" 
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>   
>   
> {code}
> A user should be able to create a datasource using the gfsh command {{create 
> jndi-binding }}
>  Then a datasource will be created with the supplied options and the binding 
> will be created without the user having to restart the existing server(s)
> Please look at Geode's schema for a list of attributes that can be set: 
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]



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

[jira] [Updated] (GEODE-4733) Replace and remove trivial methods from ObjectUtils

[ASF GitHub Bot (JIRA)]

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

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

> Replace and remove trivial methods from ObjectUtils
> ---
>
> Key: GEODE-4733
> URL: https://issues.apache.org/jira/browse/GEODE-4733
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>
> For instance, {{defaultIfNull(T... values)}} is exclusively called with two 
> input parameters, while the method name and signature makes it unclear that 
> the second value is meant to be the default value if the first parameter is 
> null.
> This method can be cleanly replaced by a ternary {{v1 != null ? v1 : v2}}.



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

[jira] [Updated] (GEODE-4737) User Guide: Describe addition of JSON specs to gfsh commands

[Dave Barnes (JIRA)]

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

Dave Barnes updated GEODE-4737:
---
Description: 
Some new gfsh commands can take a JSON spec. Examples include `alter region 
--entry-idle-time-custom-expiry` and `create region --cache-listener`.

Add a general description of the syntax to the gfsh section of the manual so 
individual command-reference entries can point to a centralized explanation, 
rather than repeating the syntax details each time.

One developer has requested that we state that the JSON parser recognizes 
double quotes as well as single quotes. Some JSON parsers accept only single 
quotes.

  was:
Some new gfsh commands can take a JSON spec. Examples include `alter region 
--entry-idle-time-custom-expiry` and `create region --cache-listener`.

Add a general description of the syntax to the gfsh section of the manual so 
individual command-reference entries can point to a centralized explanation, 
rather than repeating the syntax details each time.

One developer has requested that we state that the JSON parser recognizes 
double quotes as well as single quotes. Some JSON parsers only handle single 
quotes.


> User Guide: Describe addition of JSON specs to gfsh commands
> 
>
> Key: GEODE-4737
> URL: https://issues.apache.org/jira/browse/GEODE-4737
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Dave Barnes
>Priority: Major
>
> Some new gfsh commands can take a JSON spec. Examples include `alter region 
> --entry-idle-time-custom-expiry` and `create region --cache-listener`.
> Add a general description of the syntax to the gfsh section of the manual so 
> individual command-reference entries can point to a centralized explanation, 
> rather than repeating the syntax details each time.
> One developer has requested that we state that the JSON parser recognizes 
> double quotes as well as single quotes. Some JSON parsers accept only single 
> quotes.



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

[jira] [Resolved] (GEODE-4228) Add marker to the fileAndChunkRegion after the lucene index is created

[nabarun (JIRA)]

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

nabarun resolved GEODE-4228.

Resolution: Fixed

> Add marker to the fileAndChunkRegion after the lucene index is created
> --
>
> Key: GEODE-4228
> URL: https://issues.apache.org/jira/browse/GEODE-4228
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: nabarun
>Priority: Major
>
> -- After Lucene is done creating the index, it must put a marker in the 
> FileAndChunkRegion 
> -- This will enable Geode to realize that Lucene Indexes are ready to be used 
> for querying.



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

[jira] [Closed] (GEODE-4228) Add marker to the fileAndChunkRegion after the lucene index is created

[nabarun (JIRA)]

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

nabarun closed GEODE-4228.
--

> Add marker to the fileAndChunkRegion after the lucene index is created
> --
>
> Key: GEODE-4228
> URL: https://issues.apache.org/jira/browse/GEODE-4228
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Reporter: nabarun
>Priority: Major
>
> -- After Lucene is done creating the index, it must put a marker in the 
> FileAndChunkRegion 
> -- This will enable Geode to realize that Lucene Indexes are ready to be used 
> for querying.



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

[jira] [Commented] (GEODE-4341) Geode Native C# Example (cache creation, pooling, basic put/get/remove)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4341:


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

GEODE-4341: Fix missing line in README.md


> Geode Native C# Example (cache creation, pooling, basic put/get/remove)
> ---
>
> Key: GEODE-4341
> URL: https://issues.apache.org/jira/browse/GEODE-4341
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4341) Geode Native C# Example (cache creation, pooling, basic put/get/remove)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4341:


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

GEODE-4341: Added rename to README


> Geode Native C# Example (cache creation, pooling, basic put/get/remove)
> ---
>
> Key: GEODE-4341
> URL: https://issues.apache.org/jira/browse/GEODE-4341
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4341) Geode Native C# Example (cache creation, pooling, basic put/get/remove)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4341:


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

GEODE-4341: Added startserver and stopserver scripts


> Geode Native C# Example (cache creation, pooling, basic put/get/remove)
> ---
>
> Key: GEODE-4341
> URL: https://issues.apache.org/jira/browse/GEODE-4341
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4341) Geode Native C# Example (cache creation, pooling, basic put/get/remove)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4341:


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

GEODE-4341: Set new location for locator and server

Signed-off-by: Ivan Godwin 


> Geode Native C# Example (cache creation, pooling, basic put/get/remove)
> ---
>
> Key: GEODE-4341
> URL: https://issues.apache.org/jira/browse/GEODE-4341
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4341) Geode Native C# Example (cache creation, pooling, basic put/get/remove)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4341:


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

GEODE-4341: Working example of PutGetRemove


> Geode Native C# Example (cache creation, pooling, basic put/get/remove)
> ---
>
> Key: GEODE-4341
> URL: https://issues.apache.org/jira/browse/GEODE-4341
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized

[Eric Shu (JIRA)]

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

Eric Shu updated GEODE-4738:

Affects Version/s: 1.4.0

> EventSeqNum and versionVector in a region are accessed when they are not yet 
> initialized
> 
>
> Key: GEODE-4738
> URL: https://issues.apache.org/jira/browse/GEODE-4738
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.4.0
>Reporter: Eric Shu
>Priority: Major
>
> It is possible that eventSeqNum and versionVector are accessed when they are  
> not initialized yet. This could cause transaction to fail on the node just 
> start up.
> {noformat}
> Got unexpected exception org.apache.geode.cache.CommitIncompleteException: 
> Incomplete commit of transaction TXId: 
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
>   Caused by the following exceptions:  From member: 
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
>  java.lang.NullPointerException
>   at 
> org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
>   at 
> org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
>   at 
> org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
>   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:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   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$4$1.run(ClusterDistributionManager.java:788)
>   at java.lang.Thread.run(Thread.java:748).
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
>   at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
>   at 
> org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
>   at 
> org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
>   at 
> org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
>   at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
>   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:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
>   at 
> 

[jira] [Commented] (GEODE-4341) Geode Native C# Example (cache creation, pooling, basic put/get/remove)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4341:


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

GEODE-4341: Added cmake files for examples


> Geode Native C# Example (cache creation, pooling, basic put/get/remove)
> ---
>
> Key: GEODE-4341
> URL: https://issues.apache.org/jira/browse/GEODE-4341
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (GEODE-2685) request that ParitionedRegion getStatistics be a supported operation

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-2685:
-
Labels: starter storage_2  (was: storage_2)

> request that ParitionedRegion getStatistics be a supported operation
> 
>
> Key: GEODE-2685
> URL: https://issues.apache.org/jira/browse/GEODE-2685
> Project: Geode
>  Issue Type: Improvement
>  Components: regions
>Reporter: Darrel Schneider
>Priority: Major
>  Labels: starter, storage_2
>
> The current implementation of PartitionedRegion getStatistics always throws 
> UnsupportedOperationException.
> It would be nice for this operation to be supported.
> I think the statistics it returns could be a snapshot of the state of the 
> local buckets in the PR at the time getStatistics is called. This could be 
> implemented by iterating over the local internal BucketRegions and asking 
> them for their statistics. For a PR accessor (no local buckets) the only stat 
> that is needed is misses since you have no local buckets and every operation 
> is a miss.



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

[jira] [Commented] (GEODE-3813) Region registerInterest API usage of type parameters is broken

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-3813:


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

GEODE-3813: Improved and fixed formatting in javaDoc for deprecated behavior 
(#1500)



> Region registerInterest API usage of type parameters is broken
> --
>
> Key: GEODE-3813
> URL: https://issues.apache.org/jira/browse/GEODE-3813
> Project: Geode
>  Issue Type: Bug
>  Components: client queues, docs
>Reporter: Kirk Lund
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> The registerInterest API works for single key registration but is broken for 
> all other types of registration if the Region is declared with type 
> parameters:
> Single key (works):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1);
> {noformat}
> ALL_KEYS token is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest("ALL_KEYS");
> {noformat}
> List of keys is broken (fails to compile):
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> List listOfKeys = new ArrayList<>();
> listOfKeys.add(1);
> listOfKeys.add(2);
> region.registerInterest(listOfKeys);
> {noformat}
> When this ticket is fixed and the API is updated, we should consider adding 
> support for var args:
> {noformat}
> Region region = clientRegionFactory.create(regionName);
> region.registerInterest(1, 2, 3);
> {noformat}



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

[jira] [Updated] (GEODE-3137) Replace all time values internally with std::chrono types

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-3137:
-
Labels: starter  (was: )

> Replace all time values internally with std::chrono types
> -
>
> Key: GEODE-3137
> URL: https://issues.apache.org/jira/browse/GEODE-3137
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>  Labels: starter
>
> Remove ambiguity of time values by using 
> [{{std::chrono}}|http://en.cppreference.com/w/cpp/chrono] types used 
> internally. 



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

[jira] [Assigned] (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 reassigned GEODE-4685:


Assignee: Udo Kohlmeyer

> 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
>
> Replace with the solution from GEODE-4679



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

[jira] [Assigned] (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 reassigned GEODE-4679:


Assignee: Udo Kohlmeyer

> 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
>
> +*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] [Assigned] (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 reassigned GEODE-4679:


Assignee: (was: Udo Kohlmeyer)

> 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
>Priority: Major
>
> +*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] [Created] (GEODE-4737) User Guide: Describe addition of JSON specs to gfsh commands

[Dave Barnes (JIRA)]

Dave Barnes created GEODE-4737:
--

 Summary: User Guide: Describe addition of JSON specs to gfsh 
commands
 Key: GEODE-4737
 URL: https://issues.apache.org/jira/browse/GEODE-4737
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Dave Barnes


Some new gfsh commands can take a JSON spec. Examples include `alter region 
--entry-idle-time-custom-expiry` and `create region --cache-listener`.

Add a general description of the syntax to the gfsh section of the manual so 
individual command-reference entries can point to a centralized explanation, 
rather than repeating the syntax details each time.

One developer has requested that we state that the JSON parser recognizes 
double quotes as well as single quotes. Some JSON parsers only handle single 
quotes.



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

[jira] [Created] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized

[Eric Shu (JIRA)]

Eric Shu created GEODE-4738:
---

 Summary: EventSeqNum and versionVector in a region are accessed 
when they are not yet initialized
 Key: GEODE-4738
 URL: https://issues.apache.org/jira/browse/GEODE-4738
 Project: Geode
  Issue Type: Bug
  Components: regions
Reporter: Eric Shu


It is possible that eventSeqNum and versionVector are accessed when they are  
not initialized yet. This could cause transaction to fail on the node just 
start up.

{noformat}
Got unexpected exception org.apache.geode.cache.CommitIncompleteException: 
Incomplete commit of transaction TXId: 
rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
  Caused by the following exceptions:  From member: 
rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
 java.lang.NullPointerException
at 
org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
at 
org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
at 
org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
at 
org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
at 
org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
at 
org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
at 
org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
at 
org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
at 
org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
at 
org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
at 
org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
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:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
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$4$1.run(ClusterDistributionManager.java:788)
at java.lang.Thread.run(Thread.java:748).
at 
org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
at 
org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
at 
org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
at 
org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
at 
org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
at 
org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
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:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
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$6$1.run(ClusterDistributionManager.java:862)
at java.lang.Thread.run(Thread.java:748)
{noformat}

And 
{noformat}
Got unexpected exception org.apache.geode.cache.CommitIncompleteException: 
Incomplete commit of transaction TXId: 
r02-s02(edgegemfire2_r02-s02_10305:10305:loner):36970:e226a1a8:edgegemfire2_r02-s02_10305:11669.
  Caused by the following exceptions:  From member: 

[jira] [Commented] (GEODE-4737) User Guide: Describe addition of JSON specs to gfsh commands

[Dave Barnes (JIRA)]

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

Dave Barnes commented on GEODE-4737:


Example from the gfsh `create region --jndi-binding` command showing multiple 
JSON specs:

--datasource-config-properties=\{'name':'name1','type':'type1','value':'value1'},\{'name':'name2','type':'type2','value':'value2'}"

 

> User Guide: Describe addition of JSON specs to gfsh commands
> 
>
> Key: GEODE-4737
> URL: https://issues.apache.org/jira/browse/GEODE-4737
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Dave Barnes
>Priority: Major
>
> Some new gfsh commands can take a JSON spec. Examples include `alter region 
> --entry-idle-time-custom-expiry` and `create region --cache-listener`.
> Add a general description of the syntax to the gfsh section of the manual so 
> individual command-reference entries can point to a centralized explanation, 
> rather than repeating the syntax details each time.
> One developer has requested that we state that the JSON parser recognizes 
> double quotes as well as single quotes. Some JSON parsers accept only single 
> quotes.



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

[jira] [Reopened] (GEODE-3915) supply arguments over gfsh while initializing Declarable

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller reopened GEODE-3915:

  Assignee: Karen Smoler Miller

Reopening ticket, as the documentation has not been completed.

> supply arguments over gfsh while initializing Declarable
> 
>
> Key: GEODE-3915
> URL: https://issues.apache.org/jira/browse/GEODE-3915
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> User implementations of the Declarable interface may want to pass in 
> arguments while the class is being initialized. We should provide ability to 
> pass these arguments from gfsh. 



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

[jira] [Updated] (GEODE-4144) CI failure: org.apache.geode.internal.cache.ha.PutAllDUnitTest > testPutAll FAILED

[Diane Hardman (JIRA)]

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

Diane Hardman updated GEODE-4144:
-
Fix Version/s: 1.4.0

> CI failure: org.apache.geode.internal.cache.ha.PutAllDUnitTest > testPutAll 
> FAILED
> --
>
> Key: GEODE-4144
> URL: https://issues.apache.org/jira/browse/GEODE-4144
> Project: Geode
>  Issue Type: Bug
>  Components: client queues
>Affects Versions: 1.4.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.4.0
>
> Attachments: geode-4144.logs
>
>
> {noformat}
> org.apache.geode.internal.cache.ha.PutAllDUnitTest > testPutAll FAILED
> java.lang.AssertionError: expected: 
> 

[jira] [Updated] (GEODE-1383) Please add gemfire,heap, xml configuration information to start of every log file

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-1383:
-
Labels: LogBanner starter  (was: LogBanner)

> Please add gemfire,heap, xml configuration information to start of every log 
> file
> -
>
> Key: GEODE-1383
> URL: https://issues.apache.org/jira/browse/GEODE-1383
> Project: Geode
>  Issue Type: Improvement
>  Components: logging
>Reporter: Jens Deppe
>Priority: Major
>  Labels: LogBanner, starter
>
> We often have situations where we have difficulty establishing the 
> configuration or JVM startup arguments, or XML configuration without multiple 
> interactions with the customer, even when they've provided logs. When the 
> customer has rolled over enough, and we overwrite the "parent" first log, we 
> then lose all of that detail from startup that often proves very helpful.
> If it would be easy to incorporate this startup configuration information 
> into the beginning of each log file as we rollover, we would always have it 
> and be able to be more productive working on tickets and improve customer 
> satisfaction.



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

[jira] [Updated] (GEODE-1383) Please add gemfire,heap, xml configuration information to start of every log file

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-1383:
-
Description: 
We often have situations where we have difficulty establishing the 
configuration or JVM startup arguments, or XML configuration without multiple 
interactions with the customer, even when they've provided logs. When the 
customer has rolled over enough, and we overwrite the "parent" first log, we 
then lose all of that detail from startup that often proves very helpful.

If it would be easy to incorporate this startup configuration information into 
the beginning of each log file as we rollover, we would always have it and be 
able to be more productive debugging prod issues and ultimately have happier 
users.

  was:
We often have situations where we have difficulty establishing the 
configuration or JVM startup arguments, or XML configuration without multiple 
interactions with the customer, even when they've provided logs. When the 
customer has rolled over enough, and we overwrite the "parent" first log, we 
then lose all of that detail from startup that often proves very helpful.

If it would be easy to incorporate this startup configuration information into 
the beginning of each log file as we rollover, we would always have it and be 
able to be more productive working on tickets and improve customer satisfaction.


> Please add gemfire,heap, xml configuration information to start of every log 
> file
> -
>
> Key: GEODE-1383
> URL: https://issues.apache.org/jira/browse/GEODE-1383
> Project: Geode
>  Issue Type: Improvement
>  Components: logging
>Reporter: Jens Deppe
>Priority: Major
>  Labels: LogBanner, starter
>
> We often have situations where we have difficulty establishing the 
> configuration or JVM startup arguments, or XML configuration without multiple 
> interactions with the customer, even when they've provided logs. When the 
> customer has rolled over enough, and we overwrite the "parent" first log, we 
> then lose all of that detail from startup that often proves very helpful.
> If it would be easy to incorporate this startup configuration information 
> into the beginning of each log file as we rollover, we would always have it 
> and be able to be more productive debugging prod issues and ultimately have 
> happier users.



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

[jira] [Updated] (GEODE-3835) DistributedSystemBridgeJUnitTest should use TemporaryFolder

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-3835:
-
Labels: starter  (was: )

> DistributedSystemBridgeJUnitTest should use TemporaryFolder
> ---
>
> Key: GEODE-3835
> URL: https://issues.apache.org/jira/browse/GEODE-3835
> Project: Geode
>  Issue Type: Improvement
>  Components: jmx, management, tests
>Reporter: Kirk Lund
>Priority: Major
>  Labels: starter
>
> DistributedSystemBridgeJUnitTest should use TemporaryFolder instead of "/tmp".
> [separated DistributedSystemBridgeJUnitTest from GEODE-1338]



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

[jira] [Commented] (GEODE-4341) Geode Native C# Example (cache creation, pooling, basic put/get/remove)

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4341:


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

GEODE-4341: Incorporate PR feedback


> Geode Native C# Example (cache creation, pooling, basic put/get/remove)
> ---
>
> Key: GEODE-4341
> URL: https://issues.apache.org/jira/browse/GEODE-4341
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  Remaining Estimate: 0h
>




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

[jira] [Assigned] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized

[Eric Shu (JIRA)]

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

Eric Shu reassigned GEODE-4738:
---

Assignee: Eric Shu

> EventSeqNum and versionVector in a region are accessed when they are not yet 
> initialized
> 
>
> Key: GEODE-4738
> URL: https://issues.apache.org/jira/browse/GEODE-4738
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.4.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
>
> It is possible that eventSeqNum and versionVector are accessed when they are  
> not initialized yet. This could cause transaction to fail on the node just 
> start up.
> {noformat}
> Got unexpected exception org.apache.geode.cache.CommitIncompleteException: 
> Incomplete commit of transaction TXId: 
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
>   Caused by the following exceptions:  From member: 
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
>  java.lang.NullPointerException
>   at 
> org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
>   at 
> org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
>   at 
> org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
>   at 
> org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
>   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:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   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$4$1.run(ClusterDistributionManager.java:788)
>   at java.lang.Thread.run(Thread.java:748).
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
>   at 
> org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
>   at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
>   at 
> org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
>   at 
> org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
>   at 
> org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
>   at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
>   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:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
>   at 
> 

[jira] [Created] (GEODE-4739) Null reference exception when using CLI reflection serializer and default constructor is missing

[Ryan McMahon (JIRA)]

Ryan McMahon created GEODE-4739:
---

 Summary: Null reference exception when using CLI reflection 
serializer and default constructor is missing
 Key: GEODE-4739
 URL: https://issues.apache.org/jira/browse/GEODE-4739
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Ryan McMahon


When using reflection based auto serialization and the CLI Geode Native client, 
it is required that any domain objects implement default constructors.  If a 
default constructor isn't implemented, then serialization fails ungracefully 
with a null reference exception.  Better error handling for this case should be 
added.

Steps to reproduce:
 # Open the PdxAutoSerializer example in the examples packaged with geode-native
 # Remove the default constructor from the Order class
 # Run the example and observe the null reference exception

Acceptance criteria:

A test should be written which captures the same steps to reproduce described 
above. Better error handling which indicates the root of the issue should be 
implemented, rather than throwing a null reference exception.



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

[jira] [Resolved] (GEODE-4327) OQL Support for Modulus & Other Arithmetic Operators

[Karen Smoler Miller (JIRA)]

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

Karen Smoler Miller resolved GEODE-4327.

   Resolution: Fixed
Fix Version/s: 1.5.0

> OQL Support for Modulus & Other Arithmetic Operators
> 
>
> Key: GEODE-4327
> URL: https://issues.apache.org/jira/browse/GEODE-4327
> Project: Geode
>  Issue Type: Improvement
>  Components: docs, querying
>Reporter: Jason Huynh
>Assignee: Karen Smoler Miller
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> It would be nice to be able to do 'mod', '%', '+', '-', '/', '*' in a query 
> and have the corresponding arithmetic/mod calculation be evaluated in the 
> query.
>  
> simple example:
> "Select * from /region r where r.id % 12 = 1"
> or
> "Select * from /region r where r.age * 10 = 100"



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

[jira] [Updated] (GEODE-3137) Replace all time values internally with std::chrono types

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-3137:
-
Labels:   (was: starter)

> Replace all time values internally with std::chrono types
> -
>
> Key: GEODE-3137
> URL: https://issues.apache.org/jira/browse/GEODE-3137
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>
> Remove ambiguity of time values by using 
> [{{std::chrono}}|http://en.cppreference.com/w/cpp/chrono] types used 
> internally. 



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

[jira] [Updated] (GEODE-4740) CI Failure: LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats

[Jason Huynh (JIRA)]

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

Jason Huynh updated GEODE-4740:
---
Summary: CI Failure: 
LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats  (was: 
CI Failure: 
LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats.testPartitionedSerialPropagationToTwoWanSites)

> CI Failure: 
> LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats
> ---
>
> Key: GEODE-4740
> URL: https://issues.apache.org/jira/browse/GEODE-4740
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Jason Huynh
>Priority: Major
>
> This test failed in a recent concourse run
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest > 
> listIndexWithStatsShouldReturnCorrectStats FAILED
>  java.lang.AssertionError: 
>  Expecting:
>  <["3"]>
>  to contain exactly in any order:
>  <["2"]>
>  elements not found:
>  <["2"]>
>  and elements not expected:
>  <["3"]>
>  at 
> org.apache.geode.test.junit.assertions.CommandResultAssert.tableHasColumnWithExactValuesInAnyOrder(CommandResultAssert.java:179)
>  at 
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats(LuceneIndexCommandsDUnitTest.java:154)



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

[jira] [Updated] (GEODE-4740) CI Failure: LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats

[Jason Huynh (JIRA)]

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

Jason Huynh updated GEODE-4740:
---
Summary: CI Failure: 
LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats  (was: 
CI Failure: 
LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats.testPartitionedSerialPropagationToTwoWanSites)

> CI Failure: 
> LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats
> ---
>
> Key: GEODE-4740
> URL: https://issues.apache.org/jira/browse/GEODE-4740
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Jason Huynh
>Priority: Major
>
> This test failed in a recent concourse run
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest > 
> listIndexWithStatsShouldReturnCorrectStats FAILED
>  java.lang.AssertionError: 
>  Expecting:
>  <["3"]>
>  to contain exactly in any order:
>  <["2"]>
>  elements not found:
>  <["2"]>
>  and elements not expected:
>  <["3"]>
>  at 
> org.apache.geode.test.junit.assertions.CommandResultAssert.tableHasColumnWithExactValuesInAnyOrder(CommandResultAssert.java:179)
>  at 
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats(LuceneIndexCommandsDUnitTest.java:154)



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

[jira] [Updated] (GEODE-4559) Remove singleton calls from product code in org.apache.geode.cache.util

[Darrel Schneider (JIRA)]

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

Darrel Schneider updated GEODE-4559:

Component/s: docs

> Remove singleton calls from product code in org.apache.geode.cache.util
> ---
>
> Key: GEODE-4559
> URL: https://issues.apache.org/jira/browse/GEODE-4559
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, regions
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> These product classes in org.apache.geode.cache.util invoke singleton getters.
> GemFireCacheImpl.getInstance():
> * AutoBalancer$GeodeCacheFacade



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

[jira] [Updated] (GEODE-4729) Rearrange Geode Native Quickstarts and Examples

[ASF GitHub Bot (JIRA)]

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

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

> Rearrange Geode Native Quickstarts and Examples
> ---
>
> Key: GEODE-4729
> URL: https://issues.apache.org/jira/browse/GEODE-4729
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>
> The goal of this ticket is to restructure the Geode Native docs to make the 
> addition of examples easier.



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

[jira] [Updated] (GEODE-4541) Remove singleton calls from regions product code in org.apache.geode.internal.cache

[ASF GitHub Bot (JIRA)]

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

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

> Remove singleton calls from regions product code in 
> org.apache.geode.internal.cache
> ---
>
> Key: GEODE-4541
> URL: https://issues.apache.org/jira/browse/GEODE-4541
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>
> These regions product classes in org.apache.geode.internal.cache invoke 
> singleton getters.
> GemFireCacheImpl.getInstance():
> * CacheServerLauncher
> * EntryEventImpl
> * GemFireCacheImpl
> * DistributedPutAllOperation
> InternalDistributedSystem.getAnyInstance():
> * EventStateHelper
> * GemFireCacheImpl
> * PartitionAttributesImpl
> * PartitionedRegionHelper



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

[jira] [Commented] (GEODE-4541) Remove singleton calls from regions product code in org.apache.geode.internal.cache

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4541:


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

GEODE-4541: remove singleton calls (#1463)

* removed getAnyInstance call from PartitionedRegionHelper

* removed getInstance call from CacheServerLauncher

* removed getAnyInstance call from EventStateHelper

* DistributedPutAllOperation no longer calls GemFireCacheImpl.getInstance

* EntryEventImpl no longer calls getInstance.
This fix requires that when an EntryEventImpl is deserialized
that setRegion will be called on it before the values are accessed.
Also encapsulated the "region" field and got rid of getLocalRegion
in favor of getRegion.


> Remove singleton calls from regions product code in 
> org.apache.geode.internal.cache
> ---
>
> Key: GEODE-4541
> URL: https://issues.apache.org/jira/browse/GEODE-4541
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> These regions product classes in org.apache.geode.internal.cache invoke 
> singleton getters.
> GemFireCacheImpl.getInstance():
> * CacheServerLauncher
> * EntryEventImpl
> * GemFireCacheImpl
> * DistributedPutAllOperation
> InternalDistributedSystem.getAnyInstance():
> * EventStateHelper
> * GemFireCacheImpl
> * PartitionAttributesImpl
> * PartitionedRegionHelper



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

[jira] [Created] (GEODE-4740) CI Failure: LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats.testPartitionedSerialPropagationToTwoWanSites

[Jason Huynh (JIRA)]

Jason Huynh created GEODE-4740:
--

 Summary: CI Failure: 
LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats.testPartitionedSerialPropagationToTwoWanSites
 Key: GEODE-4740
 URL: https://issues.apache.org/jira/browse/GEODE-4740
 Project: Geode
  Issue Type: Bug
  Components: lucene
Reporter: Jason Huynh


This test failed in a recent concourse run
org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest > 
listIndexWithStatsShouldReturnCorrectStats FAILED
 java.lang.AssertionError: 
 Expecting:
 <["3"]>
 to contain exactly in any order:
 <["2"]>
 elements not found:
 <["2"]>
 and elements not expected:
 <["3"]>
 at 
org.apache.geode.test.junit.assertions.CommandResultAssert.tableHasColumnWithExactValuesInAnyOrder(CommandResultAssert.java:179)
 at 
org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats(LuceneIndexCommandsDUnitTest.java:154)



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

[jira] [Updated] (GEODE-4740) CI Failure: LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats.testPartitionedSerialPropagationToTwoWanSites

[Jason Huynh (JIRA)]

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

Jason Huynh updated GEODE-4740:
---
Summary: CI Failure: 
LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats.testPartitionedSerialPropagationToTwoWanSites
  (was: CI Failure: 
LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats)

> CI Failure: 
> LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats.testPartitionedSerialPropagationToTwoWanSites
> -
>
> Key: GEODE-4740
> URL: https://issues.apache.org/jira/browse/GEODE-4740
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Jason Huynh
>Priority: Major
>
> This test failed in a recent concourse run
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest > 
> listIndexWithStatsShouldReturnCorrectStats FAILED
>  java.lang.AssertionError: 
>  Expecting:
>  <["3"]>
>  to contain exactly in any order:
>  <["2"]>
>  elements not found:
>  <["2"]>
>  and elements not expected:
>  <["3"]>
>  at 
> org.apache.geode.test.junit.assertions.CommandResultAssert.tableHasColumnWithExactValuesInAnyOrder(CommandResultAssert.java:179)
>  at 
> org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.listIndexWithStatsShouldReturnCorrectStats(LuceneIndexCommandsDUnitTest.java:154)



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

[jira] [Commented] (GEODE-4407) Separate incremental backup logic from backup task and oplog

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4407:


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

GEODE-4407 (#1499): Refactoring incremental backup logic

Removed dependency on target location while fetching backup files from source.


> Separate incremental backup logic from backup task and oplog
> 
>
> Key: GEODE-4407
> URL: https://issues.apache.org/jira/browse/GEODE-4407
> Project: Geode
>  Issue Type: Sub-task
>  Components: persistence
>Reporter: Nick Reich
>Assignee: Anilkumar Gingade
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Incremental backup examines the oplog from current destination to the 
> previously backed up destination to generate oplogs to be backed up. This 
> logic is present in both backup task and oplog. We need to separate this out 
> so the logic can be used for different backup destinations. 



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

[jira] [Commented] (GEODE-4559) Remove singleton calls from product code in org.apache.geode.cache.util

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4559:


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

GEODE-4559: pass the Cache to a Declarable (#1422)

* Declarable now has a default method named "initialize(Cache, Properties)".
This allows a Declarable to know the cache that created it.
Deprecated Declarable.init(Properties).
Note that for backwards compatibility, the product calls
both these methods. Also the two Declarables that the product
implements, AutoBalancer and ReflectionBasedAutoSerializer,
implement both these methods but after the first calls subsequent
calls of init or initialize will be noops.

* initialize on ReflectionBasedAutoSerializer now call setRegionService with 
the cache.
init and initialize can now be called multiple times and each time the 
properties will
be set again. This is for backwards compatibility.

* The AutoBalancer no longer looks up the static cache.
but instead of given one by the product calling setCache
during initialization.



> Remove singleton calls from product code in org.apache.geode.cache.util
> ---
>
> Key: GEODE-4559
> URL: https://issues.apache.org/jira/browse/GEODE-4559
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> These product classes in org.apache.geode.cache.util invoke singleton getters.
> GemFireCacheImpl.getInstance():
> * AutoBalancer$GeodeCacheFacade



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

[jira] [Resolved] (GEODE-4559) Remove singleton calls from product code in org.apache.geode.cache.util

[Darrel Schneider (JIRA)]

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

Darrel Schneider resolved GEODE-4559.
-
   Resolution: Fixed
Fix Version/s: 1.5.0

> Remove singleton calls from product code in org.apache.geode.cache.util
> ---
>
> Key: GEODE-4559
> URL: https://issues.apache.org/jira/browse/GEODE-4559
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, regions
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> These product classes in org.apache.geode.cache.util invoke singleton getters.
> GemFireCacheImpl.getInstance():
> * AutoBalancer$GeodeCacheFacade



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

[jira] [Commented] (GEODE-4559) Remove singleton calls from product code in org.apache.geode.cache.util

[Darrel Schneider (JIRA)]

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

Darrel Schneider commented on GEODE-4559:
-

Note that for geode 1.5 a new external api Declarable.initialize(Cache, 
Properties) has been added.

Also Declarable.init(Properties) has been deprecated.

 

> Remove singleton calls from product code in org.apache.geode.cache.util
> ---
>
> Key: GEODE-4559
> URL: https://issues.apache.org/jira/browse/GEODE-4559
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, regions
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> These product classes in org.apache.geode.cache.util invoke singleton getters.
> GemFireCacheImpl.getInstance():
> * AutoBalancer$GeodeCacheFacade



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

[jira] [Assigned] (GEODE-4741) DUnit launches ChildVMs with hardcoded heap size

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-4741:


Assignee: Kirk Lund

> DUnit launches ChildVMs with hardcoded heap size
> 
>
> Key: GEODE-4741
> URL: https://issues.apache.org/jira/browse/GEODE-4741
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> This can result in tests such as PRQueryDUnitTest.testQueryResultsFromMembers 
> passing in gradle but failing in an IDE such as IntelliJ. 
> Adding -Xmx to the JUnit configuration for 
> PRQueryDUnitTest.testQueryResultsFromMembers in IntelliJ causes this test to 
> start passing. Moving the code in testQueryResultsFromMembers from the JUnit 
> controller JVM to a ChildVM also causes the test to start passing (because 
> all 3 datastores are sized equivalently instead of having one be different 
> size).
> The better solution is to change DUnit's ProcessManager to launch ChildVMs 
> with the same heap size as the main JUnit controller JVM. Then they will 
> always be equivalent in all environments.



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

[jira] [Created] (GEODE-4741) DUnit launches ChildVMs with hardcoded heap size

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-4741:


 Summary: DUnit launches ChildVMs with hardcoded heap size
 Key: GEODE-4741
 URL: https://issues.apache.org/jira/browse/GEODE-4741
 Project: Geode
  Issue Type: Bug
  Components: tests
Reporter: Kirk Lund


This can result in tests such as PRQueryDUnitTest.testQueryResultsFromMembers 
passing in gradle but failing in an IDE such as IntelliJ. 

Adding -Xmx to the JUnit configuration for 
PRQueryDUnitTest.testQueryResultsFromMembers in IntelliJ causes this test to 
start passing. Moving the code in testQueryResultsFromMembers from the JUnit 
controller JVM to a ChildVM also causes the test to start passing (because all 
3 datastores are sized equivalently instead of having one be different size).

The better solution is to change DUnit's ProcessManager to launch ChildVMs with 
the same heap size as the main JUnit controller JVM. Then they will always be 
equivalent in all environments.



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

[jira] [Resolved] (GEODE-4541) Remove singleton calls from regions product code in org.apache.geode.internal.cache

[Darrel Schneider (JIRA)]

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

Darrel Schneider resolved GEODE-4541.
-
   Resolution: Fixed
Fix Version/s: 1.5.0

> Remove singleton calls from regions product code in 
> org.apache.geode.internal.cache
> ---
>
> Key: GEODE-4541
> URL: https://issues.apache.org/jira/browse/GEODE-4541
> Project: Geode
>  Issue Type: Sub-task
>  Components: regions
>Reporter: Kirk Lund
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> These regions product classes in org.apache.geode.internal.cache invoke 
> singleton getters.
> GemFireCacheImpl.getInstance():
> * CacheServerLauncher
> * EntryEventImpl
> * GemFireCacheImpl
> * DistributedPutAllOperation
> InternalDistributedSystem.getAnyInstance():
> * EventStateHelper
> * GemFireCacheImpl
> * PartitionAttributesImpl
> * PartitionedRegionHelper



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

[jira] [Updated] (GEODE-2321) Pulse application works incorrectly in some locales

[Vadim Lotarev (JIRA)]

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

Vadim Lotarev updated GEODE-2321:
-
Component/s: (was: docs)

> Pulse application works incorrectly in some locales
> ---
>
> Key: GEODE-2321
> URL: https://issues.apache.org/jira/browse/GEODE-2321
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Vadim Lotarev
>Priority: Major
>
> I noticed that Pulse application is not able to show cluster view in my 
> locale. Doing some investigations I revealed the warning messages like: 
> {{serviceException \[for service ClusterDetails\] = For input string: "2,71"}}
> {{serviceException \[for service ClusterMembersRGraph\] = For input string: 
> "58,27"}}
> I guess the reason is in parsing numeric values - it looks like coma "," is 
> hard coded in Pulse as a decimal separator; so if your region settings have 
> separate value (like mine - ".") you'll get such a problem. The workaround 
> could be to force usage of US region starting locator: 
> {{--J=-Duser.region=US}}.



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

[jira] [Commented] (GEODE-2321) Pulse application works incorrectly in some locales

[Vadim Lotarev (JIRA)]

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

Vadim Lotarev commented on GEODE-2321:
--

I don't agree that this is a documentation issue. These number are not entering 
by users but used internally. So, users from other locales are just not able to 
run pulse. This is definitely a bug.

> Pulse application works incorrectly in some locales
> ---
>
> Key: GEODE-2321
> URL: https://issues.apache.org/jira/browse/GEODE-2321
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Vadim Lotarev
>Priority: Major
>
> I noticed that Pulse application is not able to show cluster view in my 
> locale. Doing some investigations I revealed the warning messages like: 
> {{serviceException \[for service ClusterDetails\] = For input string: "2,71"}}
> {{serviceException \[for service ClusterMembersRGraph\] = For input string: 
> "58,27"}}
> I guess the reason is in parsing numeric values - it looks like coma "," is 
> hard coded in Pulse as a decimal separator; so if your region settings have 
> separate value (like mine - ".") you'll get such a problem. The workaround 
> could be to force usage of US region starting locator: 
> {{--J=-Duser.region=US}}.



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

[jira] [Commented] (GEODE-4721) Being invoked within JTA Region.values() does return empty collection

[Vadim Lotarev (JIRA)]

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

Vadim Lotarev commented on GEODE-4721:
--

Geode 1.4. It would require some time to prepare a test case. I could try but 
probably your developers will do that faster. Just create some region, put some 
value here and invoke values() within JTA.

> Being invoked within JTA Region.values() does return empty collection
> -
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
>  Issue Type: Bug
>  Components: regions, transactions
>Reporter: Vadim Lotarev
>Priority: Major
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other 
> operations returns data, for example this workaround works (though less 
> efficient): {{region.getAll(region.keySet()).values()}}, also 
> {{Region.size()}} returns correct value.



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

[jira] [Commented] (GEODE-4691) Gfsh command Start Locator shows inconsistent behavior with auto-connecting with a Security Manager

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4691:


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

GEODE-4691: Gfsh command Start Locator shows inconsistent behavior wi… (#1478)

...th auto-connecting with a Security Manager


> Gfsh command Start Locator shows inconsistent behavior with auto-connecting 
> with a Security Manager
> ---
>
> Key: GEODE-4691
> URL: https://issues.apache.org/jira/browse/GEODE-4691
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh, security
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When starting a locator in gfsh like this
> {code:java}
> start locator --name=locator1{code}
> the default behavior is to auto-connect gfsh to the locator.
> From the gfsh start locator help:
> {code:java}
> connect
> When connect is set to false , Gfsh does not automatically connect to the 
> locator which is started
> using this command.
> Required: false
> Default (if the parameter is specified without value): true
> Default (if the parameter is not specified): true{code}
> When starting the locator with a Security Manager like this
> {code:java}
> start locator --name=locator1 
> --J=-Dgemfire.security-manager=org.apache.geode.examples.SimpleSecurityManager{code}
> The result is that gfsh does not auto connect to the locator. However this is 
> not listed in the help command and is inconsistent in the user expectation.
>  
> Solution and accceptance criteria:
> Update the output of 
> {code:java}
> start locator 
> --J=-Dgemfire.security-manager=org.apache.geode.examples.SimpleSecurityManager{code}
> to indicate that it is not auto-connected. New output:
> {code:java}
> Security Manager is enabled - unable to auto-connect. Please use connect with 
> --user and --password to connect to locator.{code}
> Update gfsh help to correctly list the behavior when the Security Manager is 
> set via the --J parameter
>  
> gfsh should display correct connect help message for
> {code:java}
> help start locator{code}
> when using Security Manager.
> {code:java}
> connect
> When connect is set to false or when locator is started with a security 
> manager using --J=-Dgemfire.security-manager option, Gfsh does not 
> automatically connect to the locator which is started using this command.
> Required: false
> Default (if the parameter is specified without value): true
> Default (if the parameter is not specified): true{code}
>  



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

[jira] [Commented] (GEODE-3875) gfsh command to create jndi binding

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-3875:


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

GEODE-3875: gfsh command to create jndi binding (#1475)



> gfsh command to create jndi binding
> ---
>
> Key: GEODE-3875
> URL: https://issues.apache.org/jira/browse/GEODE-3875
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h
>  Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>   
>  jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
>   password="changeme" 
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>   
>   
> {code}
> A user should be able to create a datasource using the gfsh command {{create 
> jndi-binding }}
>  Then a datasource will be created with the supplied options and the binding 
> will be created without the user having to restart the existing server(s)
> Please look at Geode's schema for a list of attributes that can be set: 
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]



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