[jira] [Updated] (GEODE-9138) Add warning in server logs when data event is ignored as a duplicate
[ https://issues.apache.org/jira/browse/GEODE-9138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-9138: - Component/s: logging > Add warning in server logs when data event is ignored as a duplicate > > > Key: GEODE-9138 > URL: https://issues.apache.org/jira/browse/GEODE-9138 > Project: Geode > Issue Type: Bug > Components: client/server, logging >Reporter: Diane Hardman >Priority: Major > > Under certain rare conditions, a client may send or resend a data event with > an eventId that causes the server to interpret it as a duplicate event and > discard it. > It is currently impossible to trace when this happens without extra logging > added. > From Barry: > No, if the server thinks it has seen the event, it silently eats it. See > DistributedEventTracker.hasSeenEvent. It has a trace log message but thats it. > The log message that tracks this behavior in the server needs to be added > permanently. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9138) Add warning in server logs when data event is ignored as a duplicate
Diane Hardman created GEODE-9138: Summary: Add warning in server logs when data event is ignored as a duplicate Key: GEODE-9138 URL: https://issues.apache.org/jira/browse/GEODE-9138 Project: Geode Issue Type: Bug Components: client/server Reporter: Diane Hardman Under certain rare conditions, a client may send or resend a data event with an eventId that causes the server to interpret it as a duplicate event and discard it. It is currently impossible to trace when this happens without extra logging added. >From Barry: No, if the server thinks it has seen the event, it silently eats it. See DistributedEventTracker.hasSeenEvent. It has a trace log message but thats it. The log message that tracks this behavior in the server needs to be added permanently. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-8378) Clean up SNI proxy tests usage of keystore, truststore files
Diane Hardman created GEODE-8378: Summary: Clean up SNI proxy tests usage of keystore, truststore files Key: GEODE-8378 URL: https://issues.apache.org/jira/browse/GEODE-8378 Project: Geode Issue Type: Improvement Components: native client Reporter: Diane Hardman Follow-up to GEODE-7508. New SNI proxy tests still contain local copies of keystore and truststore files which should be removed and these tests updated to reference the common files. This will prevent these tests from becoming brittle over time. Here's where I found the extraneous files: find . -name *.jks ./ssl_keys/server_keys/server_keystore.jks ./ssl_keys/server_keys/server_truststore.jks ./cppcache/integration/test/sni-test-config/geode-config/server-clementine-keystore.jks ./cppcache/integration/test/sni-test-config/geode-config/server-dolores-keystore.jks ./cppcache/integration/test/sni-test-config/geode-config/truststore.jks ./cppcache/integration/test/sni-test-config/geode-config/locator-maeve-keystore.jks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7794) __GEMFIRE_JSON PDX type has invalid PdxType
[ https://issues.apache.org/jira/browse/GEODE-7794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman resolved GEODE-7794. -- Fix Version/s: 1.13.0 Resolution: Fixed > __GEMFIRE_JSON PDX type has invalid PdxType > --- > > Key: GEODE-7794 > URL: https://issues.apache.org/jira/browse/GEODE-7794 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Matthew Reddington >Priority: Major > Fix For: 1.13.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > The native client is built on the presumption that class name is unique. > Since the introduction of __GEMFIRE_JSON, that is no longer the case. Where > the logic presumes it can use cached deserialization rules in the form of a > PdxType, looked up by name, this is no longer the case. > > What we have observed is if a cache instance does not have a PdxType for a > __GEMFIRE_JSON class instance, the first get and deserialization will > succeed, but all subsequent gets will result in an empty PdxWrapper. > > Steps to reproduce: > 1) Instantiate an instance of Cache. > 2) Put a PDX value with class name __GEMFIRE_JSON. > 3) Instantiate a second instance of Cache. > 4) Use this cache to make two consecutive gets of the PDX value. Inspect > the results. > > Observations: > 1) The first get will succeed in returning an instance of PdxInstance with > the expected fields and values as per step #2. > 2) The second get will return a PdxWrapper of class name __GEMFIRE_JSON and > a user object of null. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7694) PdxType comparison should favor typeId rather than class name
[ https://issues.apache.org/jira/browse/GEODE-7694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman resolved GEODE-7694. -- Fix Version/s: 1.12.0 Resolution: Fixed > PdxType comparison should favor typeId rather than class name > - > > Key: GEODE-7694 > URL: https://issues.apache.org/jira/browse/GEODE-7694 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.12.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The `operator<` method of PdxType in the native client simply compares the > class names, which is incorrect and leads to the fact that, in NC, you cannot > currently have two separate PDX types with the same class name. The > comparison should favor type ID first, then if both type IDs are 0 (true for > local regions), fall back to class name. This will still fail for local > regions in the scenario where class names are the same, but it's much, much > better than we have now. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7646) Simplify SSL Examples by Eliminating Need for LD_LIBRARY_PATH on Linux
[ https://issues.apache.org/jira/browse/GEODE-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman resolved GEODE-7646. -- Fix Version/s: 1.12.0 Resolution: Fixed > Simplify SSL Examples by Eliminating Need for LD_LIBRARY_PATH on Linux > -- > > Key: GEODE-7646 > URL: https://issues.apache.org/jira/browse/GEODE-7646 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.12.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The new SSL examples for the native client currently require the > LD_LIBRARY_PATH environment variable to include the path to our crypto > library (libcryptoImpl.so) on Linux. This ticket is to eliminate the need for > this environment variable and make Linux and OSX be consistent. > The driving force to fix this was the recent switch to using RPATH to bake in > the path to our crypto library into the executable. On newer versions of OSX, > System Integrity Protection (SIP) ignores LD_LIBRARY_PATH. Using RPATH was > the solution for this. However, until this fix the RPATH solution doesn't > work on Linux. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7625) Remove broken DH support
[ https://issues.apache.org/jira/browse/GEODE-7625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman resolved GEODE-7625. -- Fix Version/s: 1.12.0 Resolution: Fixed > Remove broken DH support > > > Key: GEODE-7625 > URL: https://issues.apache.org/jira/browse/GEODE-7625 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob Barrett >Priority: Major > Fix For: 1.12.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The DH support in geode native client has been broken since donation. There > are currently no enabled tests for DH. The current sources compile but > guarantee a memory access violation. All 4 implementation in the code base > have the same bug. I recommend removal of the source to cleanup the code and > build. > If DH support is required in the client at a later date we can either recover > the sources or better yet start over with testing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7612) Move statistics and logging implementation into .cpp files
[ https://issues.apache.org/jira/browse/GEODE-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman resolved GEODE-7612. -- Fix Version/s: 1.12.0 Resolution: Fixed > Move statistics and logging implementation into .cpp files > -- > > Key: GEODE-7612 > URL: https://issues.apache.org/jira/browse/GEODE-7612 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.12.0 > > Time Spent: 50m > Remaining Estimate: 0h > > As a developer, I would like to minimize the time spent recompiling code that > I haven't modified. One important way to improve this situation in the > native client is to move some of the bazillions of inline methods declared in > headers into .cpp files. A change to one of these methods then triggers a > recompile of just that file, rather than the large number of native client > files that inevitably include the header. > This item covers the above transformation for the internal classes involved > in logging and statistics. While there, we should clean up a couple of other > things that are unnecessary, such as the use of our own `NonCopyable` and > `NonAssignable`, both of which can now easily be accomplished with a standard > C++ 11 mechanism. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7620) Improve build on macOS Catalina
[ https://issues.apache.org/jira/browse/GEODE-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman resolved GEODE-7620. -- Fix Version/s: 1.12.0 Resolution: Fixed > Improve build on macOS Catalina > --- > > Key: GEODE-7620 > URL: https://issues.apache.org/jira/browse/GEODE-7620 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob Barrett >Priority: Major > Fix For: 1.12.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Improve build to not require SDK headers installation. > Update third party dependencies. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4346) Geode Native C# Example (Server-side function example)
[ https://issues.apache.org/jira/browse/GEODE-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4346: - Fix Version/s: 1.9.0 > Geode Native C# Example (Server-side function example) > -- > > Key: GEODE-4346 > URL: https://issues.apache.org/jira/browse/GEODE-4346 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 4h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4337) Geode Native C++ Example (Server-side function execution)
[ https://issues.apache.org/jira/browse/GEODE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4337: - Fix Version/s: 1.9.0 > Geode Native C++ Example (Server-side function execution) > - > > Key: GEODE-4337 > URL: https://issues.apache.org/jira/browse/GEODE-4337 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 8h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7785) Remove hard-coded SSL keystore/truststore paths from test code
[ https://issues.apache.org/jira/browse/GEODE-7785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7785: - Fix Version/s: 1.13.0 > Remove hard-coded SSL keystore/truststore paths from test code > -- > > Key: GEODE-7785 > URL: https://issues.apache.org/jira/browse/GEODE-7785 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The changes in PR #555 accidentally included some hard-coded paths to > retrieve SSL keystore/truststore files. This appears to have been overlooked > because the hard-coded paths are assigned to global test variables that > aren't, in fact, used. They should just be deleted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7783) Introduce dispersion on connections expiration
[ https://issues.apache.org/jira/browse/GEODE-7783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7783: - Fix Version/s: 1.13.0 > Introduce dispersion on connections expiration > -- > > Key: GEODE-7783 > URL: https://issues.apache.org/jira/browse/GEODE-7783 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.13.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > We are suffering performance issues due to c++ native client connections > expiration. > It would be convenient to introduce some dispersion so not all connections > are closed and open at the same time. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7528) Race condition in native CQ integration tests
[ https://issues.apache.org/jira/browse/GEODE-7528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7528: - Fix Version/s: 1.12.0 > Race condition in native CQ integration tests > - > > Key: GEODE-7528 > URL: https://issues.apache.org/jira/browse/GEODE-7528 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Fix For: 1.12.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Race conditions exist in the CQ new native integration tests. The tests only > wait for one counter to reach its threshold before continuing to check that > all counters have hit their thresholds. It is possible for the first counter > to be at threshold but the later not to be. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7520) Don't run clang-format in regular build steps
[ https://issues.apache.org/jira/browse/GEODE-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7520: - Fix Version/s: (was: 1.12.0) > Don't run clang-format in regular build steps > - > > Key: GEODE-7520 > URL: https://issues.apache.org/jira/browse/GEODE-7520 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > *We should* stop running clang-format as part of the "build" step in all CI > build pipelines > *Because* Visual Studio ships with _broken_ versions of clang-format from > time to time that crash while formatting our code, and this kills the Windows > build job. > We already have an agreed-upon version of clang-format, it's already running > on Travis CI for pull requests _and_ in private CI pipelines, we do _not_ > need it to be run for all flavors on all platforms every time we push to a > branch with a private pipeline or to a release branch or to develop. To fix > this properly, once and for all, we should: > i. disable clang-format in the build step for all flavors of all pipelines > ii. Create a separate clang-format job in all pipelines for _one_ flavor, > e.g. Ubuntu Debug > iii. Create an (optional) git commit hook for developers to use that will > _not allow you to push_ with outstanding formatting changes. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7520) Don't run clang-format in regular build steps
[ https://issues.apache.org/jira/browse/GEODE-7520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7520: - Fix Version/s: 1.12.0 > Don't run clang-format in regular build steps > - > > Key: GEODE-7520 > URL: https://issues.apache.org/jira/browse/GEODE-7520 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Fix For: 1.12.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > *We should* stop running clang-format as part of the "build" step in all CI > build pipelines > *Because* Visual Studio ships with _broken_ versions of clang-format from > time to time that crash while formatting our code, and this kills the Windows > build job. > We already have an agreed-upon version of clang-format, it's already running > on Travis CI for pull requests _and_ in private CI pipelines, we do _not_ > need it to be run for all flavors on all platforms every time we push to a > branch with a private pipeline or to a release branch or to develop. To fix > this properly, once and for all, we should: > i. disable clang-format in the build step for all flavors of all pipelines > ii. Create a separate clang-format job in all pipelines for _one_ flavor, > e.g. Ubuntu Debug > iii. Create an (optional) git commit hook for developers to use that will > _not allow you to push_ with outstanding formatting changes. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7429) Chocolatey install of active Perl times out
[ https://issues.apache.org/jira/browse/GEODE-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7429: - Fix Version/s: 1.12.0 > Chocolatey install of active Perl times out > --- > > Key: GEODE-7429 > URL: https://issues.apache.org/jira/browse/GEODE-7429 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Fix For: 1.12.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It is timing out when using packer buuld-windows.json -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7222) Add CMake support for building only the static library of cppcache
[ https://issues.apache.org/jira/browse/GEODE-7222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7222: - Fix Version/s: 1.11.0 > Add CMake support for building only the static library of cppcache > -- > > Key: GEODE-7222 > URL: https://issues.apache.org/jira/browse/GEODE-7222 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ivan Godwin >Priority: Major > Fix For: 1.11.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > We would like to have the ability to build only the static library of > cppcache, along with its dependencies. This would make it easier for external > projects that have Apache Geode Native Client as a dependency, and only want > the static library. > Note: This is required because we don't ship the static version of Apache > Geode Native Client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7180) Integration tests broken after IPv6 support (GEODE-7086)
[
https://issues.apache.org/jira/browse/GEODE-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-7180:
-
Fix Version/s: 1.11.0
> Integration tests broken after IPv6 support (GEODE-7086)
>
>
> Key: GEODE-7180
> URL: https://issues.apache.org/jira/browse/GEODE-7180
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> After merging the PR for GEODE-7086 and fixing Windows build breaks, it
> appears nearly all integration tests are failing on RHEL7 and Windows.
> Ubuntu appears to be okay, but I'm not 100% convinced yet, I only know that
> tests pass on *our* particular Ubuntu setup.
>
> The logs from RHEL7 give the following hint:
>
> {{C++ exception with description "Unknown host localhost" thrown in the test
> body.}}
>
> Which is coming from this line in the source:
>
> {{./cppcache/src/PoolFactory.cpp: throw IllegalArgumentException("Unknown
> host " + host);}}
>
> More info will be added here as investigation proceeds.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7113) Rat error in geode-native CI due to missing header in ./packer/windows/install-doxygen.ps1 file
[ https://issues.apache.org/jira/browse/GEODE-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7113: - Fix Version/s: 1.10.0 > Rat error in geode-native CI due to missing header in > ./packer/windows/install-doxygen.ps1 file > --- > > Key: GEODE-7113 > URL: https://issues.apache.org/jira/browse/GEODE-7113 > Project: Geode > Issue Type: Bug > Components: build, ci >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Fix For: 1.10.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The CI in the geode-native is broken due to > ./packer/windows/install-doxygen.ps1 lacking copyright header. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7086) Support of IPv6 In geode-native driver
[ https://issues.apache.org/jira/browse/GEODE-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7086: - Fix Version/s: 1.10.0 > Support of IPv6 In geode-native driver > -- > > Key: GEODE-7086 > URL: https://issues.apache.org/jira/browse/GEODE-7086 > Project: Geode > Issue Type: New Feature > Components: native client >Affects Versions: 1.9.0 >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: needs-review, pull-request-available > Fix For: 1.10.0 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > Currently geode-native does not support IPv6. Add impacts in geode-native for > support of IPv6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7056) Update Geode version in native client CI
[ https://issues.apache.org/jira/browse/GEODE-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7056: - Fix Version/s: 1.10.0 > Update Geode version in native client CI > > > Key: GEODE-7056 > URL: https://issues.apache.org/jira/browse/GEODE-7056 > Project: Geode > Issue Type: Wish > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.10.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Geode native client CI is using old Geode version (1.6.0) > It can be seen in logs: > -- Found Geode: /apache-geode-1.6.0/bin/gfsh (found suitable version "1.6.0", > minimum required is "1.0") -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7041) Write Test for FunctionService::OnServers() in New Test Framework
[ https://issues.apache.org/jira/browse/GEODE-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7041: - Fix Version/s: 1.10.0 > Write Test for FunctionService::OnServers() in New Test Framework > - > > Key: GEODE-7041 > URL: https://issues.apache.org/jira/browse/GEODE-7041 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.10.0 > > > Currently there are no C++ tests for this API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6957) Write Logging benchmarks to establish baseline performance
[ https://issues.apache.org/jira/browse/GEODE-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6957: - Fix Version/s: 1.10.0 > Write Logging benchmarks to establish baseline performance > -- > > Key: GEODE-6957 > URL: https://issues.apache.org/jira/browse/GEODE-6957 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We're hoping to soon remove the internal logging class from native client and > replace it with a 3rd party logger. Part of our due dilligence for the > effort should involve verifying that there are no performance regressions, so > we need a few simple benchmarks written to do some console and file logging. > We'll record #s for these on a couple of test machines, then re-run the > benchmarks on the same machines with the new logger and compare. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6961) Server error messages may contain leading whitespace
[ https://issues.apache.org/jira/browse/GEODE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6961: - Fix Version/s: 1.10.0 > Server error messages may contain leading whitespace > > > Key: GEODE-6961 > URL: https://issues.apache.org/jira/browse/GEODE-6961 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > > While debugging test failures, I discovered that a negative test case for > `Region::PutAll` was failing on _only one_ of our test machines, because the > Geode server returns an error string on our Linux test machine which contains > _no_ leading whitespace, but the same error string on our Mac test box starts > with _one_ leading space. The simple fix is to trim the leading space in the > native client, but perhaps it's worth a bit of someone's time later on to > determine what the difference is actually about. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6914) Switch the XML parser from libxml to xerces
[ https://issues.apache.org/jira/browse/GEODE-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6914: - Fix Version/s: 1.10.0 > Switch the XML parser from libxml to xerces > > > Key: GEODE-6914 > URL: https://issues.apache.org/jira/browse/GEODE-6914 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Matthew Reddington >Priority: Major > Fix For: 1.10.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > This is becoming a pain point on multiple dev platforms, so we need to switch > to something modern. On MacOS, libxml2 no longer builds on Mojave with > out-of-the-box tools, because /usr/include and /usr/lib have been removed > from the system. You can build it by running an installer package that Apple > includes with the tools _for the time being_, but it's going away, and BTW > having these directories causes problems with other packages (OpenSSL). On > Windows, the libxml build has a custom build step that _runs a javascript > file from the command line_, so if anything moves the .js file association > away from the windows scripting host (many, many applications do this, not > least of which is Webstorm IDE), you can't build libxml2 without swapping > back file associations manually. In short, it hurts when we do this, so > let's not do this any more. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6826) Refactor TcrConnection::readMessageChunked
[ https://issues.apache.org/jira/browse/GEODE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6826: - Fix Version/s: 1.10.0 > Refactor TcrConnection::readMessageChunked > -- > > Key: GEODE-6826 > URL: https://issues.apache.org/jira/browse/GEODE-6826 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.10.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Having debugged through a problem in this code recently, I can state with > authority that it is nigh onto unreadable in its current state, and needs to > be refactored into several helper methods to obviate the logic. The task > being performed here is not complex, so the code to perform it needs to > reflect that. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6835) AuthenticationException when using subscription and AuthInitialize
[ https://issues.apache.org/jira/browse/GEODE-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6835: - Fix Version/s: 1.10.0 > AuthenticationException when using subscription and AuthInitialize > -- > > Key: GEODE-6835 > URL: https://issues.apache.org/jira/browse/GEODE-6835 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.10.0 > > > When using subscription and AuthInitialize in conjunction while doing region > puts in a loop, the Geode server eventually appears to think the connection > is dead and throws an AuthenticationException. Correct behavior in this > circumstance, according to the Geode team, is to attempt to re-authenticate > and continue on. Again according to Geode, the Java-based client has this > retry logic and is working properly, but it appears the native client is > missing retry logic in at least one code path. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6718) Refactor TcrConnection::sendRequestForChunkedResponse, derived class, and remove pass-through calls in TrcConnection and derived
[ https://issues.apache.org/jira/browse/GEODE-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6718: - Fix Version/s: 1.10.0 > Refactor TcrConnection::sendRequestForChunkedResponse, derived class, and > remove pass-through calls in TrcConnection and derived > > > Key: GEODE-6718 > URL: https://issues.apache.org/jira/browse/GEODE-6718 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.10.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > This is a small thing we can do to make the code more readable and > maintainable. TcrEndpoint only has one derived class, TcrPoolEndPoint, and > the method sendRequestForChunkedResponse in both is simply a pass-through to > call TcrConnection::sendRequestForChunkedResponse. None of the parameters to > the TcrConnection call are unknown to calling code, so nothing at all is > being abstracted by having these methods on Tcr*Endpoint. Additionally, the > base class is abstract, so the implementation in TcrEndpoint is unreachable > code, and even though the method is virtual it is declared protected, so > nothing outside Tcr*Endpoint could possibly care about it. In short, the > method is gratuitous and removing it will clarify the code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6642) CacheAttributes header was left in the public header collection
[
https://issues.apache.org/jira/browse/GEODE-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6642:
-
Fix Version/s: 1.10.0
> CacheAttributes header was left in the public header collection
> ---
>
> Key: GEODE-6642
> URL: https://issues.apache.org/jira/browse/GEODE-6642
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.8.0
>Reporter: Jacob Barrett
>Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {{CacheAttributes}} is not longer necessary and was inadvertently left in the
> public headers. The factory, {{CacheAttributesFactory}} was removed prior to
> the first release. All public APIs using {{CacheAttributes}} were removed
> prior to the first release.
> It should be safe to remove the header completely and cleanup internal usage
> of this class without effecting the public API and ABI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6624) SIGABRT Due to nested exceptions when value returned that can't be deserialized
[ https://issues.apache.org/jira/browse/GEODE-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6624: - Fix Version/s: 1.10.0 > SIGABRT Due to nested exceptions when value returned that can't be > deserialized > --- > > Key: GEODE-6624 > URL: https://issues.apache.org/jira/browse/GEODE-6624 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.10.0 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > This gets a little weird, but in a nutshell: > * a client app needs to deploy a jar file containing a custom > DataSerializable object _without_ a default constructor, and a server > function that returns a value of this type > * Then, the app needs to call execute on a function service on a region (or > maybe a server, we're not sure it's relevant) to call the function that > returns the value of the class that's missing the default dtor > * In response, the server will send back a payload with dscode=45 > (DataSerializable), then a byte field for the type, which will be set to > dscode 43 (Class), then a string which is the name of the class, then the > bytes resulting from a call to toData() on that class instance > * The native client cannot correctly interpret this message, so the worker > thread that is trying to decode the message stores an exception to throw > later. > * Later on in the main thread, an exception gets thrown in > TcrMessage::readMessageChunked, but on the way out of readMessageChunked the > dtor for the contained FinalizeProcessChunk object gets called, which calls > m_reply.processChunk, which _also_ throws an exception, at which point the > process aborts because of the nested exceptions > We need to eat the 2nd exception, and throw the 1st, so that client apps can > catch the exception _and_ get an accurate message about what went wrong. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6597) ClientMetaDataService Causes Can't Pass GCHandle Across AppDomains Error
[ https://issues.apache.org/jira/browse/GEODE-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6597: - Fix Version/s: 1.9.0 > ClientMetaDataService Causes Can't Pass GCHandle Across AppDomains Error > > > Key: GEODE-6597 > URL: https://issues.apache.org/jira/browse/GEODE-6597 > Project: Geode > Issue Type: Bug >Reporter: Michael Martell >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Background thread used by ClientMetaDataService is used to update the native > client's meta. This thread was missed in the fix for solving appdomain > problems. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6575) Windows configuration 'RelWithDebInfo' doesn't build properly
[ https://issues.apache.org/jira/browse/GEODE-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6575: - Fix Version/s: 1.9.0 > Windows configuration 'RelWithDebInfo' doesn't build properly > - > > Key: GEODE-6575 > URL: https://issues.apache.org/jira/browse/GEODE-6575 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Several .net projects in the tree don't currently have this configuration, so > we need to add them. Going forward it's going to be critical to be able to > generate optimized Windows builds with debug symbols. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6547) Geode-Native User Guide - document 'sslputget' example
[ https://issues.apache.org/jira/browse/GEODE-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6547: - Fix Version/s: 1.9.0 > Geode-Native User Guide - document 'sslputget' example > -- > > Key: GEODE-6547 > URL: https://issues.apache.org/jira/browse/GEODE-6547 > Project: Geode > Issue Type: Sub-task > Components: docs, native client >Reporter: Dave Barnes >Priority: Major > Fix For: 1.9.0 > > > Document the 'sslputget' example. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6567) Geode native doesn't compile with gcc 8.x
[ https://issues.apache.org/jira/browse/GEODE-6567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6567: - Fix Version/s: 1.9.0 > Geode native doesn't compile with gcc 8.x > - > > Key: GEODE-6567 > URL: https://issues.apache.org/jira/browse/GEODE-6567 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jorge Perez Burgos >Priority: Minor > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Geode driver cannot compile with gcc 8.x due to several warnings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6538) Update Geode Native docs for v1.9
[ https://issues.apache.org/jira/browse/GEODE-6538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6538: - Fix Version/s: 1.9.0 > Update Geode Native docs for v1.9 > - > > Key: GEODE-6538 > URL: https://issues.apache.org/jira/browse/GEODE-6538 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Fix For: 1.9.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Update the version number in doc sources for the geode-native user guide -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6507) Move all clangformat projects into subfolder
[ https://issues.apache.org/jira/browse/GEODE-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6507: - Fix Version/s: 1.9.0 > Move all clangformat projects into subfolder > > > Key: GEODE-6507 > URL: https://issues.apache.org/jira/browse/GEODE-6507 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.9.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Improve readability of the solution by moving all clangformat projects into a > clangformat subdir. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6491) Can't Run ASP.NET apps that use geode-native with authentication
[ https://issues.apache.org/jira/browse/GEODE-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6491: - Fix Version/s: 1.9.0 > Can't Run ASP.NET apps that use geode-native with authentication > > > Key: GEODE-6491 > URL: https://issues.apache.org/jira/browse/GEODE-6491 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.9.0 > > Time Spent: 40m > Remaining Estimate: 0h > > If authentication is not used, ASP.NET apps that use geode-native work just > fine. However, when we run such apps using geode-native with authentication, > a .NET System.ArgumentException is thrown with this message: "Can't pass > GCHandle across appDomains". > > This is being marked as a Major bug, since to run apps in Pivotal Cloud > Foundry requires using authentication. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6469) Remove cryptoimpl.lib from nativeclient release
[ https://issues.apache.org/jira/browse/GEODE-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6469: - Fix Version/s: 1.9.0 > Remove cryptoimpl.lib from nativeclient release > --- > > Key: GEODE-6469 > URL: https://issues.apache.org/jira/browse/GEODE-6469 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > We build and ship a sample SSL encryption library called cryptoimpl, which is > a dependency of the nativeclient. On Windows, our install currently includes > the cryptoimpl.dll and cryptoimpl.lib. The cryptoimpl.lib is an import > library and should not be part of the release artifacts -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6300) Assertion in CLI tests re: bad AppDomain
[
https://issues.apache.org/jira/browse/GEODE-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6300:
-
Fix Version/s: 1.9.0
> Assertion in CLI tests re: bad AppDomain
>
>
> Key: GEODE-6300
> URL: https://issues.apache.org/jira/browse/GEODE-6300
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> From the ci logs
> (http://concourse-nativeclient.gemfire.pivotal.io/teams/main/pipelines/build-develop/jobs/cli-test-windows-debug/builds/64):
>
> System.ArgumentException: Cannot pass a GCHandle across AppDomains.
> Parameter name: handle
> at System.Runtime.InteropServices.GCHandle.InternalCheckDomain(IntPtr handle)
> at System.Runtime.InteropServices.GCHandle.FromIntPtr(IntPtr value)
> at gcroot ^>.\{dtor}(gcroot* )
> at
> apache.geode.client.ManagedDataSerializablePrimitive.\{dtor}(ManagedDataSerializablePrimitive*
> )
> at
> apache.geode.client.ManagedDataSerializablePrimitive.__vbaseDtor(ManagedDataSerializablePrimitive*
> )
> at
> apache.geode.client.ManagedDataSerializablePrimitive.__vecDelDtor(ManagedDataSerializablePrimitive*
> , UInt32 A_0)
> at
> std._Ref_count._Destroy(_Ref_count*
> )
> errorlevel 0
> + exitcode=1
> + echo exitcode=1
> exitcode=1
> + exit 1
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6262) Cppcache Unit Tests Don't Support Multiple Iterations
[ https://issues.apache.org/jira/browse/GEODE-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6262: - Fix Version/s: 1.9.0 > Cppcache Unit Tests Don't Support Multiple Iterations > - > > Key: GEODE-6262 > URL: https://issues.apache.org/jira/browse/GEODE-6262 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > TcrMessageTest uses some funky macros to create compare strings for gtest > EXPECT_MESSAGE. The compare strings don't work when multiple iterations of > the tests, the sequence number causes overflow of the field. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6250) Port testCache tests to new integration framework
[ https://issues.apache.org/jira/browse/GEODE-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6250: - Fix Version/s: 1.9.0 > Port testCache tests to new integration framework > - > > Key: GEODE-6250 > URL: https://issues.apache.org/jira/browse/GEODE-6250 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > As a developer on NC, I would very much like to be able to debug my > integration tests in an IDE. As a matter of course we're going to port all > existing tests to the new framework and delete the old code. The new > framework is simpler and uses gtest, so we can debug it in the CLion IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6245) Fix microsoft specific pragma compiler warnings.
[ https://issues.apache.org/jira/browse/GEODE-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6245: - Fix Version/s: 1.9.0 > Fix microsoft specific pragma compiler warnings. > > > Key: GEODE-6245 > URL: https://issues.apache.org/jira/browse/GEODE-6245 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6249) Port AttributesMutator test to new framework
[ https://issues.apache.org/jira/browse/GEODE-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6249: - Fix Version/s: 1.9.0 > Port AttributesMutator test to new framework > > > Key: GEODE-6249 > URL: https://issues.apache.org/jira/browse/GEODE-6249 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 2h > Remaining Estimate: 0h > > As a developer on NC, I would very much like to be able to debug my > integration tests in an IDE. As a matter of course we're going to port all > existing tests to the new framework and delete the old code. The new > framework is simpler and uses gtest, so we can debug it in the CLion IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6229) Need an Ubuntu Packer image
[ https://issues.apache.org/jira/browse/GEODE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6229: - Fix Version/s: 1.9.0 > Need an Ubuntu Packer image > --- > > Key: GEODE-6229 > URL: https://issues.apache.org/jira/browse/GEODE-6229 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Assignee: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h > Remaining Estimate: 0h > > As a user of NC, I need to be able to build/run on Ubuntu in addition to > RedHat. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6240) Fix rat complaints
[
https://issues.apache.org/jira/browse/GEODE-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6240:
-
Fix Version/s: 1.9.0
> Fix rat complaints
> --
>
> Key: GEODE-6240
> URL: https://issues.apache.org/jira/browse/GEODE-6240
> Project: Geode
> Issue Type: Task
> Components: native client
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{packer/ubuntu/files/etc/systemd/system/update-hosts.service}} and
> {{packer/ubuntu/files/usr/local/bin/update-hosts.sh}} are missing licenses
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6226) The release file naming should be congruent with core
[
https://issues.apache.org/jira/browse/GEODE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6226:
-
Fix Version/s: 1.9.0
> The release file naming should be congruent with core
> -
>
> Key: GEODE-6226
> URL: https://issues.apache.org/jira/browse/GEODE-6226
> Project: Geode
> Issue Type: Task
> Components: native client
>Reporter: Charlie Black
>Priority: Major
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the release file naming it looks like we are not in compliance with the
> core.
> {{
> apache-geode-1.8.0-src.tgz
> apache-geode-1.8.0-src.tgz.asc
> apache-geode-1.8.0-src.tgz.sha256
> apache-geode-1.8.0.tgz
> apache-geode-1.8.0.tgz.asc
> apache-geode-1.8.0.tgz.sha256
> apache-geode-examples-1.8.0.tar.gz
> apache-geode-examples-1.8.0.tar.gz.asc
> apache-geode-examples-1.8.0.tar.gz.sha256
> apache-geode-examples-1.8.0.zip
> apache-geode-examples-1.8.0.zip.asc
> apache-geode-examples-1.8.0.zip.sha256
> apache-geode-native-1.8.0-Source.tar.gz
> apache-geode-native-1.8.0-Source.tar.gz.asc
> apache-geode-native-1.8.0-Source.tar.gz.sha512}}
> In this example, we would need to change "Source" to src. Also any reason we
> are 512 and the core is 256 if there isn't a reason make the sha the same
> number of bits.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6211) Geode Native C# Example (Exception Handling)
[ https://issues.apache.org/jira/browse/GEODE-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6211: - Fix Version/s: 1.9.0 > Geode Native C# Example (Exception Handling) > > > Key: GEODE-6211 > URL: https://issues.apache.org/jira/browse/GEODE-6211 > Project: Geode > Issue Type: Sub-task > Components: examples, native client >Reporter: Charlie Black >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > As a user, I would like to see an example of how to handle a common exception > thrown by Geode. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6199) Remove pdxautoserializer from contrib
[ https://issues.apache.org/jira/browse/GEODE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6199: - Fix Version/s: 1.9.0 > Remove pdxautoserializer from contrib > - > > Key: GEODE-6199 > URL: https://issues.apache.org/jira/browse/GEODE-6199 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This code was moved to contrib in preparation for removal, and no longer > compiles. Time to get rid of it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6210) Geode Native C++ Example (Transaction with Retry)
[ https://issues.apache.org/jira/browse/GEODE-6210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6210: - Fix Version/s: 1.9.0 > Geode Native C++ Example (Transaction with Retry) > - > > Key: GEODE-6210 > URL: https://issues.apache.org/jira/browse/GEODE-6210 > Project: Geode > Issue Type: Sub-task > Components: examples, native client >Reporter: Charlie Black >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > As an end user, I would like to see an example of how to handle a common > exception thrown by Geode. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6165) Need a workaround to install Doxygen on Windows AMI
[ https://issues.apache.org/jira/browse/GEODE-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6165: - Fix Version/s: 1.9.0 > Need a workaround to install Doxygen on Windows AMI > --- > > Key: GEODE-6165 > URL: https://issues.apache.org/jira/browse/GEODE-6165 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Our install-dependencies.ps1 script that runs when we create a Windows build > image is failing because the underlying URL for the Doxygen Chocolatey > installer has gone bad, and the Chocolatey package isn't being actively > updated. Until the package is fixed, we need a way to install Doxygen on our > AMIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6160) CPack ignore syntax isn't properly escaped
[
https://issues.apache.org/jira/browse/GEODE-6160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6160:
-
Fix Version/s: 1.9.0
> CPack ignore syntax isn't properly escaped
> --
>
> Key: GEODE-6160
> URL: https://issues.apache.org/jira/browse/GEODE-6160
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In our .cpackignore file, we have lines of the form "\.foo", for example, but
> the regex syntax also has to be escaped like a C string for some reason, aka "
> .foo".
>
> Repro steps:
> * Configure using cmake in a clean repo
> * cd into cmake build dir
> * run 'cpack -G TGZ ---config CPackSourceConfig.cmake' to generate a source
> package
> Expected result
> * Source package generated without complaints
> Actual result
> * Source package generated
> * cpack complains about syntax, for example:
> {code:java}
> CMake Warning (dev) at
> /Users/pivotal/Workspace/cmake-build-debug/geode-native/CPackSourceConfig.cmake:74
> (set):
> Syntax error in cmake code at
>
>
> /Users/pivotal/Workspace/cmake-build-debug/geode-native/CPackSourceConfig.cmake:74
>
> when parsing string
>
>
> /\.git/;/\.DS_Store;/build-./;/build/;/\.settings/;/\.cproject;/\.project;/\.idea/;\.vs/;\.vscode/;/examples/dotnet/./bin/;/examples/dotnet/.*/obj/;\.ruby-version
>
> Invalid escape sequence \.
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6114) C++ examples can't be built individually if they need a jar file
[ https://issues.apache.org/jira/browse/GEODE-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6114: - Fix Version/s: 1.9.0 > C++ examples can't be built individually if they need a jar file > > > Key: GEODE-6114 > URL: https://issues.apache.org/jira/browse/GEODE-6114 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Our documentation says to cd into the individual example directory, aka > cpp/<>, and run cmake commands from there to build. If you do > this for an example that requires example.jar, the utilities directory is not > built, so there is no jar file to deploy, thus you can't run the example. If > an example requires example.jar, it needs to ensure the utilities directory > is built in its CMakeLists.txt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6139) Fix rat complaints about files for 1.8 release
[ https://issues.apache.org/jira/browse/GEODE-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6139: - Fix Version/s: 1.9.0 > Fix rat complaints about files for 1.8 release > -- > > Key: GEODE-6139 > URL: https://issues.apache.org/jira/browse/GEODE-6139 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Rat is griping about the missing license headers in a few of the source > files, so these need to be added. It's also complaining about a few config > files which do NOT need license headers, so these need to be added to > .ratignore. We also saw some leftover stuff in a cmake-build-debug folder, > so we need to make sure the directory is git cleaned before the release > manager runs cpack. Lastly, one file was mysteriously absent from the > documentation in the final package, so we need to verify that this was > spurious or get the file properly added. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6054) Make geode-native build with VS 2017 runtime
[ https://issues.apache.org/jira/browse/GEODE-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6054: - Fix Version/s: 1.9.0 > Make geode-native build with VS 2017 runtime > > > Key: GEODE-6054 > URL: https://issues.apache.org/jira/browse/GEODE-6054 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 5h > Remaining Estimate: 0h > > Just need to configure cmake locally with VS 2017 runtime, build and run > tests and make sure everything is copacetic. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-5957) Unexpected exception when executing an unknown function.
[ https://issues.apache.org/jira/browse/GEODE-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-5957: - Fix Version/s: 1.9.0 > Unexpected exception when executing an unknown function. > > > Key: GEODE-5957 > URL: https://issues.apache.org/jira/browse/GEODE-5957 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::MessageException: : message from server could not be > handled -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6007) Fix LGTM complaints in NC code base
[ https://issues.apache.org/jira/browse/GEODE-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6007: - Fix Version/s: 1.11.0 > Fix LGTM complaints in NC code base > --- > > Key: GEODE-6007 > URL: https://issues.apache.org/jira/browse/GEODE-6007 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.11.0 > > Time Spent: 2h > Remaining Estimate: 0h > > This is showing stuff that is bad practice in general, and may open us up to > maliciousness. There are two main situations in which we find lots of usage > of snprintf with raw char buffers, which are: > * formatting messages for exceptions > * formatting messages for logging > For the exception messages, we should switch to something known to be safe - > a vsxprintf implementation, boost::format, std::stringstream, whatever. As > long as we stop declaring raw char buffers on the stack, it's all good > > For logging, the situation is even dumber. The various LOG* macros in the > code _already_ take a format string and varargs, so as far as I know we > essentially need to move the printf-style arguments into the logging macro > and get rid of the other nonsense. We may even buy a tiny performance > improvement due to the fact that that logging macros can be compiled out of > the code. > > UPDATE: Report from running LGTM on our code may be found at > [https://lgtm.com/projects/g/apache/geode-native/alerts/?mode=list.] This > report has issues with tons of printf-style format specifiers, so it catches > most of the snprintf stuff pointed out above. MANY OF THESE ARE BUFFER > OVERFLOW ISSUES, and must be addressed in the name of security. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4841) Switch declaration of HashMapOfPools to 'using' in PoolManagerImpl
[ https://issues.apache.org/jira/browse/GEODE-4841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4841: - Fix Version/s: 1.9.0 > Switch declaration of HashMapOfPools to 'using' in PoolManagerImpl > -- > > Key: GEODE-4841 > URL: https://issues.apache.org/jira/browse/GEODE-4841 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Currently this is a convenience typedef in the header file, and comes with > all the associated baggage - pollutes the global namespace, etc. We should > be good C++11 citizens and remove the typedef, replacing it with a 'using' > statement at class scope closer to where we actually need the type. Or, just > declare variables of this type as 'auto' in PoolManagerImpl, even more > convenient. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-5708) Memory corruption in c++ client
[ https://issues.apache.org/jira/browse/GEODE-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-5708: - Fix Version/s: 1.9.0 > Memory corruption in c++ client > --- > > Key: GEODE-5708 > URL: https://issues.apache.org/jira/browse/GEODE-5708 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jorge Perez Burgos >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Attachments: > fix-memory-allocation-d0ff5d7e393f17955f54d3fe0bdf2694c78e9a7e.patch > > Time Spent: 50m > Remaining Estimate: 0h > > When using partition regions there is a double free the ends corrupting the > client process. This is caused because instead of assigning shared pointers > directly the content of a shared pointer is assign to another shared pointer > so the reference count is messed up. I attach a tentative fix/workaround that > copies the content although the best option is possibly to create a new or > modify a constructor in VersionedCacheableObjectPartList class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4348) Geode Native C# Example (SSL example)
[ https://issues.apache.org/jira/browse/GEODE-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4348: - Fix Version/s: 1.9.0 > Geode Native C# Example (SSL example) > - > > Key: GEODE-4348 > URL: https://issues.apache.org/jira/browse/GEODE-4348 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Fix For: 1.9.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4340) Geode Native C++ Example (Authentication)
[ https://issues.apache.org/jira/browse/GEODE-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4340: - Fix Version/s: 1.9.0 > Geode Native C++ Example (Authentication) > - > > Key: GEODE-4340 > URL: https://issues.apache.org/jira/browse/GEODE-4340 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Priority: Major > Fix For: 1.9.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > It's easy to get Authentication and securing a connection with SSL confused > because they almost always go hand in hand. This example shows how to require > username and password to perform actions on a specific region. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-4339) Geode Native C++ Example (SSL example)
[ https://issues.apache.org/jira/browse/GEODE-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-4339: - Fix Version/s: 1.9.0 > Geode Native C++ Example (SSL example) > -- > > Key: GEODE-4339 > URL: https://issues.apache.org/jira/browse/GEODE-4339 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Addison >Assignee: Ivan Godwin >Priority: Major > Fix For: 1.9.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > This is example should show how to set up a secure connection between a > client and the cluster. The example should still have a start cluster and > build client script with instruction on how to run the client. The example > should not include its own certificates. Rather, there should be a directory > where the user can drop certs from https://letsencrypt.org/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-3415) Add support for certificate chain files in SSL configuration
[ https://issues.apache.org/jira/browse/GEODE-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-3415: - Fix Version/s: 1.10.0 > Add support for certificate chain files in SSL configuration > > > Key: GEODE-3415 > URL: https://issues.apache.org/jira/browse/GEODE-3415 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob Barrett >Priority: Major > Fix For: 1.10.0 > > Time Spent: 3h > Remaining Estimate: 0h > > Native client does not support certificate chain files so certificates signed > by intermediates may not be trusted if the intermediate is not explicitly > trusted by the destination servers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-3287) Remove Assert.hpp
[ https://issues.apache.org/jira/browse/GEODE-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-3287: - Fix Version/s: (was: 1.10.0) > Remove Assert.hpp > - > > Key: GEODE-3287 > URL: https://issues.apache.org/jira/browse/GEODE-3287 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Ernest Burghardt >Assignee: Blake Bender >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > replace with std::assert -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-3287) Remove Assert.hpp
[ https://issues.apache.org/jira/browse/GEODE-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-3287: - Fix Version/s: 1.10.0 > Remove Assert.hpp > - > > Key: GEODE-3287 > URL: https://issues.apache.org/jira/browse/GEODE-3287 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Ernest Burghardt >Assignee: Blake Bender >Priority: Major > Fix For: 1.10.0 > > Time Spent: 1h > Remaining Estimate: 0h > > replace with std::assert -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-2484) Remove ACE from native client dependencies
[ https://issues.apache.org/jira/browse/GEODE-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-2484: - Fix Version/s: 1.9.0 > Remove ACE from native client dependencies > -- > > Key: GEODE-2484 > URL: https://issues.apache.org/jira/browse/GEODE-2484 > Project: Geode > Issue Type: Task > Components: native client >Reporter: David Kimura >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 10.5h > Remaining Estimate: 0h > > Remove ACE from native client dependencies. > Replace ACE usage with C++11 and/or Boost 1.63+ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6800) CacheableFileName linker error
[
https://issues.apache.org/jira/browse/GEODE-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6800:
-
Fix Version/s: 1.10.0
> CacheableFileName linker error
> --
>
> Key: GEODE-6800
> URL: https://issues.apache.org/jira/browse/GEODE-6800
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Ivan Godwin
>Assignee: Ivan Godwin
>Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When building a program using CacheableFileName, linker errors are
> encountered. This has only been observed with certain versions of gcc and
> clang.
> {code:c++}undefined reference to `VTT for
> apache::geode::client::CacheableFileName'{code}
> Adding the ppa:ubuntu-toolchain-r/test respository to Ubuntu 16.04, GCC 5.5.0
> is installable and may be used to reproduce.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7619) Confusing error message when cryptoImpl is not on the path
Diane Hardman created GEODE-7619: Summary: Confusing error message when cryptoImpl is not on the path Key: GEODE-7619 URL: https://issues.apache.org/jira/browse/GEODE-7619 Project: Geode Issue Type: Bug Components: native client Reporter: Diane Hardman When following the example sslputget on Linux, if I don't have LD_LIBRARY_PATH set to the location where libcryptoImpl.so resides, when the app does it's first put, the error is ambiguous and caused me to question if I was referencing an incorrect locator IP address. Here is the error message generated: terminate called after throwing an instance of 'std::_Nested_exception' what(): : No locators available Aborted (core dumped) Prefer a more specific error message such as "Could not connect to locator configured with SSL; could not find libcryptoImpl.so. Is LD_LIBRARY_PATH set?" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7511) Support Long DNS Names
[ https://issues.apache.org/jira/browse/GEODE-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7511: - Fix Version/s: (was: 1.11.0) 1.12.0 > Support Long DNS Names > -- > > Key: GEODE-7511 > URL: https://issues.apache.org/jira/browse/GEODE-7511 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.12.0 > > Time Spent: 50m > Remaining Estimate: 0h > > NodeJS client was failing on PCC 1.9.1. Long DNS was introduced in PCC 1.9.1 > for locator and server members. The spec for DNS says names can be up to > approximately 256 characters. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7419) Complete info about geode-native integration tests
[ https://issues.apache.org/jira/browse/GEODE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7419: - Fix Version/s: (was: 1.11.0) 1.12.0 > Complete info about geode-native integration tests > -- > > Key: GEODE-7419 > URL: https://issues.apache.org/jira/browse/GEODE-7419 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.12.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Complete info about the two sets of geode-native integration tests, and the > preference of implementing new tests using GoogleTest. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6312) Missing Prerequisite in BUILDING.md
[ https://issues.apache.org/jira/browse/GEODE-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6312: - Fix Version/s: (was: 1.11.0) 1.12.0 > Missing Prerequisite in BUILDING.md > --- > > Key: GEODE-6312 > URL: https://issues.apache.org/jira/browse/GEODE-6312 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.12.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The BUILDING.md prerequisites for the native client is missing the JDK, which > is required for building the server side java functions used in some of the > integration tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7451) Add certificate & private key in correct order to avoid exception
[ https://issues.apache.org/jira/browse/GEODE-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7451: - Fix Version/s: (was: 1.11.0) 1.12.0 > Add certificate & private key in correct order to avoid exception > - > > Key: GEODE-7451 > URL: https://issues.apache.org/jira/browse/GEODE-7451 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.12.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When using TLS, geode native client throws an exception due to wrong order on > method calling: > "Exception while querying locator: apache::geode::client::SslException: > Invalid SSL keystore password." > This is due to in SSLImpl.cpp constructor, the private key is added before > the certificate. According to ACE documentation, we should reverse order due > to when the private key is added it is verified against the certificate. So > we should call sslctx->private_key after calling sslctx->certificate > http://www.aoc.nrao.edu/php/tjuerges/ALMA/ACE-5.8.1/html/ace/a00493.html#a5fa01171382ad69ac372dae7e3860211 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-6312) Missing Prerequisite in BUILDING.md
[ https://issues.apache.org/jira/browse/GEODE-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6312: - Fix Version/s: (was: 1.12.0) 1.11.0 > Missing Prerequisite in BUILDING.md > --- > > Key: GEODE-6312 > URL: https://issues.apache.org/jira/browse/GEODE-6312 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The BUILDING.md prerequisites for the native client is missing the JDK, which > is required for building the server side java functions used in some of the > integration tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7182) TcpSslConn.cpp does not compile with gcc 8.3
[ https://issues.apache.org/jira/browse/GEODE-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7182: - Fix Version/s: (was: 1.11.0) 1.10.0 > TcpSslConn.cpp does not compile with gcc 8.3 > > > Key: GEODE-7182 > URL: https://issues.apache.org/jira/browse/GEODE-7182 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Owen Nichols >Priority: Major > Fix For: 1.10.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > I tried to build native client using: > $ gcc --version > gcc (Debian 8.3.0-6) 8.3.0 > $ cmake --version > cmake version 3.13.4 > $ openssl version > OpenSSL 1.1.1c 28 May 2019 > and got: > cppcache/src/TcpSslConn.cpp:60: error: catching polymorphic type 'class > std::exception' by value > The BUILDING.md states that I should be able to use "GCC 5 or newer". > Fixing the code to resolve this warning is a straightforward 1-character > change and a good idea anyway even if the official pipelines continue to > compile using older compilers that don't generate this warning yet. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7198) C++ authinitialize example hangs
[ https://issues.apache.org/jira/browse/GEODE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7198: - Fix Version/s: (was: 1.11.0) > C++ authinitialize example hangs > > > Key: GEODE-7198 > URL: https://issues.apache.org/jira/browse/GEODE-7198 > Project: Geode > Issue Type: Bug > Components: native client >Affects Versions: 1.8.0 >Reporter: Diane Hardman >Assignee: Charlie Black >Priority: Major > Attachments: server.log > > Time Spent: 20m > Remaining Estimate: 0h > > After building geode-native from develop branch on my mac, I then followed > the instructions to build the geode-native examples found here: > [https://github.com/apache/geode-native/tree/develop/examples] > Trying to run the authinitialize example resulted in a hang. > 1. First I needed to correct the startserver.sh script to remove spaces > around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. > 2. Running cpp-authinitialize seems to hang when executing GetCredentials: > dhardman$ ./cpp-authinitialize > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::NotConnectedException: : not connected to Geode > Abort trap: 6 > > Expected: The README file indicates the following output > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::getCredentials called > a = 1 > b = 2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7429) Chocolatey install of active Perl times out
[ https://issues.apache.org/jira/browse/GEODE-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7429: - Fix Version/s: (was: 1.11.0) > Chocolatey install of active Perl times out > --- > > Key: GEODE-7429 > URL: https://issues.apache.org/jira/browse/GEODE-7429 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > It is timing out when using packer buuld-windows.json -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7203) C++ examples need to be updated
[ https://issues.apache.org/jira/browse/GEODE-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7203: - Fix Version/s: 1.11.0 > C++ examples need to be updated > --- > > Key: GEODE-7203 > URL: https://issues.apache.org/jira/browse/GEODE-7203 > Project: Geode > Issue Type: Bug > Components: examples, native client >Reporter: Diane Hardman >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > After reviewing the C++ native client examples I found several problems: > # Transaction - README should be updated to indicate random output; > currently it says to expect the following output, but this will be different > each time: Created cache > Created region 'exampleRegion' > Rolled back transaction - retrying(4) > Rolled back transaction - retrying(3) > Rolled back transaction - retrying(2) > Committed transaction - exiting > # functionexecution - this is the only example that spins up a server named > 'the-server'; the startserver.sh script should be updated to reflect the same > name used in all other examples 'server'. > # pdxserializable - either the README needs to change to show the actual > output of running the client app, or main.cpp should be changed to produce > the same output presented in the README. The second get (of Customer2) is > currently not formatted for printing like the first get (of Customer1). > # All examples: stopserver.sh should cleanup leftover directories locator/, > server/, and any *.gfs. If there is any reason to keep these around for > failing tests, then a separate cleanup.sh script should do this. > # authinitialize - startserver.sh fails due to extra spaces around '=' when > setting RESOLVEDPATH and AUTHENTICATOR. This example also fails to run, > instead hangs when executing getCredentials, but this was filed as GEODE-7198. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7225) Update OpenSSL download URL in Windows Packer script
[ https://issues.apache.org/jira/browse/GEODE-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7225: - Fix Version/s: 1.11.0 > Update OpenSSL download URL in Windows Packer script > > > Key: GEODE-7225 > URL: https://issues.apache.org/jira/browse/GEODE-7225 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The Windows build of OpenSSL has bumped from 1.1c to 1.1d, and our download > script for Windows is now failing with 404 errors. Just need to change one > character in the URL and we're good to go. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7207) FIx Remaining LGTM "Error" level alerts
[ https://issues.apache.org/jira/browse/GEODE-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7207: - Fix Version/s: 1.11.0 > FIx Remaining LGTM "Error" level alerts > --- > > Key: GEODE-7207 > URL: https://issues.apache.org/jira/browse/GEODE-7207 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.11.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > We're down to a manageable number of these now, it should be fairly short > work to fix the remaining issues. > > Acceptance criteria: > When a PR is submitted and LGTM scans the code base, the report for this PR > shows 12 alerts fixed, all of which are "error" level alerts, and no new > alerts introduced. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7285) Several Examples Don't Work on Windows
[ https://issues.apache.org/jira/browse/GEODE-7285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7285: - Fix Version/s: 1.11.0 > Several Examples Don't Work on Windows > -- > > Key: GEODE-7285 > URL: https://issues.apache.org/jira/browse/GEODE-7285 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The list of examples below do not work do to a mismatch between the server > start/stop scripts and the code. Specifically, several scripts create/destroy > a region of one name, but the example code tries to use a region of a > different name. > Broken examples: > * continuousquery (Windows) > * dataserializable (Windows) > * pdxserializable (Windows) > * pdxserializer (Windows) > * transaction (Windows) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7235) Disable new Clang warnings to fix build for now
[ https://issues.apache.org/jira/browse/GEODE-7235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7235: - Fix Version/s: 1.11.0 > Disable new Clang warnings to fix build for now > --- > > Key: GEODE-7235 > URL: https://issues.apache.org/jira/browse/GEODE-7235 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Fix For: 1.11.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Apple pushed an XCode update a couple of days ago to version ` > Apple clang version 11.0.0 (clang-1100.0.33.8)`. This version flags some new > warnings in our code, and since we have warnings-as-errors turned on we blow > up. Fixing these warnings is non-trivial, so we need to disable them in the > top-level CMakeLists.txt and file another Jira issue to do the real fix. > * Steps to repro: > Sync up to the latest `develop` branch of Native Client on a Mac and build > * Expected Result: > Geode Native builds, and produces our libraries > * Actual Result: > Clang warns about "implicitly deleted copy/move ctors declared as default" in > a product header, gives a warning about UTF-8 string literals in test code, > then build fails. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7429) Chocolatey install of active Perl times out
[ https://issues.apache.org/jira/browse/GEODE-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7429: - Fix Version/s: 1.11.0 > Chocolatey install of active Perl times out > --- > > Key: GEODE-7429 > URL: https://issues.apache.org/jira/browse/GEODE-7429 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Oleske >Priority: Major > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It is timing out when using packer buuld-windows.json -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7347) Race condition between Cache and ClientMetadataService
[ https://issues.apache.org/jira/browse/GEODE-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7347: - Fix Version/s: 1.11.0 > Race condition between Cache and ClientMetadataService > -- > > Key: GEODE-7347 > URL: https://issues.apache.org/jira/browse/GEODE-7347 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Matthew Reddington >Assignee: Michael Oleske >Priority: Major > Fix For: 1.11.0 > > Time Spent: 40m > Remaining Estimate: 0h > > It was discovered that the ClientMetadataService would call into CacheImpl, > which contains a backreference to Cache, and this could occur in the middle > of a Cache move, where the pimpl pointer was updated, but not the > backreference. > The solution will be to guard the pimpl during the move, so the Cache can > update it's pimpl and the backreference. There exists > CacheImpl::doIfDestroyNotPending that locks the pimpl while executing a > function to facilitate this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7419) Complete info about geode-native integration tests
[ https://issues.apache.org/jira/browse/GEODE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7419: - Fix Version/s: (was: 1.12.0) 1.11.0 > Complete info about geode-native integration tests > -- > > Key: GEODE-7419 > URL: https://issues.apache.org/jira/browse/GEODE-7419 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Minor > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Complete info about the two sets of geode-native integration tests, and the > preference of implementing new tests using GoogleTest. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7451) Add certificate & private key in correct order to avoid exception
[ https://issues.apache.org/jira/browse/GEODE-7451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7451: - Fix Version/s: (was: 1.12.0) 1.11.0 > Add certificate & private key in correct order to avoid exception > - > > Key: GEODE-7451 > URL: https://issues.apache.org/jira/browse/GEODE-7451 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Alberto Bustamante Reyes >Assignee: Alberto Bustamante Reyes >Priority: Major > Labels: pull-request-available > Fix For: 1.11.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When using TLS, geode native client throws an exception due to wrong order on > method calling: > "Exception while querying locator: apache::geode::client::SslException: > Invalid SSL keystore password." > This is due to in SSLImpl.cpp constructor, the private key is added before > the certificate. According to ACE documentation, we should reverse order due > to when the private key is added it is verified against the certificate. So > we should call sslctx->private_key after calling sslctx->certificate > http://www.aoc.nrao.edu/php/tjuerges/ALMA/ACE-5.8.1/html/ace/a00493.html#a5fa01171382ad69ac372dae7e3860211 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7426) Integration tests segfault on MacOs with geode-native
[ https://issues.apache.org/jira/browse/GEODE-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7426: - Fix Version/s: (was: 1.12.0) 1.11.0 > Integration tests segfault on MacOs with geode-native > - > > Key: GEODE-7426 > URL: https://issues.apache.org/jira/browse/GEODE-7426 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > A segfault occurs on MacOS when running any of the integration tests. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7198) C++ authinitialize example hangs
[ https://issues.apache.org/jira/browse/GEODE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-7198: - Attachment: server.log > C++ authinitialize example hangs > > > Key: GEODE-7198 > URL: https://issues.apache.org/jira/browse/GEODE-7198 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Diane Hardman >Priority: Major > Attachments: server.log > > > After building geode-native from develop branch on my mac, I then followed > the instructions to build the geode-native examples found here: > [https://github.com/apache/geode-native/tree/develop/examples] > Trying to run the authinitialize example resulted in a hang. > 1. First I needed to correct the startserver.sh script to remove spaces > around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. > 2. Running cpp-authinitialize seems to hang when executing GetCredentials: > dhardman$ ./cpp-authinitialize > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::NotConnectedException: : not connected to Geode > Abort trap: 6 > > Expected: The README file indicates the following output > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::getCredentials called > a = 1 > b = 2 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7198) C++ authinitialize example hangs
[ https://issues.apache.org/jira/browse/GEODE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928951#comment-16928951 ] Diane Hardman commented on GEODE-7198: -- Another issue, why is this labeled as a warning in the server log? [warn 2019/09/12 16:50:54.616 PDT tid=0x3e] Server connection from [identity(0.0.0.0(default_GeodeDS:51001:loner):2:Native_cdgdecdece51001:default_GeodeDS,connection=1; port=58813]: Security exception: org.apache.geode.security.AuthenticationFailedException: javaobject.SimpleAuthenticator, caused by: java.lang.ClassNotFoundException: javaobject.SimpleAuthenticator > C++ authinitialize example hangs > > > Key: GEODE-7198 > URL: https://issues.apache.org/jira/browse/GEODE-7198 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Diane Hardman >Priority: Major > > After building geode-native from develop branch on my mac, I then followed > the instructions to build the geode-native examples found here: > [https://github.com/apache/geode-native/tree/develop/examples] > Trying to run the authinitialize example resulted in a hang. > 1. First I needed to correct the startserver.sh script to remove spaces > around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. > 2. Running cpp-authinitialize seems to hang when executing GetCredentials: > dhardman$ ./cpp-authinitialize > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::NotConnectedException: : not connected to Geode > Abort trap: 6 > > Expected: The README file indicates the following output > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::getCredentials called > a = 1 > b = 2 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-7198) C++ authinitialize example hangs
[ https://issues.apache.org/jira/browse/GEODE-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928949#comment-16928949 ] Diane Hardman commented on GEODE-7198: -- After modifying main.cpp to set log-level to 'debug', I am seeing the following exception in server.log file: Security exception: org.apache.geode.security.AuthenticationFailedException: javaobject.SimpleAuthenticator, caused by: java.lang.ClassNotFoundException: javaobject.SimpleAuthenticator > C++ authinitialize example hangs > > > Key: GEODE-7198 > URL: https://issues.apache.org/jira/browse/GEODE-7198 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Diane Hardman >Priority: Major > > After building geode-native from develop branch on my mac, I then followed > the instructions to build the geode-native examples found here: > [https://github.com/apache/geode-native/tree/develop/examples] > Trying to run the authinitialize example resulted in a hang. > 1. First I needed to correct the startserver.sh script to remove spaces > around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. > 2. Running cpp-authinitialize seems to hang when executing GetCredentials: > dhardman$ ./cpp-authinitialize > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > ExampleAuthInitialize::GetCredentials called > libc++abi.dylib: terminating with uncaught exception of type > apache::geode::client::NotConnectedException: : not connected to Geode > Abort trap: 6 > > Expected: The README file indicates the following output > ExampleAuthInitialize::ExampleAuthInitialize called > ExampleAuthInitialize::getCredentials called > a = 1 > b = 2 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7203) C++ examples need to be updated
Diane Hardman created GEODE-7203: Summary: C++ examples need to be updated Key: GEODE-7203 URL: https://issues.apache.org/jira/browse/GEODE-7203 Project: Geode Issue Type: Bug Components: examples, native client Reporter: Diane Hardman After reviewing the C++ native client examples I found several problems: # Transaction - README should be updated to indicate random output; currently it says to expect the following output, but this will be different each time: Created cache Created region 'exampleRegion' Rolled back transaction - retrying(4) Rolled back transaction - retrying(3) Rolled back transaction - retrying(2) Committed transaction - exiting # functionexecution - this is the only example that spins up a server named 'the-server'; the startserver.sh script should be updated to reflect the same name used in all other examples 'server'. # pdxserializable - either the README needs to change to show the actual output of running the client app, or main.cpp should be changed to produce the same output presented in the README. The second get (of Customer2) is currently not formatted for printing like the first get (of Customer1). # All examples: stopserver.sh should cleanup leftover directories locator/, server/, and any *.gfs. If there is any reason to keep these around for failing tests, then a separate cleanup.sh script should do this. # authinitialize - startserver.sh fails due to extra spaces around '=' when setting RESOLVEDPATH and AUTHENTICATOR. This example also fails to run, instead hangs when executing getCredentials, but this was filed as GEODE-7198. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (GEODE-7198) C++ authinitialize example hangs
Diane Hardman created GEODE-7198: Summary: C++ authinitialize example hangs Key: GEODE-7198 URL: https://issues.apache.org/jira/browse/GEODE-7198 Project: Geode Issue Type: Bug Components: native client Reporter: Diane Hardman After building geode-native from develop branch on my mac, I then followed the instructions to build the geode-native examples found here: [https://github.com/apache/geode-native/tree/develop/examples] Trying to run the authinitialize example resulted in a hang. 1. First I needed to correct the startserver.sh script to remove spaces around the '=' for setting RESOLVEDPATH and AUTHENTICATOR env vars. 2. Running cpp-authinitialize seems to hang when executing GetCredentials: dhardman$ ./cpp-authinitialize ExampleAuthInitialize::ExampleAuthInitialize called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called ExampleAuthInitialize::GetCredentials called libc++abi.dylib: terminating with uncaught exception of type apache::geode::client::NotConnectedException: : not connected to Geode Abort trap: 6 Expected: The README file indicates the following output ExampleAuthInitialize::ExampleAuthInitialize called ExampleAuthInitialize::getCredentials called a = 1 b = 2 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (GEODE-6527) Update PartitionRegionConfig info when altering loader/writer
[ https://issues.apache.org/jira/browse/GEODE-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793209#comment-16793209 ] Diane Hardman commented on GEODE-6527: -- I started a cluster, created a region, data-source, and added a jdbc-mapping, then ran my client that successfully does a put and a get. When I tried to add another server to the cluster, I got the following exception: ``` gfsh>start server --name=server3 --classpath=/Users/dhardman/data-extensions/jdbc/mysql-connector-java-8.0.13/mysql-connector-java-8.0.13.jar --server-port=40406 Starting a Geode Server in /Users/dhardman/data-extensions/jdbc/server3... The Cache Server process terminated unexpectedly with exit status 1. Please refer to the log file in /Users/dhardman/data-extensions/jdbc/server3 for full details. Exception in thread "main" java.lang.IllegalStateException: Incompatible CacheLoader. CacheLoader is null in partitionedRegion Parent on another datastore. at org.apache.geode.internal.cache.PartitionRegionConfigValidator.validateCacheLoaderWriterBetweenDataStores(PartitionRegionConfigValidator.java:364) at org.apache.geode.internal.cache.PartitionedRegion.registerPartitionedRegion(PartitionedRegion.java:1388) at org.apache.geode.internal.cache.PartitionedRegion.initPRInternals(PartitionedRegion.java:1000) at org.apache.geode.internal.cache.PartitionedRegion.initialize(PartitionedRegion.java:1168) at org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3053) at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2948) at org.apache.geode.internal.cache.xmlcache.RegionCreation.createRoot(RegionCreation.java:237) at org.apache.geode.internal.cache.xmlcache.CacheCreation.initializeRegions(CacheCreation.java:633) at org.apache.geode.internal.cache.xmlcache.CacheCreation.create(CacheCreation.java:575) at org.apache.geode.internal.cache.xmlcache.CacheXmlParser.create(CacheXmlParser.java:337) at org.apache.geode.internal.cache.GemFireCacheImpl.loadCacheXml(GemFireCacheImpl.java:4282) at org.apache.geode.internal.cache.ClusterConfigurationLoader.applyClusterXmlConfiguration(ClusterConfigurationLoader.java:197) at org.apache.geode.internal.cache.GemFireCacheImpl.applyJarAndXmlFromClusterConfig(GemFireCacheImpl.java:1231) at org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1195) at org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:181) at org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:147) at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:138) at org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) at org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:870) at org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:787) at org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:717) at org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:237) ``` > Update PartitionRegionConfig info when altering loader/writer > - > > Key: GEODE-6527 > URL: https://issues.apache.org/jira/browse/GEODE-6527 > Project: Geode > Issue Type: Bug >Reporter: Scott Jewell >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When AttributesMutator alters a partitioned regions loader and/or writer > these changes should be reflected in the PartitionRegionConfig node > information. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6225) add support to create jdbc-mapping for catalog and schema
[ https://issues.apache.org/jira/browse/GEODE-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742556#comment-16742556 ] Diane Hardman commented on GEODE-6225: -- The --schema and --catalog options for `create jdbc-mapping` command are provided to meet the JDBC API standard. These options assume the JDBC driver for the target RDBMS specified by the user understands and appropriately uses these specifications. If the JDBC driver for the target RDBMS does not utilize schema or catalog parameters in the JDBC API but these are required to identify the correct table, the user can add the schema and/or catalog notation in the URL specification in the `create data-source` command. > add support to create jdbc-mapping for catalog and schema > - > > Key: GEODE-6225 > URL: https://issues.apache.org/jira/browse/GEODE-6225 > Project: Geode > Issue Type: Improvement > Components: docs, extensions >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The JDBC api support a catalog and schema option. Currently the JDBC > connector always set these to null. The create jdbc-mapping should have > options that allow users to specify non-default values for catalog and schema. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6217) Region created with --group option does NOT get saved in cluster config
[
https://issues.apache.org/jira/browse/GEODE-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-6217:
-
Description:
I have created a server in a group and then created a region to only be put on
servers in that group. When I then export cluster config to my screen, the
region is not shown.
Here are the steps to reproduce:
{panel:title=gfsh Session}
gfsh>start locator --name=locator1
gfsh>configure pdx --read-serialized=true
--auto-serializable-classes=io.pivotal.gemfire.demo.entity.*
gfsh>start server --name=server1 --group=PersonGroup
#NOTE: this second server is NOT in the group
gfsh>start server --name=server2 --server-port=40405
#NOTE: the describe server commands show one server is in the group, the other
not
gfsh>describe member --name=server1
Name : server1
Id : 172.17.0.2(server1:1257):41001
Host : gpdb.pivotal.io
Regions :
PID : 1257
Groups : PersonGroup
Used Heap : 74M
Max Heap : 1324M
Working Dir : /root/demo/server1
Log file : /root/demo/server1/server1.log
Locators : 172.17.0.2[10334]
Cache Server Information
Server Bind :
Server Port : 40404
Running : true
Client Connections : 0
gfsh>describe member --name=server2
Name : server2
Id : 172.17.0.2(server2:1348):41002
Host : gpdb.pivotal.io
Regions :
PID : 1348
Groups :
Used Heap : 50M
Max Heap : 1324M
Working Dir : /root/demo/server2
Log file : /root/demo/server2/server2.log
Locators : 172.17.0.2[10334]
Cache Server Information
Server Bind :
Server Port : 40405
Running : true
Client Connections : 0
#Now create a new region for the server group; i.e. only add the region to
server1
gfsh>create region --name=Parent --type=PARTITION --redundant-copies=1
--group=PersonGroup
Member | Status | Message
--- | -- | -
server1 | OK | Region "/Parent" created on "server1"
Changes to configuration for group 'PersonGroup' are persisted.
gfsh>describe region --name=Parent
..
Name : Parent
Data Policy : partition
Hosting Members : server1
Non-Default Attributes Shared By Hosting Members
Type | Name | Value
- | | -
Region | size | 0
| data-policy | PARTITION
Partition | redundant-copies | 1
#Add another region without the server group so it's stored on both servers
gfsh>create region --name=LargeRegion --type=PARTITION --redundant-copies=0
Member | Status | Message
--- | -- | --
server1 | OK | Region "/LargeRegion" created on "server1"
server2 | OK | Region "/LargeRegion" created on "server2"
Changes to configuration for group 'cluster' are persisted.
#Now export cluster config to the screen:
gfsh>export cluster-configuration
cluster.xml:
http://geode.apache.org/schema/lucene
[http://geode.apache.org/schema/lucene/lucene-1.0.xsd]
[http://geode.apache.org/schema/cache]
[http://geode.apache.org/schema/cache/cache-1.0.xsd]
[http://geode.apache.org/schema/jdbc]
[http://geode.apache.org/schema/jdbc/jdbc-1.0.xsd] gpdb
[http://schema.pivotal.io/gemfire/gpdb/gpdb-3.3.xsd] gpdb
[http://schema.pivotal.io/gemfire/gpdb/gpdb-3.3.xsd];
xmlns="http://geode.apache.org/schema/cache;
xmlns:gpdb="http://schema.pivotal.io/gemfire/gpdb;
xmlns:lucene="http://geode.apache.org/schema/lucene;
xmlns:jdbc="http://geode.apache.org/schema/jdbc;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
org.apache.geode.pdx.ReflectionBasedAutoSerializer
io.pivotal.gemfire.demo.entity.*
#The exported cluster config shows LargeRegion but NOT Parent region.
{panel}
was:
I have created a server in a group and then created a region to only be put on
servers in that group. When I then export cluster config to my screen, the
region is not shown.
Here are the steps to reproduce:
```
gfsh>start locator --name=locator1
gfsh>configure pdx --read-serialized=true
--auto-serializable-classes=io.pivotal.gemfire.demo.entity.*
gfsh>start server --name=server1 --group=PersonGroup
#NOTE: this second server is NOT in the group
gfsh>start server --name=server2 --server-port=40405
#NOTE: the describe server commands show one server is in the group, the other
not
gfsh>describe member --name=server1
Name : server1
Id : 172.17.0.2(server1:1257):41001
Host : gpdb.pivotal.io
Regions :
PID : 1257
Groups : PersonGroup
[jira] [Updated] (GEODE-6217) Region created with --group option does NOT get saved in cluster config
[ https://issues.apache.org/jira/browse/GEODE-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6217: - Affects Version/s: 1.8.0 > Region created with --group option does NOT get saved in cluster config > --- > > Key: GEODE-6217 > URL: https://issues.apache.org/jira/browse/GEODE-6217 > Project: Geode > Issue Type: Bug > Components: configuration >Affects Versions: 1.8.0 >Reporter: Diane Hardman >Priority: Major > > I have created a server in a group and then created a region to only be put > on servers in that group. When I then export cluster config to my screen, the > region is not shown. > Here are the steps to reproduce: > ``` > gfsh>start locator --name=locator1 > gfsh>configure pdx --read-serialized=true > --auto-serializable-classes=io.pivotal.gemfire.demo.entity.* > gfsh>start server --name=server1 --group=PersonGroup > #NOTE: this second server is NOT in the group > gfsh>start server --name=server2 --server-port=40405 > #NOTE: the describe server commands show one server is in the group, the > other not > gfsh>describe member --name=server1 > Name : server1 > Id : 172.17.0.2(server1:1257):41001 > Host : gpdb.pivotal.io > Regions : > PID : 1257 > Groups : PersonGroup > Used Heap : 74M > Max Heap : 1324M > Working Dir : /root/demo/server1 > Log file : /root/demo/server1/server1.log > Locators : 172.17.0.2[10334] > > Cache Server Information > Server Bind : > Server Port : 40404 > Running : true > Client Connections : 0 > > gfsh>describe member --name=server2 > Name : server2 > Id : 172.17.0.2(server2:1348):41002 > Host : gpdb.pivotal.io > Regions : > PID : 1348 > Groups : > Used Heap : 50M > Max Heap : 1324M > Working Dir : /root/demo/server2 > Log file : /root/demo/server2/server2.log > Locators : 172.17.0.2[10334] > > Cache Server Information > Server Bind : > Server Port : 40405 > Running : true > Client Connections : 0 > #Now create a new region for the server group; i.e. only add the region to > server1 > gfsh>create region --name=Parent --type=PARTITION --redundant-copies=1 > --group=PersonGroup > Member | Status | Message > --- | -- | - > server1 | OK | Region "/Parent" created on "server1" > > > > > Changes to configuration for group 'PersonGroup' are persisted. > gfsh>describe region --name=Parent > .. > Name : Parent > Data Policy : partition > Hosting Members : server1 > > Non-Default Attributes Shared By Hosting Members > > Type | Name | Value > - | | - > Region | size | 0 > | data-policy | PARTITION > Partition | redundant-copies | 1 > #Add another region without the server group so it's stored on both servers > gfsh>create region --name=LargeRegion --type=PARTITION --redundant-copies=0 > Member | Status | Message > --- | -- | -- > server1 | OK | Region "/LargeRegion" created on "server1" > server2 | OK | Region "/LargeRegion" created on "server2" > > > > > Changes to configuration for group 'cluster' are persisted. > #Now export cluster config to the screen: > gfsh>export cluster-configuration > cluster.xml: > xsi:schemaLocation="http://geode.apache.org/schema/lucene > http://geode.apache.org/schema/lucene/lucene-1.0.xsd > http://geode.apache.org/schema/cache > http://geode.apache.org/schema/cache/cache-1.0.xsd > http://geode.apache.org/schema/jdbc > http://geode.apache.org/schema/jdbc/jdbc-1.0.xsd gpdb > http://schema.pivotal.io/gemfire/gpdb/gpdb-3.3.xsd gpdb > http://schema.pivotal.io/gemfire/gpdb/gpdb-3.3.xsd; > xmlns="http://geode.apache.org/schema/cache; > xmlns:gpdb="http://schema.pivotal.io/gemfire/gpdb; > xmlns:lucene="http://geode.apache.org/schema/lucene; > xmlns:jdbc="http://geode.apache.org/schema/jdbc; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;> > persistent="false"> > > > org.apache.geode.pdx.ReflectionBasedAutoSerializer > > io.pivotal.gemfire.demo.entity.* > > > > > connection-url="jdbc:postgresql://localhost:5432/gemfire_db" > jndi-name="datasource" password="changeme" type="SimpleDataSource" > user-name="g2c_user"/> > > > enable-async-conflation="false" enable-subscription-conflation="false" > multicast-enabled="false" disk-synchronous="true" statistics-enabled="false" >
[jira] [Created] (GEODE-6217) Region created with --group option does NOT get saved in cluster config
Diane Hardman created GEODE-6217: Summary: Region created with --group option does NOT get saved in cluster config Key: GEODE-6217 URL: https://issues.apache.org/jira/browse/GEODE-6217 Project: Geode Issue Type: Bug Components: configuration Reporter: Diane Hardman I have created a server in a group and then created a region to only be put on servers in that group. When I then export cluster config to my screen, the region is not shown. Here are the steps to reproduce: ``` gfsh>start locator --name=locator1 gfsh>configure pdx --read-serialized=true --auto-serializable-classes=io.pivotal.gemfire.demo.entity.* gfsh>start server --name=server1 --group=PersonGroup #NOTE: this second server is NOT in the group gfsh>start server --name=server2 --server-port=40405 #NOTE: the describe server commands show one server is in the group, the other not gfsh>describe member --name=server1 Name : server1 Id : 172.17.0.2(server1:1257):41001 Host : gpdb.pivotal.io Regions : PID : 1257 Groups : PersonGroup Used Heap : 74M Max Heap : 1324M Working Dir : /root/demo/server1 Log file : /root/demo/server1/server1.log Locators : 172.17.0.2[10334] Cache Server Information Server Bind : Server Port : 40404 Running : true Client Connections : 0 gfsh>describe member --name=server2 Name : server2 Id : 172.17.0.2(server2:1348):41002 Host : gpdb.pivotal.io Regions : PID : 1348 Groups : Used Heap : 50M Max Heap : 1324M Working Dir : /root/demo/server2 Log file : /root/demo/server2/server2.log Locators : 172.17.0.2[10334] Cache Server Information Server Bind : Server Port : 40405 Running : true Client Connections : 0 #Now create a new region for the server group; i.e. only add the region to server1 gfsh>create region --name=Parent --type=PARTITION --redundant-copies=1 --group=PersonGroup Member | Status | Message --- | -- | - server1 | OK | Region "/Parent" created on "server1" Changes to configuration for group 'PersonGroup' are persisted. gfsh>describe region --name=Parent .. Name : Parent Data Policy : partition Hosting Members : server1 Non-Default Attributes Shared By Hosting Members Type | Name | Value - | | - Region | size | 0 | data-policy | PARTITION Partition | redundant-copies | 1 #Add another region without the server group so it's stored on both servers gfsh>create region --name=LargeRegion --type=PARTITION --redundant-copies=0 Member | Status | Message --- | -- | -- server1 | OK | Region "/LargeRegion" created on "server1" server2 | OK | Region "/LargeRegion" created on "server2" Changes to configuration for group 'cluster' are persisted. #Now export cluster config to the screen: gfsh>export cluster-configuration cluster.xml: http://geode.apache.org/schema/lucene http://geode.apache.org/schema/lucene/lucene-1.0.xsd http://geode.apache.org/schema/cache http://geode.apache.org/schema/cache/cache-1.0.xsd http://geode.apache.org/schema/jdbc http://geode.apache.org/schema/jdbc/jdbc-1.0.xsd gpdb http://schema.pivotal.io/gemfire/gpdb/gpdb-3.3.xsd gpdb http://schema.pivotal.io/gemfire/gpdb/gpdb-3.3.xsd; xmlns="http://geode.apache.org/schema/cache; xmlns:gpdb="http://schema.pivotal.io/gemfire/gpdb; xmlns:lucene="http://geode.apache.org/schema/lucene; xmlns:jdbc="http://geode.apache.org/schema/jdbc; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;> org.apache.geode.pdx.ReflectionBasedAutoSerializer io.pivotal.gemfire.demo.entity.* #The exported cluster config shows LargeRegion but NOT Parent region. ``` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6088) Enable command availability for JDBC commands
[ https://issues.apache.org/jira/browse/GEODE-6088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman updated GEODE-6088: - Component/s: gfsh extensions > Enable command availability for JDBC commands > - > > Key: GEODE-6088 > URL: https://issues.apache.org/jira/browse/GEODE-6088 > Project: Geode > Issue Type: Task > Components: extensions, gfsh >Reporter: Scott Jewell >Priority: Major > > The JDBC commands should support the GFSH command availability indicator. > Commands should only be available when connect to a distributed system. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3967) if put hits concurrent modification exception should still notify serial gateway sender
[ https://issues.apache.org/jira/browse/GEODE-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diane Hardman resolved GEODE-3967. -- My mistake, this should not have been reopened. > if put hits concurrent modification exception should still notify serial > gateway sender > --- > > Key: GEODE-3967 > URL: https://issues.apache.org/jira/browse/GEODE-3967 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In serial gateway sender, the event arrives at secondary will be put into > unprocessedMap and wait for event from primary queue to distribute over, then > remove it from the unprocessedMap. > If the put at primary member (member with primary queue) failed with CME, the > event in unprocessedMap will never be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6026) Lucene test classes should not be listed in Javadocs
Diane Hardman created GEODE-6026: Summary: Lucene test classes should not be listed in Javadocs Key: GEODE-6026 URL: https://issues.apache.org/jira/browse/GEODE-6026 Project: Geode Issue Type: Bug Components: lucene Reporter: Diane Hardman Fix For: 1.7.0 In the latest Javadocs for Lucene there are several test classes and utilities listed that should not be: package org.apache.geode.cache.lucene.test under package org.apache.geode.cache.lucene Class Summary: * DummyLuceneSerializer * LuceneIntegrationTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5414) Create a geode-example for WAN replication
[ https://issues.apache.org/jira/browse/GEODE-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547235#comment-16547235 ] Diane Hardman commented on GEODE-5414: -- Initial version of this new WAN example can be found here: https://github.com/dihardman/geode-examples/tree/feature/GEODE-5414 > Create a geode-example for WAN replication > -- > > Key: GEODE-5414 > URL: https://issues.apache.org/jira/browse/GEODE-5414 > Project: Geode > Issue Type: Improvement > Components: examples >Reporter: Diane Hardman >Assignee: Diane Hardman >Priority: Major > > Create a simple example for implementing WAN replication between 2 Geode > clusters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
