[jira] [Updated] (GEODE-4967) Cleanup compiler warnings with Clang

[ASF GitHub Bot (JIRA)]

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

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

> Cleanup compiler warnings with Clang
> 
>
> Key: GEODE-4967
> URL: https://issues.apache.org/jira/browse/GEODE-4967
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Major
>  Labels: pull-request-available
>
> Too many compiler warnings makes for lots of noise when compiling. Warnings 
> lead to errors. Make all warnings errors.



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

[jira] [Reopened] (GEODE-4968) Parameterize Find Module for Examples

[Michael Oleske (JIRA)]

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

Michael Oleske reopened GEODE-4968:
---

> Parameterize Find Module for Examples
> -
>
> Key: GEODE-4968
> URL: https://issues.apache.org/jira/browse/GEODE-4968
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Ryan McMahon
>Assignee: Michael Oleske
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Adds the ability to override the product name in Find cmake script for 
> examples.



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

[jira] [Commented] (GEODE-4957) The key used in a putIfAbsent call that returns null may not be the one in the RegionEntry

[Darrel Schneider (JIRA)]

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

Darrel Schneider commented on GEODE-4957:
-

I think this is what is happening:

Thread 1 does putIfAbsent(k1, v1) and adds a new RegionEntry to the map with k1 
and value REMOVE_PHASE1

Thread 2 does putIfAbsent(k2, v2) and finds the RegionEntry that Thread 1 added 
because k1.equals(k2). It syncs this RegionEntry and sets the value to v2. It 
returns null because the old value was REMOVE_PHASE1.

Thread 1 then syncs the RegionEntry and finds the value is v2 so putIfAbsent 
does not put but returns v2.

So when this happens the key will be k1 even though Thread 2 is the one that 
did the putIfAbsent.

I think we can fix this by having AbstractRegionMap.basicPut when it is doing a 
create (ifNew==true) check to see if the key has the same identity (==) as the 
one on the region entry. If it is not identical then it can change the key on 
the RegionEntry. Since the key has the same hash I think this is safe.

 Another solution is to treat REMOVE_PHASE1 with a non-identical key like we do 
REMOVE_PHASE2. In that case we remove the old RegionEntry and then create a new 
one and do a retry. The problem with this is two or more threads could keep 
doing this to each other, spinning around possibly forever.

The best solution would be to refactor getOrCreateRegionEntry so that when it 
adds a new RegionEntry that is REMOVE_PHASE1 it is already synced. The code 
used to be this way but was changed when the getOrCreateRegionEntry method was 
introduced. If we could do it like this then this bug goes away because no 
other thread can change the RegionEntry we add with REMOVE_PHASE1 so it will 
already have our key in it.

 

> The key used in a putIfAbsent call that returns null may not be the one in 
> the RegionEntry
> --
>
> Key: GEODE-4957
> URL: https://issues.apache.org/jira/browse/GEODE-4957
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Barry Oglesby
>Priority: Major
>
> With simultaneous putIfAbsent calls, sometimes the thread that returns null 
> is not the thread that actually creates the RegionEntry.
> Below is some logging that shows this behavior.
> Thread-77 returns null from the putIfAbsent call (which means there was no 
> previous value). 1 ms before Thread-77's putEntryIfAbsent call, Thread-9 
> creates the RegionEntry. You can see that because not only is oldRe=null for 
> Thread-9, but also the event's key (eventKey) and entry's key (reKey) are 
> identical. But Thread-9 returns a non-null old value.
> {noformat}
> Thread-77 at 1522187267493: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@6a8119a0 
> (key=ComplexKey[identity=1682369152; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); 
> oldRe=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null)
> Thread-77 at 1522187267493: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=1682369152; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-77 at 1522187267500: LocalRegion.putIfAbsent returning null
> {noformat}
> {noformat}
> Thread-9 at 1522187267492: AbstractRegionMap.putEntryIfAbsent 
> regionEntry=VersionedStatsDiskLRURegionEntryHeapObjectKey@1aac7604 
> (key=ComplexKey[identity=342592289; key=key]; rawValue=REMOVED_PHASE1; 
> version=\{v0; rv0; ds=0; time=0};member=null); oldRe=null
> Thread-9 at 1522187267495: AbstractRegionMap.basicPut 
> eventKey=ComplexKey[identity=342592289; key=key]; 
> reKey=ComplexKey[identity=342592289; key=key]
> Thread-9 at 1522187267504: LocalRegion.putIfAbsent returning v1
> {noformat}



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

[jira] [Updated] (GEODE-4993) GatewaySender connection stats are captured but not stored

[Barry Oglesby (JIRA)]

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

Barry Oglesby updated GEODE-4993:
-
Attachment: geode-4993.diff

> GatewaySender connection stats are captured but not stored
> --
>
> Key: GEODE-4993
> URL: https://issues.apache.org/jira/browse/GEODE-4993
> Project: Geode
>  Issue Type: Improvement
>  Components: wan
>Reporter: Barry Oglesby
>Priority: Major
> Attachments: geode-4993.diff
>
>
> The GatewaySender connection stats are captured but not stored in the gfs 
> file. a GatewaySenderEventRemoteDispatcher causes ConnectionStats to be 
> created when its connection is created. For some reason, these are saved to a 
> DummyStatisticsFactory (which causes them not to be saved):
> {noformat}
> if (pool.getGatewaySender() != null) {
>  stats = new ConnectionStats(new DummyStatisticsFactory(), statName, 
> this.poolStats);
> }
> {noformat}
> If something like this were done instead, then those statistics would be 
> saved in the gfs file under an appropriate name:
> {noformat}
> if (pool.getGatewaySender() != null) {
>  String statName = pool.getGatewaySender().getId() + "-" + 
> location.toString();
>  stats = new ConnectionStats(ds, "GatewaySender", statName, this.poolStats);
> }
> public ConnectionStats(StatisticsFactory factory, String prefix, String name,
>  PoolStats poolStats/* , GatewayStats gatewayStats */) {
>  this.stats = factory.createAtomicStatistics(type, prefix + "Stats-" + name);
>  this.sendStats = factory.createAtomicStatistics(sendType, prefix + 
> "SendStats-" + name);
>  this.poolStats = poolStats;
> }
> {noformat}
> The kinds of stats tracked by the ConnectionStats include:
> - connections
> - sentBytes
> - receivedBytes
> Here is a stack trace showing where the ConnectionStats are created:
> {noformat}
> java.lang.Exception: Stack trace
>  at java.lang.Thread.dumpStack(Thread.java:1329)
>  at 
> org.apache.geode.cache.client.internal.ConnectionStats.(ConnectionStats.java:1716)
>  at 
> org.apache.geode.cache.client.internal.EndpointManagerImpl.getStats(EndpointManagerImpl.java:225)
>  at 
> org.apache.geode.cache.client.internal.EndpointManagerImpl.referenceEndpoint(EndpointManagerImpl.java:75)
>  at 
> org.apache.geode.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:124)
>  at 
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:137)
>  at 
> org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:259)
>  at 
> org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:242)
>  at 
> org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:910)
>  at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:398)
>  at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:331)
>  at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher._dispatchBatch(GatewaySenderEventRemoteDispatcher.java:208)
>  at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.dispatchBatch(GatewaySenderEventRemoteDispatcher.java:157)
>  at 
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:610)
>  at 
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1051)
> {noformat}
>  



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

[jira] [Created] (GEODE-4993) GatewaySender connection stats are captured but not stored

[Barry Oglesby (JIRA)]

Barry Oglesby created GEODE-4993:


 Summary: GatewaySender connection stats are captured but not stored
 Key: GEODE-4993
 URL: https://issues.apache.org/jira/browse/GEODE-4993
 Project: Geode
  Issue Type: Improvement
  Components: wan
Reporter: Barry Oglesby


The GatewaySender connection stats are captured but not stored in the gfs file. 
a GatewaySenderEventRemoteDispatcher causes ConnectionStats to be created when 
its connection is created. For some reason, these are saved to a 
DummyStatisticsFactory (which causes them not to be saved):
{noformat}
if (pool.getGatewaySender() != null) {
 stats = new ConnectionStats(new DummyStatisticsFactory(), statName, 
this.poolStats);
}
{noformat}
If something like this were done instead, then those statistics would be saved 
in the gfs file under an appropriate name:
{noformat}
if (pool.getGatewaySender() != null) {
 String statName = pool.getGatewaySender().getId() + "-" + location.toString();
 stats = new ConnectionStats(ds, "GatewaySender", statName, this.poolStats);
}

public ConnectionStats(StatisticsFactory factory, String prefix, String name,
 PoolStats poolStats/* , GatewayStats gatewayStats */) {
 this.stats = factory.createAtomicStatistics(type, prefix + "Stats-" + name);
 this.sendStats = factory.createAtomicStatistics(sendType, prefix + 
"SendStats-" + name);
 this.poolStats = poolStats;
}
{noformat}
The kinds of stats tracked by the ConnectionStats include:

- connections
- sentBytes
- receivedBytes

Here is a stack trace showing where the ConnectionStats are created:
{noformat}
java.lang.Exception: Stack trace
 at java.lang.Thread.dumpStack(Thread.java:1329)
 at 
org.apache.geode.cache.client.internal.ConnectionStats.(ConnectionStats.java:1716)
 at 
org.apache.geode.cache.client.internal.EndpointManagerImpl.getStats(EndpointManagerImpl.java:225)
 at 
org.apache.geode.cache.client.internal.EndpointManagerImpl.referenceEndpoint(EndpointManagerImpl.java:75)
 at 
org.apache.geode.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:124)
 at 
org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:137)
 at 
org.apache.geode.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:259)
 at 
org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:242)
 at 
org.apache.geode.cache.client.internal.PoolImpl.acquireConnection(PoolImpl.java:910)
 at 
org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.initializeConnection(GatewaySenderEventRemoteDispatcher.java:398)
 at 
org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.getConnection(GatewaySenderEventRemoteDispatcher.java:331)
 at 
org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher._dispatchBatch(GatewaySenderEventRemoteDispatcher.java:208)
 at 
org.apache.geode.internal.cache.wan.GatewaySenderEventRemoteDispatcher.dispatchBatch(GatewaySenderEventRemoteDispatcher.java:157)
 at 
org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:610)
 at 
org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1051)
{noformat}

 



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

[jira] [Commented] (GEODE-4972) Move VersionManager into geode-old-versions module

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4972:


Commit 31b51bddb66f7605bbe70b30b648b3d78a797604 in geode's branch 
refs/heads/develop from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=31b51bd ]

GEODE-4972: Move VersionManager to geode-old-versions module (#1703)

- This will facilitate other modules being able to use VersionManager;
  specifically geode-junit.

> Move VersionManager into geode-old-versions module
> --
>
> Key: GEODE-4972
> URL: https://issues.apache.org/jira/browse/GEODE-4972
> Project: Geode
>  Issue Type: Task
>  Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> This is a precursor to GEODE-4971



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

[jira] [Created] (GEODE-4992) port multi cache tests from clicache to cppcache

[Ernest Burghardt (JIRA)]

Ernest Burghardt created GEODE-4992:
---

 Summary: port multi cache tests from clicache to cppcache
 Key: GEODE-4992
 URL: https://issues.apache.org/jira/browse/GEODE-4992
 Project: Geode
  Issue Type: Improvement
  Components: native client
Reporter: Ernest Burghardt


in clicache there are integrationtest2 and test2 - need to port the multi-cache 
tests to cppcache



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

[jira] [Commented] (GEODE-4912) Change DistributedSystem::create to return value type

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4912:


Commit cddcacdb21d9e49546ec8f4082db882522e6608b in geode-native's branch 
refs/heads/develop from M. Oleske
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=cddcacd ]

GEODE-4912: Return value for DistributedSystem::create (#246)



> Change DistributedSystem::create to return value type
> -
>
> Key: GEODE-4912
> URL: https://issues.apache.org/jira/browse/GEODE-4912
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Blake Bender
>Assignee: Blake Bender
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 3h
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4950) Improve spotless -- upgrade version

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4950:


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

Geode-4950 + GEODE-4951: Upgrade spotless version and reduce run time.

* GEODE-4950: Update spotless plugin to newest version.
* GEODE-4951: Allow spotless to skip UP-TO-DATE files.


> Improve spotless -- upgrade version
> ---
>
> Key: GEODE-4950
> URL: https://issues.apache.org/jira/browse/GEODE-4950
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>




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

[jira] [Commented] (GEODE-4951) Improve spotless -- Improve runtime with bump method

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4951:


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

Geode-4950 + GEODE-4951: Upgrade spotless version and reduce run time.

* GEODE-4950: Update spotless plugin to newest version.
* GEODE-4951: Allow spotless to skip UP-TO-DATE files.


> Improve spotless -- Improve runtime with bump method
> 
>
> Key: GEODE-4951
> URL: https://issues.apache.org/jira/browse/GEODE-4951
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4951) Improve spotless -- Improve runtime with bump method

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4951:


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

Geode-4950 + GEODE-4951: Upgrade spotless version and reduce run time.

* GEODE-4950: Update spotless plugin to newest version.
* GEODE-4951: Allow spotless to skip UP-TO-DATE files.


> Improve spotless -- Improve runtime with bump method
> 
>
> Key: GEODE-4951
> URL: https://issues.apache.org/jira/browse/GEODE-4951
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>




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

[jira] [Resolved] (GEODE-4840) CacheLoader that loads PdxInstance requires class to be on classpath if pdx-read-serialized is false

[Darrel Schneider (JIRA)]

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

Darrel Schneider resolved GEODE-4840.
-
   Resolution: Fixed
Fix Version/s: 1.6.0

> CacheLoader that loads PdxInstance requires class to be on classpath if 
> pdx-read-serialized is false
> 
>
> Key: GEODE-4840
> URL: https://issues.apache.org/jira/browse/GEODE-4840
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Affects Versions: 1.5.0
>Reporter: Anilkumar Gingade
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> When remote get invokes the CacheLoader that loads PdxInstance; it tries to 
> deserialize the object if pdx-read-serialized is false (requires pdx domain 
> class to be on classpath): which may not be true in client-server scenario.



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

[jira] [Comment Edited] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database

[Darrel Schneider (JIRA)]

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

Darrel Schneider edited comment on GEODE-4833 at 4/3/18 9:07 PM:
-

It is not NULL but a Character whose value is zero that postgres will not write 
to columns of type text (like CHAR and VARCHAR).

So this last postgres failure that reopened this bug is actually a different 
problem than the original issue.

 

 


was (Author: dschneider):
It is not NULL by a Character whose value is zero that postgres to columns of 
type text (like CHAR and VARCHAR).

 

> JdbcWriter and JdbcAsyncWriter may fail to write null fields to database
> 
>
> Key: GEODE-4833
> URL: https://issues.apache.org/jira/browse/GEODE-4833
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.4.0
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Both JdbcWriter and JdbcAsyncWriter end up calling the JDBC method 
> PreparedStatement.setObject with a value of "null" if the pdx field contains 
> "null".
> This will work with jdbc drivers that support sending "non-typed Null" to the 
> backend database.
> But some drivers do not support this and these puts will fail with a 
> SQLException.
> For portability the jdbc connector should be changed to not pass "null" to 
> setObject without a type.
>  



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

[jira] [Assigned] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database

[Darrel Schneider (JIRA)]

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

Darrel Schneider reassigned GEODE-4833:
---

Assignee: Nick Reich  (was: Darrel Schneider)

> JdbcWriter and JdbcAsyncWriter may fail to write null fields to database
> 
>
> Key: GEODE-4833
> URL: https://issues.apache.org/jira/browse/GEODE-4833
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.4.0
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Both JdbcWriter and JdbcAsyncWriter end up calling the JDBC method 
> PreparedStatement.setObject with a value of "null" if the pdx field contains 
> "null".
> This will work with jdbc drivers that support sending "non-typed Null" to the 
> backend database.
> But some drivers do not support this and these puts will fail with a 
> SQLException.
> For portability the jdbc connector should be changed to not pass "null" to 
> setObject without a type.
>  



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

[jira] [Updated] (GEODE-4991) JDBC connector should not hard code quotes around identifiers in SQL statements

[ASF GitHub Bot (JIRA)]

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

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

> JDBC connector should not hard code quotes around identifiers in SQL 
> statements
> ---
>
> Key: GEODE-4991
> URL: https://issues.apache.org/jira/browse/GEODE-4991
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>
> Currently the JDBC connector has double quotes around all identifiers in SQL 
> statements it creates.
> Instead of always using double quotes, it should instead ask JDBC using 
> java.sql.DatabaseMetaData.getIdentifierQuoteString() what the quote string is 
> and use that.
> For databases that do not support quoting identifiers a space is returned.



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

[jira] [Assigned] (GEODE-4952) Improve spotless -- automatically remove unused imports.

[Patrick Rhomberg (JIRA)]

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

Patrick Rhomberg reassigned GEODE-4952:
---

Assignee: Patrick Rhomberg

> Improve spotless -- automatically remove unused imports.
> 
>
> Key: GEODE-4952
> URL: https://issues.apache.org/jira/browse/GEODE-4952
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (GEODE-4952) Improve spotless -- automatically remove unused imports.

[ASF GitHub Bot (JIRA)]

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

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

> Improve spotless -- automatically remove unused imports.
> 
>
> Key: GEODE-4952
> URL: https://issues.apache.org/jira/browse/GEODE-4952
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>




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

[jira] [Updated] (GEODE-4936) Update version dependency for jackson-databind

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4936:
--
Component/s: pulse

> Update version dependency for jackson-databind
> --
>
> Key: GEODE-4936
> URL: https://issues.apache.org/jira/browse/GEODE-4936
> Project: Geode
>  Issue Type: Bug
>  Components: build, pulse
>Affects Versions: 1.5.0
>Reporter: Kenneth Howe
>Priority: Major
>
> jackson-databind version 2.9.5 fixes an incomplete fix in version 2.9.4



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

[jira] [Updated] (GEODE-4849) Internal REST endpoints in geode-core can be obfuscated by those in geode-web-api

[ASF GitHub Bot (JIRA)]

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

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

> Internal REST endpoints in geode-core can be obfuscated by those in 
> geode-web-api
> -
>
> Key: GEODE-4849
> URL: https://issues.apache.org/jira/browse/GEODE-4849
> Project: Geode
>  Issue Type: Bug
>  Components: rest (dev)
>Reporter: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
>
> For instance, a GET to {{http://localhost:8080/geode/v1/version}} is 
> returning 
> {noformat}
> {
> "cause": "The Region identified by name (version) could not be found!"
> }
> {noformat}
> because it is matching the endpoint in {{PdxBasedCrudController}}:
> {noformat}
>   @RequestMapping(method = RequestMethod.GET, value = "/{region}",
>   produces = MediaType.APPLICATION_JSON_UTF8_VALUE)
> {noformat}
> rather than the intended endpoint in {{ShellCommandsController}}:
> {noformat}
>   @RequestMapping(method = RequestMethod.GET, value = "/version")
> {noformat}
> Similar errors exist for {{/mbean}}, {{/regions}}, {{/indexes}}, and 
> {{/management}}.



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

[jira] [Updated] (GEODE-4991) JDBC connector should not hard code quotes around identifiers in SQL statements

[Darrel Schneider (JIRA)]

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

Darrel Schneider updated GEODE-4991:

Affects Version/s: 1.6.0

> JDBC connector should not hard code quotes around identifiers in SQL 
> statements
> ---
>
> Key: GEODE-4991
> URL: https://issues.apache.org/jira/browse/GEODE-4991
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>
> Currently the JDBC connector has double quotes around all identifiers in SQL 
> statements it creates.
> Instead of always using double quotes, it should instead ask JDBC using 
> java.sql.DatabaseMetaData.getIdentifierQuoteString() what the quote string is 
> and use that.
> For databases that do not support quoting identifiers a space is returned.



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

[jira] [Created] (GEODE-4991) JDBC connector should not hard code quotes around identifiers in SQL statements

[Darrel Schneider (JIRA)]

Darrel Schneider created GEODE-4991:
---

 Summary: JDBC connector should not hard code quotes around 
identifiers in SQL statements
 Key: GEODE-4991
 URL: https://issues.apache.org/jira/browse/GEODE-4991
 Project: Geode
  Issue Type: Bug
  Components: extensions, regions
Reporter: Darrel Schneider


Currently the JDBC connector has double quotes around all identifiers in SQL 
statements it creates.

Instead of always using double quotes, it should instead ask JDBC using 
java.sql.DatabaseMetaData.getIdentifierQuoteString() what the quote string is 
and use that.

For databases that do not support quoting identifiers a space is returned.



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

[jira] [Assigned] (GEODE-4991) JDBC connector should not hard code quotes around identifiers in SQL statements

[Darrel Schneider (JIRA)]

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

Darrel Schneider reassigned GEODE-4991:
---

Assignee: Darrel Schneider

> JDBC connector should not hard code quotes around identifiers in SQL 
> statements
> ---
>
> Key: GEODE-4991
> URL: https://issues.apache.org/jira/browse/GEODE-4991
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>Priority: Major
>
> Currently the JDBC connector has double quotes around all identifiers in SQL 
> statements it creates.
> Instead of always using double quotes, it should instead ask JDBC using 
> java.sql.DatabaseMetaData.getIdentifierQuoteString() what the quote string is 
> and use that.
> For databases that do not support quoting identifiers a space is returned.



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

[jira] [Commented] (GEODE-4920) Alter region does not update PartitionRegionConfig of the region

[Kirk Lund (JIRA)]

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

Kirk Lund commented on GEODE-4920:
--

Also, note that any Region config that is not referenced on 
org.apache.geode.cache.AttributesMutator is not currently wired up for mutation 
at runtime.

For example, if you allow mutation of colocation info in PartitionRegionConfig, 
then that would require further product changes.

> Alter region does not update PartitionRegionConfig of the region
> 
>
> Key: GEODE-4920
> URL: https://issues.apache.org/jira/browse/GEODE-4920
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, regions
>Reporter: nabarun
>Priority: Major
>
> While using the "alter region" gfsh command to update / mutate the region 
> with new attributes like eviction parameters, the new attributes are not 
> updated in the PartitionedRegionConfig.
> This maybe important because PartitionRegionConfig members are used to 
> determine colocation complete, validation of the gatewaySenders etc.
> GEODE-4919 PR has been raised to add the gateways senders to the PR config.
> We need to determine which command parameters of "alter region" command need 
> to be updated to the PRConfig after the region is altered



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

[jira] [Resolved] (GEODE-4968) Parameterize Find Module for Examples

[Michael Oleske (JIRA)]

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

Michael Oleske resolved GEODE-4968.
---
Resolution: Fixed

> Parameterize Find Module for Examples
> -
>
> Key: GEODE-4968
> URL: https://issues.apache.org/jira/browse/GEODE-4968
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Ryan McMahon
>Assignee: Michael Oleske
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Adds the ability to override the product name in Find cmake script for 
> examples.



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

[jira] [Commented] (GEODE-4920) Alter region does not update PartitionRegionConfig of the region

[Darrel Schneider (JIRA)]

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

Darrel Schneider commented on GEODE-4920:
-

It looks to me like the eviction attributes are broken. 
EvictionAttributesMutator lets you change the maximum but this code ignores 
that change when updating the PartitionRegionConfig:
{noformat}
private PartitionRegionConfig getPRConfigWithLatestExpirationAttributes() {
PartitionRegionConfig prConfig = this.prRoot.get(getRegionIdentifier());
return new PartitionRegionConfig(prConfig.getPRId(), prConfig.getFullPath(),
prConfig.getPartitionAttrs(), prConfig.getScope(), 
prConfig.getEvictionAttributes(),
this.getRegionIdleTimeout(), this.getRegionTimeToLive(), 
this.getEntryIdleTimeout(),
this.getEntryTimeToLive(), prConfig.getGatewaySenderIds());
}
{noformat}
Note that this code gets the mutated expiration attributes but rereads the 
eviction attributes from the existing prConfig.
 The PartitionRegionConfig only uses this to log a warning so it is not a huge 
problem:
{noformat}
if (ea.getAction().isLocalDestroy()) {
// LRUHeap doesn't support maximum, but other eviction algos do
if (!ea.getAlgorithm().isLRUHeap() && ea.getMaximum() != prconfEa.getMaximum()) 
{
logger.warn(LocalizedMessage.create(
LocalizedStrings.PartitionedRegion_0_EVICTIONATTRIBUTES_1_DO_NOT_MATCH_WITH_OTHER_2,
new Object[] {pr.getFullPath(), ea, prconfEa}));
}
}
{noformat}

> Alter region does not update PartitionRegionConfig of the region
> 
>
> Key: GEODE-4920
> URL: https://issues.apache.org/jira/browse/GEODE-4920
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, regions
>Reporter: nabarun
>Priority: Major
>
> While using the "alter region" gfsh command to update / mutate the region 
> with new attributes like eviction parameters, the new attributes are not 
> updated in the PartitionedRegionConfig.
> This maybe important because PartitionRegionConfig members are used to 
> determine colocation complete, validation of the gatewaySenders etc.
> GEODE-4919 PR has been raised to add the gateways senders to the PR config.
> We need to determine which command parameters of "alter region" command need 
> to be updated to the PRConfig after the region is altered



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

[jira] [Commented] (GEODE-4867) Query execution time expiration must stop all query execution

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4867:


Commit 132dfc8950fe85f70c71eb0563eefb9f8dcb5f7f in geode's branch 
refs/heads/develop from nabarun
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=132dfc8 ]

GEODE-4867: Unused imports

* Removed unused imports from the previous commit.


> Query execution time expiration must stop all query execution
> -
>
> Key: GEODE-4867
> URL: https://issues.apache.org/jira/browse/GEODE-4867
> Project: Geode
>  Issue Type: Bug
>  Components: querying
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> *+Current behavior+* :
> When the query execution time expires in the QueryMonitor, the isCancelled 
> boolean is set. But  this is used in only once in the 
> executeQueryOnRemoteAndLocalNodes in DefaultQuery but this is checked at the 
> end after the entire query is executed.
> This results in entire query being executed even though the time for query 
> execution had expired.
> *+Solution+* :
> The time expiration flag needs to be checked in a similar fashion as 
> isLowMemory, which is checked in nearly every step of execution of the query 
> hence the query is stopped when the execution time had expired.
> [no checks needed in the index module]



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

[jira] [Resolved] (GEODE-4872) JdbcReader throws serialization exception for byte[] when the field type is Object

[Darrel Schneider (JIRA)]

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

Darrel Schneider resolved GEODE-4872.
-
   Resolution: Fixed
Fix Version/s: 1.6.0

> JdbcReader throws serialization exception for byte[] when the field type is 
> Object
> --
>
> Key: GEODE-4872
> URL: https://issues.apache.org/jira/browse/GEODE-4872
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.4.0
>Reporter: Anilkumar Gingade
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> JdbcReader when creating PdxInstance throws serialization exception for 
> byte[] when its field type is treated as Object. This field is mapped in the 
> table as blob column.
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote 
> server on 10.118.33.196(66546:loner):64576:da7cbe2f: 
> org.apache.geode.pdx.PdxSerializationException: Exception while serializing a 
> PDX field
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:179)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
>     at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
>     at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
>     at 
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
>     at 
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2768)
>     at 
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1490)
>     at 
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1313)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1298)
>     at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
>     at 
> org.apache.geode.connectors.jdbc.JdbcDUnitTest.lambda$clientGetReadsFromDBWithPdxClassName$bb17a952$1(JdbcDUnitTest.java:348)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at hydra.MethExecutor.executeObject(MethExecutor.java:244)
>     at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
>     at sun.rmi.transport.Transport$1.run(Transport.java:200)
>     at sun.rmi.transport.Transport$1.run(Transport.java:197)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
>     at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
>     at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>     at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>     at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.geode.pdx.PdxSerializationException: Exception while 
> serializing a PDX field
>     at 
> org.apache.geode.pdx.internal.PdxOutputStream.writeObject(PdxOutputStream.java:84)
>     at 
> org.apache.geode.pdx.internal.PdxWriterImpl.writeObject(PdxWriterImpl.java:329)
>     at 
> 

[jira] [Updated] (GEODE-4872) JdbcReader throws serialization exception for byte[] when the field type is Object

[Darrel Schneider (JIRA)]

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

Darrel Schneider updated GEODE-4872:

Affects Version/s: (was: 1.6.0)
   1.4.0

> JdbcReader throws serialization exception for byte[] when the field type is 
> Object
> --
>
> Key: GEODE-4872
> URL: https://issues.apache.org/jira/browse/GEODE-4872
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.4.0
>Reporter: Anilkumar Gingade
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> JdbcReader when creating PdxInstance throws serialization exception for 
> byte[] when its field type is treated as Object. This field is mapped in the 
> table as blob column.
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote 
> server on 10.118.33.196(66546:loner):64576:da7cbe2f: 
> org.apache.geode.pdx.PdxSerializationException: Exception while serializing a 
> PDX field
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:179)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
>     at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
>     at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
>     at 
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
>     at 
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2768)
>     at 
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1490)
>     at 
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1313)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1298)
>     at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
>     at 
> org.apache.geode.connectors.jdbc.JdbcDUnitTest.lambda$clientGetReadsFromDBWithPdxClassName$bb17a952$1(JdbcDUnitTest.java:348)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at hydra.MethExecutor.executeObject(MethExecutor.java:244)
>     at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
>     at sun.rmi.transport.Transport$1.run(Transport.java:200)
>     at sun.rmi.transport.Transport$1.run(Transport.java:197)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
>     at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
>     at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>     at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>     at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.geode.pdx.PdxSerializationException: Exception while 
> serializing a PDX field
>     at 
> org.apache.geode.pdx.internal.PdxOutputStream.writeObject(PdxOutputStream.java:84)
>     at 
> org.apache.geode.pdx.internal.PdxWriterImpl.writeObject(PdxWriterImpl.java:329)
>  

[jira] [Commented] (GEODE-4872) JdbcReader throws serialization exception for byte[] when the field type is Object

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4872:


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

GEODE-4872: handle Blob when reading from JDBC (#1692)

When a pdx BYTE_ARRAY or OBJECT field is read and
the column type is BLOB, getBlob is called and
its value is converted to a byte[].


> JdbcReader throws serialization exception for byte[] when the field type is 
> Object
> --
>
> Key: GEODE-4872
> URL: https://issues.apache.org/jira/browse/GEODE-4872
> Project: Geode
>  Issue Type: Bug
>  Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Assignee: Darrel Schneider
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> JdbcReader when creating PdxInstance throws serialization exception for 
> byte[] when its field type is treated as Object. This field is mapped in the 
> table as blob column.
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote 
> server on 10.118.33.196(66546:loner):64576:da7cbe2f: 
> org.apache.geode.pdx.PdxSerializationException: Exception while serializing a 
> PDX field
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:179)
>     at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
>     at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
>     at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
>     at 
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
>     at 
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2768)
>     at 
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1490)
>     at 
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1313)
>     at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1298)
>     at 
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
>     at 
> org.apache.geode.connectors.jdbc.JdbcDUnitTest.lambda$clientGetReadsFromDBWithPdxClassName$bb17a952$1(JdbcDUnitTest.java:348)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at hydra.MethExecutor.executeObject(MethExecutor.java:244)
>     at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
>     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
>     at sun.rmi.transport.Transport$1.run(Transport.java:200)
>     at sun.rmi.transport.Transport$1.run(Transport.java:197)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
>     at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
>     at java.security.AccessController.doPrivileged(Native Method)
>     at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
>     at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>     at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>     at 

[jira] [Commented] (GEODE-3237) Loading cluster configuration from a dir that does not have complete CC will throw NPE

[Sai Boorlagadda (JIRA)]

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

Sai Boorlagadda commented on GEODE-3237:


Modified error messages:

1) he option load-cluster-configuration-from-dir=true is specified but the 
option -cluster-config-dir needs to be set with a directory to the cluster 
config. (removed file at the end)

2) No cluster configuration is found or missing config for certain groups in {0}

> Loading cluster configuration from a dir that does not have complete CC will 
> throw NPE
> --
>
> Key: GEODE-3237
> URL: https://issues.apache.org/jira/browse/GEODE-3237
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, gfsh
>Reporter: Jinmei Liao
>Priority: Major
>
> We should handle the error more gracefully and informatively. Currently if 
> user did the following:
> gfsh> start locator --name=locator
>  gfsh> shutdown --include-lcoator=true
>  gfsh> start locator --name=locator --load-cluster-configuration-from-dir=true
> the console message says "Cluster configuration service has been started, but 
> its not running yet",
>  and there is an NPE in the log:
>  [error 2017/07/18 10:22:38.357 PDT locator  
> tid=0x41] null
>  java.lang.NullPointerException
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.loadSharedConfigurationFromDisk(ClusterConfigurationService.java:618)
>  at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:441)
>  at 
> org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:613)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  at 
> org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:665)
>  at 
> org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:922)
>  at java.lang.Thread.run(Thread.java:745)
> The error message if no directory is specified, should be saying:
> {code:java}
> The option load-cluster-configuration-from-dir=true is specified but the 
> option -cluster-config-dir needs to be set with a directory to the cluster 
> config file.{code}
> The error message if the directory is specified but cluster config file is 
> not found in that directory:
> {code:java}
> No cluster configuration is found in {code}
>  
>  



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

[jira] [Updated] (GEODE-629) Replace use of org.json with Jackson JSON library

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-629:
-
Component/s: gfsh
 configuration

> Replace use of org.json with Jackson JSON library
> -
>
> Key: GEODE-629
> URL: https://issues.apache.org/jira/browse/GEODE-629
> Project: Geode
>  Issue Type: Improvement
>  Components: configuration, gfsh, serialization
>Reporter: Jens Deppe
>Priority: Major
>  Labels: json
> Attachments: json.patch
>
>
> Currently we're using two different JSON libraries; org.json and jackson. We 
> have customized org.json in the module gemfire-json.
> We should try and consolidate on a single JSON library - namely jackson as it 
> is much more capable than org.json.



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

[jira] [Resolved] (GEODE-4983) PluckStacks is no longer detecting idle executors and weeding them out

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt resolved GEODE-4983.
-
   Resolution: Fixed
Fix Version/s: 1.6.0

> PluckStacks is no longer detecting idle executors and weeding them out
> --
>
> Key: GEODE-4983
> URL: https://issues.apache.org/jira/browse/GEODE-4983
> Project: Geode
>  Issue Type: Bug
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Fix For: 1.6.0
>
>
> The PluckStacks utility is supposed to detect idle threads in stack dumps and 
> ignore them but it is no longer doing so.  It failed with java 8 build 161.



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

[jira] [Closed] (GEODE-4983) PluckStacks is no longer detecting idle executors and weeding them out

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt closed GEODE-4983.
---

> PluckStacks is no longer detecting idle executors and weeding them out
> --
>
> Key: GEODE-4983
> URL: https://issues.apache.org/jira/browse/GEODE-4983
> Project: Geode
>  Issue Type: Bug
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
> Fix For: 1.6.0
>
>
> The PluckStacks utility is supposed to detect idle threads in stack dumps and 
> ignore them but it is no longer doing so.  It failed with java 8 build 161.



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

[jira] [Commented] (GEODE-4968) Parameterize Find Module for Examples

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4968:


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

GEODE-4968: Parameterized product names in Find module (#253)

- Add example generation to top-level CMakeLists.txt
- Only include dotnet on windows

Signed-off-by: Ryan McMahon 
Signed-off-by: Michael Oleske 


> Parameterize Find Module for Examples
> -
>
> Key: GEODE-4968
> URL: https://issues.apache.org/jira/browse/GEODE-4968
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Ryan McMahon
>Assignee: Michael Oleske
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Adds the ability to override the product name in Find cmake script for 
> examples.



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

[jira] [Commented] (GEODE-4983) PluckStacks is no longer detecting idle executors and weeding them out

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4983:


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

GEODE-4983 PluckStacks is no longer detecting idle executors and weeding them 
out

fixing check for idle executors


> PluckStacks is no longer detecting idle executors and weeding them out
> --
>
> Key: GEODE-4983
> URL: https://issues.apache.org/jira/browse/GEODE-4983
> Project: Geode
>  Issue Type: Bug
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>
> The PluckStacks utility is supposed to detect idle threads in stack dumps and 
> ignore them but it is no longer doing so.  It failed with java 8 build 161.



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

[jira] [Commented] (GEODE-4981) CI failure: SSLConfigurationFactoryJUnitTest.getNonSSLConfiguration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4981:


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

GEODE-4981 CI failure: SSLConfigurationFactoryJUnitTest.getNonSSLConfiguration

fixing another test that configures SSL and leaves state behind


> CI failure: SSLConfigurationFactoryJUnitTest.getNonSSLConfiguration
> ---
>
> Key: GEODE-4981
> URL: https://issues.apache.org/jira/browse/GEODE-4981
> Project: Geode
>  Issue Type: Bug
>  Components: messaging
>Reporter: Bruce Schuchardt
>Priority: Major
> Fix For: 1.6.0
>
>
> This test seems to have been infected by some other test leaving SSL state 
> behind.  For distributed tests we clean up SSL configuration state after a 
> test is run but for non-distributed tests this isn't done.
> {noformat}
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> org.apache.geode.internal.net.SSLConfigurationFactoryJUnitTest.assertSSLConfig(SSLConfigurationFactoryJUnitTest.java:310)
>   at 
> org.apache.geode.internal.net.SSLConfigurationFactoryJUnitTest.getNonSSLConfiguration(SSLConfigurationFactoryJUnitTest.java:73)
> {noformat}
> We probably need to sweep all of the SSL unit tests and make sure they're 
> properly cleaning up after themselves by calling SocketCreatorFactory.close().



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

[jira] [Resolved] (GEODE-4979) Incorrect description in documentation of ResourcePermission in OQL

[Dave Barnes (JIRA)]

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

Dave Barnes resolved GEODE-4979.

   Resolution: Fixed
Fix Version/s: 1.6.0

Thank you to Masaki Yamakawa for the fix!

> Incorrect description in documentation of ResourcePermission in OQL
> ---
>
> Key: GEODE-4979
> URL: https://issues.apache.org/jira/browse/GEODE-4979
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Masaki Yamakawa
>Assignee: Dave Barnes
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In the OQL Authorization, the description in documentation of 
> ResourcePermission is incorrect. It is 'DATA:READ' in the description, but 
> 'DATA:READ:RegionName' is actually.
> The document page is as follows:
> [https://geode.apache.org/docs/guide/14/managing/security/implementing_authorization.html]
>  



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

[jira] [Assigned] (GEODE-4979) Incorrect description in documentation of ResourcePermission in OQL

[Dave Barnes (JIRA)]

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

Dave Barnes reassigned GEODE-4979:
--

Assignee: Dave Barnes

> Incorrect description in documentation of ResourcePermission in OQL
> ---
>
> Key: GEODE-4979
> URL: https://issues.apache.org/jira/browse/GEODE-4979
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Masaki Yamakawa
>Assignee: Dave Barnes
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In the OQL Authorization, the description in documentation of 
> ResourcePermission is incorrect. It is 'DATA:READ' in the description, but 
> 'DATA:READ:RegionName' is actually.
> The document page is as follows:
> [https://geode.apache.org/docs/guide/14/managing/security/implementing_authorization.html]
>  



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

[jira] [Updated] (GEODE-4919) Alter regions must update PRconfig

[nabarun (JIRA)]

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

nabarun updated GEODE-4919:
---
Component/s: (was: gfsh)
 wan

> Alter regions must update PRconfig
> --
>
> Key: GEODE-4919
> URL: https://issues.apache.org/jira/browse/GEODE-4919
> Project: Geode
>  Issue Type: Bug
>  Components: wan
>Reporter: nabarun
>Assignee: nabarun
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Altering the region to add parallel gateway sender to non colocated regions 
> must fail.
> The check is done using the PartitionRegionConfig but we never update it 
> after altering the region to add the gateway sender.



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

[jira] [Commented] (GEODE-4979) Incorrect description in documentation of ResourcePermission in OQL

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4979:


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

GEODE-4979: Incorrect description in docs of ResourcePermission in OQL


> Incorrect description in documentation of ResourcePermission in OQL
> ---
>
> Key: GEODE-4979
> URL: https://issues.apache.org/jira/browse/GEODE-4979
> Project: Geode
>  Issue Type: Bug
>  Components: docs
>Reporter: Masaki Yamakawa
>Priority: Minor
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In the OQL Authorization, the description in documentation of 
> ResourcePermission is incorrect. It is 'DATA:READ' in the description, but 
> 'DATA:READ:RegionName' is actually.
> The document page is as follows:
> [https://geode.apache.org/docs/guide/14/managing/security/implementing_authorization.html]
>  



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

[jira] [Resolved] (GEODE-4893) import cluster configuration command shuts down the existing servers

[Barbara Pruijn (JIRA)]

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

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

> import cluster configuration command shuts down the existing servers
> 
>
> Key: GEODE-4893
> URL: https://issues.apache.org/jira/browse/GEODE-4893
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, docs, gfsh
>Affects Versions: 1.4.0
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> `import cluster-configuration --zip-file-name=...` in a cluster which has 
> locator and servers (Server has no application regions defined yet). the 
> server is shutdown without any message in the logs as to why the server was 
> shutdown. Gfsh says import was successful.
> On manual restart of the server I can see that the config was actually 
> imported successfully.
>  
> We had added the feature that user can do an {{import cluster-configuration 
> --zip-file-name=...}} without shutting down the vanilla servers, and the 
> servers cache would just bounce. We should
>  # make sure the server's cache is completely empty. i.e. not just without 
> regions, should not have any other entities like async event queue, disk 
> stores etc.
>  # make sure after the import, the servers are not shut down.
> We have ClusterConfigImportDUnitTest.testImportWithRunningServer to test this 
> scenaio, in the Dunit environment, the servers are not shut down after the 
> import. We will need to write a similar acceptance tests to expose the 
> problem.



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

[jira] [Updated] (GEODE-4986) Refactor GMSEncrypt

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt updated GEODE-4986:

Summary: Refactor GMSEncrypt  (was: Refactor GEMSEncrypt)

> Refactor GMSEncrypt
> ---
>
> Key: GEODE-4986
> URL: https://issues.apache.org/jira/browse/GEODE-4986
> Project: Geode
>  Issue Type: Bug
>Reporter: Brian Rowe
>Assignee: Brian Rowe
>Priority: Major
>
> This class and surrounding code is a mess with confusing, poorly named, 
> redundant, and simply unused pieces of code.



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

[jira] [Resolved] (GEODE-4981) CI failure: SSLConfigurationFactoryJUnitTest.getNonSSLConfiguration

[Bruce Schuchardt (JIRA)]

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

Bruce Schuchardt resolved GEODE-4981.
-
   Resolution: Fixed
Fix Version/s: 1.6.0

> CI failure: SSLConfigurationFactoryJUnitTest.getNonSSLConfiguration
> ---
>
> Key: GEODE-4981
> URL: https://issues.apache.org/jira/browse/GEODE-4981
> Project: Geode
>  Issue Type: Bug
>  Components: messaging
>Reporter: Bruce Schuchardt
>Priority: Major
> Fix For: 1.6.0
>
>
> This test seems to have been infected by some other test leaving SSL state 
> behind.  For distributed tests we clean up SSL configuration state after a 
> test is run but for non-distributed tests this isn't done.
> {noformat}
> java.lang.AssertionError: expected: but was:
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:834)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:144)
>   at 
> org.apache.geode.internal.net.SSLConfigurationFactoryJUnitTest.assertSSLConfig(SSLConfigurationFactoryJUnitTest.java:310)
>   at 
> org.apache.geode.internal.net.SSLConfigurationFactoryJUnitTest.getNonSSLConfiguration(SSLConfigurationFactoryJUnitTest.java:73)
> {noformat}
> We probably need to sweep all of the SSL unit tests and make sure they're 
> properly cleaning up after themselves by calling SocketCreatorFactory.close().



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

[jira] [Assigned] (GEODE-4386) gfsh command to describe jndi binding

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn reassigned GEODE-4386:
-

Assignee: Joey McAllister

> gfsh command to describe jndi binding
> -
>
> Key: GEODE-4386
> URL: https://issues.apache.org/jira/browse/GEODE-4386
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Joey McAllister
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  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 describe a datasource using the gfsh command 
> {{describe jndi-binding --name=jndi-binding-name}}
>  Then list the particular datasource with attributes and don't display the 
> password.
>  The
> {code:java}
> describe  jndi-binding{code} command should be able to describe any 
> jndi-binding that is output by the {code} list jndi-binding{code} command. 
> The output of the {code} describe jndi-binding{code} needs to indicate 
> whether a binding is active or not.
> 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] [Resolved] (GEODE-4386) gfsh command to describe jndi binding

[Barbara Pruijn (JIRA)]

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

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

> gfsh command to describe jndi binding
> -
>
> Key: GEODE-4386
> URL: https://issues.apache.org/jira/browse/GEODE-4386
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Assignee: Joey McAllister
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  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 describe a datasource using the gfsh command 
> {{describe jndi-binding --name=jndi-binding-name}}
>  Then list the particular datasource with attributes and don't display the 
> password.
>  The
> {code:java}
> describe  jndi-binding{code} command should be able to describe any 
> jndi-binding that is output by the {code} list jndi-binding{code} command. 
> The output of the {code} describe jndi-binding{code} needs to indicate 
> whether a binding is active or not.
> 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-4386) gfsh command to describe jndi binding

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4386:
--
Fix Version/s: 1.6.0

> gfsh command to describe jndi binding
> -
>
> Key: GEODE-4386
> URL: https://issues.apache.org/jira/browse/GEODE-4386
> Project: Geode
>  Issue Type: Sub-task
>  Components: docs, gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  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 describe a datasource using the gfsh command 
> {{describe jndi-binding --name=jndi-binding-name}}
>  Then list the particular datasource with attributes and don't display the 
> password.
>  The
> {code:java}
> describe  jndi-binding{code} command should be able to describe any 
> jndi-binding that is output by the {code} list jndi-binding{code} command. 
> The output of the {code} describe jndi-binding{code} needs to indicate 
> whether a binding is active or not.
> 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] [Resolved] (GEODE-3456) "null" node showing up in Pulse UI

[Barbara Pruijn (JIRA)]

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

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

> "null" node showing up in Pulse UI
> --
>
> Key: GEODE-3456
> URL: https://issues.apache.org/jira/browse/GEODE-3456
> Project: Geode
>  Issue Type: Bug
>  Components: management, pulse
>Affects Versions: 1.2.0
>Reporter: Jon Roberts
>Priority: Major
>  Labels: pull-request-available, starter
> Fix For: 1.6.0
>
> Attachments: Screen Shot 2017-08-16 at 4.48.03 PM.png, Screen Shot 
> 2017-08-16 at 4.48.11 PM.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> 4 node cluster (2 locators and 2 servers)
> Start locators:
> gfsh start locator --name=locator1 --dir=/logs/locator1 --port=10334 
> --properties-file=/home/gpadmin/gemfire1.properties 
> --locators=ec2-107-23-210-6.compute-1.amazonaws.com[10334],ec2-34-227-81-77.compute-1.amazonaws.com[10334]
> gemfire1.properties
> jmx-manager-hostname-for-clients=ec2-107-23-210-6.compute-1.amazonaws.com
> mcast-port=0
> conserve-sockets=false
> gfsh start locator --name=locator2 --dir=/logs/locator1 --port=10334 
> --properties-file=/home/gpadmin/gemfire1.properties 
> --locators=ec2-107-23-210-6.compute-1.amazonaws.com[10334],ec2-34-227-81-77.compute-1.amazonaws.com[10334]
> gemfire2.properties
> jmx-manager-hostname-for-clients=
> mcast-port=0
> conserve-sockets=false
> Start servers
> gfsh start server --name=server1 --dir=/logs/server 
> --locators=ec2-107-23-210-6.compute-1.amazonaws.com[10334],ec2-34-227-81-77.compute-1.amazonaws.com[10334]
> gfsh start server --name=server2 --dir=/logs/server 
> --locators=ec2-107-23-210-6.compute-1.amazonaws.com[10334],ec2-34-227-81-77.compute-1.amazonaws.com[10334]



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

[jira] [Updated] (GEODE-3456) "null" node showing up in Pulse UI

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-3456:
--
Fix Version/s: 1.6.0

> "null" node showing up in Pulse UI
> --
>
> Key: GEODE-3456
> URL: https://issues.apache.org/jira/browse/GEODE-3456
> Project: Geode
>  Issue Type: Bug
>  Components: management, pulse
>Affects Versions: 1.2.0
>Reporter: Jon Roberts
>Priority: Major
>  Labels: pull-request-available, starter
> Fix For: 1.6.0
>
> Attachments: Screen Shot 2017-08-16 at 4.48.03 PM.png, Screen Shot 
> 2017-08-16 at 4.48.11 PM.png
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> 4 node cluster (2 locators and 2 servers)
> Start locators:
> gfsh start locator --name=locator1 --dir=/logs/locator1 --port=10334 
> --properties-file=/home/gpadmin/gemfire1.properties 
> --locators=ec2-107-23-210-6.compute-1.amazonaws.com[10334],ec2-34-227-81-77.compute-1.amazonaws.com[10334]
> gemfire1.properties
> jmx-manager-hostname-for-clients=ec2-107-23-210-6.compute-1.amazonaws.com
> mcast-port=0
> conserve-sockets=false
> gfsh start locator --name=locator2 --dir=/logs/locator1 --port=10334 
> --properties-file=/home/gpadmin/gemfire1.properties 
> --locators=ec2-107-23-210-6.compute-1.amazonaws.com[10334],ec2-34-227-81-77.compute-1.amazonaws.com[10334]
> gemfire2.properties
> jmx-manager-hostname-for-clients=
> mcast-port=0
> conserve-sockets=false
> Start servers
> gfsh start server --name=server1 --dir=/logs/server 
> --locators=ec2-107-23-210-6.compute-1.amazonaws.com[10334],ec2-34-227-81-77.compute-1.amazonaws.com[10334]
> gfsh start server --name=server2 --dir=/logs/server 
> --locators=ec2-107-23-210-6.compute-1.amazonaws.com[10334],ec2-34-227-81-77.compute-1.amazonaws.com[10334]



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

[jira] [Updated] (GEODE-4990) Race Condition When Using Cluster Configuration Service

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4990:
--
Affects Version/s: 1.4.0

> Race Condition When Using Cluster Configuration Service
> ---
>
> Key: GEODE-4990
> URL: https://issues.apache.org/jira/browse/GEODE-4990
> Project: Geode
>  Issue Type: Bug
>  Components: configuration, locator
>Affects Versions: 1.4.0
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
>
> There's a small window of time on which the locator 
> ({{enable-cluster-configuration=true}}) is receiving TCP requests from 
> starting up servers ({{use-cluster-configuration=true}}) but the cluster 
> configuration service is not yet fully loaded, because of this the servers 
> fail to startup and throw the following exception:
> {noformat}
> Exception in thread "main" org.apache.geode.cache.execute.FunctionException: 
> java.lang.NullPointerException
>   at 
> org.apache.geode.internal.cache.execute.FunctionStreamingResultCollector.getResult(FunctionStreamingResultCollector.java:232)
>   at 
> org.apache.geode.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:285)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1036)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:835)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:775)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:764)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:175)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:222)
>   at 
> org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52)
>   at 
> org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:844)
>   at 
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:762)
>   at 
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:692)
>   at 
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:226)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
>   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.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.access$000(DistributionManager.java:108)
>   at 
> org.apache.geode.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:970)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> The logs from the locator, when using {{log-level=fine}} show the following:
> {noformat}
> [fine 2018/04/03 15:24:40.501 IST locator1  
> tid=0x51] Exception occurred on remote member while executing Function: 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction
> java.lang.NullPointerException
>   at 
> org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
>   at 
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
>   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.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
>   at 
> org.apache.geode.distributed.internal.DistributionManager.access$000(DistributionManager.java:108)
>   at 
> 

[jira] [Resolved] (GEODE-4985) Updated security implementation example CMake to use FindGeodeNative module.

[Ernest Burghardt (JIRA)]

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

Ernest Burghardt resolved GEODE-4985.
-
Resolution: Not A Problem

> Updated security implementation example CMake to use FindGeodeNative module.
> 
>
> Key: GEODE-4985
> URL: https://issues.apache.org/jira/browse/GEODE-4985
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Major
>




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

[jira] [Created] (GEODE-4990) Race Condition When Using Cluster Configuration Service

[JIRA]

Juan José Ramos Cassella created GEODE-4990:
---

 Summary: Race Condition When Using Cluster Configuration Service
 Key: GEODE-4990
 URL: https://issues.apache.org/jira/browse/GEODE-4990
 Project: Geode
  Issue Type: Bug
  Components: configuration, locator
Reporter: Juan José Ramos Cassella


There's a small window of time on which the locator 
({{enable-cluster-configuration=true}}) is receiving TCP requests from starting 
up servers ({{use-cluster-configuration=true}}) but the cluster configuration 
service is not yet fully loaded, because of this the servers fail to startup 
and throw the following exception:

{noformat}
Exception in thread "main" org.apache.geode.cache.execute.FunctionException: 
java.lang.NullPointerException
at 
org.apache.geode.internal.cache.execute.FunctionStreamingResultCollector.getResult(FunctionStreamingResultCollector.java:232)
at 
org.apache.geode.internal.cache.ClusterConfigurationLoader.requestConfigurationFromLocators(ClusterConfigurationLoader.java:285)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.requestSharedConfiguration(GemFireCacheImpl.java:1036)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:835)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:775)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:764)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:175)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:222)
at 
org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52)
at 
org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:844)
at 
org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:762)
at 
org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:692)
at 
org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:226)
Caused by: java.lang.NullPointerException
at 
org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
at 
org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
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.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
at 
org.apache.geode.distributed.internal.DistributionManager.access$000(DistributionManager.java:108)
at 
org.apache.geode.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:970)
at java.lang.Thread.run(Thread.java:748)
{noformat}

The logs from the locator, when using {{log-level=fine}} show the following:

{noformat}
[fine 2018/04/03 15:24:40.501 IST locator1  
tid=0x51] Exception occurred on remote member while executing Function: 
org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction
java.lang.NullPointerException
at 
org.apache.geode.management.internal.configuration.functions.GetClusterConfigurationFunction.execute(GetClusterConfigurationFunction.java:55)
at 
org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:186)
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.DistributionManager.runUntilShutdown(DistributionManager.java:1099)
at 
org.apache.geode.distributed.internal.DistributionManager.access$000(DistributionManager.java:108)
at 
org.apache.geode.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:970)
at java.lang.Thread.run(Thread.java:748)

[fine 2018/04/03 15:24:40.502 IST locator1  
tid=0x51] Replying with exception: ReplyMessage processorId=2 from null with 
exception org.apache.geode.distributed.internal.ReplyException: 
java.lang.NullPointerException
org.apache.geode.distributed.internal.ReplyException: 

[jira] [Commented] (GEODE-4988) NUnit needs to use .NET 4.5.2

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4988:


Commit 6a5c01b7b0a28e0c0f1375c425d5176bef356f87 in geode-native's branch 
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=6a5c01b ]

GEODE-4988: Auto confirm .NET 3.5 for Nunit.


> NUnit needs to use .NET 4.5.2
> -
>
> Key: GEODE-4988
> URL: https://issues.apache.org/jira/browse/GEODE-4988
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ernest Burghardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> CLICACHE tests need to use .NET 4.5.2



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

[jira] [Commented] (GEODE-4988) NUnit needs to use .NET 4.5.2

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4988:


Commit 7df84b5c3b7e9b5d7f6b19cb9e494353a50b43b8 in geode-native's branch 
refs/heads/develop from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=7df84b5 ]

GEODE-4988: Install .NET 3.5 for Nunit.


> NUnit needs to use .NET 4.5.2
> -
>
> Key: GEODE-4988
> URL: https://issues.apache.org/jira/browse/GEODE-4988
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ernest Burghardt
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> CLICACHE tests need to use .NET 4.5.2



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