[jira] [Commented] (GEODE-4385) gfsh command to list jndi binding

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4385:


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

GEODE-4385: Update help message for list jndi-binding (#1575)

- Also add ResourcePermission for the same command

> gfsh command to list jndi binding
> -
>
> Key: GEODE-4385
> URL: https://issues.apache.org/jira/browse/GEODE-4385
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Barbara Pruijn
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 50m
>  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 list a datasource using the gfsh command {{list 
> jndi-binding}}
>  Then all jndi-binding names will be displayed.
> 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-4802) Geode cluster hanged after network problems

[Eugene Nedzvetsky (JIRA)]

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

Eugene Nedzvetsky updated GEODE-4802:
-
Description: 
Test preparation:
 # create file bin/server1/gemfire.properties with property 
membership-port-range=2025-2030
 # create file bin/server2/gemfire.propertieswith property 
membership-port-range=2035-2040
 # Download network problems emulator [https://jagt.github.io/clumsy]
 # Fill field 'filtering' in Clumsy: tcp and (tcp.DstPort == 2025 or 
tcp.DstPort == 2026 or tcp.DstPort == 2027 or tcp.DstPort == 2028 or 
tcp.DstPort == 2029 or tcp.DstPort == 2030). Select function 'Drop' and set 
Chance=100%. See clumsy2.jpg

Steps to reproduce
 # Start gfsh
 # start locator --name=locator1
 # start server --name=server1 --server-port=40411
 # start server --name=server2 --server-port=40412
 # create region --name=regionA --type=REPLICATE
 # put --region=regionA --key="1" --value="one"
 # Click on 'start' button in Clumsy
 # put --region=regionA --key="1" --value="onev2"
 # Wait *15s* and click on 'stop' in Clumsy

Gfsh console has hung.

bin\server1\server1.log:

[warning 2018/03/07 18:02:50.360 PST server1  
tid=0x4b] 15 seconds have elapsed while waiting for replies: 
 on 
192.168.100.109(server1:14416):2045 whose current membership list is: 
[[192.168.100.109(server2:12804):2035, 
192.168.100.109(locator1:15628:locator):1024, 
192.168.100.109(server1:14416):2045]]

Pulse has shown 'normal' status for both servers.

Gfsh works again if server1 process was killed.

Also  i've reproduced another issue with the same scenario on my test 
environment(see [^threaddump.log])

 

  was:
Test preparation:
 # create file bin/server1/gemfire.properties with property 
membership-port-range=2025-2030
 # create file bin/server2/gemfire.propertieswith property 
membership-port-range=2035-2040
 # Download network problems emulator [https://jagt.github.io/clumsy]
 # Fill field 'filtering' in Clumsy: tcp and (tcp.DstPort == 2025 or 
tcp.DstPort == 2026 or tcp.DstPort == 2027 or tcp.DstPort == 2028 or 
tcp.DstPort == 2029 or tcp.DstPort == 2030). Select function 'Drop' and set 
Chance=100%. See clumsy2.jpg

Steps to reproduce
 # Start gfsh
 # start locator --name=locator1
 # start server --name=server1 --server-port=40411
 # start server --name=server2 --server-port=40412
 # create region --name=regionA --type=REPLICATE
 # put --region=regionA --key="1" --value="one"
 # Click on 'start' button in Clumsy
 # put --region=regionA --key="1" --value="onev2"
 # Wait *15s* and click on 'stop' in Clumsy

Gfsh console has hung.

bin\server1\server1.log:

[warning 2018/03/07 18:02:50.360 PST server1  
tid=0x4b] 15 seconds have elapsed while waiting for replies: 
 on 
192.168.100.109(server1:14416):2045 whose current membership list is: 
[[192.168.100.109(server2:12804):2035, 
192.168.100.109(locator1:15628:locator):1024, 
192.168.100.109(server1:14416):2045]]

Pulse has shown 'normal' status for both servers.

Gfsh works again if server1 process was killed.


> Geode cluster hanged after network problems
> ---
>
> Key: GEODE-4802
> URL: https://issues.apache.org/jira/browse/GEODE-4802
> Project: Geode
>  Issue Type: Bug
>Reporter: Eugene Nedzvetsky
>Priority: Major
> Attachments: clumsy2.jpg, threaddump.log
>
>
> Test preparation:
>  # create file bin/server1/gemfire.properties with property 
> membership-port-range=2025-2030
>  # create file bin/server2/gemfire.propertieswith property 
> membership-port-range=2035-2040
>  # Download network problems emulator [https://jagt.github.io/clumsy]
>  # Fill field 'filtering' in Clumsy: tcp and (tcp.DstPort == 2025 or 
> tcp.DstPort == 2026 or tcp.DstPort == 2027 or tcp.DstPort == 2028 or 
> tcp.DstPort == 2029 or tcp.DstPort == 2030). Select function 'Drop' and set 
> Chance=100%. See clumsy2.jpg
> Steps to reproduce
>  # Start gfsh
>  # start locator --name=locator1
>  # start server --name=server1 --server-port=40411
>  # start server --name=server2 --server-port=40412
>  # create region --name=regionA --type=REPLICATE
>  # put --region=regionA --key="1" --value="one"
>  # Click on 'start' button in Clumsy
>  # put --region=regionA --key="1" --value="onev2"
>  # Wait *15s* and click on 'stop' in Clumsy
> Gfsh console has hung.
> bin\server1\server1.log:
> [warning 2018/03/07 18:02:50.360 PST server1  
> tid=0x4b] 15 seconds have elapsed while waiting for replies: 
>  replies from [192.168.100.109(server2:12804):2035]> on 
> 

[jira] [Updated] (GEODE-4802) Geode cluster hanged after network problems

[Eugene Nedzvetsky (JIRA)]

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

Eugene Nedzvetsky updated GEODE-4802:
-
Attachment: threaddump.log

> Geode cluster hanged after network problems
> ---
>
> Key: GEODE-4802
> URL: https://issues.apache.org/jira/browse/GEODE-4802
> Project: Geode
>  Issue Type: Bug
>Reporter: Eugene Nedzvetsky
>Priority: Major
> Attachments: clumsy2.jpg, threaddump.log
>
>
> Test preparation:
>  # create file bin/server1/gemfire.properties with property 
> membership-port-range=2025-2030
>  # create file bin/server2/gemfire.propertieswith property 
> membership-port-range=2035-2040
>  # Download network problems emulator [https://jagt.github.io/clumsy]
>  # Fill field 'filtering' in Clumsy: tcp and (tcp.DstPort == 2025 or 
> tcp.DstPort == 2026 or tcp.DstPort == 2027 or tcp.DstPort == 2028 or 
> tcp.DstPort == 2029 or tcp.DstPort == 2030). Select function 'Drop' and set 
> Chance=100%. See clumsy2.jpg
> Steps to reproduce
>  # Start gfsh
>  # start locator --name=locator1
>  # start server --name=server1 --server-port=40411
>  # start server --name=server2 --server-port=40412
>  # create region --name=regionA --type=REPLICATE
>  # put --region=regionA --key="1" --value="one"
>  # Click on 'start' button in Clumsy
>  # put --region=regionA --key="1" --value="onev2"
>  # Wait *15s* and click on 'stop' in Clumsy
> Gfsh console has hung.
> bin\server1\server1.log:
> [warning 2018/03/07 18:02:50.360 PST server1  
> tid=0x4b] 15 seconds have elapsed while waiting for replies: 
>  replies from [192.168.100.109(server2:12804):2035]> on 
> 192.168.100.109(server1:14416):2045 whose current membership list is: 
> [[192.168.100.109(server2:12804):2035, 
> 192.168.100.109(locator1:15628:locator):1024, 
> 192.168.100.109(server1:14416):2045]]
> Pulse has shown 'normal' status for both servers.
> Gfsh works again if server1 process was killed.



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

[jira] [Updated] (GEODE-4802) Geode cluster hanged after network problems

[Eugene Nedzvetsky (JIRA)]

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

Eugene Nedzvetsky updated GEODE-4802:
-
Attachment: clumsy2.jpg

> Geode cluster hanged after network problems
> ---
>
> Key: GEODE-4802
> URL: https://issues.apache.org/jira/browse/GEODE-4802
> Project: Geode
>  Issue Type: Bug
>Reporter: Eugene Nedzvetsky
>Priority: Major
> Attachments: clumsy2.jpg
>
>
> Test preparation:
>  # create file bin/server1/gemfire.properties with property 
> membership-port-range=2025-2030
>  # create file bin/server2/gemfire.propertieswith property 
> membership-port-range=2035-2040
>  # Download network problems emulator [https://jagt.github.io/clumsy]
>  # Fill field 'filtering' in Clumsy: tcp and (tcp.DstPort == 2025 or 
> tcp.DstPort == 2026 or tcp.DstPort == 2027 or tcp.DstPort == 2028 or 
> tcp.DstPort == 2029 or tcp.DstPort == 2030). Select function 'Drop' and set 
> Chance=100%. See clumsy2.jpg
> Steps to reproduce
>  # Start gfsh
>  # start locator --name=locator1
>  # start server --name=server1 --server-port=40411
>  # start server --name=server2 --server-port=40412
>  # create region --name=regionA --type=REPLICATE
>  # put --region=regionA --key="1" --value="one"
>  # Click on 'start' button in Clumsy
>  # put --region=regionA --key="1" --value="onev2"
>  # Wait *15s* and click on 'stop' in Clumsy
> Gfsh console has hung.
> bin\server1\server1.log:
> [warning 2018/03/07 18:02:50.360 PST server1  
> tid=0x4b] 15 seconds have elapsed while waiting for replies: 
>  replies from [192.168.100.109(server2:12804):2035]> on 
> 192.168.100.109(server1:14416):2045 whose current membership list is: 
> [[192.168.100.109(server2:12804):2035, 
> 192.168.100.109(locator1:15628:locator):1024, 
> 192.168.100.109(server1:14416):2045]]
> Pulse has shown 'normal' status for both servers.
> Gfsh works again if server1 process was killed.



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

[jira] [Created] (GEODE-4802) Geode cluster hanged after network problems

[Eugene Nedzvetsky (JIRA)]

Eugene Nedzvetsky created GEODE-4802:


 Summary: Geode cluster hanged after network problems
 Key: GEODE-4802
 URL: https://issues.apache.org/jira/browse/GEODE-4802
 Project: Geode
  Issue Type: Bug
Reporter: Eugene Nedzvetsky


Test preparation:
 # create file bin/server1/gemfire.properties with property 
membership-port-range=2025-2030
 # create file bin/server2/gemfire.propertieswith property 
membership-port-range=2035-2040
 # Download network problems emulator [https://jagt.github.io/clumsy]
 # Fill field 'filtering' in Clumsy: tcp and (tcp.DstPort == 2025 or 
tcp.DstPort == 2026 or tcp.DstPort == 2027 or tcp.DstPort == 2028 or 
tcp.DstPort == 2029 or tcp.DstPort == 2030). Select function 'Drop' and set 
Chance=100%. See clumsy2.jpg

Steps to reproduce
 # Start gfsh
 # start locator --name=locator1
 # start server --name=server1 --server-port=40411
 # start server --name=server2 --server-port=40412
 # create region --name=regionA --type=REPLICATE
 # put --region=regionA --key="1" --value="one"
 # Click on 'start' button in Clumsy
 # put --region=regionA --key="1" --value="onev2"
 # Wait *15s* and click on 'stop' in Clumsy

Gfsh console has hung.

bin\server1\server1.log:

[warning 2018/03/07 18:02:50.360 PST server1  
tid=0x4b] 15 seconds have elapsed while waiting for replies: 
 on 
192.168.100.109(server1:14416):2045 whose current membership list is: 
[[192.168.100.109(server2:12804):2035, 
192.168.100.109(locator1:15628:locator):1024, 
192.168.100.109(server1:14416):2045]]

Pulse has shown 'normal' status for both servers.

Gfsh works again if server1 process was killed.



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

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


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

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


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



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

[jira] [Updated] (GEODE-4768) protobuf driver is not closing its socket connections to the locator

[ASF GitHub Bot (JIRA)]

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

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

> protobuf driver is not closing its socket connections to the locator
> 
>
> Key: GEODE-4768
> URL: https://issues.apache.org/jira/browse/GEODE-4768
> Project: Geode
>  Issue Type: Task
>  Components: client/server
>Reporter: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>
> While reviewing code in the experimental protobuf driver I noticed that the 
> findAServer method is creating socket connections to locators but is not 
> closing them.  Ideally it would abort the socket connections by setting 
> solinger to zero so the locator doesn't accumulate sockets in a time-wait 
> state.  See GEODE-871.



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

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

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-4801:
-
Summary: Readme should link to "how to contribute" on wiki  (was: Website 
should link to "how to contribute" on wiki)

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




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

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

[Alexander Murmann (JIRA)]

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

Alexander Murmann reassigned GEODE-4801:


Assignee: Alexander Murmann

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




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

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

[Alexander Murmann (JIRA)]

Alexander Murmann created GEODE-4801:


 Summary: Website should link to "how to contribute" on wiki
 Key: GEODE-4801
 URL: https://issues.apache.org/jira/browse/GEODE-4801
 Project: Geode
  Issue Type: Improvement
  Components: website
Reporter: Alexander Murmann






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

[jira] [Updated] (GEODE-2727) optimize new 1.8 ConcurrentMap default methods on Region

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-2727:
-
Labels: region_interface storage_2  (was: region_interface starter++ 
storage_2)

> optimize new 1.8 ConcurrentMap default methods on Region
> 
>
> Key: GEODE-2727
> URL: https://issues.apache.org/jira/browse/GEODE-2727
> Project: Geode
>  Issue Type: Improvement
>  Components: regions
>Reporter: Darrel Schneider
>Priority: Major
>  Labels: region_interface, storage_2
>
> In JDK 1.8 ConcurrentMap added the following default methods to the interface:
> getOrDefault
>  computeIfAbsent
>  computeIfPresent
>  compute
>  merge
>  foreach
>  replaceAll
> All of the default implementations of these methods have issues with get 
> returning null when the key actually exists. So they do not support invalid 
> region entries.
>  The other problem with all of them (except getOrDefault) is that they will 
> make multiple round trips when done from a proxy. In a distributed 
> environment we should implement these to send the lambda to the primary so 
> that the entire operation can be done with one message and while the 
> RegionEntry is locked.
>  This would require that the lambda parameter by serializable which would be 
> consistent with what we do for other parameters to Region methods (for 
> example "put").
>  From a performance point of view "foreach" and "replaceAll" are the worst 
> since they bring back to whoever is executing the method all the keys and 
> values from the entire cluster.
>  It is also worth considering how the operations behave in a geode 
> transaction.



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

[jira] [Updated] (GEODE-85) Extract memcached adaptor from core

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-85:
---
Labels: starter  (was: low-hanging-fruit starter)

> Extract memcached adaptor from core
> ---
>
> Key: GEODE-85
> URL: https://issues.apache.org/jira/browse/GEODE-85
> Project: Geode
>  Issue Type: Task
>  Components: extensions
>Reporter: Swapnil Bawaskar
>Priority: Major
>  Labels: starter
>
> GemFire memcached adapter (also referred to as gemcached) is part of 
> gemfire-core. It needs to be extracted into a 'gemfire-memcached-adapter' 
> directory.



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

[jira] [Updated] (GEODE-1241) Rename classes and methods that are misspelled with "propogation"

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-1241:
-
Labels: starter  (was: low-hanging-fruit starter)

> Rename classes and methods that are misspelled with "propogation"
> -
>
> Key: GEODE-1241
> URL: https://issues.apache.org/jira/browse/GEODE-1241
> Project: Geode
>  Issue Type: Wish
>  Components: general
>Reporter: Kirk Lund
>Priority: Trivial
>  Labels: starter
>
> The correct spelling is "propagation"
> ConcurrentWANPropogation_1_DUnitTest
> ConcurrentWANPropogation_2_DUnitTest
> ConcurrentWANPropogation_2_DUnitTest.testSerialPropogationWithFilter
> DataSerializerPropogationDUnitTest
> ParallelWANPropogationConcurrentOpsOffHeapDUnitTest
> ParallelWANStatsDUnitTest.testParallelPropogationWithFilter
> SerialWANPropogationDUnitTest
> SerialWANPropogationOffHeapDUnitTest
> SerialWANPropogation_PartitionedRegionDUnitTest
> SerialWANPropogation_PartitionedRegionOffHeapDUnitTest
> SerialWANPropogationsFeatureDUnitTest
> SerialWANPropogationsFeatureDUnitTest.testSerialPropogationWithFilter
> SerialWANStatsDUnitTest.testSerialPropogationWithFilter
> There are some misspellings in comments as well.



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

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

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-4658:
-
Labels: starter++  (was: Starter)

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



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

[jira] [Commented] (GEODE-517) multi-tenant memcached server

[Alexander Murmann (JIRA)]

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

Alexander Murmann commented on GEODE-517:
-

[~dalyssakim] Are you still working on this? If not it might be great to 
unassign yourself so that others can safely pick it up. Thanks!

> multi-tenant memcached server
> -
>
> Key: GEODE-517
> URL: https://issues.apache.org/jira/browse/GEODE-517
> Project: Geode
>  Issue Type: Improvement
>  Components: memcached
>Reporter: Swapnil Bawaskar
>Assignee: Alyssa Kim
>Priority: Major
>  Labels: starter
>
> One can start multiple memcached servers within the same Geode process. All 
> these servers however use only a single region to store data. 
> When the memcached server is started, we need ability to pass the region name 
> in which data is stored.



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

[jira] [Updated] (GEODE-3200) ServerConnection.authzRequest is no longer used

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-3200:
-
Labels: starter++  (was: newbie++)

> ServerConnection.authzRequest is no longer used
> ---
>
> Key: GEODE-3200
> URL: https://issues.apache.org/jira/browse/GEODE-3200
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server, security
>Reporter: Galen O'Sullivan
>Priority: Major
>  Labels: starter++
>
> ServerConnection has a private member called authzRequest that is no longer 
> used.
> ServerConnection.getAuthzRequest() is used in a few places, but may not be 
> relevant anymore.
> authzRequest should be removed or used to cache the value if it can be 
> cached, and we should probably have a look at getAuthzRequest to make sure 
> it's still used.
> This class is expected to undergo significant refactoring due to GEODE-3074, 
> you might want to have a chat with whoever is working on that to avoid merge 
> conflicts.



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

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

[Brian Rowe (JIRA)]

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

Brian Rowe reassigned GEODE-4750:
-

Assignee: Brian Rowe

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



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

[jira] [Updated] (GEODE-85) Extract memcached adaptor from core

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-85:
---
Labels: low-hanging-fruit starter  (was: low-hanging-fruit newbie)

> Extract memcached adaptor from core
> ---
>
> Key: GEODE-85
> URL: https://issues.apache.org/jira/browse/GEODE-85
> Project: Geode
>  Issue Type: Task
>  Components: extensions
>Reporter: Swapnil Bawaskar
>Priority: Major
>  Labels: low-hanging-fruit, starter
>
> GemFire memcached adapter (also referred to as gemcached) is part of 
> gemfire-core. It needs to be extracted into a 'gemfire-memcached-adapter' 
> directory.



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

[jira] [Updated] (GEODE-1241) Rename classes and methods that are misspelled with "propogation"

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-1241:
-
Labels: low-hanging-fruit starter  (was: low-hanging-fruit newbie starter)

> Rename classes and methods that are misspelled with "propogation"
> -
>
> Key: GEODE-1241
> URL: https://issues.apache.org/jira/browse/GEODE-1241
> Project: Geode
>  Issue Type: Wish
>  Components: general
>Reporter: Kirk Lund
>Priority: Trivial
>  Labels: low-hanging-fruit, starter
>
> The correct spelling is "propagation"
> ConcurrentWANPropogation_1_DUnitTest
> ConcurrentWANPropogation_2_DUnitTest
> ConcurrentWANPropogation_2_DUnitTest.testSerialPropogationWithFilter
> DataSerializerPropogationDUnitTest
> ParallelWANPropogationConcurrentOpsOffHeapDUnitTest
> ParallelWANStatsDUnitTest.testParallelPropogationWithFilter
> SerialWANPropogationDUnitTest
> SerialWANPropogationOffHeapDUnitTest
> SerialWANPropogation_PartitionedRegionDUnitTest
> SerialWANPropogation_PartitionedRegionOffHeapDUnitTest
> SerialWANPropogationsFeatureDUnitTest
> SerialWANPropogationsFeatureDUnitTest.testSerialPropogationWithFilter
> SerialWANStatsDUnitTest.testSerialPropogationWithFilter
> There are some misspellings in comments as well.



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

[jira] [Updated] (GEODE-1409) Pulse view does not display cluster and members when in France

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-1409:
-
Labels: starter  (was: newbie)

> Pulse view does not display cluster and members when in France
> --
>
> Key: GEODE-1409
> URL: https://issues.apache.org/jira/browse/GEODE-1409
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Eitan Suez
>Priority: Major
>  Labels: starter
>
> If you setup your cluster with user.country=FR and user.language=fr (france) 
> when starting your locator and servers, then when you start pulse, log in, 
> you will not see your cluster nor any members.
> the reason is that the http post that the client does to the pulse controller 
> (/pulseUpdate) does not return members.
> we see this in the pulse logs:
> [WARNING 2016/05/17 10:15:56.489 CEST qtp22145019-209 tid=0xd1] (msgTID=209 
> msgSN=29665) [PULSE]
> [com.vmware.gemfire.tools.pulse.internal.log.PulseLogWriter]
> serviceException [for service ClusterMembersRGraph] = For input string: 
> "30,58"
>  
> it looks like the service exception might have some kind of number parsing 
> exception when encountering numeric values formatted according to the french 
> locale.  so it encounters 30,58 and doesn't properly interpret it as 30.58.. 
> that has the side effect of fetching cluster information not returning 
> anything.



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

[jira] [Updated] (GEODE-1505) Fix spelling of IndexMaintainceJUnitTest

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-1505:
-
Labels: starter  (was: newbie starter)

> Fix spelling of IndexMaintainceJUnitTest
> 
>
> Key: GEODE-1505
> URL: https://issues.apache.org/jira/browse/GEODE-1505
> Project: Geode
>  Issue Type: Task
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Srikanth Manvi
>Priority: Major
>  Labels: starter
>
> IndexMaintainceJUnitTest should be renamed to IndexMaintenanceJUnitTest.



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

[jira] [Updated] (GEODE-1730) Cleanup SmHelper, SharedLibrary, PureJavaMode classes

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-1730:
-
Labels: starter  (was: newbie starter)

> Cleanup SmHelper, SharedLibrary, PureJavaMode classes
> -
>
> Key: GEODE-1730
> URL: https://issues.apache.org/jira/browse/GEODE-1730
> Project: Geode
>  Issue Type: Improvement
>  Components: general
>Reporter: Kirk Lund
>Priority: Minor
>  Labels: starter
>
> These classes are for the GemFire native code which is not in Geode. There 
> are a couple of methods still used on these classes such as is64bit() which 
> could be moved to another class such as SystemUtils.



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

[jira] [Updated] (GEODE-1729) Removing redundant import of org.junit.experimental.categories.Category

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-1729:
-
Labels: starter  (was: newbie starter)

> Removing redundant import of org.junit.experimental.categories.Category
> ---
>
> Key: GEODE-1729
> URL: https://issues.apache.org/jira/browse/GEODE-1729
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: nabarun
>Assignee: nabarun
>Priority: Major
>  Labels: starter
>
> While updating from JUnit 3 to Junit 4 redundant 
> org.junit.experimental.categories.Category import statements were inserted. 
> These need to be removed



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

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

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-2321:
-
Labels: starter  (was: newbie)

> 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
>  Labels: starter
>
> 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] [Updated] (GEODE-1842) Execution of query from GFSH or Pulse may kill a Server with StackOverflowError

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-1842:
-
Labels: StackOverflowError gfsh json starter  (was: StackOverflowError gfsh 
json newbie)

> Execution of query from GFSH or Pulse may kill a Server with 
> StackOverflowError
> ---
>
> Key: GEODE-1842
> URL: https://issues.apache.org/jira/browse/GEODE-1842
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh, pulse
>Reporter: Kirk Lund
>Priority: Critical
>  Labels: StackOverflowError, gfsh, json, starter
>
> TypedJson is prone to StackOverflowErrors which results in SystemFailure 
> shutdown of any Geode server that hits this problem. Below is the latest 
> error stack reported against TypedJson:
> {noformat}
> java.lang.StackOverflowError
> at java.lang.Class.getEnclosingMethodInfo(Class.java:1072)
> at java.lang.Class.getEnclosingClass(Class.java:1272)
> at java.lang.Class.getSimpleBinaryName(Class.java:1443)
> at java.lang.Class.getSimpleName(Class.java:1309)
> at java.lang.Class.getCanonicalName(Class.java:1399)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.internalToExternal(TypedJson.java:626)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeType(TypedJson.java:610)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:345)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitSpecialObjects(TypedJson.java:517)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:353)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitChildrens(TypedJson.java:670)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.addVal(TypedJson.java:323)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeVal(TypedJson.java:314)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:357)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitChildrens(TypedJson.java:670)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.addVal(TypedJson.java:323)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeVal(TypedJson.java:314)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:357)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitSpecialObjects(TypedJson.java:517)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:353)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitChildrens(TypedJson.java:670)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.addVal(TypedJson.java:323)
> at 
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeVal(TypedJson.java:314)
> {noformat}
> QueryDataFunction uses TypedJson to serialize query results into JSON to 
> return to GFSH or Pulse. Rather than maintain a broken custom JSON parser, we 
> should replace TypedJson with Jackson.
> This example will go into infinite recursion until it produces a 
> StackOverflowError:
> {noformat}
> public class Root {
>   public Root getRoot() {
> return this;
>   }
>   public Child getChild() { // getter that returns unique instances
> return new Child();
>   }
> }
> public class Child {
>   public Child getChild() {
> return this;
>   }
> }
> {noformat}
> This example will go into an infinite loop until it produces OutOfMemoryError:
> {noformat}
> public class Replicator {
>   public Replicator getReplicator() { // getter that returns unique instances
> return new Replicator();
>   }
> }
> {noformat}



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

[jira] [Updated] (GEODE-3057) Keep Thread Local Comm Buffer in selector thread

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-3057:
-
Labels: starter  (was: newbie)

> Keep Thread Local Comm Buffer in selector thread
> 
>
> Key: GEODE-3057
> URL: https://issues.apache.org/jira/browse/GEODE-3057
> Project: Geode
>  Issue Type: Improvement
>  Components: client/server
>Reporter: Galen O'Sullivan
>Priority: Major
>  Labels: starter
>
> In {{ServerConnection.run()}}, we currently pull a comm buffer from the pool 
> every time that {run} is called by a selector, and release it back after the 
> particular message.
> This buffer is allocated in a {{ThreadLocal}}, so it would make more sense to 
> have the selector thread own a buffer that all commands running on that 
> selector can use.
> As a side note, maybe it would make sense to split the run function in two, 
> with {run} being called in the connection-per-thread case and 
> {{doMessageOnSelector}} or so being called by the selector?



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

[jira] [Updated] (GEODE-2600) Inconsistent spacing of headers in Startup Configuration log

[Alexander Murmann (JIRA)]

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

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

> Inconsistent spacing of headers in Startup Configuration log
> 
>
> Key: GEODE-2600
> URL: https://issues.apache.org/jira/browse/GEODE-2600
> Project: Geode
>  Issue Type: Bug
>  Components: logging
>Affects Versions: 1.2.0
>Reporter: Patrick Rhomberg
>Priority: Trivial
>  Labels: LogBanner, starter
>
> Note the extra space before the initial ###.
> {noformat}
> [info 2017/03/06 14:29:30.003 PST loc1  tid=0x1] Startup Configuration:
>### GemFire Properties defined with system property ###
>   enable-cluster-configuration=true
>   load-cluster-configuration-from-dir=false
>   ### GemFire Properties defined with api ###
> {noformat}



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

[jira] [Updated] (GEODE-3911) Authentication failures produce exception stacktraces in log files.

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-3911:
-
Labels: starter  (was: newbie)

> Authentication failures produce exception stacktraces in log files.
> ---
>
> Key: GEODE-3911
> URL: https://issues.apache.org/jira/browse/GEODE-3911
> Project: Geode
>  Issue Type: Bug
>  Components: pulse, security
>Reporter: Jens Deppe
>Priority: Major
>  Labels: starter
>
> When running pulse along with the `SimpleSecurityManager` I notice quite a 
> few authentication failure stacktraces like:
> {noformat}
> [warning 2017/10/26 07:14:27.773 PDT locator1  Connection(9)-10.118.33.247> tid=0x7d] Authentication failed for token 
> submission [org.apache.geode.internal.security.shiro.GeodeAuthenticationToken 
> - cluster,data, rememberMe=false].  Possible unexpected error? (Typical or 
> expected login exceptions should extend from AuthenticationException).
> org.apache.geode.security.AuthenticationFailedException: invalid 
> username/password
> at 
> org.apache.geode.examples.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:41)
> at 
> org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:52)
> at 
> org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
> at 
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
> at 
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
> at 
> org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
> at 
> org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
> at 
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
> at 
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at 
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:139)
> at 
> org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:60)
> at 
> javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
> at 
> javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
> 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:346)
> 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:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> We shouldn't need to dump these out, but just log a message.



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

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

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-3456:
-
Labels: starter  (was: newbie)

> "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: starter
> Attachments: Screen Shot 2017-08-16 at 4.48.03 PM.png, Screen Shot 
> 2017-08-16 at 4.48.11 PM.png
>
>
> 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-3183) Pulse shows more members than in the cluster

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-3183:
-
Labels: starter  (was: newbie)

> Pulse shows more members than in the cluster
> 
>
> Key: GEODE-3183
> URL: https://issues.apache.org/jira/browse/GEODE-3183
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Swapnil Bawaskar
>Priority: Major
>  Labels: starter
> Attachments: Screen Shot 2017-07-10 at 5.13.21 PM.png
>
>
> Pulse shows 8 members in the cluster, when there are only 7 members !Screen 
> Shot 2017-07-10 at 5.13.21 PM.png!
> gfsh list members returns the correct number of members
> {noformat}
> gfsh>list members
>   Name   | Id
>  | 
> -
> locator-f4ed455e-a646-404d-b2b5-b417371a75a6 | 
> 10.74.46.201(locator-f4ed455e-a646-404d-b2b5-b417371a75a6:8584:locator):49152
> locator-7cdb6f32-283a-4686-8f39-f0dbb1f8da8e | 
> 10.74.46.202(locator-7cdb6f32-283a-4686-8f39-f0dbb1f8da8e:8772:locator):49152
> locator-c7fa8a7a-db00-4ff8-aed2-ca9f95e533bd | 
> 10.74.46.203(locator-c7fa8a7a-db00-4ff8-aed2-ca9f95e533bd:8792:locator):49152
> cacheserver-fcdca55a-e0c7-4bf8-88a8-7db89f9f06bc | 
> 10.74.46.204(cacheserver-fcdca55a-e0c7-4bf8-88a8-7db89f9f06bc:8655):49152
> cacheserver-6dce325e-277b-414b-bd3b-b7e8bfb350e7 | 
> 10.74.46.205(cacheserver-6dce325e-277b-414b-bd3b-b7e8bfb350e7:8808):49152
> cacheserver-bede53d8-84c1-493d-a5dc-04e93ad07526 | 
> 10.74.46.206(cacheserver-bede53d8-84c1-493d-a5dc-04e93ad07526:8857):49152
> cacheserver-e475f1e7-f809-4fb5-8b67-9fbc4a7543e9 | 
> 10.74.46.207(cacheserver-e475f1e7-f809-4fb5-8b67-9fbc4a7543e9:8849):49152
> {noformat}



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

[jira] [Updated] (GEODE-3912) Incorrect regions shown in Pulse ClusterView

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-3912:
-
Labels: starter  (was: newbie)

> Incorrect regions shown in Pulse ClusterView
> 
>
> Key: GEODE-3912
> URL: https://issues.apache.org/jira/browse/GEODE-3912
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Jens Deppe
>Priority: Major
>  Labels: starter
> Attachments: screenshot-1.png
>
>
> I have a 3-node cluster and have created 2 replicated regions and 1 
> partitioned. Each region contains 20 entries. I'm using the 
> SimpleSecurityManager for access control.
> Under the 'ClusterView' each server shows an incorrect view of the regions it 
> is hosting. Specifically it only shows a single region where it should be 
> showing all 3 regions.



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

[jira] [Updated] (GEODE-4687) Impossible to execute query on some specific member in Pulse DataBrowser

[Alexander Murmann (JIRA)]

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

Alexander Murmann updated GEODE-4687:
-
Labels: starter  (was: newbie)

> Impossible to execute query on some specific member in Pulse DataBrowser
> 
>
> Key: GEODE-4687
> URL: https://issues.apache.org/jira/browse/GEODE-4687
> Project: Geode
>  Issue Type: Bug
>  Components: pulse
>Reporter: Vadim Lotarev
>Priority: Major
>  Labels: starter
> Attachments: screenshot.91.jpg, screenshot.92.jpg
>
>
> It is impossible to execute query on some specific member. The reason is in 
> difference between member ID values used in Pulse and 
> {{org.apache.geode.management.internal.beans.QueryDataFunction}} class. For 
> example, Pulse passes the following ID: 
> {{VLOTAREV(inventory-vlotarev-40405:11780):1026}} but 
> {{QueryDataFunction}} tries to compare it with the following value:  
> {{192.168.63.37(inventory-vlotarev-40405:11780):1026}}. See 
> screenshots attached.



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

[jira] [Updated] (GEODE-4788) change back the behavior of test code of getSomeKeys to ignore exceptions

[xiaojian zhou (JIRA)]

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

xiaojian zhou updated GEODE-4788:
-
Fix Version/s: 1.5.0

> change back the behavior of test code of getSomeKeys to ignore exceptions
> -
>
> Key: GEODE-4788
> URL: https://issues.apache.org/jira/browse/GEODE-4788
> Project: Geode
>  Issue Type: New Feature
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0, 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In GEODE-2673, getSomeKeys' behavior was changed to throw exception when 
> detected some exceptions. 
> We need to change it back to ignore the exceptions as test code. 



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

[jira] [Commented] (GEODE-4788) change back the behavior of test code of getSomeKeys to ignore exceptions

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4788:


Commit 7696633eb838b00f7baa8546385886028c7da14e in geode's branch 
refs/heads/release/1.5.0 from zhouxh
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7696633 ]

GEODE-4788: change back the behavior of test code of getSomeKeys to ignore 
exceptions#


> change back the behavior of test code of getSomeKeys to ignore exceptions
> -
>
> Key: GEODE-4788
> URL: https://issues.apache.org/jira/browse/GEODE-4788
> Project: Geode
>  Issue Type: New Feature
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0, 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In GEODE-2673, getSomeKeys' behavior was changed to throw exception when 
> detected some exceptions. 
> We need to change it back to ignore the exceptions as test code. 



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

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

[ASF GitHub Bot (JIRA)]

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

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

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



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

[jira] [Updated] (GEODE-4800) Handle relative paths for backup baseline directories

[ASF GitHub Bot (JIRA)]

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

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

> Handle relative paths for backup baseline directories
> -
>
> Key: GEODE-4800
> URL: https://issues.apache.org/jira/browse/GEODE-4800
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
>
> Backups that specify a relative path for the baseline directory for 
> incremental backups no longer function correctly: the restore script has 
> invalid paths for recovery.



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

[jira] [Assigned] (GEODE-4800) Handle relative paths for backup baseline directories

[Nick Reich (JIRA)]

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

Nick Reich reassigned GEODE-4800:
-

Assignee: Nick Reich

> Handle relative paths for backup baseline directories
> -
>
> Key: GEODE-4800
> URL: https://issues.apache.org/jira/browse/GEODE-4800
> Project: Geode
>  Issue Type: Bug
>  Components: persistence
>Reporter: Nick Reich
>Assignee: Nick Reich
>Priority: Major
>
> Backups that specify a relative path for the baseline directory for 
> incremental backups no longer function correctly: the restore script has 
> invalid paths for recovery.



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

[jira] [Created] (GEODE-4800) Handle relative paths for backup baseline directories

[Nick Reich (JIRA)]

Nick Reich created GEODE-4800:
-

 Summary: Handle relative paths for backup baseline directories
 Key: GEODE-4800
 URL: https://issues.apache.org/jira/browse/GEODE-4800
 Project: Geode
  Issue Type: Bug
  Components: persistence
Reporter: Nick Reich


Backups that specify a relative path for the baseline directory for incremental 
backups no longer function correctly: the restore script has invalid paths for 
recovery.



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

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

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4685:


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

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


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



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

[jira] [Commented] (GEODE-4793) DUnit tests fail on Windows

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4793:


Commit 7becb7c2526b338b7cef5a73c2a3d96c1156208b in geode's branch 
refs/heads/feature/GEODE-4685 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7becb7c ]

GEODE-4793: Ensure that Files.list() closes resources (#1572)

- This was causing some DUnits to fail on Windows.

> DUnit tests fail on Windows
> ---
>
> Key: GEODE-4793
> URL: https://issues.apache.org/jira/browse/GEODE-4793
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Various tests will fail on Windows with errors similar to the following:
> {noformat}
> [vm0] [error 2018/03/07 04:38:13.670 UTC  Connection(1)-10.32.110.121> tid=19] Error occurred while initializing 
> cluster configuration
> [vm0] java.lang.RuntimeException: Error occurred while initializing cluster 
> configuration
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.getConfigurationRegion(ClusterConfigurationService.java:731)
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:459)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startSharedConfigurationService(InternalLocator.java:1332)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:668)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:647)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:309)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:78)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:59)
> [vm0] at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$1c67b668$1(ClusterStartupRule.java:157)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> [vm0] at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at 
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> [vm0] Caused by: java.io.IOException: Cannot create directory at 
> C:\Users\Administrator\geode\geode-core\dunit\vm0\ConfigDiskDir_locator-0
> [vm0] at 
> 

[jira] [Commented] (GEODE-4777) Add UITest job to concourse develop pipeline

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4777:


Commit 7ab0c6bee8efcca72a0d341e1167dd196ebe157b in geode's branch 
refs/heads/feature/GEODE-4685 from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7ab0c6b ]

GEODE-4777: Add UITest job to concourse develop pipeline (#1571)



> Add UITest job to concourse develop pipeline
> 
>
> Key: GEODE-4777
> URL: https://issues.apache.org/jira/browse/GEODE-4777
> Project: Geode
>  Issue Type: Task
>  Components: ci, pulse
>Reporter: Sai Boorlagadda
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Add a UITest job to concourse develop pipeline to run `gradlew uiTest` to run 
> selenium tests as part of the CI pipeline.



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

[jira] [Commented] (GEODE-4781) Categorize Lucene tests

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4781:


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

GEODE-4781: Converted LuceneTest to an interface


> Categorize Lucene tests
> ---
>
> Key: GEODE-4781
> URL: https://issues.apache.org/jira/browse/GEODE-4781
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: nabarun
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4217) gfsh create jdbc-connection command allows a password to be set without a user name

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4217:


Commit 18560c0c45f68601aa3cc6e6ddcaa7ba15f17be6 in geode's branch 
refs/heads/feature/GEODE-4685 from [~nreich]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=18560c0 ]

GEODE-4217: Add validation to CreateConnectionCommand (#1566)

* Do not allow creation of connection if user is null but password is not

> gfsh create jdbc-connection command  allows a password to be set without a 
> user name
> 
>
> Key: GEODE-4217
> URL: https://issues.apache.org/jira/browse/GEODE-4217
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The gfsh create jdbc-connection command  allows a password to be set without 
> a user name.
> If you configure a password you must also configure a user name and this 
> should be validated.



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

[jira] [Commented] (GEODE-4788) change back the behavior of test code of getSomeKeys to ignore exceptions

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4788:


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

GEODE-4788: change back the behavior of test code of getSomeKeys to ignore 
exceptions. (#1564)



> change back the behavior of test code of getSomeKeys to ignore exceptions
> -
>
> Key: GEODE-4788
> URL: https://issues.apache.org/jira/browse/GEODE-4788
> Project: Geode
>  Issue Type: New Feature
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In GEODE-2673, getSomeKeys' behavior was changed to throw exception when 
> detected some exceptions. 
> We need to change it back to ignore the exceptions as test code. 



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

[jira] [Created] (GEODE-4799) Remove static member variables from Apache.Geode.Client.Serializable

[Michael Martell (JIRA)]

Michael Martell created GEODE-4799:
--

 Summary: Remove static member variables from 
Apache.Geode.Client.Serializable
 Key: GEODE-4799
 URL: https://issues.apache.org/jira/browse/GEODE-4799
 Project: Geode
  Issue Type: Improvement
  Components: native client
Reporter: Michael Martell


Currently this class contains a bunch of static member variables. These need to 
be converted to instance variables.

This change will allow each cache instance to have its own custom serializer 
without needing to use a chained serializer.



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

[jira] [Resolved] (GEODE-4343) Geode Native C# Example (put/get of custom objects using PDXAutoserializer)

[Addison (JIRA)]

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

Addison resolved GEODE-4343.

Resolution: Fixed

> Geode Native C# Example (put/get of custom objects using PDXAutoserializer)
> ---
>
> Key: GEODE-4343
> URL: https://issues.apache.org/jira/browse/GEODE-4343
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Addison
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>




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

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

[Darrel Schneider (JIRA)]

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

Darrel Schneider updated GEODE-4798:

Affects Version/s: 1.5.0

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



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

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

[Darrel Schneider (JIRA)]

Darrel Schneider created GEODE-4798:
---

 Summary: JdbcConnectorException can not be deserialized
 Key: GEODE-4798
 URL: https://issues.apache.org/jira/browse/GEODE-4798
 Project: Geode
  Issue Type: Bug
  Components: regions
Reporter: Darrel Schneider


The JdbcConnectorException cannot be deserialized because it is not a "trusted" 
class. Also the SQLException it usually wraps will also fail deserialization so 
it might be better to not create JdbcConnectorException instances whose cause 
is a SQLException. Instead do some type of conversion of the SQLException.

The following is some information about how to get JdbcConnectorException to be 
trusted by the serialization code:
Create a new DistributionService like this lucene one:

LuceneDistributedSystemService
geode-lucene/src/main/resources/META-INF/services/org.apache.geode.distributed.internal.DistributedSystemService
It returns a text file with a whitelist.

Add a test like 
org.apache.geode.codeAnalysis.AnalyzeLuceneSerializablesJUnitTest



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

[jira] [Updated] (GEODE-4751) Add function execution to Protobuf driver

[ASF GitHub Bot (JIRA)]

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

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

> Add function execution to Protobuf driver
> -
>
> Key: GEODE-4751
> URL: https://issues.apache.org/jira/browse/GEODE-4751
> Project: Geode
>  Issue Type: New Feature
>  Components: client/server
>Reporter: Bruce Schuchardt
>Assignee: Michael Dodge
>Priority: Major
>  Labels: pull-request-available
>
> The experimental protobuf driver needs to have function execution added to 
> its API.
> executeFunctionOnServer(s) and executeFunctionOnGroup(s)
> The functionality has already been implemented in the server.



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

[jira] [Assigned] (GEODE-2999) New flow: Put if absent

[Galen O'Sullivan (JIRA)]

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

Galen O'Sullivan reassigned GEODE-2999:
---

Assignee: Galen O'Sullivan

> New flow: Put if absent
> ---
>
> Key: GEODE-2999
> URL: https://issues.apache.org/jira/browse/GEODE-2999
> Project: Geode
>  Issue Type: Sub-task
>  Components: client/server
>Reporter: Brian Baynes
>Assignee: Galen O'Sullivan
>Priority: Major
>
> As a dev using the new protocol, I need to be able to put an entry only if it 
> doesn't already exist in the cache.
> Create proto message definitions and op handler for "put-if-absent" messages.
> Client should receive error if key already exists. Put should only succeed if 
> key did not already exist.
>  



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

[jira] [Updated] (GEODE-4795) User Guide: Inequality queries return UNDEFINED entries

[ASF GitHub Bot (JIRA)]

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

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

> User Guide: Inequality queries return UNDEFINED entries
> ---
>
> Key: GEODE-4795
> URL: https://issues.apache.org/jira/browse/GEODE-4795
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
>  Labels: pull-request-available
>
> The section describing OQL operators 
> [http://geode.apache.org/docs/guide/14/developing/query_additional/operators.html]
>  should state that inequality queries return results for which the search 
> field is UNDEFINED.



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

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

[nabarun (JIRA)]

nabarun created GEODE-4797:
--

 Summary: Categorize all WAN tests as WANTest 
 Key: GEODE-4797
 URL: https://issues.apache.org/jira/browse/GEODE-4797
 Project: Geode
  Issue Type: Bug
  Components: wan
Reporter: nabarun






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

[jira] [Updated] (GEODE-4775) Apply ArgumentRedactor to JVM arguments.

[Barbara Pruijn (JIRA)]

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

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

> Apply ArgumentRedactor to JVM arguments.
> 
>
> Key: GEODE-4775
> URL: https://issues.apache.org/jira/browse/GEODE-4775
> Project: Geode
>  Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>




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

[jira] [Commented] (GEODE-4766) PRCustomPartitioningDUnitTest should be in package org.apache.geode.internal.cache

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4766:


Commit 922ab8363510fea117c14376d90de765d4d5c556 in geode's branch 
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=922ab83 ]

GEODE-4766: move PRCustomPartitioningDUnitTest to internal.cache (#1542)



> PRCustomPartitioningDUnitTest should be in package 
> org.apache.geode.internal.cache
> --
>
> Key: GEODE-4766
> URL: https://issues.apache.org/jira/browse/GEODE-4766
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> PRCustomPartitioningDUnitTest should be in package 
> org.apache.geode.internal.cache



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

[jira] [Updated] (GEODE-4788) change back the behavior of test code of getSomeKeys to ignore exceptions

[xiaojian zhou (JIRA)]

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

xiaojian zhou updated GEODE-4788:
-
Description: 
In GEODE-2673, getSomeKeys' behavior was changed to throw exception when 
detected some exceptions. 

We need to change it back to ignore the exceptions as test code. 

  was:
{noformat}
CLIENT 
vm_12_thr_15_accessor1_rs-FullRegression-2018-03-03-05-01-17-client-8_4804
TASK[0] parReg.execute.FunctionServiceTest.HydraTask_doRandomFunctionExecutions
ERROR util.TestException: Test Issue - Got the exception 

util.TestException: Test Issue - Got the exception 
at parReg.execute.FunctionServiceTest.getSomeKeys(FunctionServiceTest.java:508)
at 
parReg.execute.FunctionServiceTest.doRandomFunctionExecutions(FunctionServiceTest.java:473)
at 
parReg.execute.FunctionServiceTest.HydraTask_doRandomFunctionExecutions(FunctionServiceTest.java:436)
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.execute(MethExecutor.java:181)
at hydra.MethExecutor.execute(MethExecutor.java:149)
at hydra.TestTask.execute(TestTask.java:192)
at hydra.RemoteTestModule$1.run(RemoteTestModule.java:212)
Caused by: java.lang.RuntimeException: 
org.apache.geode.internal.cache.ForceReattemptException: FetchKeysResponse got 
remote CacheClosedException; forcing reattempt.
at 
org.apache.geode.internal.cache.PartitionedRegionGetSomeKeys.getSomeKeys(PartitionedRegionGetSomeKeys.java:74)
at parReg.execute.FunctionServiceTest.getSomeKeys(FunctionServiceTest.java:502)
... 10 more
Caused by: org.apache.geode.internal.cache.ForceReattemptException: 
FetchKeysResponse got remote CacheClosedException; forcing reattempt.
at 
org.apache.geode.internal.cache.partitioned.FetchKeysMessage$FetchKeysResponse.waitForKeys(FetchKeysMessage.java:546)
at 
org.apache.geode.internal.cache.PartitionedRegionGetSomeKeys.getSomeKeys(PartitionedRegionGetSomeKeys.java:66)
... 11 more
Caused by: org.apache.geode.cache.CacheClosedException: Remote cache is closed: 
rs-FullRegression-2018-03-03-05-01-17-client-8(dataStoregemfire5_rs-FullRegression-2018-03-03-05-01-17-client-8_4776:4776):1031
at 
org.apache.geode.internal.cache.GemFireCacheImpl.getCacheClosedException(GemFireCacheImpl.java:1588)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.getCacheClosedException(GemFireCacheImpl.java:1576)
at 
org.apache.geode.internal.cache.partitioned.PartitionMessage.process(PartitionMessage.java:304)
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:1118)
at 
org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109)
at 
org.apache.geode.distributed.internal.ClusterDistributionManager$8$1.run(ClusterDistributionManager.java:943)
at java.lang.Thread.run(Thread.java:748)

CLIENT 
vm_15_thr_29_accessor4_rs-FullRegression-2018-03-03-05-01-17-client-8_4918
TASK[0] parReg.execute.FunctionServiceTest.HydraTask_doRandomFunctionExecutions
ERROR util.TestException: Test Issue - Got the exception 

util.TestException: Test Issue - Got the exception 
at parReg.execute.FunctionServiceTest.getSomeKeys(FunctionServiceTest.java:508)
at 
parReg.execute.FunctionServiceTest.doRandomFunctionExecutions(FunctionServiceTest.java:473)
at 
parReg.execute.FunctionServiceTest.HydraTask_doRandomFunctionExecutions(FunctionServiceTest.java:436)
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.execute(MethExecutor.java:{noformat}

Summary: change back the behavior of test code of getSomeKeys to ignore 
exceptions  (was: parReg.execute.FunctionServiceTest.getSomeKeys failed with 
util.TestException: Test Issue - Got the exception)

> change back the behavior of test code of getSomeKeys to ignore exceptions
> -
>
> Key: GEODE-4788
> URL: https://issues.apache.org/jira/browse/GEODE-4788
> Project: Geode
>  

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

[Kirk Lund (JIRA)]

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

Kirk Lund reassigned GEODE-4796:


Assignee: Kirk Lund

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



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

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

[Kirk Lund (JIRA)]

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

Kirk Lund updated GEODE-4796:
-
Component/s: extensions

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



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

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

[Kirk Lund (JIRA)]

Kirk Lund created GEODE-4796:


 Summary: jdbc-1.0.xsd should exist at 
http://geode.apache.org/schema/jdbc
 Key: GEODE-4796
 URL: https://issues.apache.org/jira/browse/GEODE-4796
 Project: Geode
  Issue Type: Bug
Reporter: Kirk Lund


jdbc-1.0.xsd should added it to the geode-site repo on the asf-site branch:
{noformat}
~/code/geode-site (asf-site)$ find . -name *.xsd
./schema/lucene/lucene-1.0.xsd
./schema/cache/cache-1.0.xsd
{noformat}



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

[jira] [Commented] (GEODE-4793) DUnit tests fail on Windows

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4793:


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

GEODE-4793: Ensure that Files.list() closes resources (#1572)

- This was causing some DUnits to fail on Windows.

> DUnit tests fail on Windows
> ---
>
> Key: GEODE-4793
> URL: https://issues.apache.org/jira/browse/GEODE-4793
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Various tests will fail on Windows with errors similar to the following:
> {noformat}
> [vm0] [error 2018/03/07 04:38:13.670 UTC  Connection(1)-10.32.110.121> tid=19] Error occurred while initializing 
> cluster configuration
> [vm0] java.lang.RuntimeException: Error occurred while initializing cluster 
> configuration
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.getConfigurationRegion(ClusterConfigurationService.java:731)
> [vm0] at 
> org.apache.geode.distributed.internal.ClusterConfigurationService.initSharedConfiguration(ClusterConfigurationService.java:459)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startSharedConfigurationService(InternalLocator.java:1332)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:668)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:647)
> [vm0] at 
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:309)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> [vm0] at 
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:78)
> [vm0] at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:59)
> [vm0] at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$1c67b668$1(ClusterStartupRule.java:157)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> [vm0] at 
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at 
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:361)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> [vm0] Caused by: java.io.IOException: Cannot create directory at 
> C:\Users\Administrator\geode\geode-core\dunit\vm0\ConfigDiskDir_locator-0
> [vm0] at 
> 

[jira] [Assigned] (GEODE-4795) User Guide: Inequality queries return UNDEFINED entries

[Dave Barnes (JIRA)]

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

Dave Barnes reassigned GEODE-4795:
--

Assignee: Dave Barnes

> User Guide: Inequality queries return UNDEFINED entries
> ---
>
> Key: GEODE-4795
> URL: https://issues.apache.org/jira/browse/GEODE-4795
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
>
> The section describing OQL operators 
> [http://geode.apache.org/docs/guide/14/developing/query_additional/operators.html]
>  should state that inequality queries return results for which the search 
> field is UNDEFINED.



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

[jira] [Created] (GEODE-4795) User Guide: Inequality queries return UNDEFINED entries

[Dave Barnes (JIRA)]

Dave Barnes created GEODE-4795:
--

 Summary: User Guide: Inequality queries return UNDEFINED entries
 Key: GEODE-4795
 URL: https://issues.apache.org/jira/browse/GEODE-4795
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Dave Barnes


The section describing OQL operators 
[http://geode.apache.org/docs/guide/14/developing/query_additional/operators.html]
 should state that inequality queries return results for which the search field 
is UNDEFINED.



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

[jira] [Updated] (GEODE-3540) unable to gfsh destroy gateway-sender

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-3540:
--
Component/s: docs

> unable to gfsh destroy gateway-sender
> -
>
> Key: GEODE-3540
> URL: https://issues.apache.org/jira/browse/GEODE-3540
> Project: Geode
>  Issue Type: Bug
>  Components: docs, gfsh, wan
>Reporter: Raphaël Enrici
>Assignee: Sai Boorlagadda
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Dear all,
> while playing with wan setup we found that we are unable to destroy a 
> declared sender configuration.
> You can reproduce this in a simple one node setup with apache geode 1.2.0:
> * start a locator
> * start a server
> * create a gateway-sender
> * destroy the gateway-sender => messages are ok
> * list gateways, the gateway-sender is still here although we just destroyed 
> it
> * if you try to destroy it again, you get "ERROR: GateWaySender with Id  
> sender not found"
> * if you list gateways again, the gateway is still here, you can even start 
> and stop it although it is not functional anymore.
> * restarting the whole cluster does not change anything.
> Maybe we missed something concerning this, if the answer to this is a RTFM 
> one, sorry for the noise.
> Keep up the good work.
> Best,
> Raphaël
> Here are shrinked outputs concerning this problem:
> {quote}
> gfsh> start locator --name=happylocator
> gfsh> start server --name=happyserver1
> gfsh>create gateway-sender --id=sender --remote-distributed-system-id=2
>Member| Status
>  | 
> happyserver1 | GatewaySender "sender" created on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member  | Remote Cluster 
> Id |  Type  | Status  | Queued Events | Receiver Location
>  | --- | 
> - | -- | --- | - | -
> sender   | 192.168.0.6(happyserver1:1689):1025 | 2
>  | Serial | Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
>  | --
> happyserver1 | GatewaySender "sender" destroyed on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member  | Remote Cluster 
> Id |  Type  |   Status| Queued Events | Receiver Location
>  | --- | 
> - | -- | --- | - | -
> sender   | 192.168.0.6(happyserver1:1689):1025 | 2
>  | Serial | Not Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
>  | --
> happyserver1 | ERROR: GateWaySender with Id  sender not found
> gfsh>start gateway-sender --id sender
> Member  | Result | Message
> --- | -- | 
> -
> 192.168.0.6(happyserver1:1689):1025 | OK | GatewaySender sender is 
> started on member 192.168.0.6(happyserv..
> {quote}



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

[jira] [Resolved] (GEODE-4764) NPEs encountered during lucene create index (on existing region)

[Shelley Lynn Hughes-Godfrey (JIRA)]

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

Shelley Lynn Hughes-Godfrey resolved GEODE-4764.

   Resolution: Fixed
Fix Version/s: 1.6.0

Fixed on develop:

{noformat}
commit 70415070443137941ff1c1b750af81cf4442f6ef
Author: Lynn Hughes-Godfrey 
Date:   Thu Mar 1 17:22:23 2018 -0800

GEODE-4764: Address NPEs during Lucene index creation on existing region

* Don't add the aeq to the region until the data region has been created
* When iterating over list of local primary bucketIds (during reindexing), 
check for null return value when retrieving a specific bucket
* Added tests for same.
{noformat}

> NPEs encountered during lucene create index (on existing region)
> 
>
> Key: GEODE-4764
> URL: https://issues.apache.org/jira/browse/GEODE-4764
> Project: Geode
>  Issue Type: Sub-task
>  Components: lucene
>Affects Versions: 1.5.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> There are currently two potential NPEs in LuceneServiceImpl during index 
> creation on an existing region.
> The first occurs when a bucket is moved during indexing:
> {noformat}
> at 
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createLuceneIndexOnDataRegion(LuceneServiceImpl.java:294)
> at 
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndexOnExistingRegion(LuceneServiceImpl.java:277)
> at 
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:257)
> at 
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:226)
> at 
> org.apache.geode.cache.lucene.internal.LuceneIndexFactoryImpl.create(LuceneIndexFactoryImpl.java:70)
> {noformat}
> The second occurs when the LuceneEventListener attempts to process events 
> before the Lucene Index has been fully initialized (and userRegion set).
> {noformat}
> at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:164)
> at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:80)
> at 
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:610)
> at 
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1051)
> Caused by: java.lang.NullPointerException
> at 
> org.apache.geode.cache.lucene.internal.AbstractPartitionedRepositoryManager.getRepository(AbstractPartitionedRepositoryManager.java:70)
> at 
> org.apache.geode.cache.lucene.internal.LuceneEventListener.process(LuceneEventListener.java:86)
> at 
> org.apache.geode.cache.lucene.internal.LuceneEventListener.processEvents(LuceneEventListener.java:63)
> at 
> org.apache.geode.internal.cache.wan.GatewaySenderEventCallbackDispatcher.dispatchBatch(GatewaySenderEventCallbackDispatcher.java:154)
> ... 3 more
> {noformat}



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

[jira] [Resolved] (GEODE-4217) gfsh create jdbc-connection command allows a password to be set without a user name

[Nick Reich (JIRA)]

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

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

> gfsh create jdbc-connection command  allows a password to be set without a 
> user name
> 
>
> Key: GEODE-4217
> URL: https://issues.apache.org/jira/browse/GEODE-4217
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The gfsh create jdbc-connection command  allows a password to be set without 
> a user name.
> If you configure a password you must also configure a user name and this 
> should be validated.



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

[jira] [Commented] (GEODE-4217) gfsh create jdbc-connection command allows a password to be set without a user name

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4217:


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

GEODE-4217: Add validation to CreateConnectionCommand (#1566)

* Do not allow creation of connection if user is null but password is not

> gfsh create jdbc-connection command  allows a password to be set without a 
> user name
> 
>
> Key: GEODE-4217
> URL: https://issues.apache.org/jira/browse/GEODE-4217
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Nick Reich
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The gfsh create jdbc-connection command  allows a password to be set without 
> a user name.
> If you configure a password you must also configure a user name and this 
> should be validated.



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

[jira] [Commented] (GEODE-4779) Categorize OQL Query and Index Tests

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on GEODE-4779:


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

GEODE-4779: Categorize OQLQuery and OQLIndex Tests (#1555)



> Categorize OQL Query and Index Tests
> 
>
> Key: GEODE-4779
> URL: https://issues.apache.org/jira/browse/GEODE-4779
> Project: Geode
>  Issue Type: Task
>  Components: querying
>Reporter: Jason Huynh
>Assignee: Jason Huynh
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Add a new category for tests and mark query and index tests appropriately



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

[jira] [Commented] (GEODE-4788) parReg.execute.FunctionServiceTest.getSomeKeys failed with util.TestException: Test Issue - Got the exception

[Anthony Baker (JIRA)]

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

Anthony Baker commented on GEODE-4788:
--

I think you meant revision cf5f83a2501877b5459c20f3ece6aafe1f6becf2.


> parReg.execute.FunctionServiceTest.getSomeKeys failed with 
> util.TestException: Test Issue - Got the exception
> -
>
> Key: GEODE-4788
> URL: https://issues.apache.org/jira/browse/GEODE-4788
> Project: Geode
>  Issue Type: New Feature
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.6.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> {noformat}
> CLIENT 
> vm_12_thr_15_accessor1_rs-FullRegression-2018-03-03-05-01-17-client-8_4804
> TASK[0] 
> parReg.execute.FunctionServiceTest.HydraTask_doRandomFunctionExecutions
> ERROR util.TestException: Test Issue - Got the exception 
> util.TestException: Test Issue - Got the exception 
> at 
> parReg.execute.FunctionServiceTest.getSomeKeys(FunctionServiceTest.java:508)
> at 
> parReg.execute.FunctionServiceTest.doRandomFunctionExecutions(FunctionServiceTest.java:473)
> at 
> parReg.execute.FunctionServiceTest.HydraTask_doRandomFunctionExecutions(FunctionServiceTest.java:436)
> 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.execute(MethExecutor.java:181)
> at hydra.MethExecutor.execute(MethExecutor.java:149)
> at hydra.TestTask.execute(TestTask.java:192)
> at hydra.RemoteTestModule$1.run(RemoteTestModule.java:212)
> Caused by: java.lang.RuntimeException: 
> org.apache.geode.internal.cache.ForceReattemptException: FetchKeysResponse 
> got remote CacheClosedException; forcing reattempt.
> at 
> org.apache.geode.internal.cache.PartitionedRegionGetSomeKeys.getSomeKeys(PartitionedRegionGetSomeKeys.java:74)
> at 
> parReg.execute.FunctionServiceTest.getSomeKeys(FunctionServiceTest.java:502)
> ... 10 more
> Caused by: org.apache.geode.internal.cache.ForceReattemptException: 
> FetchKeysResponse got remote CacheClosedException; forcing reattempt.
> at 
> org.apache.geode.internal.cache.partitioned.FetchKeysMessage$FetchKeysResponse.waitForKeys(FetchKeysMessage.java:546)
> at 
> org.apache.geode.internal.cache.PartitionedRegionGetSomeKeys.getSomeKeys(PartitionedRegionGetSomeKeys.java:66)
> ... 11 more
> Caused by: org.apache.geode.cache.CacheClosedException: Remote cache is 
> closed: 
> rs-FullRegression-2018-03-03-05-01-17-client-8(dataStoregemfire5_rs-FullRegression-2018-03-03-05-01-17-client-8_4776:4776):1031
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.getCacheClosedException(GemFireCacheImpl.java:1588)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.getCacheClosedException(GemFireCacheImpl.java:1576)
> at 
> org.apache.geode.internal.cache.partitioned.PartitionMessage.process(PartitionMessage.java:304)
> 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:1118)
> at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109)
> at 
> org.apache.geode.distributed.internal.ClusterDistributionManager$8$1.run(ClusterDistributionManager.java:943)
> at java.lang.Thread.run(Thread.java:748)
> 
> CLIENT 
> vm_15_thr_29_accessor4_rs-FullRegression-2018-03-03-05-01-17-client-8_4918
> TASK[0] 
> parReg.execute.FunctionServiceTest.HydraTask_doRandomFunctionExecutions
> ERROR util.TestException: Test Issue - Got the exception 
> util.TestException: Test Issue - Got the exception 
> at 
> parReg.execute.FunctionServiceTest.getSomeKeys(FunctionServiceTest.java:508)
> at 
> parReg.execute.FunctionServiceTest.doRandomFunctionExecutions(FunctionServiceTest.java:473)
> at 
> parReg.execute.FunctionServiceTest.HydraTask_doRandomFunctionExecutions(FunctionServiceTest.java:436)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

[jira] [Updated] (GEODE-4771) Configuring 'auto-serializable-classes' incorrectly sets 'check-portability' as 'true'

[ASF GitHub Bot (JIRA)]

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

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

> Configuring 'auto-serializable-classes' incorrectly sets 'check-portability' 
> as 'true'
> --
>
> Key: GEODE-4771
> URL: https://issues.apache.org/jira/browse/GEODE-4771
> Project: Geode
>  Issue Type: Bug
>  Components: gfsh
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
>  Labels: pull-request-available
>
> According to the documentation, the [configure 
> pdx|https://geode.apache.org/docs/guide/14/tools_modules/gfsh/command-pages/configure.html]
>  command should set the {{check-portability}} parameter as {{false}} when the 
> user configures a list of auto serializable classes through the 
> {{--auto-serializable-classes}} parameter. However, {{check-portability}} 
> parameter is set as {{true}} by default.
> The problematic code is below:
>  
> {code:title=ConfigurePDXCommand.java|borderStyle=solid}
> @CliCommand(value = CliStrings.CONFIGURE_PDX, help = 
> CliStrings.CONFIGURE_PDX__HELP)
> @CliMetaData(relatedTopic = CliStrings.TOPIC_GEODE_REGION)
> @ResourceOperation(resource = ResourcePermission.Resource.CLUSTER, operation 
> = ResourcePermission.Operation.MANAGE)
> public Result configurePDX(
>   ...
>   @CliOption(key = CliStrings.CONFIGURE_PDX__AUTO__SERIALIZER__CLASSES, 
> /* auto-serializable-classes */
>   help = CliStrings.CONFIGURE_PDX__AUTO__SERIALIZER__CLASSES__HELP) 
> String[] patterns, /* the patterns which are matched against domain class 
> names to determine whether they should be serialized, serialization done by 
> the auto-serializer will throw an exception if the object of these classes 
> are not portable to non-java languages */
>   @CliOption(key = 
> CliStrings.CONFIGURE_PDX__PORTABLE__AUTO__SERIALIZER__CLASSES /* 
> portable-auto-serializable-classes */,
>   help = 
> CliStrings.CONFIGURE_PDX__PORTABLE__AUTO__SERIALIZER__CLASSES__HELP) String[] 
> portablePatterns /* the patterns which are matched against domain class names 
> to determine whether they should be serialized */) {
>   ...
>   if (patterns != null) {
>   ReflectionBasedAutoSerializer nonPortableAutoSerializer 
> = new ReflectionBasedAutoSerializer(true, patterns);
>   cache.setPdxSerializer(nonPortableAutoSerializer);
>   ird.addLine("PDX Serializer : " + 
> cache.getPdxSerializer().getClass().getName());
>   ird.addLine("Non portable classes :" + 
> Arrays.toString(patterns));
>   }
> ...
> {code}
> The help text for parameters {{auto-serializable-classes}} and 
> {{portable-auto-serializable-classes}} is also wrong, it's clear that they 
> should be swapped.
>  



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

[jira] [Updated] (GEODE-4792) ArgumentRedactor regex should be rewritten to be more clear.

[Barbara Pruijn (JIRA)]

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

Barbara Pruijn updated GEODE-4792:
--
Component/s: security

> ArgumentRedactor regex should be rewritten to be more clear.
> 
>
> Key: GEODE-4792
> URL: https://issues.apache.org/jira/browse/GEODE-4792
> Project: Geode
>  Issue Type: Improvement
>  Components: security
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> Even though I wrote it and it has a lot of comments, it's still hard to read 
> the ArgumentRedactor's regex.  It should be broken apart for better 
> readability.



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

[jira] [Created] (GEODE-4794) ConfigurePDXCommand Fails When Using Defaults

[JIRA]

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

 Summary: ConfigurePDXCommand Fails When Using Defaults
 Key: GEODE-4794
 URL: https://issues.apache.org/jira/browse/GEODE-4794
 Project: Geode
  Issue Type: Bug
  Components: docs, gfsh
Reporter: Juan José Ramos Cassella


While working on a fix for  GEODE-4771 I've came across another bug: the 
{{configure pdx}} command fails when no parameters are specified, even when we 
state in the [User 
Guide|http://geode.apache.org/docs/guide/14/tools_modules/gfsh/command-pages/configure.html]
 that no parameters are mandatory.

The source code doesn't enforce any of the parameters and, as such, the 
resulting {{XmlEntity}} ends up being empty, so a {{NullPointerException}} is 
thrown when the command tries to persist the changes to the cluster 
configuration service:
{code:java}
[error 2018/03/07 11:07:48.242 GMT locator1  
tid=0x55] error updating cluster configuration for group cluster
java.lang.NullPointerException
at java.io.StringReader.(StringReader.java:50)
at 
org.apache.geode.management.internal.configuration.utils.XmlUtils.createNode(XmlUtils.java:242)
at 
org.apache.geode.management.internal.configuration.utils.XmlUtils.addNewNode(XmlUtils.java:133)
at 
org.apache.geode.distributed.internal.ClusterConfigurationService.addXmlEntity(ClusterConfigurationService.java:204)
at 
org.apache.geode.management.internal.cli.commands.ConfigurePDXCommand.lambda$configurePDX$0(ConfigurePDXCommand.java:131)
at 
org.apache.geode.management.internal.cli.commands.GfshCommand.persistClusterConfiguration(GfshCommand.java:72)
at 
org.apache.geode.management.internal.cli.commands.ConfigurePDXCommand.configurePDX(ConfigurePDXCommand.java:130)
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 
org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
at 
org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
at 
org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
at 
org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
at 
org.apache.geode.management.internal.cli.remote.OnlineCommandProcessor.executeCommand(OnlineCommandProcessor.java:133)
at 
org.apache.geode.management.internal.beans.MemberMBeanBridge.processCommand(MemberMBeanBridge.java:1579)
at 
org.apache.geode.management.internal.beans.MemberMBean.processCommand(MemberMBean.java:412)
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.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
at 
com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193)
at 
com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175)
at 
com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117)
at 
com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54)
at 
com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
at 
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
at 
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
at 
javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
at 
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
at 
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1401)
at 
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)