[jira] [Created] (GEODE-1908) DistributedSystem.connect call not configuring p2p server with SSL

2016-09-16 Thread Hitesh Khamesra (JIRA) 
Hitesh Khamesra created GEODE-1908:
--

 Summary: DistributedSystem.connect call not configuring p2p server 
with SSL
 Key: GEODE-1908
 URL: https://issues.apache.org/jira/browse/GEODE-1908
 Project: Geode
  Issue Type: Bug
  Components: membership
Reporter: Hitesh Khamesra
 Fix For: 2.0.0-incubating


javax.net.ssl.SSLHandshakeException: Remote host closed connection during 
handshake
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:992)
at 
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
at 
sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
at 
org.apache.geode.internal.net.SocketCreator.configureClientSSLSocket(SocketCreator.java:1058)
at 
org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:947)
at 
org.apache.geode.internal.net.SocketCreator.connect(SocketCreator.java:907)
at 
org.apache.geode.internal.net.SocketCreator.connectForServer(SocketCreator.java:888)
at org.apache.geode.internal.tcp.Connection.(Connection.java:1291)
at 
org.apache.geode.internal.tcp.Connection.createSender(Connection.java:1072)
at 
org.apache.geode.internal.tcp.ConnectionTable.handleNewPendingConnection(ConnectionTable.java:366)
at 
org.apache.geode.internal.tcp.ConnectionTable.getUnorderedOrConserveSockets(ConnectionTable.java:482)
at 
org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:669)
at 
org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:965)
at 
org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:560)
at 
org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:327)
at 
org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:620)
at 
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1685)
at 
org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.send(GMSMembershipManager.java:1861)
at 
org.apache.geode.distributed.internal.DistributionChannel.send(DistributionChannel.java:88)
at 
org.apache.geode.distributed.internal.DistributionManager.sendOutgoing(DistributionManager.java:3402)
at 
org.apache.geode.distributed.internal.StartupOperation.sendStartupMessage(StartupOperation.java:75)
at 
org.apache.geode.distributed.internal.DistributionManager.sendStartupMessage(DistributionManager.java:2649)
at 
org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:550)
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:659)
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:299)
at 
org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:237)
at 
hydra.DistributedSystemHelper._connect(DistributedSystemHelper.java:110)
at 
hydra.DistributedSystemHelper.connect(DistributedSystemHelper.java:73)
at hydra.CacheHelper.createCache(CacheHelper.java:95)
at hct.HierCache.initServerRegion(HierCache.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at hydra.MethExecutor.execute(MethExecutor.java:199)
at hydra.MethExecutor.execute(MethExecutor.java:163)
at hydra.TestTask.execute(TestTask.java:195)
at hydra.RemoteTestModule$1.run(RemoteTestModule.java:216)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at sun.security.ssl.InputRecord.read(InputRecord.java:505)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
... 38 more



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (GEODE-1907) QueryDataFunction does not add LIMIT clause if space is missing after FROM clause

2016-09-16 Thread Kirk Lund (JIRA) 

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

Kirk Lund reassigned GEODE-1907:


Assignee: Kirk Lund

> QueryDataFunction does not add LIMIT clause if space is missing after FROM 
> clause
> -
>
> Key: GEODE-1907
> URL: https://issues.apache.org/jira/browse/GEODE-1907
> Project: Geode
>  Issue Type: Bug
>  Components: management, querying
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
>
> Apparently "SELECT * FROM/MyRegion" is a valid query in Geode, however if 
> this query is used from GFSH or Pulse, then QueryDataFunction will fail to 
> add a LIMIT clause because there is no space between FROM and the region name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1906) Misspelled word "Successfuly" is reported in results of QueryDataFunction

2016-09-16 Thread Kirk Lund (JIRA) 

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

Kirk Lund updated GEODE-1906:
-
Priority: Trivial  (was: Major)

> Misspelled word "Successfuly" is reported in results of QueryDataFunction 
> --
>
> Key: GEODE-1906
> URL: https://issues.apache.org/jira/browse/GEODE-1906
> Project: Geode
>  Issue Type: Bug
>  Components: management, querying
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
>
> This misspelling is duplicated a couple more places as well:
> /Users/klund/dev/gemfire/open [504]$ git grep 
> 'Successfuly'
> geode-core/src/main/java/org/apache/geode/management/internal/beans/QueryDataFunction.java:
>   private static String QUERY_EXEC_SUCCESS = "Query Executed Successfuly";
> geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
> "testMetaDataCleanupOnSinglePRNodeFail() Completed Successfuly 
> ..");
> geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
> "testMetaDataCleanupOnMultiplePRNodeFail() Completed Successfuly 
> ..");



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1907) QueryDataFunction does not add LIMIT clause if space is missing after FROM clause

2016-09-16 Thread Kirk Lund (JIRA) 

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

Kirk Lund updated GEODE-1907:
-
Priority: Minor  (was: Major)

> QueryDataFunction does not add LIMIT clause if space is missing after FROM 
> clause
> -
>
> Key: GEODE-1907
> URL: https://issues.apache.org/jira/browse/GEODE-1907
> Project: Geode
>  Issue Type: Bug
>  Components: management, querying
>Reporter: Kirk Lund
>Priority: Minor
>
> Apparently "SELECT * FROM/MyRegion" is a valid query in Geode, however if 
> this query is used from GFSH or Pulse, then QueryDataFunction will fail to 
> add a LIMIT clause because there is no space between FROM and the region name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1907) QueryDataFunction does not add LIMIT clause if space is missing after FROM clause

2016-09-16 Thread Kirk Lund (JIRA) 
Kirk Lund created GEODE-1907:


 Summary: QueryDataFunction does not add LIMIT clause if space is 
missing after FROM clause
 Key: GEODE-1907
 URL: https://issues.apache.org/jira/browse/GEODE-1907
 Project: Geode
  Issue Type: Bug
  Components: management, querying
Reporter: Kirk Lund


Apparently "SELECT * FROM/MyRegion" is a valid query in Geode, however if this 
query is used from GFSH or Pulse, then QueryDataFunction will fail to add a 
LIMIT clause because there is no space between FROM and the region name.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1906) Misspelled word "Successfuly" is reported in results of QueryDataFunction

2016-09-16 Thread Kirk Lund (JIRA) 

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

Kirk Lund updated GEODE-1906:
-
Description: 
Two tests are hardcoded to look for this misspelling:

/Users/klund/dev/gemfire/open [504]$ git grep 
'Successfuly'

geode-core/src/main/java/org/apache/geode/management/internal/beans/QueryDataFunction.java:
  private static String QUERY_EXEC_SUCCESS = "Query Executed Successfuly";

geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
"testMetaDataCleanupOnSinglePRNodeFail() Completed Successfuly 
..");

geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
"testMetaDataCleanupOnMultiplePRNodeFail() Completed Successfuly 
..");


  was:
Two tests are hardcoded to look for this misspelling:
{noformat}
/Users/klund/dev/gemfire/open [504]$ git grep 
'Successfuly'
geode-core/src/main/java/org/apache/geode/management/internal/beans/QueryDataFunction.java:
  private static String QUERY_EXEC_SUCCESS = "Query Executed Successfuly";
geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
"testMetaDataCleanupOnSinglePRNodeFail() Completed Successfuly 
..");
geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
"testMetaDataCleanupOnMultiplePRNodeFail() Completed Successfuly 
..");
{noformat}


> Misspelled word "Successfuly" is reported in results of QueryDataFunction 
> --
>
> Key: GEODE-1906
> URL: https://issues.apache.org/jira/browse/GEODE-1906
> Project: Geode
>  Issue Type: Bug
>  Components: management, querying
>Reporter: Kirk Lund
>
> Two tests are hardcoded to look for this misspelling:
> /Users/klund/dev/gemfire/open [504]$ git grep 
> 'Successfuly'
> geode-core/src/main/java/org/apache/geode/management/internal/beans/QueryDataFunction.java:
>   private static String QUERY_EXEC_SUCCESS = "Query Executed Successfuly";
> geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
> "testMetaDataCleanupOnSinglePRNodeFail() Completed Successfuly 
> ..");
> geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
> "testMetaDataCleanupOnMultiplePRNodeFail() Completed Successfuly 
> ..");



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1906) Misspelled word "Successfuly" is reported in results of QueryDataFunction

2016-09-16 Thread Kirk Lund (JIRA) 
Kirk Lund created GEODE-1906:


 Summary: Misspelled word "Successfuly" is reported in results of 
QueryDataFunction 
 Key: GEODE-1906
 URL: https://issues.apache.org/jira/browse/GEODE-1906
 Project: Geode
  Issue Type: Bug
  Components: management, querying
Reporter: Kirk Lund


Two tests are hardcoded to look for this misspelling:
{noformat}
/Users/klund/dev/gemfire/open [504]$ git grep 
'Successfuly'
geode-core/src/main/java/org/apache/geode/management/internal/beans/QueryDataFunction.java:
  private static String QUERY_EXEC_SUCCESS = "Query Executed Successfuly";
geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
"testMetaDataCleanupOnSinglePRNodeFail() Completed Successfuly 
..");
geode-core/src/test/java/org/apache/geode/internal/cache/PartitionedRegionHAFailureAndRecoveryDUnitTest.java:
"testMetaDataCleanupOnMultiplePRNodeFail() Completed Successfuly 
..");
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1886) StoredObject instanceof checks in EntryEventImpl slow down heap operations

2016-09-16 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-1886:


Commit b7518411d93ded8a8c83af6964ff74acb04a31ac in incubator-geode's branch 
refs/heads/develop from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b751841 ]

GEODE-1886: optimize off-heap reference checks

EntryEventImpl now tests the region's off-heap boolean
before it will ask if the new/old value is an instanceof
StoredObject.


> StoredObject instanceof checks in EntryEventImpl slow down heap operations
> --
>
> Key: GEODE-1886
> URL: https://issues.apache.org/jira/browse/GEODE-1886
> Project: Geode
>  Issue Type: Bug
>  Components: offheap
>Reporter: Darrel Schneider
>Assignee: Darrel Schneider
>
> The instanceof checks added to EntryEventImpl for offheap have slowed down 
> the performance of heap. This slow down will probably only be noticed when 
> the cache operation is local. When the operations is distributed the network 
> adds enough overhead that the extra time in the instanceof checks is not 
> noticed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (GEODE-1904) start server should skip assertAvailablePort if --cache-xml is specified when --server-port is not specified

2016-09-16 Thread Kirk Lund (JIRA) 

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

Kirk Lund resolved GEODE-1904.
--
   Resolution: Invalid
Fix Version/s: 1.0.0-incubating

Closing this ticket because it's an invalid request. 

The current behavior is expected. If --server-port is not specified then start 
server will start a server on the default port 40404. If --server-port is 
specified then it will start a server on the specified port instead. In both 
cases, it will also start listening to additional ports that are specified in 
the cache.xml.

If a user wants to disable the default server on port 40404, then the user must 
specify --disable-default-server.




> start server should skip assertAvailablePort if --cache-xml is specified when 
> --server-port is not specified
> 
>
> Key: GEODE-1904
> URL: https://issues.apache.org/jira/browse/GEODE-1904
> Project: Geode
>  Issue Type: Wish
>  Components: management
>Reporter: Kirk Lund
>Assignee: Swapnil Bawaskar
> Fix For: 1.0.0-incubating
>
>
> 1) start a server with --server-port 40404
> 2) start a 2nd server without specifying --server-port or 
> --disable-default-server but do specify --cache-xml containing a unique 
> server port
> 3) start will fail due to assertAvailablePort
> The error will look something like:
> java.lang.RuntimeException: An IO error occurred while starting a Server in 
> /dx2-office-dhcp32 on dx2-office-dhcp32[40404]: Network is unreachable; port 
> (40404) is not available on localhost.
> Work-around is to specify --disable-default-server in step #2. This will 
> cause it to skip assertAvailablePort(40404).
> I believe it's more intuitive to the user if we also make the change to skip 
> assertAvailablePort(40404) if --cache-xml is specified when --server-port is 
> not  specified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (GEODE-1904) start server should skip assertAvailablePort if --cache-xml is specified when --server-port is not specified

2016-09-16 Thread Kirk Lund (JIRA) 

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

Kirk Lund closed GEODE-1904.


> start server should skip assertAvailablePort if --cache-xml is specified when 
> --server-port is not specified
> 
>
> Key: GEODE-1904
> URL: https://issues.apache.org/jira/browse/GEODE-1904
> Project: Geode
>  Issue Type: Wish
>  Components: management
>Reporter: Kirk Lund
>Assignee: Swapnil Bawaskar
>
> 1) start a server with --server-port 40404
> 2) start a 2nd server without specifying --server-port or 
> --disable-default-server but do specify --cache-xml containing a unique 
> server port
> 3) start will fail due to assertAvailablePort
> The error will look something like:
> java.lang.RuntimeException: An IO error occurred while starting a Server in 
> /dx2-office-dhcp32 on dx2-office-dhcp32[40404]: Network is unreachable; port 
> (40404) is not available on localhost.
> Work-around is to specify --disable-default-server in step #2. This will 
> cause it to skip assertAvailablePort(40404).
> I believe it's more intuitive to the user if we also make the change to skip 
> assertAvailablePort(40404) if --cache-xml is specified when --server-port is 
> not  specified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1904) start server should skip assertAvailablePort if --cache-xml is specified when --server-port is not specified

2016-09-16 Thread Kirk Lund (JIRA) 

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

Kirk Lund updated GEODE-1904:
-
Fix Version/s: (was: 1.0.0-incubating)

> start server should skip assertAvailablePort if --cache-xml is specified when 
> --server-port is not specified
> 
>
> Key: GEODE-1904
> URL: https://issues.apache.org/jira/browse/GEODE-1904
> Project: Geode
>  Issue Type: Wish
>  Components: management
>Reporter: Kirk Lund
>Assignee: Swapnil Bawaskar
>
> 1) start a server with --server-port 40404
> 2) start a 2nd server without specifying --server-port or 
> --disable-default-server but do specify --cache-xml containing a unique 
> server port
> 3) start will fail due to assertAvailablePort
> The error will look something like:
> java.lang.RuntimeException: An IO error occurred while starting a Server in 
> /dx2-office-dhcp32 on dx2-office-dhcp32[40404]: Network is unreachable; port 
> (40404) is not available on localhost.
> Work-around is to specify --disable-default-server in step #2. This will 
> cause it to skip assertAvailablePort(40404).
> I believe it's more intuitive to the user if we also make the change to skip 
> assertAvailablePort(40404) if --cache-xml is specified when --server-port is 
> not  specified.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (GEODE-1899) Address the custom 'clean' gradle task warning

2016-09-16 Thread Jared Stewart (JIRA) 

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

Jared Stewart reassigned GEODE-1899:


Assignee: Jared Stewart  (was: Kirk Lund)

> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1524) Swagger UI does not show query errors

2016-09-16 Thread Hitesh Khamesra (JIRA) 

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

Hitesh Khamesra commented on GEODE-1524:


 4xx Client error –  codes are used to tell the client that a fault has taken 
place on THEIR side. They should not re-transmit the same request again, but 
fix the error first.
5xx Server error – codes that tell the client the server failed to fulfill an 
apparently valid request.  The client can continue and try again with the 
request without modification. 

> Swagger UI does not show query errors
> -
>
> Key: GEODE-1524
> URL: https://issues.apache.org/jira/browse/GEODE-1524
> Project: Geode
>  Issue Type: Improvement
>  Components: rest (dev)
>Reporter: Jens Deppe
>Assignee: Udo Kohlmeyer
>  Labels: bug-hunt
>
> I'm playing with UDA and running adhoc queries through the Swagger UI. 
> However, if I have a catastrophic error in my query the Swagger UI doesn't 
> display it and I'm left with a 'progress spinner' bar. However, the same 
> query from the command line does produce an appropriate error. For example, 
> here I'm trying to use my {{sumuda}} function in a query:
> {noformat}
> (2.7)jdeppe@deppe-mbp bughunt-2016 $ curl -v -H "Accept: application/json" 
> 'http://127.0.0.1:8080/gemfire-api/v1/queries/adhoc?q=select%20sumuda(index)%20from%20%2Ffoo'
> *   Trying 127.0.0.1...
> * Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> > GET /gemfire-api/v1/queries/adhoc?q=select%20sumuda(index)%20from%20%2Ffoo 
> > HTTP/1.1
> > Host: 127.0.0.1:8080
> > User-Agent: curl/7.43.0
> > Accept: application/json
> >
> < HTTP/1.1 500 Server Error
> < Date: Fri, 10 Jun 2016 19:52:26 GMT
> < Content-Type: application/json
> < Accept-Charset: big5, big5-hkscs, cesu-8, euc-jp, euc-kr, gb18030, gb2312, 
> gbk, ibm-thai, ibm00858, ibm01140, ibm01141, ibm01142, ibm01143, ibm01144, 
> ibm01145, ibm01146, ibm01147, ibm01148, ibm01149, ibm037, ibm1026, ibm1047, 
> ibm273, ibm277, ibm278, ibm280, ibm284, ibm285, ibm290, ibm297, ibm420, 
> ibm424, ibm437, ibm500, ibm775, ibm850, ibm852, ibm855, ibm857, ibm860, 
> ibm861, ibm862, ibm863, ibm864, ibm865, ibm866, ibm868, ibm869, ibm870, 
> ibm871, ibm918, iso-2022-cn, iso-2022-jp, iso-2022-jp-2, iso-2022-kr, 
> iso-8859-1, iso-8859-13, iso-8859-15, iso-8859-2, iso-8859-3, iso-8859-4, 
> iso-8859-5, iso-8859-6, iso-8859-7, iso-8859-8, iso-8859-9, jis_x0201, 
> jis_x0212-1990, koi8-r, koi8-u, shift_jis, tis-620, us-ascii, utf-16, 
> utf-16be, utf-16le, utf-32, utf-32be, utf-32le, utf-8, windows-1250, 
> windows-1251, windows-1252, windows-1253, windows-1254, windows-1255, 
> windows-1256, windows-1257, windows-1258, windows-31j, x-big5-hkscs-2001, 
> x-big5-solaris, x-compound_text, x-euc-jp-linux, x-euc-tw, x-eucjp-open, 
> x-ibm1006, x-ibm1025, x-ibm1046, x-ibm1097, x-ibm1098, x-ibm1112, x-ibm1122, 
> x-ibm1123, x-ibm1124, x-ibm1166, x-ibm1364, x-ibm1381, x-ibm1383, x-ibm300, 
> x-ibm33722, x-ibm737, x-ibm833, x-ibm834, x-ibm856, x-ibm874, x-ibm875, 
> x-ibm921, x-ibm922, x-ibm930, x-ibm933, x-ibm935, x-ibm937, x-ibm939, 
> x-ibm942, x-ibm942c, x-ibm943, x-ibm943c, x-ibm948, x-ibm949, x-ibm949c, 
> x-ibm950, x-ibm964, x-ibm970, x-iscii91, x-iso-2022-cn-cns, x-iso-2022-cn-gb, 
> x-iso-8859-11, x-jis0208, x-jisautodetect, x-johab, x-macarabic, 
> x-maccentraleurope, x-maccroatian, x-maccyrillic, x-macdingbat, x-macgreek, 
> x-machebrew, x-maciceland, x-macroman, x-macromania, x-macsymbol, x-macthai, 
> x-macturkish, x-macukraine, x-ms932_0213, x-ms950-hkscs, x-ms950-hkscs-xp, 
> x-mswin-936, x-pck, x-sjis_0213, x-utf-16le-bom, x-utf-32be-bom, 
> x-utf-32le-bom, x-windows-50220, x-windows-50221, x-windows-874, 
> x-windows-949, x-windows-950, x-windows-iso2022jp
> < Content-Length: 5211
> < Server: Jetty(9.3.6.v20151106)
> <
> {"message" : "Server has encountered while executing Adhoc query!", 
> "stackTrace" : 
> "com.gemstone.gemfire.rest.internal.web.exception.GemfireRestException: 
> Server has encountered while executing Adhoc query!
>   at 
> com.gemstone.gemfire.rest.internal.web.controllers.QueryAccessController.runAdhocQuery(QueryAccessController.java:208)
>   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.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:222)
>   at 
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
>   at 
>

[jira] [Updated] (GEODE-1899) Address the custom 'clean' gradle task warning

2016-09-16 Thread Jared Stewart (JIRA) 

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

Jared Stewart updated GEODE-1899:
-
Assignee: Kirk Lund  (was: Jared Stewart)

> Address the custom 'clean' gradle task warning
> --
>
> Key: GEODE-1899
> URL: https://issues.apache.org/jira/browse/GEODE-1899
> Project: Geode
>  Issue Type: Improvement
>  Components: build, management
>Reporter: Jared Stewart
>Assignee: Kirk Lund
>Priority: Minor
>
> Geode cannot be built using the latest release of Gradle: 
> {code}Defining custom 'clean' task when using the standard Gradle lifecycle 
> plugins has been deprecated and is scheduled to be removed in Gradle 3.0{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1905) Address UnknownPropertyException when running tests with Gradle 3.0+

2016-09-16 Thread Jared Stewart (JIRA) 

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

Jared Stewart updated GEODE-1905:
-
Labels: build management  (was: )

> Address UnknownPropertyException when running tests with Gradle 3.0+
> 
>
> Key: GEODE-1905
> URL: https://issues.apache.org/jira/browse/GEODE-1905
> Project: Geode
>  Issue Type: Improvement
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>  Labels: build, management
>
> When executing 'gradle test' with a Gradle version >=3.0, the task fails with 
> the following exception:
> {code}
> FAILURE: Build completed with 15 failures.
> 1: Task failed with an exception.
> ---
> * Where:
> Script 'geode/gradle/test.gradle' line: 22
> * What went wrong:
> Execution failed for task ':extensions/geode-modules:test'.
> > Could not get unknown property 'AvailablePortFinder' for root project 
> > 'geode' of type org.gradle.api.Project.
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> ==
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (GEODE-1905) Address UnknownPropertyException when running tests with Gradle 3.0+

2016-09-16 Thread Jared Stewart (JIRA) 

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

Jared Stewart commented on GEODE-1905:
--

AvailablePortFinder was deprecated in [Gradle 2.8 | 
https://docs.gradle.org/2.8/release-notes#deprecated-classes-and-constants] and 
removed in Gradle 3.0.  

I took a look into how the Gradle project itself dealt with this change, and 
they [use| 
https://github.com/gradle/gradle/blob/2703311c33e8a295ba7ccb29a62ed8be761ef66f/subprojects/internal-performance-testing/src/main/groovy/org/gradle/performance/fixture/HonestProfilerCollector.groovy]
  the Apache MINA library's 
{{[org.apache.mina.util.AvailablePortFinder|https://mina.apache.org/mina-project/apidocs/src-html/org/apache/mina/util/AvailablePortFinder.html]}}
 class.

> Address UnknownPropertyException when running tests with Gradle 3.0+
> 
>
> Key: GEODE-1905
> URL: https://issues.apache.org/jira/browse/GEODE-1905
> Project: Geode
>  Issue Type: Improvement
>Reporter: Jared Stewart
>
> When executing 'gradle test' with a Gradle version >=3.0, the task fails with 
> the following exception:
> {code}
> FAILURE: Build completed with 15 failures.
> 1: Task failed with an exception.
> ---
> * Where:
> Script 'geode/gradle/test.gradle' line: 22
> * What went wrong:
> Execution failed for task ':extensions/geode-modules:test'.
> > Could not get unknown property 'AvailablePortFinder' for root project 
> > 'geode' of type org.gradle.api.Project.
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> ==
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (GEODE-1905) Address UnknownPropertyException when running tests with Gradle 3.0+

2016-09-16 Thread Jared Stewart (JIRA) 

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

Jared Stewart reassigned GEODE-1905:


Assignee: Jared Stewart

> Address UnknownPropertyException when running tests with Gradle 3.0+
> 
>
> Key: GEODE-1905
> URL: https://issues.apache.org/jira/browse/GEODE-1905
> Project: Geode
>  Issue Type: Improvement
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>
> When executing 'gradle test' with a Gradle version >=3.0, the task fails with 
> the following exception:
> {code}
> FAILURE: Build completed with 15 failures.
> 1: Task failed with an exception.
> ---
> * Where:
> Script 'geode/gradle/test.gradle' line: 22
> * What went wrong:
> Execution failed for task ':extensions/geode-modules:test'.
> > Could not get unknown property 'AvailablePortFinder' for root project 
> > 'geode' of type org.gradle.api.Project.
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> ==
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (GEODE-1905) Address UnknownPropertyException when running tests with Gradle 3.0+

2016-09-16 Thread Jared Stewart (JIRA) 

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

Jared Stewart updated GEODE-1905:
-
Description: 
When executing 'gradle test' with a Gradle version >=3.0, the task fails with 
the following exception:

{code}
FAILURE: Build completed with 15 failures.

1: Task failed with an exception.
---
* Where:
Script 'geode/gradle/test.gradle' line: 22

* What went wrong:
Execution failed for task ':extensions/geode-modules:test'.
> Could not get unknown property 'AvailablePortFinder' for root project 'geode' 
> of type org.gradle.api.Project.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output.
==
{code}

  was:
When executing 'gradle test' with a Gradle version >=3.0, the task fail with 
the following exception:

{code}
FAILURE: Build completed with 15 failures.

1: Task failed with an exception.
---
* Where:
Script 'geode/gradle/test.gradle' line: 22

* What went wrong:
Execution failed for task ':extensions/geode-modules:test'.
> Could not get unknown property 'AvailablePortFinder' for root project 'geode' 
> of type org.gradle.api.Project.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output.
==
{code}


> Address UnknownPropertyException when running tests with Gradle 3.0+
> 
>
> Key: GEODE-1905
> URL: https://issues.apache.org/jira/browse/GEODE-1905
> Project: Geode
>  Issue Type: Improvement
>Reporter: Jared Stewart
>
> When executing 'gradle test' with a Gradle version >=3.0, the task fails with 
> the following exception:
> {code}
> FAILURE: Build completed with 15 failures.
> 1: Task failed with an exception.
> ---
> * Where:
> Script 'geode/gradle/test.gradle' line: 22
> * What went wrong:
> Execution failed for task ':extensions/geode-modules:test'.
> > Could not get unknown property 'AvailablePortFinder' for root project 
> > 'geode' of type org.gradle.api.Project.
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output.
> ==
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (GEODE-1905) Address UnknownPropertyException when running tests with Gradle 3.0+

2016-09-16 Thread Jared Stewart (JIRA) 
Jared Stewart created GEODE-1905:


 Summary: Address UnknownPropertyException when running tests with 
Gradle 3.0+
 Key: GEODE-1905
 URL: https://issues.apache.org/jira/browse/GEODE-1905
 Project: Geode
  Issue Type: Improvement
Reporter: Jared Stewart


When executing 'gradle test' with a Gradle version >=3.0, the task fail with 
the following exception:

{code}
FAILURE: Build completed with 15 failures.

1: Task failed with an exception.
---
* Where:
Script 'geode/gradle/test.gradle' line: 22

* What went wrong:
Execution failed for task ':extensions/geode-modules:test'.
> Could not get unknown property 'AvailablePortFinder' for root project 'geode' 
> of type org.gradle.api.Project.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output.
==
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)