[jira] [Commented] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets
[
https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845368#comment-16845368
]
Darrel Schneider commented on GEODE-6472:
-
I changed the LocalRegion.get to do nothing on a BucketRegion. This fixed the
double counting on the CachePerfStats that represents the entire cache. But on
the CachePerfStats for just the partitioned region it had the correct get count
before but with my change is now zero.
Also the misses on the entire cache is half the gets (the gets that are double
counted). But every get was a hit so misses should have been zero.
The CachePerfStats misses on the partitioned region were also correct (always
zero).
> cachePerfStats:gets is double incremented on partitioned region gets
>
>
> Key: GEODE-6472
> URL: https://issues.apache.org/jira/browse/GEODE-6472
> Project: Geode
> Issue Type: Bug
> Components: statistics
>Reporter: Jacob S. Barrett
>Assignee: Mario Kevo
>Priority: Major
> Labels: review
> Fix For: 1.10.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The cache level stats, cachePerfStats, shows double the gets for portioned
> region stats.
> If a client does 1000 gets/second on a partitioned region and you examine the
> servers stats archive you will see {{cachePerfStats:gets}} will show 2000
> (and change) gets/second while {{RegionStats-partitioned:gets}} will show
> 1000 gets/second.
> Other region/cache stats, like put, may also be effected similarly.
> May effect versions older than 1.8.
> A test should be written to assert that region and cache stats are relatively
> the same for cases where only one region is being accessed on the cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets
[
https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845354#comment-16845354
]
Darrel Schneider commented on GEODE-6472:
-
The previous fix for this changed code that is only used in some rare
situations (look at the callers of Get70.getValueAndIsObject). A normal client
get calls Get70.getEntry and it ends up calling methods on LocalRegion that the
previous fix did not change.
> cachePerfStats:gets is double incremented on partitioned region gets
>
>
> Key: GEODE-6472
> URL: https://issues.apache.org/jira/browse/GEODE-6472
> Project: Geode
> Issue Type: Bug
> Components: statistics
>Reporter: Jacob S. Barrett
>Assignee: Mario Kevo
>Priority: Major
> Labels: review
> Fix For: 1.10.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The cache level stats, cachePerfStats, shows double the gets for portioned
> region stats.
> If a client does 1000 gets/second on a partitioned region and you examine the
> servers stats archive you will see {{cachePerfStats:gets}} will show 2000
> (and change) gets/second while {{RegionStats-partitioned:gets}} will show
> 1000 gets/second.
> Other region/cache stats, like put, may also be effected similarly.
> May effect versions older than 1.8.
> A test should be written to assert that region and cache stats are relatively
> the same for cases where only one region is being accessed on the cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-6789) locator fails to start even though ports in membership-port-range are available
[
https://issues.apache.org/jira/browse/GEODE-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845352#comment-16845352
]
ASF subversion and git services commented on GEODE-6789:
Commit ffe00a46cf2a04d32fb8fbe5c319dab993b26053 in geode's branch
refs/heads/feature/GEODE-6789 from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ffe00a4 ]
GEODE-6789 locator fails to start even though ports in membership-port-range
are available
Do not rely on exception text to determine whether a bind() operation
failed. Instead, treat all SocketAcceptions thrown by server socket
creation a failure to bind to an inet socket address.
> locator fails to start even though ports in membership-port-range are
> available
> ---
>
> Key: GEODE-6789
> URL: https://issues.apache.org/jira/browse/GEODE-6789
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>
> A locator with membership-port-range of 1-2 threw a
> GemFireConfigException even though ports in that range were available.
> {noformat}
> org.apache.geode.GemFireConfigException: Unable to allocate a failure
> detection port in the membership-port range
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.createServerSocket(GMSHealthMonitor.java:679)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.started(GMSHealthMonitor.java:946)
> at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> at
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:341)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> at
> hydra.DistributedSystemHelper.startLocatorAndDS(DistributedSystemHelper.java:382)
> at
> rollingupgrade.RollingUpgradeTest.HydraTask_startLocatorAndDS(RollingUpgradeTest.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at hydra.MethExecutor.execute(MethExecutor.java:173)
> at hydra.MethExecutor.execute(MethExecutor.java:141)
> at hydra.TestTask.execute(TestTask.java:197)
> at hydra.RemoteTestModule$1.run(RemoteTestModule.java:213)
> Caused by: java.net.SocketException: Address already in use (Listen failed)
> at java.net.PlainSocketImpl.socketListen(Native Method)
> at
> java.net.AbstractPlainSocketImpl.listen(AbstractPlainSocketImpl.java:399)
> at java.net.ServerSocket.bind(ServerSocket.java:376)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:748)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocketUsingPortRange(SocketCreator.java:828)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.createServerSocket(GMSHealthMonitor.java:675)
> ... 22 more{noformat}
>
> The code that checks for free ports in that range looks for a BindException.
> If one isn't found it looks for a SocketException with the message "Invalid
> argument: listen failed". In this failure the text was "Address already in
> use (Listen failed)", which causes the search for a free port to terminate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-6790) Refactor DataSourceCreateException to correctly capture cause
[ https://issues.apache.org/jira/browse/GEODE-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-6790: - Assignee: Jens Deppe > Refactor DataSourceCreateException to correctly capture cause > - > > Key: GEODE-6790 > URL: https://issues.apache.org/jira/browse/GEODE-6790 > Project: Geode > Issue Type: Task > Components: jdbc >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6790) Refactor DataSourceCreateException to correctly capture cause
Jens Deppe created GEODE-6790: - Summary: Refactor DataSourceCreateException to correctly capture cause Key: GEODE-6790 URL: https://issues.apache.org/jira/browse/GEODE-6790 Project: Geode Issue Type: Task Components: jdbc Reporter: Jens Deppe -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-6789) locator fails to start even though ports in membership-port-range are available
[
https://issues.apache.org/jira/browse/GEODE-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-6789:
---
Assignee: Bruce Schuchardt
> locator fails to start even though ports in membership-port-range are
> available
> ---
>
> Key: GEODE-6789
> URL: https://issues.apache.org/jira/browse/GEODE-6789
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Bruce Schuchardt
>Assignee: Bruce Schuchardt
>Priority: Major
>
> A locator with membership-port-range of 1-2 threw a
> GemFireConfigException even though ports in that range were available.
> {noformat}
> org.apache.geode.GemFireConfigException: Unable to allocate a failure
> detection port in the membership-port range
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.createServerSocket(GMSHealthMonitor.java:679)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.started(GMSHealthMonitor.java:946)
> at
> org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
> at
> org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:341)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
> at
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
> at
> hydra.DistributedSystemHelper.startLocatorAndDS(DistributedSystemHelper.java:382)
> at
> rollingupgrade.RollingUpgradeTest.HydraTask_startLocatorAndDS(RollingUpgradeTest.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at hydra.MethExecutor.execute(MethExecutor.java:173)
> at hydra.MethExecutor.execute(MethExecutor.java:141)
> at hydra.TestTask.execute(TestTask.java:197)
> at hydra.RemoteTestModule$1.run(RemoteTestModule.java:213)
> Caused by: java.net.SocketException: Address already in use (Listen failed)
> at java.net.PlainSocketImpl.socketListen(Native Method)
> at
> java.net.AbstractPlainSocketImpl.listen(AbstractPlainSocketImpl.java:399)
> at java.net.ServerSocket.bind(ServerSocket.java:376)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:748)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocketUsingPortRange(SocketCreator.java:828)
> at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.createServerSocket(GMSHealthMonitor.java:675)
> ... 22 more{noformat}
>
> The code that checks for free ports in that range looks for a BindException.
> If one isn't found it looks for a SocketException with the message "Invalid
> argument: listen failed". In this failure the text was "Address already in
> use (Listen failed)", which causes the search for a free port to terminate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-6789) locator fails to start even though ports in membership-port-range are available
Bruce Schuchardt created GEODE-6789:
---
Summary: locator fails to start even though ports in
membership-port-range are available
Key: GEODE-6789
URL: https://issues.apache.org/jira/browse/GEODE-6789
Project: Geode
Issue Type: Bug
Components: core
Reporter: Bruce Schuchardt
A locator with membership-port-range of 1-2 threw a
GemFireConfigException even though ports in that range were available.
{noformat}
org.apache.geode.GemFireConfigException: Unable to allocate a failure detection
port in the membership-port range
at
org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.createServerSocket(GMSHealthMonitor.java:679)
at
org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.started(GMSHealthMonitor.java:946)
at
org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181)
at
org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:106)
at
org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:90)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1027)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.(ClusterDistributionManager.java:1061)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:554)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:763)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:355)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:341)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:335)
at
org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:211)
at
hydra.DistributedSystemHelper.startLocatorAndDS(DistributedSystemHelper.java:382)
at
rollingupgrade.RollingUpgradeTest.HydraTask_startLocatorAndDS(RollingUpgradeTest.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hydra.MethExecutor.execute(MethExecutor.java:173)
at hydra.MethExecutor.execute(MethExecutor.java:141)
at hydra.TestTask.execute(TestTask.java:197)
at hydra.RemoteTestModule$1.run(RemoteTestModule.java:213)
Caused by: java.net.SocketException: Address already in use (Listen failed)
at java.net.PlainSocketImpl.socketListen(Native Method)
at
java.net.AbstractPlainSocketImpl.listen(AbstractPlainSocketImpl.java:399)
at java.net.ServerSocket.bind(ServerSocket.java:376)
at
org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:748)
at
org.apache.geode.internal.net.SocketCreator.createServerSocketUsingPortRange(SocketCreator.java:828)
at
org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.createServerSocket(GMSHealthMonitor.java:675)
... 22 more{noformat}
The code that checks for free ports in that range looks for a BindException.
If one isn't found it looks for a SocketException with the message "Invalid
argument: listen failed". In this failure the text was "Address already in use
(Listen failed)", which causes the search for a free port to terminate.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GEODE-6725) Still need to support building on RHEL6
[ https://issues.apache.org/jira/browse/GEODE-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-6725. --- Fixed in PR #470 > Still need to support building on RHEL6 > --- > > Key: GEODE-6725 > URL: https://issues.apache.org/jira/browse/GEODE-6725 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > It turns out we still have some folks asking for this, so we need to adapt > the build to accomodate either RHEL6 or RHEL7. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6725) Still need to support building on RHEL6
[ https://issues.apache.org/jira/browse/GEODE-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-6725. - Resolution: Fixed > Still need to support building on RHEL6 > --- > > Key: GEODE-6725 > URL: https://issues.apache.org/jira/browse/GEODE-6725 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > It turns out we still have some folks asking for this, so we need to adapt > the build to accomodate either RHEL6 or RHEL7. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6718. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6718. --- Fixed in linked PR > 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 > 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 (v7.6.3#76005)
[jira] [Commented] (GEODE-6675) Eliminate TcrEndpoint::sendRequestForChunkedResponse and derived-class implementations
[ https://issues.apache.org/jira/browse/GEODE-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845230#comment-16845230 ] Blake Bender commented on GEODE-6675: - Used #6718 to fix this, so marking earlier bug a dupe > Eliminate TcrEndpoint::sendRequestForChunkedResponse and derived-class > implementations > -- > > Key: GEODE-6675 > URL: https://issues.apache.org/jira/browse/GEODE-6675 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > This method is a simple pass-through to > TcrConnection::sendRequestForChunkedResponse, and uses nothing known only to > the TcrConnection-derived class. It is completely extraneous, and should be > eliminated in order to, among other things, declutter callstacks so we can > more easily determine control flow in the code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-6675) Eliminate TcrEndpoint::sendRequestForChunkedResponse and derived-class implementations
[ https://issues.apache.org/jira/browse/GEODE-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-6675. --- > Eliminate TcrEndpoint::sendRequestForChunkedResponse and derived-class > implementations > -- > > Key: GEODE-6675 > URL: https://issues.apache.org/jira/browse/GEODE-6675 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > This method is a simple pass-through to > TcrConnection::sendRequestForChunkedResponse, and uses nothing known only to > the TcrConnection-derived class. It is completely extraneous, and should be > eliminated in order to, among other things, declutter callstacks so we can > more easily determine control flow in the code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6675) Eliminate TcrEndpoint::sendRequestForChunkedResponse and derived-class implementations
[ https://issues.apache.org/jira/browse/GEODE-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-6675. - Resolution: Duplicate > Eliminate TcrEndpoint::sendRequestForChunkedResponse and derived-class > implementations > -- > > Key: GEODE-6675 > URL: https://issues.apache.org/jira/browse/GEODE-6675 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > This method is a simple pass-through to > TcrConnection::sendRequestForChunkedResponse, and uses nothing known only to > the TcrConnection-derived class. It is completely extraneous, and should be > eliminated in order to, among other things, declutter callstacks so we can > more easily determine control flow in the code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6668) Fix for compile issue of latest boost on Windows
[ https://issues.apache.org/jira/browse/GEODE-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845228#comment-16845228 ] Blake Bender commented on GEODE-6668: - This is blocking GEODE-6650 > Fix for compile issue of latest boost on Windows > > > Key: GEODE-6668 > URL: https://issues.apache.org/jira/browse/GEODE-6668 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Priority: Major > > Since we treat compiler Warnings as Errors, we need to fix a new compiler > warning due to the upgrade to latest boost. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GEODE-6650) Update to Boost 1.70.0
[ https://issues.apache.org/jira/browse/GEODE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender reopened GEODE-6650: - Resolved this prematurely - we found compiler warnings on Windows introduced by boost v1.70.0 headers, so we reverted back to v1.68.0 > Update to Boost 1.70.0 > -- > > Key: GEODE-6650 > URL: https://issues.apache.org/jira/browse/GEODE-6650 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6650) Update to Boost 1.70.0
[ https://issues.apache.org/jira/browse/GEODE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-6650. - Resolution: Fixed > Update to Boost 1.70.0 > -- > > Key: GEODE-6650 > URL: https://issues.apache.org/jira/browse/GEODE-6650 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-6650) Update to Boost 1.70.0
[ https://issues.apache.org/jira/browse/GEODE-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-6650. --- FIxed in linked PR > Update to Boost 1.70.0 > -- > > Key: GEODE-6650 > URL: https://issues.apache.org/jira/browse/GEODE-6650 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (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
]
Blake Bender closed GEODE-6642.
---
Fixed in linked PR
> 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 S. Barrett
>Priority: Major
> 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
(v7.6.3#76005)
[jira] [Resolved] (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
]
Blake Bender resolved GEODE-6642.
-
Resolution: Fixed
> 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 S. Barrett
>Priority: Major
> 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
(v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6624. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6624. --- Fixed in linked PRs > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (GEODE-6623) GemFire Native Client Has a new declarative Cache Schema
[ https://issues.apache.org/jira/browse/GEODE-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-6623. - Resolution: Fixed > GemFire Native Client Has a new declarative Cache Schema > > > Key: GEODE-6623 > URL: https://issues.apache.org/jira/browse/GEODE-6623 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Charlie Black >Assignee: Dave Barnes >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > GemFire Native Client Has a new declarative Cache Schema. The > documentation of the schema is missing. > As a user of GemFire Native client, I would like to know how to use the > schema and what is the meaning of the elements in the schema. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-6623) GemFire Native Client Has a new declarative Cache Schema
[ https://issues.apache.org/jira/browse/GEODE-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-6623. --- Fixed in linked PR > GemFire Native Client Has a new declarative Cache Schema > > > Key: GEODE-6623 > URL: https://issues.apache.org/jira/browse/GEODE-6623 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Charlie Black >Assignee: Dave Barnes >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > GemFire Native Client Has a new declarative Cache Schema. The > documentation of the schema is missing. > As a user of GemFire Native client, I would like to know how to use the > schema and what is the meaning of the elements in the schema. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6575. --- Fixed in linked PR > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6575. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6491. --- Fixed in linked PR > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6491. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6469. --- Fixed in linked PR > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6469. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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
]
Blake Bender closed GEODE-6300.
---
FIxed in linked PR
> 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
> 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
(v7.6.3#76005)
[jira] [Resolved] (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
]
Blake Bender resolved GEODE-6300.
-
Resolution: Fixed
> 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
> 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
(v7.6.3#76005)
[jira] [Closed] (GEODE-6263) Update Packer script for Windows w/new EC2 config
[ https://issues.apache.org/jira/browse/GEODE-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-6263. --- I don't know if there's a PR associated with this one, but I do know that we attempted to write proper EC2 script(s) to guarantee our drive letter was assigned to a known value, and ultimately we gave up and just adjusted our ci build scripts to use the "new" AWS default drive letter. This change is no longer needed > Update Packer script for Windows w/new EC2 config > - > > Key: GEODE-6263 > URL: https://issues.apache.org/jira/browse/GEODE-6263 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > The Powershell code is still in place to attempt to remap the secondary drive > letter under Windows, and is throwing errors now that AWS has moved the > config file in question. This code needs to be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6263) Update Packer script for Windows w/new EC2 config
[ https://issues.apache.org/jira/browse/GEODE-6263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-6263. - Resolution: Fixed > Update Packer script for Windows w/new EC2 config > - > > Key: GEODE-6263 > URL: https://issues.apache.org/jira/browse/GEODE-6263 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > The Powershell code is still in place to attempt to remap the secondary drive > letter under Windows, and is throwing errors now that AWS has moved the > config file in question. This code needs to be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6262. --- Fixed in linked PR > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6262. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6250. --- Fixed in linked PR > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6250. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6249. --- Fixed in linked PR > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6249. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6245. --- Fixed in linked PR > 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 > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-6229) Need an Ubuntu Packer image
[ https://issues.apache.org/jira/browse/GEODE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-6229. --- Fixed in linked PRs > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6245. - Resolution: Fixed > 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 > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6229) Need an Ubuntu Packer image
[ https://issues.apache.org/jira/browse/GEODE-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-6229. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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
]
Blake Bender closed GEODE-6226.
---
Fixed in linked PR
> 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
> 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
(v7.6.3#76005)
[jira] [Resolved] (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
]
Blake Bender resolved GEODE-6226.
-
Resolution: Fixed
> 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
> 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
(v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6211. --- Fixed in linked PR(s) > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6211. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (GEODE-6199) Remove pdxautoserializer from contrib
[ https://issues.apache.org/jira/browse/GEODE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-6199. --- Fixed in linked PR > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6165. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (GEODE-6199) Remove pdxautoserializer from contrib
[ https://issues.apache.org/jira/browse/GEODE-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-6199. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6165. --- Fixed in linked PR > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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
]
Blake Bender closed GEODE-6160.
---
Fixed in linked PR
> 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
> 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
(v7.6.3#76005)
[jira] [Resolved] (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
]
Blake Bender resolved GEODE-6160.
-
Resolution: Fixed
> 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
> 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
(v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6114. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6114. --- Fixed in linked PRs > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-6054. --- Long since fixed - we shipped geode-native 1.8+ with code and cmake files that build/run against the VS2017 runtime > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-6054. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Closed] (GEODE-6038) Can't Build Examples in CI
[ https://issues.apache.org/jira/browse/GEODE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-6038. --- This appears to be a leftover ticket for an old issue we've since fixed. Example builds are passing in our ci pipelines > Can't Build Examples in CI > -- > > Key: GEODE-6038 > URL: https://issues.apache.org/jira/browse/GEODE-6038 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > > Building the examples doesn't work in the CI. Looks like GEODE_ROOT isn't > being defined. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6038) Can't Build Examples in CI
[ https://issues.apache.org/jira/browse/GEODE-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-6038. - Resolution: Fixed > Can't Build Examples in CI > -- > > Key: GEODE-6038 > URL: https://issues.apache.org/jira/browse/GEODE-6038 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > > Building the examples doesn't work in the CI. Looks like GEODE_ROOT isn't > being defined. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6022) Make cmake 3.12 the minimum version
[ https://issues.apache.org/jira/browse/GEODE-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845177#comment-16845177 ] Blake Bender commented on GEODE-6022: - PR #402 updated the version of cmake used by our Linux build machine(s), but it didn't really adress the issue outlined in this ticket. It _looks like_, right now, we're getting away with setting DOTNET_TARGET_FRAMEWORK only because we're always building with cmake > 3.12, regardless of the minimum we set in the various CMakeLists.txt files. This needs to be set in CMakeLists.txt wherever we're generating .csproj files in the /clicache tree. > Make cmake 3.12 the minimum version > --- > > Key: GEODE-6022 > URL: https://issues.apache.org/jira/browse/GEODE-6022 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > A number of projects in the clicache now use DOTNET_TARGET_FRAMEWORK to > specify which version of the .NET framework to use. The cmake minimum should > be changed from 3.10 to 3.12 in all CMakeLists.txt files. > > Also, the BUILDING.md should also be changed accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5731) --hostname-for-client not working correclty
[
https://issues.apache.org/jira/browse/GEODE-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845157#comment-16845157
]
Juan José Ramos Cassella commented on GEODE-5731:
-
The problem is not reproducible using the latest Geode version {{1.9.0}}. I've
also tried the scenario in AWS without any problems, both the locator and
server are accessible through their public DNS name when
{{hostname-for-clients}} is used.
The [pull request|https://github.com/apache/geode/pull/3614] adds some tests
and checks that the actual {{hostname}} returned through {{ServerLocation}} is
accurate and matches the {{hostname-for-clients}} used when starting the member.
> --hostname-for-client not working correclty
> ---
>
> Key: GEODE-5731
> URL: https://issues.apache.org/jira/browse/GEODE-5731
> Project: Geode
> Issue Type: Bug
> Components: configuration, locator
>Affects Versions: 1.6.0
>Reporter: Alexander Murmann
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: SmallFeature
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting a server cluster on EC2 and --hostname-for-client set for
> locator and server then the locator does not return the client-bind-address.
> Locator and server were initially started with
> {code:java}
> start locator --name=locator --port=4
> --properties-file=./gemfire.properties --initial-heap=256M
> --hostname-for-clients=ec2-12-345-678-90.compute-1.amazonaws.com
> start server --name=server1 --server-port=44666
> --properties-file=./gemfire.properties --initial-heap=256M
> --start-rest-api=true --http-service-port=7676
> {code}
> After some debugging the hostname-for-client on the server was also set to be
> the public IP address.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6022) Make cmake 3.12 the minimum version
[ https://issues.apache.org/jira/browse/GEODE-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender updated GEODE-6022: Description: A number of projects in the clicache now use DOTNET_TARGET_FRAMEWORK to specify which version of the .NET framework to use. The cmake minimum should be changed from 3.10 to 3.12 in all CMakeLists.txt files. Also, the BUILDING.md should also be changed accordingly. was: A number of projects in the clicache now use DOTNET_TARTET_FRAMEWORK to specify which version of the .NET framework to use. The cmake minimum should be changed from 3.10 to 3.12 in all CMakeLists.txt files. Also, the BUILDING.md should also be changed accordingly. > Make cmake 3.12 the minimum version > --- > > Key: GEODE-6022 > URL: https://issues.apache.org/jira/browse/GEODE-6022 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > A number of projects in the clicache now use DOTNET_TARGET_FRAMEWORK to > specify which version of the .NET framework to use. The cmake minimum should > be changed from 3.10 to 3.12 in all CMakeLists.txt files. > > Also, the BUILDING.md should also be changed accordingly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6472) cachePerfStats:gets is double incremented on partitioned region gets
[
https://issues.apache.org/jira/browse/GEODE-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845068#comment-16845068
]
Darrel Schneider commented on GEODE-6472:
-
I think the cause of this is that this method: LocalRegion.get(Object, Object,
boolean, boolean, boolean, ClientProxyMembershipID, EntryEventImpl, boolean,
boolean, boolean) is called twice when a client does a get on a
PartitionedRegion. Once for the partitioned region and once for the bucket.
Here are the callstacks that show this:
{noformat}
[info 2019/05/21 10:17:01.622 PDT
tid=0x50] DEBUG calling endGet for region
BucketRegion[path='/__PR/_B__AuthRegion_87;serial=125;primary=true]
java.lang.RuntimeException: STACK
at
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1381)
at
org.apache.geode.internal.cache.PartitionedRegionDataStore.getLocally(PartitionedRegionDataStore.java:1982)
at
org.apache.geode.internal.cache.PartitionedRegion.getFromBucket(PartitionedRegion.java:4003)
at
org.apache.geode.internal.cache.PartitionedRegion.findObjectInSystem(PartitionedRegion.java:3428)
at
org.apache.geode.internal.cache.PartitionedRegionDataView.findObject(PartitionedRegionDataView.java:72)
at
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1367)
at
org.apache.geode.internal.cache.LocalRegion.getRetained(LocalRegion.java:1328)
at
org.apache.geode.internal.cache.LocalRegion.getRetained(LocalRegion.java:1313)
at
org.apache.geode.internal.cache.tier.sockets.command.Get70.getEntryRetained(Get70.java:341)
at
org.apache.geode.internal.cache.tier.sockets.command.Get70.getEntry(Get70.java:235)
at
org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:153)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:183)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:849)
at
org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:72)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1214)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$3(AcceptorImpl.java:663)
at
org.apache.geode.internal.logging.LoggingThreadFactory.lambda$0(LoggingThreadFactory.java:121)
at java.lang.Thread.run(Thread.java:748)
[info 2019/05/21 10:17:01.622 PDT
tid=0x50] DEBUG calling endGet for region Partitioned Region @23aa363a
[path='/AuthRegion'; dataPolicy=PARTITION; prId=1; isDestroyed=false;
isClosed=false; retryTimeout=360; serialNumber=7; partition
attributes=PartitionAttributes@1230457891[redundantCopies=0;localMaxMemory=3276;totalMaxMemory=2147483647;totalNumBuckets=113;partitionResolver=null;colocatedWith=null;recoveryDelay=-1;startupRecoveryDelay=0;FixedPartitionAttributes=null;partitionListeners=null];
on VM 192.168.1.36(server:56094:loner):60831:ef6d65db:server]
java.lang.RuntimeException: STACK
at
org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1381)
at
org.apache.geode.internal.cache.LocalRegion.getRetained(LocalRegion.java:1328)
at
org.apache.geode.internal.cache.LocalRegion.getRetained(LocalRegion.java:1313)
at
org.apache.geode.internal.cache.tier.sockets.command.Get70.getEntryRetained(Get70.java:341)
at
org.apache.geode.internal.cache.tier.sockets.command.Get70.getEntry(Get70.java:235)
at
org.apache.geode.internal.cache.tier.sockets.command.Get70.cmdExecute(Get70.java:153)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:183)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMessage(ServerConnection.java:849)
at
org.apache.geode.internal.cache.tier.sockets.OriginalServerConnection.doOneMessage(OriginalServerConnection.java:72)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1214)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.lambda$3(AcceptorImpl.java:663)
at
org.apache.geode.internal.logging.LoggingThreadFactory.lambda$0(LoggingThreadFactory.java:121)
at java.lang.Thread.run(Thread.java:748)
{noformat}
One way to fix this would be to have the startGet/endGet logic in this method
extracted into two simple methods on LocalRegion. BucketRegion could then
[jira] [Closed] (GEODE-5954) Client side statistics are still being generated when executing functions on server
[ https://issues.apache.org/jira/browse/GEODE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-5954. --- This is by design, stats archiving can be turned off with a property > Client side statistics are still being generated when executing functions on > server > --- > > Key: GEODE-5954 > URL: https://issues.apache.org/jira/browse/GEODE-5954 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > > The newly-added C++ "function-execution" example creates a cache, pool, and > region in the standard fashion, gets hold of the region service and executes > a function that returns some values. It does not do anything specifically > related to statistics, but stats appear to be gathered regardless. > Steps to reproduce: > # Install Geode > # install native client > # build function-execution example > # Execute startserver script for example > # Run function-execution > Expected result: > # function-execution prints out list of values > Actual result: > # function-execution prints out list of values > # native client leaves behind a file of the form "statArchive-X.gfs," > where X is a random 5-digit number > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5954) Client side statistics are still being generated when executing functions on server
[ https://issues.apache.org/jira/browse/GEODE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-5954. - Resolution: Won't Fix > Client side statistics are still being generated when executing functions on > server > --- > > Key: GEODE-5954 > URL: https://issues.apache.org/jira/browse/GEODE-5954 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > > The newly-added C++ "function-execution" example creates a cache, pool, and > region in the standard fashion, gets hold of the region service and executes > a function that returns some values. It does not do anything specifically > related to statistics, but stats appear to be gathered regardless. > Steps to reproduce: > # Install Geode > # install native client > # build function-execution example > # Execute startserver script for example > # Run function-execution > Expected result: > # function-execution prints out list of values > Actual result: > # function-execution prints out list of values > # native client leaves behind a file of the form "statArchive-X.gfs," > where X is a random 5-digit number > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6001) move dependency to OpenSSL v 1.1.1 (TLS)
[ https://issues.apache.org/jira/browse/GEODE-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-6001. - Resolution: Fixed > move dependency to OpenSSL v 1.1.1 (TLS) > > > Key: GEODE-6001 > URL: https://issues.apache.org/jira/browse/GEODE-6001 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > OpenSSL 1.1.1 (LTS) was released 2018-09-11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-6001) move dependency to OpenSSL v 1.1.1 (TLS)
[ https://issues.apache.org/jira/browse/GEODE-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-6001. --- Fixed in PR #394 > move dependency to OpenSSL v 1.1.1 (TLS) > > > Key: GEODE-6001 > URL: https://issues.apache.org/jira/browse/GEODE-6001 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Ernest Burghardt >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > OpenSSL 1.1.1 (LTS) was released 2018-09-11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5962) region.putAll crashes if the map has a key with value nullptr
[
https://issues.apache.org/jira/browse/GEODE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender closed GEODE-5962.
---
Fixed in PR #408
> region.putAll crashes if the map has a key with value nullptr
> -
>
> Key: GEODE-5962
> URL: https://issues.apache.org/jira/browse/GEODE-5962
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Sai Boorlagadda
>Priority: Major
>
> region.put guards against null key and values and throws an exception to the
> user, whereas region.putAll crashes with a message and the reason behind it
> processChunk is not handling message error type PUT_DATA_ERROR.
> {{terminating with uncaught exception of type
> apache::geode::client::MessageException: TcrMessage::processChunk: got
> unhandled message type}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5962) region.putAll crashes if the map has a key with value nullptr
[
https://issues.apache.org/jira/browse/GEODE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender resolved GEODE-5962.
-
Resolution: Fixed
> region.putAll crashes if the map has a key with value nullptr
> -
>
> Key: GEODE-5962
> URL: https://issues.apache.org/jira/browse/GEODE-5962
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Sai Boorlagadda
>Priority: Major
>
> region.put guards against null key and values and throws an exception to the
> user, whereas region.putAll crashes with a message and the reason behind it
> processChunk is not handling message error type PUT_DATA_ERROR.
> {{terminating with uncaught exception of type
> apache::geode::client::MessageException: TcrMessage::processChunk: got
> unhandled message type}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (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 ] Blake Bender closed GEODE-5957. --- We'll probably see this again from time to time in the future, but that should be addressed by specific tickets filed with specific repro steps. There's not really a reasonable way to ensure that we've adressed _every_ possible weirdo error message that could ever come back from the server. In the meantime, we fixed the ones we found in the two linked PRs. > 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 > 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 (v7.6.3#76005)
[jira] [Resolved] (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 ] Blake Bender resolved GEODE-5957. - Resolution: Fixed > 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 > 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 (v7.6.3#76005)
[jira] [Updated] (GEODE-5825) Determine where we need to write new tests to increase coverage
[ https://issues.apache.org/jira/browse/GEODE-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender updated GEODE-5825: Description: Plan: * start by rerunning all STABLE tests locally to generate a new report * use results to determine what's covered and what we still need to cover * Create a list of potential new tests we could write and what they would add to coverage was: Plan: * start by rerunning all STABLE tests locally to generate a new report * use results to write new tests against any public APIs that aren't being covered > Determine where we need to write new tests to increase coverage > --- > > Key: GEODE-5825 > URL: https://issues.apache.org/jira/browse/GEODE-5825 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Priority: Major > > Plan: > * start by rerunning all STABLE tests locally to generate a new report > * use results to determine what's covered and what we still need to cover > * Create a list of potential new tests we could write and what they would > add to coverage -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5825) Determine where we need to write new tests to increase coverage
[ https://issues.apache.org/jira/browse/GEODE-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender updated GEODE-5825: Summary: Determine where we need to write new tests to increase coverage (was: Write Tests Using New Framework to Increase Code Coverage in Key Areas) > Determine where we need to write new tests to increase coverage > --- > > Key: GEODE-5825 > URL: https://issues.apache.org/jira/browse/GEODE-5825 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Priority: Major > > Plan: > * start by rerunning all STABLE tests locally to generate a new report > * use results to write new tests against any public APIs that aren't being > covered -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-6788) CI failure: StatusServerExitCodeAcceptanceTest.classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lynn Gallinat updated GEODE-6788:
-
Affects Version/s: 1.10.0
> CI failure: StatusServerExitCodeAcceptanceTest.classMethod FAILED
> -
>
> Key: GEODE-6788
> URL: https://issues.apache.org/jira/browse/GEODE-6788
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.10.0
>Reporter: Lynn Gallinat
>Priority: Major
>
> {noformat}
> > Task :geode-assembly:acceptanceTest
> org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Process of [member-controller: gfsh -e
> start locator --name=locator-zip-proud-uniform --port=27782
> --J=-Dgemfire.enable-experimental-cluster-management-service=true -e start
> server --server-port=0 --name=server-add-wrong-book] did not exit after 2
> MINUTES] expected:<[tru]e> but was:<[fals]e>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:124)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest.classSetup(StatusServerExitCodeAcceptanceTest.java:66)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0288/test-results/acceptanceTest/1558401144/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0288/test-artifacts/1558401144/acceptancetestfiles-OpenJDK8-1.10.0-SNAPSHOT.0288.tgz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-6788) CI failure: StatusServerExitCodeAcceptanceTest.classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lynn Gallinat updated GEODE-6788:
-
Fix Version/s: (was: 1.10.0)
> CI failure: StatusServerExitCodeAcceptanceTest.classMethod FAILED
> -
>
> Key: GEODE-6788
> URL: https://issues.apache.org/jira/browse/GEODE-6788
> Project: Geode
> Issue Type: Bug
>Reporter: Lynn Gallinat
>Priority: Major
>
> {noformat}
> > Task :geode-assembly:acceptanceTest
> org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Process of [member-controller: gfsh -e
> start locator --name=locator-zip-proud-uniform --port=27782
> --J=-Dgemfire.enable-experimental-cluster-management-service=true -e start
> server --server-port=0 --name=server-add-wrong-book] did not exit after 2
> MINUTES] expected:<[tru]e> but was:<[fals]e>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:124)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
> at
> org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
> at
> org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest.classSetup(StatusServerExitCodeAcceptanceTest.java:66)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0288/test-results/acceptanceTest/1558401144/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0288/test-artifacts/1558401144/acceptancetestfiles-OpenJDK8-1.10.0-SNAPSHOT.0288.tgz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-6788) CI failure: StatusServerExitCodeAcceptanceTest.classMethod FAILED
Lynn Gallinat created GEODE-6788:
Summary: CI failure:
StatusServerExitCodeAcceptanceTest.classMethod FAILED
Key: GEODE-6788
URL: https://issues.apache.org/jira/browse/GEODE-6788
Project: Geode
Issue Type: Bug
Reporter: Lynn Gallinat
Fix For: 1.10.0
{noformat}
> Task :geode-assembly:acceptanceTest
org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest
> classMethod FAILED
org.junit.ComparisonFailure: [Process of [member-controller: gfsh -e start
locator --name=locator-zip-proud-uniform --port=27782
--J=-Dgemfire.enable-experimental-cluster-management-service=true -e start
server --server-port=0 --name=server-add-wrong-book] did not exit after 2
MINUTES] expected:<[tru]e> but was:<[fals]e>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:124)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
at
org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest.classSetup(StatusServerExitCodeAcceptanceTest.java:66)
{noformat}
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0288/test-results/acceptanceTest/1558401144/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.10.0-SNAPSHOT.0288/test-artifacts/1558401144/acceptancetestfiles-OpenJDK8-1.10.0-SNAPSHOT.0288.tgz
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-6787) when create index, met some error promt
Gang Yan created GEODE-6787: --- Summary: when create index, met some error promt Key: GEODE-6787 URL: https://issues.apache.org/jira/browse/GEODE-6787 Project: Geode Issue Type: Bug Reporter: Gang Yan process steps: 1. create a region , "REPLICATE", with keyConstraint "java.lang.Boolean" and valueConstraint "java.lang.Integer" 2. try to create index, "create index --name=customers11.name --expression=name --region=/customers11" 3. met error promt: Member | Status | Message -- | -- | -- 192.168.99.1(g1-g2-s3:83259):41004 | ERROR | org.apache.geode.cache.query.IndexInvalidException: Invalid indexed expression : ' name ' 192.168.99.1(g1-s1:83252):41002| ERROR | org.apache.geode.cache.query.IndexInvalidException: Invalid indexed expression : ' name ' 192.168.99.1(g2-s2:83256):41003| ERROR | org.apache.geode.cache.query.IndexInvalidException: Invalid indexed expression : ' name ' 192.168.99.1(s4:83263):41005 | ERROR | org.apache.geode.cache.query.IndexInvalidException: Invalid indexed expression : ' name ' 4. can not find any "Invalid indexed expression" in server log and locator log so, I think that , there may be two point can be improved: a. error msg need to be more clear, the reason is from "value constraint", not from "exression" b. in the log file , we need to record some error or info another related stuff is, when I tried to create same index twice, the error msg is not clear enough too. "create index --name=r6.id --expression=id --region=/REGION6" 1st time, it created index successfully. 2nd time , will meet error, "Index "r6.id" already exists. Create failed due to duplicate name.", it good to match expectation. And next, when I update the index name with a new name: "create index --name=r6.id2 --expression=id --region=/REGION6", it met error :"Index "r6.id2" already exists. Create failed due to duplicate definition. ", it is a bit confused, because Index "r6.id2" does not exist. the reason is the "expression" field duplicated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6733) Remove mutable static org.apache.geode.internal.net.Buffers.buffersQueue
[ https://issues.apache.org/jira/browse/GEODE-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-6733. - Resolution: Fixed Fix Version/s: 1.10.0 > Remove mutable static org.apache.geode.internal.net.Buffers.buffersQueue > > > Key: GEODE-6733 > URL: https://issues.apache.org/jira/browse/GEODE-6733 > Project: Geode > Issue Type: Sub-task > Components: core >Reporter: Robert Houghton >Assignee: Bruce Schuchardt >Priority: Major > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Changes to Geode have caused unit test ordering to shift in such a way that > NioPlainEngineTest:ensureWrappedCapacity fails because the static > Buffers.buffersQueue object is not empty at test time. > Solution: > Refactor the Buffers class to be non-static, and owned by its consumers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-6733) Remove mutable static org.apache.geode.internal.net.Buffers.buffersQueue
[ https://issues.apache.org/jira/browse/GEODE-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844976#comment-16844976 ] ASF subversion and git services commented on GEODE-6733: Commit 3ec8459e9254b7b5a553965c40b75668f9e8b673 in geode's branch refs/heads/develop from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3ec8459 ] GEODE-6733 Remove mutable static org.apache.geode.internal.net.Buffers.buffersQueue Converted static Buffers class to be a non-static buffer pool. > Remove mutable static org.apache.geode.internal.net.Buffers.buffersQueue > > > Key: GEODE-6733 > URL: https://issues.apache.org/jira/browse/GEODE-6733 > Project: Geode > Issue Type: Sub-task > Components: core >Reporter: Robert Houghton >Assignee: Bruce Schuchardt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Changes to Geode have caused unit test ordering to shift in such a way that > NioPlainEngineTest:ensureWrappedCapacity fails because the static > Buffers.buffersQueue object is not empty at test time. > Solution: > Refactor the Buffers class to be non-static, and owned by its consumers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5818) Port Remaining csharp test projects to be generated by cmake
[ https://issues.apache.org/jira/browse/GEODE-5818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844957#comment-16844957 ] Blake Bender commented on GEODE-5818: - This item can probably be resolved Won't Fix and closed in toto, but someone should investigate briefly and see if this is worth doing for the few projects listed here that aren't obviously part of our obsoleted test framework > Port Remaining csharp test projects to be generated by cmake > > > Key: GEODE-5818 > URL: https://issues.apache.org/jira/browse/GEODE-5818 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Michael Martell >Priority: Major > > These projects need porting to cmake: > * ./FwkClient/FwkClient.csproj.in > * ./DUnitFramework/DUnitFramework.csproj.in > * ./NewFwkLib/NewFwkLib.csproj.in > * ./FwkLauncher/FwkLauncher.csproj.in > * ./PdxVersion2Lib/PdxVersion2Lib.csproj.in > * ./PdxVersion1Lib/PdxVersion1Lib.csproj.in > * ./FwkUtil/FwkUtil.csproj.in > * ./SecurityUtil/SecurityUtil.csproj.in -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5802) Replace raw pointers with smart pointers
[ https://issues.apache.org/jira/browse/GEODE-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-5802. --- Too vague, will open specific tickets for specific replacements of raw pointers with smart pointers as appropriate > Replace raw pointers with smart pointers > > > Key: GEODE-5802 > URL: https://issues.apache.org/jira/browse/GEODE-5802 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Ernest Burghardt >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5802) Replace raw pointers with smart pointers
[ https://issues.apache.org/jira/browse/GEODE-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-5802. - Resolution: Won't Fix > Replace raw pointers with smart pointers > > > Key: GEODE-5802 > URL: https://issues.apache.org/jira/browse/GEODE-5802 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Ernest Burghardt >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5769) Test AppDomains against TcrChunkedResult
[ https://issues.apache.org/jira/browse/GEODE-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-5769. - Resolution: Fixed > Test AppDomains against TcrChunkedResult > > > Key: GEODE-5769 > URL: https://issues.apache.org/jira/browse/GEODE-5769 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > We recently discovered and fixed a problem with CQ and AppDomains, and the > fix should eliminate the need for appdomain code in TcrChunkedResult. We > need a test to verify, then if it works we can remove this redundant code. > Steps: > * write a C# integration-test2 test that issues a query (NOT a continuous > query) > * Remove appdomaincontext code from TcrChunkedHandler > * Verify test still passes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5769) Test AppDomains against TcrChunkedResult
[ https://issues.apache.org/jira/browse/GEODE-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-5769. --- Fixed in PR #412 > Test AppDomains against TcrChunkedResult > > > Key: GEODE-5769 > URL: https://issues.apache.org/jira/browse/GEODE-5769 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > We recently discovered and fixed a problem with CQ and AppDomains, and the > fix should eliminate the need for appdomain code in TcrChunkedResult. We > need a test to verify, then if it works we can remove this redundant code. > Steps: > * write a C# integration-test2 test that issues a query (NOT a continuous > query) > * Remove appdomaincontext code from TcrChunkedHandler > * Verify test still passes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5756) Use consistent namespace in integration-test
[ https://issues.apache.org/jira/browse/GEODE-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-5756. --- Not a productive use of our time. We're rewriting all the tests, and this will go away as part of that process > Use consistent namespace in integration-test > > > Key: GEODE-5756 > URL: https://issues.apache.org/jira/browse/GEODE-5756 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > Some of our C++ integration test code uses apache::geode::client::testing, a > bunch more of it uses apache::geode::testing, and there are probably other > variations in there because test code. Somebody need to go through it all > and put it all in apache::geode::client::testing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5756) Use consistent namespace in integration-test
[ https://issues.apache.org/jira/browse/GEODE-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-5756. - Resolution: Won't Fix > Use consistent namespace in integration-test > > > Key: GEODE-5756 > URL: https://issues.apache.org/jira/browse/GEODE-5756 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > Some of our C++ integration test code uses apache::geode::client::testing, a > bunch more of it uses apache::geode::testing, and there are probably other > variations in there because test code. Somebody need to go through it all > and put it all in apache::geode::client::testing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5746) Integration-test-2 CLI tests are flaky when run in parallel.
[ https://issues.apache.org/jira/browse/GEODE-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-5746. - Resolution: Fixed > Integration-test-2 CLI tests are flaky when run in parallel. > > > Key: GEODE-5746 > URL: https://issues.apache.org/jira/browse/GEODE-5746 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Ivan Godwin >Priority: Major > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > 8 of the past 20 cli-test-windows-debug test runs have failed. While 1 > failure may be blamed on infrastructure, the other 7 are test failures. > RegionSSLTest and RegionTest are the most frequent to fail. > The cli-test-windows-release task is not nearly as bad. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5746) Integration-test-2 CLI tests are flaky when run in parallel.
[ https://issues.apache.org/jira/browse/GEODE-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-5746. --- Fixed in the linked PRs. If we still have test framework issues (and we probably do), we'll open new tickets as appropriate > Integration-test-2 CLI tests are flaky when run in parallel. > > > Key: GEODE-5746 > URL: https://issues.apache.org/jira/browse/GEODE-5746 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Ivan Godwin >Priority: Major > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > 8 of the past 20 cli-test-windows-debug test runs have failed. While 1 > failure may be blamed on infrastructure, the other 7 are test failures. > RegionSSLTest and RegionTest are the most frequent to fail. > The cli-test-windows-release task is not nearly as bad. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5755) Remove unused methods in test code
[ https://issues.apache.org/jira/browse/GEODE-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-5755. --- This is not a productive area of the code to be working in. It's all going away when we rewrite the tests to work in the new framework > Remove unused methods in test code > -- > > Key: GEODE-5755 > URL: https://issues.apache.org/jira/browse/GEODE-5755 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > As part of the change for GEODE-5738, compiler warnings about unused member > functions had to be disabled in test code. This is not a valid long-term > strategy for the code, so these methods need to go away, either via direct > removal to a library or via wholesale refactoring of the integration test > framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5755) Remove unused methods in test code
[ https://issues.apache.org/jira/browse/GEODE-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-5755. - Resolution: Won't Fix > Remove unused methods in test code > -- > > Key: GEODE-5755 > URL: https://issues.apache.org/jira/browse/GEODE-5755 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > As part of the change for GEODE-5738, compiler warnings about unused member > functions had to be disabled in test code. This is not a valid long-term > strategy for the code, so these methods need to go away, either via direct > removal to a library or via wholesale refactoring of the integration test > framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-6786) Provide ability to delete a region using V2 REST API
Jens Deppe created GEODE-6786: - Summary: Provide ability to delete a region using V2 REST API Key: GEODE-6786 URL: https://issues.apache.org/jira/browse/GEODE-6786 Project: Geode Issue Type: New Feature Components: management Reporter: Jens Deppe -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5222) JMX metric exposed in an MBean
[ https://issues.apache.org/jira/browse/GEODE-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844717#comment-16844717 ] Alberto Bustamante Reyes commented on GEODE-5222: - Im interested on the publication of disk stores usage percentage via JMX. If I want to create a pull request for that, is it ok to use this ticket? Or should I create another one with just that issue, and set Geode 5222 as related ticket? > JMX metric exposed in an MBean > -- > > Key: GEODE-5222 > URL: https://issues.apache.org/jira/browse/GEODE-5222 > Project: Geode > Issue Type: Improvement > Components: docs, persistence >Reporter: Nick Vallely >Assignee: Alberto Bustamante Reyes >Priority: Major > > Given I need to scale down or scale up my servers based on usage > When I setup my monitoring of JMX metrics through an MBean > Then I have the ability to see Disk Free Percentage > AND Disk Free in Bytes > AND Disk Used Percentage > AND Disk Used in Bytes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
