[jira] [Created] (GEODE-3019) Refactor Struct

2017-06-01 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-3019:
---

 Summary: Refactor Struct
 Key: GEODE-3019
 URL: https://issues.apache.org/jira/browse/GEODE-3019
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett


Refactor Struct (geode/Struct.hpp):
* Replace {{char *}} with {{std::string}}
* Replace {{m_fieldname}} type with {{std::unordered_map}}
* Add vector for index to field name lookup.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client

2017-05-11 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2891:
-

[~gregvo] You need to make sure that issues you report are for the open source 
project and not for the close source commercial offering. For support on the 
commercial offering you need to go through support channels. You issue has been 
marked resolved as Invalid. I you can correct the issue you can re-open it.

> connect-timeout violation in C++ Native Client
> --
>
> Key: GEODE-2891
> URL: https://issues.apache.org/jira/browse/GEODE-2891
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Gregory Vortman
> Attachments: gemfire-connect-timeout-violation.docx
>
>
> 1.C++ native client doesn’t honour read-timeout-milli-sec in a consistent 
> way while connecting to a server
> 2.The lock on the connection pool has a very high granularity. Even if 
> the client can’t connect to one server, all other threads which are working 
> with totally different servers get affected by it



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

2017-05-11 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2891:

Fix Version/s: (was: 1.1.1)

> connect-timeout violation in C++ Native Client
> --
>
> Key: GEODE-2891
> URL: https://issues.apache.org/jira/browse/GEODE-2891
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Gregory Vortman
> Attachments: gemfire-connect-timeout-violation.docx
>
>
> 1.C++ native client doesn’t honour read-timeout-milli-sec in a consistent 
> way while connecting to a server
> 2.The lock on the connection pool has a very high granularity. Even if 
> the client can’t connect to one server, all other threads which are working 
> with totally different servers get affected by it



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Closed] (GEODE-2832) Fixing the link of README.md

2017-05-08 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett closed GEODE-2832.
---

> Fixing the link of README.md
> 
>
> Key: GEODE-2832
> URL: https://issues.apache.org/jira/browse/GEODE-2832
> Project: Geode
>  Issue Type: Bug
>  Components: docs, native client
>Reporter: Masaki Yamakawa
>Assignee: Jacob S. Barrett
>Priority: Minor
>
> Fixed an error in Markdown link notation of README.md.
> - Delete the space between the display name and the destination URL.
> - Fixed link destination of native-client-intro.html
> - Fixed link of BUILDING.md



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2832) Fixing the link of README.md

2017-05-08 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2832.
-
Resolution: Fixed

> Fixing the link of README.md
> 
>
> Key: GEODE-2832
> URL: https://issues.apache.org/jira/browse/GEODE-2832
> Project: Geode
>  Issue Type: Bug
>  Components: docs, native client
>Reporter: Masaki Yamakawa
>Assignee: Jacob S. Barrett
>Priority: Minor
>
> Fixed an error in Markdown link notation of README.md.
> - Delete the space between the display name and the destination URL.
> - Fixed link destination of native-client-intro.html
> - Fixed link of BUILDING.md



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2832) Fixing the link of README.md

2017-05-08 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2832:
---

Assignee: Jacob S. Barrett

> Fixing the link of README.md
> 
>
> Key: GEODE-2832
> URL: https://issues.apache.org/jira/browse/GEODE-2832
> Project: Geode
>  Issue Type: Bug
>  Components: docs, native client
>Reporter: Masaki Yamakawa
>Assignee: Jacob S. Barrett
>Priority: Minor
>
> Fixed an error in Markdown link notation of README.md.
> - Delete the space between the display name and the destination URL.
> - Fixed link destination of native-client-intro.html
> - Fixed link of BUILDING.md



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Closed] (GEODE-2807) Replace SharedPtr with std::shared_ptr

2017-05-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett closed GEODE-2807.
---

> Replace SharedPtr with std::shared_ptr
> --
>
> Key: GEODE-2807
> URL: https://issues.apache.org/jira/browse/GEODE-2807
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Replace proprietary SharePtr with C++11 std::shared_ptr.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2807) Replace SharedPtr with std::shared_ptr

2017-05-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2807.
-
Resolution: Duplicate

> Replace SharedPtr with std::shared_ptr
> --
>
> Key: GEODE-2807
> URL: https://issues.apache.org/jira/browse/GEODE-2807
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Replace proprietary SharePtr with C++11 std::shared_ptr.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2741) Use C++11 shared pointer over custom shared pointer

2017-05-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2741:
-

Docs Changes
* All references to {{SharedPtr}} need to be replaced with 
[{{std::shared_ptr}}|http://en.cppreference.com/w/cpp/memory/shared_ptr] 
(suggest using this link too)
* All {{\*Ptr}} typedefs replaced with explicit {{std::shared_ptr<\*>}}. For 
example, {{CacheableStringPtr}} is now {{std::shared_ptr}}. 
(not complete)


> Use C++11 shared pointer over custom shared pointer
> ---
>
> Key: GEODE-2741
> URL: https://issues.apache.org/jira/browse/GEODE-2741
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Addison
>Assignee: Jacob S. Barrett
>
> *Context*
> Now that the Native Client is compatible with C++11, we can use its shared 
> pointer over the custom shared pointer we use today.
> *Definition of Done*
> The custom shared pointer is nowhere to be found in the codebase



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2741) Use C++11 shared pointer over custom shared pointer

2017-05-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2741:
---

Assignee: Jacob S. Barrett

> Use C++11 shared pointer over custom shared pointer
> ---
>
> Key: GEODE-2741
> URL: https://issues.apache.org/jira/browse/GEODE-2741
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Addison
>Assignee: Jacob S. Barrett
>
> *Context*
> Now that the Native Client is compatible with C++11, we can use its shared 
> pointer over the custom shared pointer we use today.
> *Definition of Done*
> The custom shared pointer is nowhere to be found in the codebase



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2877) Auth handler: "Cannot pass a GCHandle across AppDomains" in GemStone::GemFire::Cache::IAuthInitialize

2017-05-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2877.
-
Resolution: Fixed

> Auth handler: "Cannot pass a GCHandle across AppDomains" in 
> GemStone::GemFire::Cache::IAuthInitialize
> -
>
> Key: GEODE-2877
> URL: https://issues.apache.org/jira/browse/GEODE-2877
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> If cache authentication module is initialized in AppDomain X and client in 
> AppDomain Y tries to authenticate then the callback results in a {{Cannot 
> pass a GCHandle across AppDomains}} error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Closed] (GEODE-2877) Auth handler: "Cannot pass a GCHandle across AppDomains" in GemStone::GemFire::Cache::IAuthInitialize

2017-05-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett closed GEODE-2877.
---

> Auth handler: "Cannot pass a GCHandle across AppDomains" in 
> GemStone::GemFire::Cache::IAuthInitialize
> -
>
> Key: GEODE-2877
> URL: https://issues.apache.org/jira/browse/GEODE-2877
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> If cache authentication module is initialized in AppDomain X and client in 
> AppDomain Y tries to authenticate then the callback results in a {{Cannot 
> pass a GCHandle across AppDomains}} error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Closed] (GEODE-2814) Native client test framework uses Xerces which depends on Curl

2017-05-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett closed GEODE-2814.
---

> Native client test framework uses Xerces which depends on Curl
> --
>
> Key: GEODE-2814
> URL: https://issues.apache.org/jira/browse/GEODE-2814
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jens Deppe
>
> The native client driver uses Xerces which is being built with a dependency 
> on Curl.  This can cause link problems due to availability of compatible 
> version
> of Curl being available.  Curl is not utilized by the Framework/Xerces and can
> be built without Curl.  Removing Curl dependency will avoid potential problems
> in the future.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2877) Auth handler: "Cannot pass a GCHandle across AppDomains" in GemStone::GemFire::Cache::IAuthInitialize

2017-05-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2877:
---

Assignee: Jacob S. Barrett

> Auth handler: "Cannot pass a GCHandle across AppDomains" in 
> GemStone::GemFire::Cache::IAuthInitialize
> -
>
> Key: GEODE-2877
> URL: https://issues.apache.org/jira/browse/GEODE-2877
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> If cache authentication module is initialized in AppDomain X and client in 
> AppDomain Y tries to authenticate then the callback results in a {{Cannot 
> pass a GCHandle across AppDomains}} error.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2814) Native client test framework uses Xerces which depends on Curl

2017-05-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2814.
-
   Resolution: Fixed
Fix Version/s: (was: 1.1.1)

> Native client test framework uses Xerces which depends on Curl
> --
>
> Key: GEODE-2814
> URL: https://issues.apache.org/jira/browse/GEODE-2814
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jens Deppe
>
> The native client driver uses Xerces which is being built with a dependency 
> on Curl.  This can cause link problems due to availability of compatible 
> version
> of Curl being available.  Curl is not utilized by the Framework/Xerces and can
> be built without Curl.  Removing Curl dependency will avoid potential problems
> in the future.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2877) Auth handler: "Cannot pass a GCHandle across AppDomains" in GemStone::GemFire::Cache::IAuthInitialize

2017-05-04 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2877:
---

 Summary: Auth handler: "Cannot pass a GCHandle across AppDomains" 
in GemStone::GemFire::Cache::IAuthInitialize
 Key: GEODE-2877
 URL: https://issues.apache.org/jira/browse/GEODE-2877
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Jacob S. Barrett


If cache authentication module is initialized in AppDomain X and client in 
AppDomain Y tries to authenticate then the callback results in a {{Cannot pass 
a GCHandle across AppDomains}} error.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2873) IllegalStateException when exception has non-ASCII characters.

2017-05-03 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2873.
-
Resolution: Fixed

> IllegalStateException when exception has non-ASCII characters.
> --
>
> Key: GEODE-2873
> URL: https://issues.apache.org/jira/browse/GEODE-2873
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>
> If exception from server contains non-ASCII characters the exception handler 
> gets IllegalStateException when trying to get the {{char*}} representation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2873) IllegalStateException when exception has non-ASCII characters.

2017-05-03 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2873:
---

 Summary: IllegalStateException when exception has non-ASCII 
characters.
 Key: GEODE-2873
 URL: https://issues.apache.org/jira/browse/GEODE-2873
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Jacob S. Barrett


If exception from server contains non-ASCII characters the exception handler 
gets IllegalStateException when trying to get the {{char*}} representation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2713) Function execution can lead to passing the address of a stack variable

2017-04-28 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2713.
-
Resolution: Fixed

> Function execution can lead to passing the address of a stack variable
> --
>
> Key: GEODE-2713
> URL: https://issues.apache.org/jira/browse/GEODE-2713
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Michael Dodge
>
> In ThinClientRegion::executeFunctionSH(), the address of a stack variable 
> (the result collector lock) is passed to the workers. If an exception occurs 
> with any of the workers, the function will return, causing the stack variable 
> to be destructed. Since the workers have the raw address, it is now a 
> dangling pointer situation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2835) Autoboxing unsigned primitives in .NET results in stack overflow.

2017-04-27 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2835:
---

 Summary: Autoboxing unsigned primitives in .NET results in stack 
overflow.
 Key: GEODE-2835
 URL: https://issues.apache.org/jira/browse/GEODE-2835
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Jacob S. Barrett


When using a PdxSerializer, like ReflectionBasedPdxSerializer that writes 
unsigned primitive types to fields it results in autoboxing those types and 
looping them back to the PdxSerializer. This can result in an infinite 
recursion and stack overflow. 

{noformat}
Serializer.RegisterPdxSerializer(new ReflectionBasedPdxSerializer());
region.put("a", new Guid());
{noformat}

Guid contains several fields, some of which are {{unsigned char}} which autobox 
to {{System::Byte}}, this gets forwarded back to the auto pdx serializer which 
sees field {{unsigned char m_value}} and autoboxes it again to {{System::Byte}} 
and ..





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2833) IPdxSerializable objects don't deserialize after custom PdxSerializer is registered.

2017-04-27 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2833:
-

See clicache/Serializable.cpp:getPdxType.

> IPdxSerializable objects don't deserialize after custom PdxSerializer is 
> registered.
> 
>
> Key: GEODE-2833
> URL: https://issues.apache.org/jira/browse/GEODE-2833
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Registing a {IPdxSerializer} disables deserialization of {IPdxSerializable} 
> classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2833) IPdxSerializable objects don't deserialize after custom PdxSerializer is registered.

2017-04-27 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2833:
---

 Summary: IPdxSerializable objects don't deserialize after custom 
PdxSerializer is registered.
 Key: GEODE-2833
 URL: https://issues.apache.org/jira/browse/GEODE-2833
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Jacob S. Barrett


Registing a {IPdxSerializer} disables deserialization of {IPdxSerializable} 
classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2807) Replace SharedPtr with std::shared_ptr

2017-04-21 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2807:
-

Docs Changes
* All references to {{SharedPtr}} need to be replaced with 
[{{std::shared_ptr}}|http://en.cppreference.com/w/cpp/memory/shared_ptr] 
(suggest using this link too)
* All {{*Ptr}} typedefs replaced with explicit {{std::shared_ptr<*>}}. For 
example, {{CacheableStringPtr}} is now {{std::shared_ptr}}. 
(not complete)


> Replace SharedPtr with std::shared_ptr
> --
>
> Key: GEODE-2807
> URL: https://issues.apache.org/jira/browse/GEODE-2807
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Replace proprietary SharePtr with C++11 std::shared_ptr.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2807) Replace SharedPtr with std::shared_ptr

2017-04-21 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2807:
---

 Summary: Replace SharedPtr with std::shared_ptr
 Key: GEODE-2807
 URL: https://issues.apache.org/jira/browse/GEODE-2807
 Project: Geode
  Issue Type: Improvement
  Components: native client
Reporter: Jacob S. Barrett


Replace proprietary SharePtr with C++11 std::shared_ptr.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2733) Crash during initialization using Xcode 8.3

2017-04-11 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2733:
-

[~mmartell] Please include references to filed bug report.


> Crash during initialization using Xcode 8.3
> ---
>
> Key: GEODE-2733
> URL: https://issues.apache.org/jira/browse/GEODE-2733
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Michael Dodge
>
> Circa 27 March 2017, Apple released the macOS 10.12.4 and Xcode 8.3 updates. 
> After applying those updates, all native client executables (e.g., unit 
> tests, integration tests, quickstarts) crashes with a SIGSEGV/EXC_BAD_ACCESS 
> with pthread_mutex_lock() which is part of the initialization of the ACE 
> libraries. We don't know whether it's caused by an incompatibility between 
> ACE and the 10.12.4 runtimes (e.g., a struct has changed in size) or if it's 
> an actual bug in the runtimes. Mike Martell found a bug that has already been 
> filed with Apple about Emacs crashing with pthread-related problems after 
> this update, so our current theory is that there's a problem in the pthreads 
> library from Apple.
> UPDATE: Dave Barnes installed just macOS 10.12.4 and has had no problems. 
> Thus, it appears that Xcode 8.3 is the culprit. Anecdotal evidence suggests 
> that Xcode 8.3 has other problems, too, which may or may not be related to 
> the crashes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2759) Update sqlite download to https

2017-04-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2759.
-
Resolution: Fixed

> Update sqlite download to https
> ---
>
> Key: GEODE-2759
> URL: https://issues.apache.org/jira/browse/GEODE-2759
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Update sqlite download to https



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2759) Update sqlite download to https

2017-04-06 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2759:
---

 Summary: Update sqlite download to https
 Key: GEODE-2759
 URL: https://issues.apache.org/jira/browse/GEODE-2759
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett


Update sqlite download to https



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2758) Solaris SPARC assembly not found at configure time.

2017-04-06 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2758:
---

 Summary: Solaris SPARC assembly not found at configure time.
 Key: GEODE-2758
 URL: https://issues.apache.org/jira/browse/GEODE-2758
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett


The path to the SPARC assembly file is incorrect in the CMakeList.txt for 
cppcache.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2755) Solaris images need Oracle support certificate/key

2017-04-05 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2755.
-
Resolution: Fixed

> Solaris images need Oracle support certificate/key
> --
>
> Key: GEODE-2755
> URL: https://issues.apache.org/jira/browse/GEODE-2755
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Solaris images need Oracle support certificate/key to download Solaris 
> Studio. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2755) Solaris images need Oracle support certificate/key

2017-04-05 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2755:
---

 Summary: Solaris images need Oracle support certificate/key
 Key: GEODE-2755
 URL: https://issues.apache.org/jira/browse/GEODE-2755
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett


Solaris images need Oracle support certificate/key to download Solaris Studio. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2714) Proposal for new api on Function interface

2017-03-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2714:
-

How about an annotation rather than an interface change?

{noformat}
@AquirePrimaryBucketReadLock
class MyFunction  {
}
{noformat}

Whatever the name is, be explicit about what it does in the name.
Other options are more generic annotation 
{{@AquirePrimaryBucketLock(Read|Write))}}.



> Proposal for new api on Function interface
> --
>
> Key: GEODE-2714
> URL: https://issues.apache.org/jira/browse/GEODE-2714
> Project: Geode
>  Issue Type: Bug
>  Components: functions
>Reporter: Hitesh Khamesra
>
> Function execution is the most useful feature of Geode. It allows you to 
> execute a user-defined function on the node which holds the primary bucket of 
> the partition region. In many cases application has colocated partition 
> regions and using function application can operate on all the colocated 
> primary buckets.
> In that function, the application makes sure that no other thread is 
> operating on same colocated keys. But during bucket rebalance there is a 
> possibility that two thread might be executing a function on the same set of 
> keys on different nodes.
> It can happen as we don't take the lock(read-lock) on a primary bucket while 
> executing the function. That allows Geode to move bucket for rebalancing.
> Proposal: Introduce the following api on Function interface to indicate the 
> need to primariness.
> boolean needPrimaryLock(); // name suggestion?
> The application would return true if they need a lock on the primary bucket. 
> Default would be false.
> Geode would call the interface and try to take readLock before executing the 
> function on that node. Otherwise, it will throw the exception and let app 
> re-execute that function.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2706) Compiler warning on use of C++14 deprecated attribute with C++11 target.

2017-03-22 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2706.
-
Resolution: Fixed

> Compiler warning on use of C++14 deprecated attribute with C++11 target.
> 
>
> Key: GEODE-2706
> URL: https://issues.apache.org/jira/browse/GEODE-2706
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> {{warning: use of the 'deprecated' attribute is a C++14 extension 
> [-Wc++14-extensions]}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2706) Compiler warning on use of C++14 deprecated attribute with C++11 target.

2017-03-22 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2706:
---

 Summary: Compiler warning on use of C++14 deprecated attribute 
with C++11 target.
 Key: GEODE-2706
 URL: https://issues.apache.org/jira/browse/GEODE-2706
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett


{{{warning: use of the 'deprecated' attribute is a C++14 extension 
[-Wc++14-extensions]}}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2706) Compiler warning on use of C++14 deprecated attribute with C++11 target.

2017-03-22 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2706:

Description: {{warning: use of the 'deprecated' attribute is a C++14 
extension [-Wc++14-extensions]}}  (was: {{{warning: use of the 'deprecated' 
attribute is a C++14 extension [-Wc++14-extensions]}}})

> Compiler warning on use of C++14 deprecated attribute with C++11 target.
> 
>
> Key: GEODE-2706
> URL: https://issues.apache.org/jira/browse/GEODE-2706
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> {{warning: use of the 'deprecated' attribute is a C++14 extension 
> [-Wc++14-extensions]}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2691) Function execution failure with property disable-chunk-handler-thread enabled.

2017-03-20 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2691:
-

Some background gained on this property is that it was added to provide a 
performance increase on function/query responses that contained lots of little 
messages where the overhead of enqueuing them on the thread pool was more 
costly than processing them inline.

With this background in mind I am in favor of dropping this property to reduce 
the test matrix. A small performance increase is not worth the complexity of 
having two different ways of processing responses. Alternatively solutions, 
such as improving the threading/queuing data structures, should be investigated 
in the future.

> Function execution failure with property disable-chunk-handler-thread enabled.
> --
>
> Key: GEODE-2691
> URL: https://issues.apache.org/jira/browse/GEODE-2691
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Critical
>
> If property {{disable-chunk-handler-thread}} enabled the function execution 
> fails with
> {{Unknown message type 61 in response, possible serialization mismatch}} 
> message.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2657) Execute Region Function sends incorrect message format

2017-03-20 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2657.
-
Resolution: Fixed

> Execute Region Function sends incorrect message format
> --
>
> Key: GEODE-2657
> URL: https://issues.apache.org/jira/browse/GEODE-2657
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: David Kimura
>Assignee: Jacob S. Barrett
>
> `TcrMessageExecuteRegionFunction` is missing a call to set `m_hasResults`. 
> This causes the message response to be parsed synchronously and not 
> asynchronously chunked. The synchronous parser does not support this message 
> type and it barfs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2691) Function execution failure with property disable-chunk-handler-thread enabled.

2017-03-20 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2691:

Priority: Critical  (was: Major)

> Function execution failure with property disable-chunk-handler-thread enabled.
> --
>
> Key: GEODE-2691
> URL: https://issues.apache.org/jira/browse/GEODE-2691
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Priority: Critical
>
> If property {{disable-chunk-handler-thread}} enabled the function execution 
> fails with
> {{Unknown message type 61 in response, possible serialization mismatch}} 
> message.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2691) Function execution failure with property disable-chunk-handler-thread enabled.

2017-03-20 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2691:
---

Assignee: Jacob S. Barrett

> Function execution failure with property disable-chunk-handler-thread enabled.
> --
>
> Key: GEODE-2691
> URL: https://issues.apache.org/jira/browse/GEODE-2691
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>Priority: Critical
>
> If property {{disable-chunk-handler-thread}} enabled the function execution 
> fails with
> {{Unknown message type 61 in response, possible serialization mismatch}} 
> message.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2602) Resolve C++11 and minimum support compilers discrepancies

2017-03-07 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2602:
-

[~ahuddy] I strongly disagree with changing this issue to a *wish*. The C++ 
client makes claims to be C++11 based but can't use some of the most basic 
functionality of C++11 due to constraints placed on it by documentation stating 
a minimum set of compilers that are in turn not fully C++11 compliant. 

> Resolve C++11 and minimum support compilers discrepancies
> -
>
> Key: GEODE-2602
> URL: https://issues.apache.org/jira/browse/GEODE-2602
> Project: Geode
>  Issue Type: Wish
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Referencing BUILDING.md our target language is C++11 and we state:
> {noformat}
> ### Required Tools
> * C++11 compiler *(see platform specific requirements)*
> {noformat}
> The problem is that our platform specific requirements do not meet the 
> minimum standards for C++11 compilers. 
> *Linux - GCC 4.8.1+*
> https://gcc.gnu.org/projects/cxx-status.html#cxx11
> Our Travis CI compiles on Linux using GCC 4.9.1.
> _Current listed minimum, 4.6,  does not support many of the C++11 features 
> currently in our source._
> *MacOS X - clang 3.3+*
> https://clang.llvm.org/cxx_status.html
> *Solaris - Solaris Studio 12.5+*
> https://docs.oracle.com/cd/E60778_01/html/E60746/bkabe.html#OSSCPgnyio
> _Currently listed minimum, 12.4, [does not 
> support|https://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#scrolltoc]
>  many concurrent features like std::atomic necessary to remove platform 
> specific concurrency code._
> *Windows - Visual Studio 2015*
> https://msdn.microsoft.com/en-us/library/hh567368(v=vs.140).aspx
> _Currently listed minimum, 2013, does not support many of the C++11 features, 
> like std::atomic_flag, necessary to remove platform specific concurrency 
> code._



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2525) Replace random number implementation with C++11 standards

2017-03-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2525:
---

Assignee: Jacob S. Barrett

> Replace random number implementation with C++11 standards
> -
>
> Key: GEODE-2525
> URL: https://issues.apache.org/jira/browse/GEODE-2525
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> Remove Mersenne Twister implementation from source. Use C++11 random where 
> appropriate. Refactor random usage to be thread safe as applicable. GsRansom 
> uses spin lock to protect. Consider thread local random.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2525) Replace random number implementation with C++11 standards

2017-03-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2525:

Issue Type: Task  (was: Bug)

> Replace random number implementation with C++11 standards
> -
>
> Key: GEODE-2525
> URL: https://issues.apache.org/jira/browse/GEODE-2525
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> Remove Mersenne Twister implementation from source. Use C++11 random where 
> appropriate. Refactor random usage to be thread safe as applicable. GsRansom 
> uses spin lock to protect. Consider thread local random.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2509) Build failed at openSUSE LEAP 42.2

2017-03-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2509:
-

Rather than attaching a patch would you be willing to open a pull request?

> Build failed at openSUSE LEAP 42.2
> --
>
> Key: GEODE-2509
> URL: https://issues.apache.org/jira/browse/GEODE-2509
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Danilo Chang
>Priority: Minor
> Attachments: fix_build_opensuse.patch
>
>
> geode-native C++ client build failed at openSUSE LEAP 42.2, because the 
> library folder name is different at 32bit or 64bit environment (lib64 at 
> 64bit environment and lib at 32bit environment). Now 2 components has this 
> issue, libxml2 and xerces-c.
> The attachment file is the solution I try to fix this issue (use --libdir to 
> specify the path). However, I don't know Geode native C++ client prefer to 
> use the same lib folder name or not. So I create this JIRA item.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2493) Replace the locking and CAS operations provided in HostAsm with C++11 standards

2017-03-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2493:
---

Assignee: Jacob S. Barrett

> Replace the locking and CAS operations provided in HostAsm with C++11 
> standards
> ---
>
> Key: GEODE-2493
> URL: https://issues.apache.org/jira/browse/GEODE-2493
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> Several platform specific locking and CAS operations are implemented in 
> HostAsm and related files. These are not portable and require porting 
> efforts. They are also not well tested. Converting the C++11 standards allows 
> the compiler to choose the code or instructions that optimize the behavior 
> required. Most if not all of the functions these files provide can be 
> replaced with C++11 standard functions.
> Some Examples:
> On Solaris SPARC we have inline assembly.
> On Solaris x86 we use Solaris specific runtime functions.
> On Windows we use really old Win32 functions that have some non-standard 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2317) native client cmake build should honor GEODE_HOME environment variable

2017-03-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2317.
-
Resolution: Fixed

> native client cmake build should honor GEODE_HOME environment variable
> --
>
> Key: GEODE-2317
> URL: https://issues.apache.org/jira/browse/GEODE-2317
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Dan Smith
>Assignee: Jacob S. Barrett
>
> The native client build currently looks for a GEODE_ROOT variable. However, 
> the convention in the java project and the geode-examples is to use a 
> GEODE_HOME environment variable to specify the location of geode. The native 
> client build should look for this environment variable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2602) Resolve C++11 and minimum support compilers discrepancies

2017-03-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2602:
-

feature/GEODE-2602 rolls up the attached blocked tickets.

> Resolve C++11 and minimum support compilers discrepancies
> -
>
> Key: GEODE-2602
> URL: https://issues.apache.org/jira/browse/GEODE-2602
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Referencing BUILDING.md our target language is C++11 and we state:
> {noformat}
> ### Required Tools
> * C++11 compiler *(see platform specific requirements)*
> {noformat}
> The problem is that our platform specific requirements do not meet the 
> minimum standards for C++11 compilers. 
> *Linux - GCC 4.8.1+*
> https://gcc.gnu.org/projects/cxx-status.html#cxx11
> Our Travis CI compiles on Linux using GCC 4.9.1.
> _Current listed minimum, 4.6,  does not support many of the C++11 features 
> currently in our source._
> *MacOS X - clang 3.3+*
> https://clang.llvm.org/cxx_status.html
> *Solaris - Solaris Studio 12.5+*
> https://docs.oracle.com/cd/E60778_01/html/E60746/bkabe.html#OSSCPgnyio
> _Currently listed minimum, 12.4, [does not 
> support|https://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#scrolltoc]
>  many concurrent features like std::atomic necessary to remove platform 
> specific concurrency code._
> *Windows - Visual Studio 2015*
> https://msdn.microsoft.com/en-us/library/hh567368(v=vs.140).aspx
> _Currently listed minimum, 2013, does not support many of the C++11 features, 
> like std::atomic_flag, necessary to remove platform specific concurrency 
> code._



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2602) Resolve C++11 and minimum support compilers discrepancies

2017-03-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2602:

Description: 
Referencing BUILDING.md our target language is C++11 and we state:
{noformat}
### Required Tools
* C++11 compiler *(see platform specific requirements)*
{noformat}

The problem is that our platform specific requirements do not meet the minimum 
standards for C++11 compilers. 

*Linux - GCC 4.8.1+*
https://gcc.gnu.org/projects/cxx-status.html#cxx11
Our Travis CI compiles on Linux using GCC 4.9.1.
_Current listed minimum, 4.6,  does not support many of the C++11 features 
currently in our source._

*MacOS X - clang 3.3+*
https://clang.llvm.org/cxx_status.html

*Solaris - Solaris Studio 12.5+*
https://docs.oracle.com/cd/E60778_01/html/E60746/bkabe.html#OSSCPgnyio
_Currently listed minimum, 12.4, [does not 
support|https://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#scrolltoc] 
many concurrent features like std::atomic necessary to remove platform specific 
concurrency code._

*Windows - Visual Studio 2015*
https://msdn.microsoft.com/en-us/library/hh567368(v=vs.140).aspx
_Currently listed minimum, 2013, does not support many of the C++11 features, 
like std::atomic_flag, necessary to remove platform specific concurrency code._

  was:
Referencing BUILDING.md our target language is C++11 and we state:
{noformat}
### Required Tools
* C++11 compiler *(see platform specific requirements)*
{noformat}

The problem is that our platform specific requirements do not meet the minimum 
standards for C++11 compilers. 

*Linux - GCC 4.8.1+*
https://gcc.gnu.org/projects/cxx-status.html#cxx11
Our Travis CI compiles on Linux using GCC 4.9.1.
_Current listed minimum, 4.6,  does not support many of the C++11 features 
currently in our source._

*MacOS X - clang 3.3+*
https://clang.llvm.org/cxx_status.html

*Solaris - Solaris Studio 12.5+*
https://docs.oracle.com/cd/E60778_01/html/E60746/bkabe.html#OSSCPgnyio
_Currently listed minimum, 12.4, [does not 
support|https://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#scrolltoc] 
many concurrent features like std::atomic necessary to remove platform specific 
concurrency code._

*Windows - Visual Studio 2015*
https://msdn.microsoft.com/en-us/library/hh567368(v=vs.140).aspx
_Currently listed minimum, 2013, does not support many of the C++11 features 
necessary necessary to remove platform specific concurrency code._


> Resolve C++11 and minimum support compilers discrepancies
> -
>
> Key: GEODE-2602
> URL: https://issues.apache.org/jira/browse/GEODE-2602
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Referencing BUILDING.md our target language is C++11 and we state:
> {noformat}
> ### Required Tools
> * C++11 compiler *(see platform specific requirements)*
> {noformat}
> The problem is that our platform specific requirements do not meet the 
> minimum standards for C++11 compilers. 
> *Linux - GCC 4.8.1+*
> https://gcc.gnu.org/projects/cxx-status.html#cxx11
> Our Travis CI compiles on Linux using GCC 4.9.1.
> _Current listed minimum, 4.6,  does not support many of the C++11 features 
> currently in our source._
> *MacOS X - clang 3.3+*
> https://clang.llvm.org/cxx_status.html
> *Solaris - Solaris Studio 12.5+*
> https://docs.oracle.com/cd/E60778_01/html/E60746/bkabe.html#OSSCPgnyio
> _Currently listed minimum, 12.4, [does not 
> support|https://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#scrolltoc]
>  many concurrent features like std::atomic necessary to remove platform 
> specific concurrency code._
> *Windows - Visual Studio 2015*
> https://msdn.microsoft.com/en-us/library/hh567368(v=vs.140).aspx
> _Currently listed minimum, 2013, does not support many of the C++11 features, 
> like std::atomic_flag, necessary to remove platform specific concurrency 
> code._



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2552) Replace NanoTimer with std::chrono / std::this_thread::sleep_for

2017-03-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2552:
---

Assignee: Jacob S. Barrett

> Replace NanoTimer with std::chrono / std::this_thread::sleep_for
> 
>
> Key: GEODE-2552
> URL: https://issues.apache.org/jira/browse/GEODE-2552
> Project: Geode
>  Issue Type: Task
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> Replace `NanoTimer` with `std::chrono` / `std::this_thread::sleep_for`



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2602) Resolve C++11 and minimum support compilers discrepancies

2017-03-06 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2602:

Description: 
Referencing BUILDING.md our target language is C++11 and we state:
{noformat}
### Required Tools
* C++11 compiler *(see platform specific requirements)*
{noformat}

The problem is that our platform specific requirements do not meet the minimum 
standards for C++11 compilers. 

*Linux - GCC 4.8.1+*
https://gcc.gnu.org/projects/cxx-status.html#cxx11
Our Travis CI compiles on Linux using GCC 4.9.1.
_Current listed minimum, 4.6,  does not support many of the C++11 features 
currently in our source._

*MacOS X - clang 3.3+*
https://clang.llvm.org/cxx_status.html

*Solaris - Solaris Studio 12.5+*
https://docs.oracle.com/cd/E60778_01/html/E60746/bkabe.html#OSSCPgnyio
_Currently listed minimum, 12.4, [does not 
support|https://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#scrolltoc] 
many concurrent features like std::atomic necessary to remove platform specific 
concurrency code._

*Windows - Visual Studio 2015*
https://msdn.microsoft.com/en-us/library/hh567368(v=vs.140).aspx
_Currently listed minimum, 2013, does not support many of the C++11 features 
necessary necessary to remove platform specific concurrency code._

  was:
Referencing BUILDING.md our target language is C++11 and we state:
{noformat}
### Required Tools
* C++11 compiler *(see platform specific requirements)*
{noformat}

The problem is that our platform specific requirements do not meet the minimum 
standards for C++11 compilers. 

*Linux - GCC 4.8.1+*
https://gcc.gnu.org/projects/cxx-status.html#cxx11
Our Travis CI compiles on Linux using GCC 4.9.1.
_Current listed minimum, 4.6,  does not support many of the C++11 features 
currently in our source._

*MacOS X - clang 3.3+*
https://clang.llvm.org/cxx_status.html

*Solaris - Solaris Studio 12.5+*
https://docs.oracle.com/cd/E60778_01/html/E60746/bkabe.html#OSSCPgnyio
_Currently listed minimum, 12.4, [does not 
support|https://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#scrolltoc] 
many concurrent features like std::atomic necessary to remove platform specific 
concurrency code._

Windows - Visual Studio 2015
https://msdn.microsoft.com/en-us/library/hh567368(v=vs.140).aspx



> Resolve C++11 and minimum support compilers discrepancies
> -
>
> Key: GEODE-2602
> URL: https://issues.apache.org/jira/browse/GEODE-2602
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Referencing BUILDING.md our target language is C++11 and we state:
> {noformat}
> ### Required Tools
> * C++11 compiler *(see platform specific requirements)*
> {noformat}
> The problem is that our platform specific requirements do not meet the 
> minimum standards for C++11 compilers. 
> *Linux - GCC 4.8.1+*
> https://gcc.gnu.org/projects/cxx-status.html#cxx11
> Our Travis CI compiles on Linux using GCC 4.9.1.
> _Current listed minimum, 4.6,  does not support many of the C++11 features 
> currently in our source._
> *MacOS X - clang 3.3+*
> https://clang.llvm.org/cxx_status.html
> *Solaris - Solaris Studio 12.5+*
> https://docs.oracle.com/cd/E60778_01/html/E60746/bkabe.html#OSSCPgnyio
> _Currently listed minimum, 12.4, [does not 
> support|https://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#scrolltoc]
>  many concurrent features like std::atomic necessary to remove platform 
> specific concurrency code._
> *Windows - Visual Studio 2015*
> https://msdn.microsoft.com/en-us/library/hh567368(v=vs.140).aspx
> _Currently listed minimum, 2013, does not support many of the C++11 features 
> necessary necessary to remove platform specific concurrency code._



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2602) Resolve C++11 and minimum support compilers discrepancies

2017-03-06 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2602:
---

 Summary: Resolve C++11 and minimum support compilers discrepancies
 Key: GEODE-2602
 URL: https://issues.apache.org/jira/browse/GEODE-2602
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett


Referencing BUILDING.md our target language is C++11 and we state:
{noformat}
### Required Tools
* C++11 compiler *(see platform specific requirements)*
{noformat}

The problem is that our platform specific requirements do not meet the minimum 
standards for C++11 compilers. 

*Linux - GCC 4.8.1+*
https://gcc.gnu.org/projects/cxx-status.html#cxx11
Our Travis CI compiles on Linux using GCC 4.9.1.
_Current listed minimum, 4.6,  does not support many of the C++11 features 
currently in our source._

*MacOS X - clang 3.3+*
https://clang.llvm.org/cxx_status.html

*Solaris - Solaris Studio 12.5+*
https://docs.oracle.com/cd/E60778_01/html/E60746/bkabe.html#OSSCPgnyio
_Currently listed minimum, 12.4, [does not 
support|https://docs.oracle.com/cd/E37069_01/html/E37071/gncix.html#scrolltoc] 
many concurrent features like std::atomic necessary to remove platform specific 
concurrency code._

Windows - Visual Studio 2015
https://msdn.microsoft.com/en-us/library/hh567368(v=vs.140).aspx




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2552) Replace NanoTimer with std::chrono / std::this_thread::sleep_for

2017-02-27 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2552:
---

 Summary: Replace NanoTimer with std::chrono / 
std::this_thread::sleep_for
 Key: GEODE-2552
 URL: https://issues.apache.org/jira/browse/GEODE-2552
 Project: Geode
  Issue Type: Task
Reporter: Jacob S. Barrett


Replace `NanoTimer` with `std::chrono` / `std::this_thread::sleep_for`



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2549) Remove unused sources

2017-02-25 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2549:

Summary: Remove unused sources  (was: Remove ACEDummy)

> Remove unused sources
> -
>
> Key: GEODE-2549
> URL: https://issues.apache.org/jira/browse/GEODE-2549
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> ACEDummy appears to be unused and may have been test code at some point.
> STLCompile appears to have been intended to force inclusion of STLPort 
> headers, which we don't use as of C++11.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2549) Remove ACEDummy

2017-02-25 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2549:

Description: 
ACEDummy appears to be unused and may have been test code at some point.

STLCompile appears to have been intended to force inclusion of STLPort headers, 
which we don't use as of C++11.


  was:ACEDummy appears to be unused and may have been test code at some point. 
Let's remove it.


> Remove ACEDummy
> ---
>
> Key: GEODE-2549
> URL: https://issues.apache.org/jira/browse/GEODE-2549
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> ACEDummy appears to be unused and may have been test code at some point.
> STLCompile appears to have been intended to force inclusion of STLPort 
> headers, which we don't use as of C++11.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2549) Remove ACEDummy

2017-02-25 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2549:
---

Assignee: Jacob S. Barrett

> Remove ACEDummy
> ---
>
> Key: GEODE-2549
> URL: https://issues.apache.org/jira/browse/GEODE-2549
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> ACEDummy appears to be unused and may have been test code at some point. 
> Let's remove it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2441) Remove PDXAutoSerializer

2017-02-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2441:
-

I am still seeing PDX Auto Serializer code in the C++ client. 

- src/pdxautoserializer/ASCLIBuiltins.hpp
- src/cppcache/include/geode/PdxAutoSerializer.hpp
- src/quickstart/cpp/PdxAutoSerializer.cpp 

And referenced in:
- src/tests/cpp/testobject/CMakeLists.txt 
- src/quickstart/cpp/CMakeLists.txt 
- src/quickstart/runcpp.sh.in 
- src/quickstart/runcpp.bat.in 



> Remove PDXAutoSerializer 
> -
>
> Key: GEODE-2441
> URL: https://issues.apache.org/jira/browse/GEODE-2441
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ernest Burghardt
>
> Remove PDXAutoSerializer utility that generates PDX serialization C++ source 
> that you can include in your project to (de)serialize your C++ classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2493) Replace the locking and CAS operations provided in HostAsm with C++11 standards

2017-02-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2493:

Description: 
Several platform specific locking and CAS operations are implemented in HostAsm 
and related files. These are not portable and require porting efforts. They are 
also not well tested. Converting the C++11 standards allows the compiler to 
choose the code or instructions that optimize the behavior required. Most if 
not all of the functions these files provide can be replaced with C++11 
standard functions.

Some Examples:
On Solaris SPARC we have inline assembly.
On Solaris x86 we use Solaris specific runtime functions.
On Windows we use really old Win32 functions that have some non-standard 
behavior.



  was:
Several platform specific locking and CAS operations are implemented in HostAsm 
and related files. These are not portable and require porting efforts. They are 
also not well tested. Converting the C++11 standards allows the compiler to 
choose the code or instructions that optimize the behavior required. Most if 
not all of the functions these files provide can be replaced with C++11 
standard functions.

Some Examples:
On Solaris SPAC we have inline assembly.
On Solaris x86 we use Solaris specific runtime functions.
On Windows we use really old Win32 functions that have some non-standard 
behavior.




> Replace the locking and CAS operations provided in HostAsm with C++11 
> standards
> ---
>
> Key: GEODE-2493
> URL: https://issues.apache.org/jira/browse/GEODE-2493
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Several platform specific locking and CAS operations are implemented in 
> HostAsm and related files. These are not portable and require porting 
> efforts. They are also not well tested. Converting the C++11 standards allows 
> the compiler to choose the code or instructions that optimize the behavior 
> required. Most if not all of the functions these files provide can be 
> replaced with C++11 standard functions.
> Some Examples:
> On Solaris SPARC we have inline assembly.
> On Solaris x86 we use Solaris specific runtime functions.
> On Windows we use really old Win32 functions that have some non-standard 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Comment Edited] (GEODE-2493) Replace the locking and CAS operations provided in HostAsm with C++11 standards

2017-02-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett edited comment on GEODE-2493 at 2/25/17 6:05 AM:
--

-Replace {{HostAsm::nanoSleep}} and {{ACE_OS::nanosleep}} with 
{{[std::this_thread::sleep_for|http://en.cppreference.com/w/cpp/thread/sleep_for]}}
 using 
{{[std::crono::nanoseconds|http://en.cppreference.com/w/cpp/chrono/duration]}}.-
All uses were eliminated when removing SpinLock.


was (Author: jbarrett):
Replace {{HostAsm::nanoSleep}} and {{ACE_OS::nanosleep}} with 
{{[std::this_thread::sleep_for|http://en.cppreference.com/w/cpp/thread/sleep_for]}}
 using 
{{[std::crono::nanoseconds|http://en.cppreference.com/w/cpp/chrono/duration]}}.

> Replace the locking and CAS operations provided in HostAsm with C++11 
> standards
> ---
>
> Key: GEODE-2493
> URL: https://issues.apache.org/jira/browse/GEODE-2493
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Several platform specific locking and CAS operations are implemented in 
> HostAsm and related files. These are not portable and require porting 
> efforts. They are also not well tested. Converting the C++11 standards allows 
> the compiler to choose the code or instructions that optimize the behavior 
> required. Most if not all of the functions these files provide can be 
> replaced with C++11 standard functions.
> Some Examples:
> On Solaris SPAC we have inline assembly.
> On Solaris x86 we use Solaris specific runtime functions.
> On Windows we use really old Win32 functions that have some non-standard 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2493) Replace the locking and CAS operations provided in HostAsm with C++11 standards

2017-02-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2493:

Summary: Replace the locking and CAS operations provided in HostAsm with 
C++11 standards  (was: Replaces the locking and CAS operations provided in 
HostAsm with C++11 standards)

> Replace the locking and CAS operations provided in HostAsm with C++11 
> standards
> ---
>
> Key: GEODE-2493
> URL: https://issues.apache.org/jira/browse/GEODE-2493
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Several platform specific locking and CAS operations are implemented in 
> HostAsm and related files. These are not portable and require porting 
> efforts. They are also not well tested. Converting the C++11 standards allows 
> the compiler to choose the code or instructions that optimize the behavior 
> required. Most if not all of the functions these files provide can be 
> replaced with C++11 standard functions.
> Some Examples:
> On Solaris SPAC we have inline assembly.
> On Solaris x86 we use Solaris specific runtime functions.
> On Windows we use really old Win32 functions that have some non-standard 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2531) Replace HostAsm::atomic* and AtomicInc with std::atomic

2017-02-22 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2531:
---

Assignee: Jacob S. Barrett

> Replace HostAsm::atomic* and AtomicInc with std::atomic
> ---
>
> Key: GEODE-2531
> URL: https://issues.apache.org/jira/browse/GEODE-2531
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> Replace {{HostAsm::atomic*}} and {{AtomicInc}} with 
> {{[std::atomic|http://en.cppreference.com/w/cpp/atomic/atomic]}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Comment Edited] (GEODE-2493) Replaces the locking and CAS operations provided in HostAsm with C++11 standards

2017-02-22 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett edited comment on GEODE-2493 at 2/23/17 5:49 AM:
--

-Replace {{HostAsm::getCpuCount}} with 
{{[std::thread::hardware_concurrency|http://en.cppreference.com/w/cpp/thread/thread/hardware_concurrency]}}.-
All uses were eliminated when removing {{SpinLock}}.


was (Author: jbarrett):
Replace {{HostAsm::getCpuCount}} with 
{{[std::thread::hardware_concurrency|http://en.cppreference.com/w/cpp/thread/thread/hardware_concurrency]}}.

> Replaces the locking and CAS operations provided in HostAsm with C++11 
> standards
> 
>
> Key: GEODE-2493
> URL: https://issues.apache.org/jira/browse/GEODE-2493
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Several platform specific locking and CAS operations are implemented in 
> HostAsm and related files. These are not portable and require porting 
> efforts. They are also not well tested. Converting the C++11 standards allows 
> the compiler to choose the code or instructions that optimize the behavior 
> required. Most if not all of the functions these files provide can be 
> replaced with C++11 standard functions.
> Some Examples:
> On Solaris SPAC we have inline assembly.
> On Solaris x86 we use Solaris specific runtime functions.
> On Windows we use really old Win32 functions that have some non-standard 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2531) Replace HostAsm::atomic* and AtomicInc with std::atomic

2017-02-22 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2531:
---

 Summary: Replace HostAsm::atomic* and AtomicInc with std::atomic
 Key: GEODE-2531
 URL: https://issues.apache.org/jira/browse/GEODE-2531
 Project: Geode
  Issue Type: Sub-task
Reporter: Jacob S. Barrett


Replace {{HostAsm::atomic*}} and {{AtomicInc}} with 
{{[std::atomic|http://en.cppreference.com/w/cpp/atomic/atomic]}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2494) Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex.

2017-02-22 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2494:
---

Assignee: Jacob S. Barrett

> Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex.
> 
>
> Key: GEODE-2494
> URL: https://issues.apache.org/jira/browse/GEODE-2494
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> Replace {{SpinLock}} class with C++11 style 
> {{[BasicLockable|http://en.cppreference.com/w/cpp/concept/BasicLockable]}} 
> class, {{spinlock_mutex}}. You can find several public domain examples of how 
> to implement a {{spinlock_mutex}} that can be used with 
> {{[std::lock_guard|http://en.cppreference.com/w/cpp/thread/lock_guard]}}.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2525) Replace random number implementation with C++11 standards

2017-02-22 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2525:

Component/s: native client

> Replace random number implementation with C++11 standards
> -
>
> Key: GEODE-2525
> URL: https://issues.apache.org/jira/browse/GEODE-2525
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Remove Mersenne Twister implementation from source. Use C++11 random where 
> appropriate. Refactor random usage to be thread safe as applicable. GsRansom 
> uses spin lock to protect. Consider thread local random.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2525) Replace random number implementation with C++11 standards

2017-02-22 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2525:
---

 Summary: Replace random number implementation with C++11 standards
 Key: GEODE-2525
 URL: https://issues.apache.org/jira/browse/GEODE-2525
 Project: Geode
  Issue Type: Bug
Reporter: Jacob S. Barrett


Remove Mersenne Twister implementation from source. Use C++11 random where 
appropriate. Refactor random usage to be thread safe as applicable. GsRansom 
uses spin lock to protect. Consider thread local random.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2142) Remove JSON.org dependency

2017-02-16 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2142:
-

[~amb] Yes, the "right" solution will not have a need for any modifications nor 
a dependency on any particular JSON or JAX-B implementations. 

> Remove JSON.org dependency
> --
>
> Key: GEODE-2142
> URL: https://issues.apache.org/jira/browse/GEODE-2142
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Anthony Baker
>Priority: Blocker
>  Labels: json
>
> ASF has determined that the JSON library should be treated as Category X and 
> is incompatible with ASLv2.
> We have until Apr-30, 2017 to remove this dependency.  Any release we ship 
> prior to that time must state this usage via NOTICE.
> http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3ccajwfca2ox62mugp+-+-v6ktbkhhgkixucjcr9syes-azfp+...@mail.gmail.com%3e
> There are related reasons for removing the JSON library anyway, but this bug 
> captures the legal reasons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2142) Remove JSON.org dependency

2017-02-16 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2142:
-

[~ukohlmeyer] and I spent a bit of time looking into the removal of JSON.org 
sources. The sources have been JSON.org modified and modularized as geode-json. 
The geode-json module is used in several locations but most heavily in the gfsh 
communication layer. We first to a stab at replacing the specific use of one 
library with another but the differences between libraries made the effort 
challenging and the time spent was likely better spent embracing something less 
specific. We then looked at re-implementing using domain objects and JAX-B but 
that again unraveled some very complex issues with the use cases in the gfsh 
communication. We then considered a wholesale re-write of gfsh communication. 
Given the time constraints from Apache to divest of this license we felt too 
much time was needed to do the "right" thing. We have come back to something 
easier and that is to replace the core sources of geode-json with those from 
the [tdunning/open-json|https://github.com/tdunning/open-json] project and 
overlay the local changes. This should take less time than anything else and 
complete this simple goal of removing the incompatible licensed code from our 
project. We will then come back around later with a proposal to overhaul the 
gfsh communication layer as part of a greater scheme to restructure Geode to be 
more modular and extendable.



> Remove JSON.org dependency
> --
>
> Key: GEODE-2142
> URL: https://issues.apache.org/jira/browse/GEODE-2142
> Project: Geode
>  Issue Type: Bug
>  Components: build
>Reporter: Anthony Baker
>Priority: Blocker
>  Labels: json
>
> ASF has determined that the JSON library should be treated as Category X and 
> is incompatible with ASLv2.
> We have until Apr-30, 2017 to remove this dependency.  Any release we ship 
> prior to that time must state this usage via NOTICE.
> http://mail-archives.apache.org/mod_mbox/incubator-general/201611.mbox/%3ccajwfca2ox62mugp+-+-v6ktbkhhgkixucjcr9syes-azfp+...@mail.gmail.com%3e
> There are related reasons for removing the JSON library anyway, but this bug 
> captures the legal reasons.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2486) Trouble setting cipher on Native Client

2017-02-16 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2486:
-

[~ahuddy] Your change to the title does not correctly reflect the problem or 
the solution in the associated fixes. Geode native does not and has not allowed 
for the setting of the SSL cipher. The attached fix does not allow you to set 
the cipher. The fix corrects the error in initialization that prevents the 
client from negotiating anything other than the NULL cipher with the server. 
The server will ultimately control the cipher that the client uses.



> Trouble setting cipher on Native Client
> ---
>
> Key: GEODE-2486
> URL: https://issues.apache.org/jira/browse/GEODE-2486
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
> Fix For: 1.2.0
>
>
> SSLImpl does not correctly initialize the OpenSSL library so ciphers other 
> than the NULL cipher can be used.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2494) Replace SpinLock class with C++11 style BasicLockable class, spinlock_mutex. You can find several public domain examples of how to implement a spinlock_mutex that can be

2017-02-15 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2494:
---

 Summary: Replace SpinLock class with C++11 style BasicLockable 
class, spinlock_mutex. You can find several public domain examples of how to 
implement a spinlock_mutex that can be used with std::lock_guard.
 Key: GEODE-2494
 URL: https://issues.apache.org/jira/browse/GEODE-2494
 Project: Geode
  Issue Type: Sub-task
  Components: native client
Reporter: Jacob S. Barrett






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2493) Replaces the locking and CAS operations provided in HostAsm with C++11 standards

2017-02-15 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2493:
-

Replace {{HostAsm::atomicAdd}} and {{AtomicInc}} with 
{{[std::atomic|http://en.cppreference.com/w/cpp/atomic/atomic]}}.

> Replaces the locking and CAS operations provided in HostAsm with C++11 
> standards
> 
>
> Key: GEODE-2493
> URL: https://issues.apache.org/jira/browse/GEODE-2493
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Several platform specific locking and CAS operations are implemented in 
> HostAsm and related files. These are not portable and require porting 
> efforts. They are also not well tested. Converting the C++11 standards allows 
> the compiler to choose the code or instructions that optimize the behavior 
> required. Most if not all of the functions these files provide can be 
> replaced with C++11 standard functions.
> Some Examples:
> On Solaris SPAC we have inline assembly.
> On Solaris x86 we use Solaris specific runtime functions.
> On Windows we use really old Win32 functions that have some non-standard 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2493) Replaces the locking and CAS operations provided in HostAsm with C++11 standards

2017-02-15 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2493:
-

Replace {{HostAsm::nanoSleep}} and {{ACE_OS::nanosleep}} with 
{{[std::this_thread::sleep_for|http://en.cppreference.com/w/cpp/thread/sleep_for]}}
 using 
{{[std::crono::nanoseconds|http://en.cppreference.com/w/cpp/chrono/duration]}}.

> Replaces the locking and CAS operations provided in HostAsm with C++11 
> standards
> 
>
> Key: GEODE-2493
> URL: https://issues.apache.org/jira/browse/GEODE-2493
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Several platform specific locking and CAS operations are implemented in 
> HostAsm and related files. These are not portable and require porting 
> efforts. They are also not well tested. Converting the C++11 standards allows 
> the compiler to choose the code or instructions that optimize the behavior 
> required. Most if not all of the functions these files provide can be 
> replaced with C++11 standard functions.
> Some Examples:
> On Solaris SPAC we have inline assembly.
> On Solaris x86 we use Solaris specific runtime functions.
> On Windows we use really old Win32 functions that have some non-standard 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2493) Replaces the locking and CAS operations provided in HostAsm with C++11 standards

2017-02-15 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2493:
-

Replace {{HostAsm::getCpuCount}} with 
{{[std::thread::hardware_concurrency|http://en.cppreference.com/w/cpp/thread/thread/hardware_concurrency]}}.

> Replaces the locking and CAS operations provided in HostAsm with C++11 
> standards
> 
>
> Key: GEODE-2493
> URL: https://issues.apache.org/jira/browse/GEODE-2493
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Several platform specific locking and CAS operations are implemented in 
> HostAsm and related files. These are not portable and require porting 
> efforts. They are also not well tested. Converting the C++11 standards allows 
> the compiler to choose the code or instructions that optimize the behavior 
> required. Most if not all of the functions these files provide can be 
> replaced with C++11 standard functions.
> Some Examples:
> On Solaris SPAC we have inline assembly.
> On Solaris x86 we use Solaris specific runtime functions.
> On Windows we use really old Win32 functions that have some non-standard 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2493) Replaces the locking and CAS operations provided in HostAsm with C++11 standards

2017-02-15 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2493:
-

Replace {{SpinLock}} class with C++11 style 
{{[BasicLockable|http://en.cppreference.com/w/cpp/concept/BasicLockable]}} 
class, {{spinlock_mutex}}. You can find several public domain examples of how 
to implement a {{spinlock_mutex}} that can be used with 
{{[std::lock_guard|http://en.cppreference.com/w/cpp/thread/lock_guard]}}.

> Replaces the locking and CAS operations provided in HostAsm with C++11 
> standards
> 
>
> Key: GEODE-2493
> URL: https://issues.apache.org/jira/browse/GEODE-2493
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>
> Several platform specific locking and CAS operations are implemented in 
> HostAsm and related files. These are not portable and require porting 
> efforts. They are also not well tested. Converting the C++11 standards allows 
> the compiler to choose the code or instructions that optimize the behavior 
> required. Most if not all of the functions these files provide can be 
> replaced with C++11 standard functions.
> Some Examples:
> On Solaris SPAC we have inline assembly.
> On Solaris x86 we use Solaris specific runtime functions.
> On Windows we use really old Win32 functions that have some non-standard 
> behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2408) Refactor CacheableDate to use C++ std::chrono

2017-02-15 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2408.
-
   Resolution: Fixed
Fix Version/s: 1.2.0

> Refactor CacheableDate to use C++ std::chrono
> -
>
> Key: GEODE-2408
> URL: https://issues.apache.org/jira/browse/GEODE-2408
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
> Fix For: 1.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2486) SSL ciphers other than NULL not supported

2017-02-15 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2486.
-
   Resolution: Fixed
Fix Version/s: 1.2.0

> SSL ciphers other than NULL not supported
> -
>
> Key: GEODE-2486
> URL: https://issues.apache.org/jira/browse/GEODE-2486
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Jacob S. Barrett
> Fix For: 1.2.0
>
>
> SSLImpl does not correctly initialize the OpenSSL library so ciphers other 
> than the NULL cipher can be used.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2487) SSL should not require external security library

2017-02-14 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2487:
---

 Summary: SSL should not require external security library
 Key: GEODE-2487
 URL: https://issues.apache.org/jira/browse/GEODE-2487
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Jacob S. Barrett


Geode Native requires that securityImpl library be compiled by the end user to 
support SSL. The rational for this has been lost but was likely to avoid either 
export control, which it does not, or to make dynamic loading of OpenSSL 
easier, which I am not sure it does.

Refactor SSL sockets to initialize and use OpenSSL (via ACE_SSL) directly and 
remove it from securityImpl library. If there is no other purpose for 
securityImpl library then purge it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2486) SSL ciphers other than NULL not supported

2017-02-14 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2486:
---

 Summary: SSL ciphers other than NULL not supported
 Key: GEODE-2486
 URL: https://issues.apache.org/jira/browse/GEODE-2486
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Jacob S. Barrett


SSLImpl does not correctly initialize the OpenSSL library so ciphers other than 
the NULL cipher can be used.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2467) Support Newer Versions of Visual Studio

2017-02-13 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2467:
-

Are you intending to break VS 2013 or just ensure that 2015 and 2017 work as 
well?

> Support Newer Versions of Visual Studio
> ---
>
> Key: GEODE-2467
> URL: https://issues.apache.org/jira/browse/GEODE-2467
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Michael Martell
>
> This task is to support building the native client with newer versions of 
> Visual Studio including VS 2015 and VS 2017.
> Reasons include:
> 1) with 2017 release date of March 7 just announced, this makes a 2013 basd 
> build really old
> 2) stronger C++11/14/17 support
> 3) dotNetty requires newer tool chains, and nice to use a single tool
> 4) much better built-in git support
> 5) there are no source changes required, only tweak is to xerces 
> CMakeLists.txt



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2480) Need to specify correct version of CMake required for building Native Client

2017-02-13 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2480:
-

Took me a few times to catch it. The version in the BUILDING.md says *4.3* but 
should be *3.4*.

> Need to specify correct version of CMake required for building Native Client
> 
>
> Key: GEODE-2480
> URL: https://issues.apache.org/jira/browse/GEODE-2480
> Project: Geode
>  Issue Type: Bug
>  Components: docs, native client
>Reporter: Akihiro Kitada
>
> According to the following doc, the version of CMake required for building 
> Native Client is *4.3* or newer.
> https://github.com/apache/geode-native/blob/develop/BUILDING.md
> However, the latest stable version of CMake is 3.7.2 as of now. Please 
> specify the correct version of CMake (it could be "*3.4* or newer" ?).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2480) Need to specify correct version of CMake required for building Native Client

2017-02-13 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2480:

Description: 
According to the following doc, the version of CMake required for building 
Native Client is *4.3* or newer.

https://github.com/apache/geode-native/blob/develop/BUILDING.md

However, the latest stable version of CMake is 3.7.2 as of now. Please specify 
the correct version of CMake (it could be "*3.4* or newer" ?).

  was:
According to the following doc, the version of CMake required for building 
Native Client is 4.3 or newer.

https://github.com/apache/geode-native/blob/develop/BUILDING.md

However, the latest stable version of CMake is 3.7.2 as of now. Please specify 
the correct version of CMake (it could be "3.4 or newer" ?).


> Need to specify correct version of CMake required for building Native Client
> 
>
> Key: GEODE-2480
> URL: https://issues.apache.org/jira/browse/GEODE-2480
> Project: Geode
>  Issue Type: Bug
>  Components: docs, native client
>Reporter: Akihiro Kitada
>
> According to the following doc, the version of CMake required for building 
> Native Client is *4.3* or newer.
> https://github.com/apache/geode-native/blob/develop/BUILDING.md
> However, the latest stable version of CMake is 3.7.2 as of now. Please 
> specify the correct version of CMake (it could be "*3.4* or newer" ?).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2439) Replace all non-standard types in all public includes / API

2017-02-13 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2439:
-

GEODE-2408 resolves the WinSock2.h and timeval issues.

> Replace all non-standard types in all public includes / API
> ---
>
> Key: GEODE-2439
> URL: https://issues.apache.org/jira/browse/GEODE-2439
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ernest Burghardt
>
> research other non-standard types in API, ACE_Time



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2408) Refactor CacheableDate to use C++ std::chrono

2017-02-02 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2408:
---

Assignee: Jacob S. Barrett

> Refactor CacheableDate to use C++ std::chrono
> -
>
> Key: GEODE-2408
> URL: https://issues.apache.org/jira/browse/GEODE-2408
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2408) Refactor CacheableDate to use C++ std::chrono

2017-01-31 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2408:
---

 Summary: Refactor CacheableDate to use C++ std::chrono
 Key: GEODE-2408
 URL: https://issues.apache.org/jira/browse/GEODE-2408
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2383) Update schema references in xml files

2017-01-31 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2383:
-

[~eburghardt] is this just a duplicate of GEODE-2336?


> Update schema references in xml files
> -
>
> Key: GEODE-2383
> URL: https://issues.apache.org/jira/browse/GEODE-2383
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Ernest Burghardt
>
> Update URLs used to be apache geode and evaluate if the xml file is used, 
> removed if un-used.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (GEODE-2317) native client cmake build should honor GEODE_HOME environment variable

2017-01-31 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2317:
---

Assignee: Jacob S. Barrett

> native client cmake build should honor GEODE_HOME environment variable
> --
>
> Key: GEODE-2317
> URL: https://issues.apache.org/jira/browse/GEODE-2317
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Dan Smith
>Assignee: Jacob S. Barrett
>
> The native client build currently looks for a GEODE_ROOT variable. However, 
> the convention in the java project and the geode-examples is to use a 
> GEODE_HOME environment variable to specify the location of geode. The native 
> client build should look for this environment variable.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (GEODE-2397) CMake findOpenSSL allows unusable versions

2017-01-31 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett commented on GEODE-2397:
-

Actually it looks like it SecurityImpl does work with OpenSSL 1.0.2 under 
certain conditions. Those conditions are not clear yet. I would change this 
ticket to identify what versions of OpenSSL are supported.

> CMake findOpenSSL allows unusable versions
> --
>
> Key: GEODE-2397
> URL: https://issues.apache.org/jira/browse/GEODE-2397
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Ernest Burghardt
>
> restrict find openssl to a 1.0.1 version



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (GEODE-2397) CMake findOpenSSL allows unusable versions

2017-01-31 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett updated GEODE-2397:

Issue Type: Task  (was: Bug)

> CMake findOpenSSL allows unusable versions
> --
>
> Key: GEODE-2397
> URL: https://issues.apache.org/jira/browse/GEODE-2397
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Ernest Burghardt
>
> restrict find openssl to a 1.0.1 version



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Resolved] (GEODE-2406) Remove "client" from product naming

2017-01-31 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2406.
-
Resolution: Fixed

> Remove "client" from product naming
> ---
>
> Key: GEODE-2406
> URL: https://issues.apache.org/jira/browse/GEODE-2406
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ernest Burghardt
>
> the Jira Component makes this very ironic



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2407) Update native docs with new product name.

2017-01-31 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2407:
---

 Summary: Update native docs with new product name.
 Key: GEODE-2407
 URL: https://issues.apache.org/jira/browse/GEODE-2407
 Project: Geode
  Issue Type: Sub-task
  Components: docs
Reporter: Jacob S. Barrett


See parent ticket for product naming changes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Reopened] (GEODE-1435) Update LICENSE for native client bundled dependencies

2017-01-31 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reopened GEODE-1435:
-
  Assignee: Jacob S. Barrett

Need to add binary distribute licensing and update source licensing errors.

> Update LICENSE for native client bundled dependencies
> -
>
> Key: GEODE-1435
> URL: https://issues.apache.org/jira/browse/GEODE-1435
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Anthony Baker
>Assignee: Jacob S. Barrett
>
> We need to declare attribution for any bundled dependencies in the native 
> client source code.  If we choose to include the native client in the binary 
> distribution, we will need to declare those bundled libraries as well.
> See 
> https://cwiki.apache.org/confluence/display/GEODE/License+Guide+for+Contributors.
> Affected files:
> - LICENSE, NOTICE (source distribution)
> - geode-assembly/src/main/dist/LICENSE, NOTICE (binary distribution)
> Initial list of bundled source dependencies:
> - MersenneTwister (src/tests/cpp/fwklib/MersenneTwister.*pp)
> The binary dependencies can be reviewed in 
> geode-client-native/src/dependencies (some of these are not shipped though):
> - libxml2
> - xerces-c
> - openssl
> - ACE
> - antlr
> - sqlite
> - doxygen
> - gtest



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] (GEODE-2308) Replace GemFire branding with Geode branding.

2017-01-31 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2308.
-
   Resolution: Fixed
Fix Version/s: 1.1.0

> Replace GemFire branding with Geode branding.
> -
>
> Key: GEODE-2308
> URL: https://issues.apache.org/jira/browse/GEODE-2308
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
> Fix For: 1.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] (GEODE-2399) Update docs to reflect branding changes on native clients.

2017-01-31 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2399:
---

 Summary: Update docs to reflect branding changes on native clients.
 Key: GEODE-2399
 URL: https://issues.apache.org/jira/browse/GEODE-2399
 Project: Geode
  Issue Type: Sub-task
  Components: docs
Reporter: Jacob S. Barrett


Native client library names change. See parent ticket for changes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] (GEODE-2344) Upgrade Geode-NC ordinal

2017-01-31 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2344.
-
   Resolution: Fixed
Fix Version/s: 1.1.0

> Upgrade Geode-NC ordinal
> 
>
> Key: GEODE-2344
> URL: https://issues.apache.org/jira/browse/GEODE-2344
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ernest Burghardt
> Fix For: 1.1.0
>
>
> currently we use 8.x ordinal, need to work using the 9.0 ordinal



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (GEODE-2376) Remove stack dump comment from ThinClientPoolDM.cpp

2017-01-27 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2376:
---

 Summary: Remove stack dump comment from ThinClientPoolDM.cpp
 Key: GEODE-2376
 URL: https://issues.apache.org/jira/browse/GEODE-2376
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett


For some strange reason there is a stack dump embedded in the source. There is 
no comment on the relevance to the section of code.



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


[jira] [Assigned] (GEODE-2308) Replace GemFire branding with Geode branding.

2017-01-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2308:
---

Assignee: Jacob S. Barrett

> Replace GemFire branding with Geode branding.
> -
>
> Key: GEODE-2308
> URL: https://issues.apache.org/jira/browse/GEODE-2308
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>




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


[jira] [Resolved] (GEODE-2316) Replace GemFire namespace with Geode namespace

2017-01-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2316.
-
   Resolution: Fixed
 Assignee: Jacob S. Barrett  (was: Michael Dodge)
Fix Version/s: 1.1.0

> Replace GemFire namespace with Geode namespace
> --
>
> Key: GEODE-2316
> URL: https://issues.apache.org/jira/browse/GEODE-2316
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Michael Dodge
>Assignee: Jacob S. Barrett
> Fix For: 1.1.0
>
>
> For the code under cppcache, replace gemfire with apache::geode::client.
> For the code under clicache, replace GemStone.GemFire.Cache.Generic and 
> GemStone.GemFire.Cache with Apache.Geode.Client.



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


[jira] [Resolved] (GEODE-2340) Update GemfireCppCache

2017-01-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2340.
-
   Resolution: Fixed
Fix Version/s: 1.1.0

> Update GemfireCppCache
> --
>
> Key: GEODE-2340
> URL: https://issues.apache.org/jira/browse/GEODE-2340
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Ernest Burghardt
> Fix For: 1.1.0
>
>
> the following files are called Gemfire* let's make them Geode*
> src//cppcache/include/gfcpp/GemfireCppCache.hpp
> src//cppcache/include/gfcpp/GemfireCppCache.inl
> Also, update inclusions usage and named components as appropriate.



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


[jira] [Resolved] (GEODE-2342) Update GemfireTypeIds

2017-01-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2342.
-
   Resolution: Fixed
Fix Version/s: 1.1.0

> Update GemfireTypeIds
> -
>
> Key: GEODE-2342
> URL: https://issues.apache.org/jira/browse/GEODE-2342
> Project: Geode
>  Issue Type: Sub-task
>  Components: native client
>Reporter: Ernest Burghardt
> Fix For: 1.1.0
>
>
> Gem fire => Geode transformation
> the following files are called Gemfire* let's make them Geode*
> src//cppcache/include/gfcpp/GemfireTypeIds.hpp
> src//cppcache/src/GemfireTypeIdsImpl.hpp
> Also, update inclusions usage and named components as appropriate.



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


[jira] [Resolved] (GEODE-2343) Windows image sshd fails to start after build user password expires

2017-01-24 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2343.
-
   Resolution: Fixed
Fix Version/s: 1.1.0

> Windows image sshd fails to start after build user password expires
> ---
>
> Key: GEODE-2343
> URL: https://issues.apache.org/jira/browse/GEODE-2343
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
> Fix For: 1.1.0
>
>
> When the password for the build user expires sshd does not start rending the 
> image useless after a period of time. 
> Disable build user password expiration in build-windows packer script.



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


[jira] [Resolved] (GEODE-2332) Remove legacy integration test xml files

2017-01-21 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett resolved GEODE-2332.
-
Resolution: Fixed

> Remove legacy integration test xml files
> 
>
> Key: GEODE-2332
> URL: https://issues.apache.org/jira/browse/GEODE-2332
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> These xml files are for an old and previously deleted testing framework.



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


[jira] [Assigned] (GEODE-2332) Remove legacy integration test xml files

2017-01-21 Thread Jacob S. Barrett (JIRA)

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

Jacob S. Barrett reassigned GEODE-2332:
---

Assignee: Jacob S. Barrett

> Remove legacy integration test xml files
> 
>
> Key: GEODE-2332
> URL: https://issues.apache.org/jira/browse/GEODE-2332
> Project: Geode
>  Issue Type: Task
>  Components: native client
>Reporter: Jacob S. Barrett
>Assignee: Jacob S. Barrett
>
> These xml files are for an old and previously deleted testing framework.



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


[jira] [Created] (GEODE-2332) Remove legacy integration test xml files

2017-01-21 Thread Jacob S. Barrett (JIRA)
Jacob S. Barrett created GEODE-2332:
---

 Summary: Remove legacy integration test xml files
 Key: GEODE-2332
 URL: https://issues.apache.org/jira/browse/GEODE-2332
 Project: Geode
  Issue Type: Task
  Components: native client
Reporter: Jacob S. Barrett


These xml files are for an old and previously deleted testing framework.



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


  1   2   >