[jira] [Commented] (GEODE-5716) Improve GfshRule to allow easy debugging of the processes started
[ https://issues.apache.org/jira/browse/GEODE-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610885#comment-16610885 ] ASF subversion and git services commented on GEODE-5716: Commit b9587c24f3a3097e811b0072d7586aaa8c39 in geode's branch refs/heads/develop from jinmeiliao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9587c2 ] GEODE-5716: add debug capability to the processes started using GfshRule (#2446) > Improve GfshRule to allow easy debugging of the processes started > - > > Key: GEODE-5716 > URL: https://issues.apache.org/jira/browse/GEODE-5716 > Project: Geode > Issue Type: Improvement > Components: configuration >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Currently GfshRule started processes for gfsh and locator/servers started, > it's hard to debug into these processes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5697) SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close
[
https://issues.apache.org/jira/browse/GEODE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-5697:
Affects Version/s: 1.7.0
> SingleThreadJTAExecutor.cleanup method should ignore exception thrown during
> cache close
>
>
> Key: GEODE-5697
> URL: https://issues.apache.org/jira/browse/GEODE-5697
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.7.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following exception cause some of the TXState is not being cleaned up due
> to the following exception.
> {noformat}
> org.apache.geode.cache.CacheClosedException: The cache is closed.
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:1563)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.AfterCompletion.waitForCondition(AfterCompletion.java:65)
> at
> org.apache.geode.internal.cache.AfterCompletion.waitUntilFinished(AfterCompletion.java:89)
> at
> org.apache.geode.internal.cache.AfterCompletion.signalAndWaitForDoOp(AfterCompletion.java:82)
> at
> org.apache.geode.internal.cache.AfterCompletion.cancel(AfterCompletion.java:94)
> at
> org.apache.geode.internal.cache.SingleThreadJTAExecutor.cleanup(SingleThreadJTAExecutor.java:65)
> at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:875)
> at org.apache.geode.internal.cache.TXState.close(TXState.java:863)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.close(TXStateProxyImpl.java:925)
> at
> org.apache.geode.internal.cache.TXManagerImpl.close(TXManagerImpl.java:663)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2408)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1372)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1022)
> at hydra.RemoteTestModule$3.run(RemoteTestModule.java:416)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5697) SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close
[
https://issues.apache.org/jira/browse/GEODE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-5697.
-
Resolution: Fixed
Fix Version/s: 1.8.0
> SingleThreadJTAExecutor.cleanup method should ignore exception thrown during
> cache close
>
>
> Key: GEODE-5697
> URL: https://issues.apache.org/jira/browse/GEODE-5697
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.7.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following exception cause some of the TXState is not being cleaned up due
> to the following exception.
> {noformat}
> org.apache.geode.cache.CacheClosedException: The cache is closed.
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:1563)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.AfterCompletion.waitForCondition(AfterCompletion.java:65)
> at
> org.apache.geode.internal.cache.AfterCompletion.waitUntilFinished(AfterCompletion.java:89)
> at
> org.apache.geode.internal.cache.AfterCompletion.signalAndWaitForDoOp(AfterCompletion.java:82)
> at
> org.apache.geode.internal.cache.AfterCompletion.cancel(AfterCompletion.java:94)
> at
> org.apache.geode.internal.cache.SingleThreadJTAExecutor.cleanup(SingleThreadJTAExecutor.java:65)
> at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:875)
> at org.apache.geode.internal.cache.TXState.close(TXState.java:863)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.close(TXStateProxyImpl.java:925)
> at
> org.apache.geode.internal.cache.TXManagerImpl.close(TXManagerImpl.java:663)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2408)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1372)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1022)
> at hydra.RemoteTestModule$3.run(RemoteTestModule.java:416)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5709) Create pipeline job to build windows image
[ https://issues.apache.org/jira/browse/GEODE-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610905#comment-16610905 ] ASF subversion and git services commented on GEODE-5709: Commit 8661b1e0347cbd4574fbb26c8e0999a646b4bd7f in geode's branch refs/heads/develop from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8661b1e ] GEODE-5709: Use external IP for winrm packer communication > Create pipeline job to build windows image > -- > > Key: GEODE-5709 > URL: https://issues.apache.org/jira/browse/GEODE-5709 > Project: Geode > Issue Type: Task > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5723) Only publish maven artifacts for SNAPSHOT versions.
Jacob S. Barrett created GEODE-5723: --- Summary: Only publish maven artifacts for SNAPSHOT versions. Key: GEODE-5723 URL: https://issues.apache.org/jira/browse/GEODE-5723 Project: Geode Issue Type: Improvement Components: build Reporter: Jacob S. Barrett -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5723) Only publish maven artifacts for SNAPSHOT versions.
[ https://issues.apache.org/jira/browse/GEODE-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5723: -- Labels: pull-request-available (was: ) > Only publish maven artifacts for SNAPSHOT versions. > --- > > Key: GEODE-5723 > URL: https://issues.apache.org/jira/browse/GEODE-5723 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5668) Switch Windows build jobs to 'heavy-lifter' model
[ https://issues.apache.org/jira/browse/GEODE-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610957#comment-16610957 ] ASF subversion and git services commented on GEODE-5668: Commit 8ce6ba63a99770d48fe086ad2ec22ed3821b2f85 in geode's branch refs/heads/concourse-staging from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8ce6ba6 ] GEODE-5668: UpdatePassingRef does not depend on Windows jobs > Switch Windows build jobs to 'heavy-lifter' model > - > > Key: GEODE-5668 > URL: https://issues.apache.org/jira/browse/GEODE-5668 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > Use the same approach we do for Linux builds, which is to launch a build > system for every job. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5697) SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close
[
https://issues.apache.org/jira/browse/GEODE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610964#comment-16610964
]
ASF subversion and git services commented on GEODE-5697:
Commit 7f605494e4cfe87c168215bb54ffaeb9c2fe9503 in geode's branch
refs/heads/concourse-staging from pivotal-eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7f60549 ]
GEODE-5697: Handle CacheClosedException when performing beforeCompletion and
afterCompletion. (#2448)
> SingleThreadJTAExecutor.cleanup method should ignore exception thrown during
> cache close
>
>
> Key: GEODE-5697
> URL: https://issues.apache.org/jira/browse/GEODE-5697
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.7.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following exception cause some of the TXState is not being cleaned up due
> to the following exception.
> {noformat}
> org.apache.geode.cache.CacheClosedException: The cache is closed.
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:1563)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.AfterCompletion.waitForCondition(AfterCompletion.java:65)
> at
> org.apache.geode.internal.cache.AfterCompletion.waitUntilFinished(AfterCompletion.java:89)
> at
> org.apache.geode.internal.cache.AfterCompletion.signalAndWaitForDoOp(AfterCompletion.java:82)
> at
> org.apache.geode.internal.cache.AfterCompletion.cancel(AfterCompletion.java:94)
> at
> org.apache.geode.internal.cache.SingleThreadJTAExecutor.cleanup(SingleThreadJTAExecutor.java:65)
> at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:875)
> at org.apache.geode.internal.cache.TXState.close(TXState.java:863)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.close(TXStateProxyImpl.java:925)
> at
> org.apache.geode.internal.cache.TXManagerImpl.close(TXManagerImpl.java:663)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2408)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1372)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1022)
> at hydra.RemoteTestModule$3.run(RemoteTestModule.java:416)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5668) Switch Windows build jobs to 'heavy-lifter' model
[ https://issues.apache.org/jira/browse/GEODE-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610963#comment-16610963 ] ASF subversion and git services commented on GEODE-5668: Commit 808c049b27b4458c68ba74d8893eab3da8c99372 in geode's branch refs/heads/concourse-staging from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=808c049 ] GEODE-5668: increase rsync up & down timeout > Switch Windows build jobs to 'heavy-lifter' model > - > > Key: GEODE-5668 > URL: https://issues.apache.org/jira/browse/GEODE-5668 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > Use the same approach we do for Linux builds, which is to launch a build > system for every job. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5709) Create pipeline job to build windows image
[ https://issues.apache.org/jira/browse/GEODE-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610960#comment-16610960 ] ASF subversion and git services commented on GEODE-5709: Commit 24f5e993f8c80d7fc7ef7882f1254592604bb100 in geode's branch refs/heads/concourse-staging from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=24f5e99 ] GEODE-5709: Add missing build image resources > Create pipeline job to build windows image > -- > > Key: GEODE-5709 > URL: https://issues.apache.org/jira/browse/GEODE-5709 > Project: Geode > Issue Type: Task > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5628) CI Failure: WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
[
https://issues.apache.org/jira/browse/GEODE-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610962#comment-16610962
]
ASF subversion and git services commented on GEODE-5628:
Commit e586c841c98e4f7f27217ede42e6059771f673cf in geode's branch
refs/heads/concourse-staging from [~mcmellawatt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e586c84 ]
GEODE-5628: Getting two random ports at once and fixing formatting (#2441)
* GEODE-5628: Getting two random ports at once and fixing formatting
Co-authored-by: Ryan McMahon
Co-authored-by: Sai Boorlagadda
> CI Failure: WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
> --
>
> Key: GEODE-5628
> URL: https://issues.apache.org/jira/browse/GEODE-5628
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Sai Boorlagadda
>Assignee: Ryan McMahon
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 40m
> Remaining Estimate: 0h
>
> CI Run: https://concourse.apachegeode-ci.info/builds/20378
> Build artifacts:
> http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/upgradeTest/1535044814/
> {code:java}
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
> > EventProcessingMixedSiteOneOldSiteTwo[from_v150] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo$$Lambda$41/436821547.run
> in VM 4 running on Host 460446c8f083 with 7 VMs with version 150
> at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.EventProcessingMixedSiteOneOldSiteTwo(WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.java:68)
> Caused by:
> java.net.BindException: Failed to create server socket on
> null[25,312]
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:752)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:709)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:675)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.initializeServerSocket(TcpServer.java:240)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.startServerThread(TcpServer.java:224)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:219)
> at
> org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:485)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:542)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:305)
> at
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocator(WANRollingUpgradeDUnitTest.java:103)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocator(WANRollingUpgradeDUnitTest.java:95)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.lambda$EventProcessingMixedSiteOneOldSiteTwo$67afc7f8$1(WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.java:68)
> Caused by:
> java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
> at java.net.ServerSocket.bind(ServerSocket.java:375)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:748)
> ... 13 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5716) Improve GfshRule to allow easy debugging of the processes started
[ https://issues.apache.org/jira/browse/GEODE-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610966#comment-16610966 ] ASF subversion and git services commented on GEODE-5716: Commit b9587c24f3a3097e811b0072d7586aaa8c39 in geode's branch refs/heads/concourse-staging from jinmeiliao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9587c2 ] GEODE-5716: add debug capability to the processes started using GfshRule (#2446) > Improve GfshRule to allow easy debugging of the processes started > - > > Key: GEODE-5716 > URL: https://issues.apache.org/jira/browse/GEODE-5716 > Project: Geode > Issue Type: Improvement > Components: configuration >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Currently GfshRule started processes for gfsh and locator/servers started, > it's hard to debug into these processes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5668) Switch Windows build jobs to 'heavy-lifter' model
[ https://issues.apache.org/jira/browse/GEODE-5668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610958#comment-16610958 ] ASF subversion and git services commented on GEODE-5668: Commit c0056a3668e14ec90d3ef6fc4eb775d0a8fa8b1b in geode's branch refs/heads/concourse-staging from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c0056a3 ] GEODE-5668: Remove debug flag from instance start script > Switch Windows build jobs to 'heavy-lifter' model > - > > Key: GEODE-5668 > URL: https://issues.apache.org/jira/browse/GEODE-5668 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > Use the same approach we do for Linux builds, which is to launch a build > system for every job. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5709) Create pipeline job to build windows image
[ https://issues.apache.org/jira/browse/GEODE-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610959#comment-16610959 ] ASF subversion and git services commented on GEODE-5709: Commit 2cd1d3232e14cae4b1d9a954b614a75207bf9f90 in geode's branch refs/heads/concourse-staging from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2cd1d32 ] GEODE-5709: Add CI job to build Windows images (#2443) > Create pipeline job to build windows image > -- > > Key: GEODE-5709 > URL: https://issues.apache.org/jira/browse/GEODE-5709 > Project: Geode > Issue Type: Task > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5709) Create pipeline job to build windows image
[ https://issues.apache.org/jira/browse/GEODE-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610967#comment-16610967 ] ASF subversion and git services commented on GEODE-5709: Commit 8661b1e0347cbd4574fbb26c8e0999a646b4bd7f in geode's branch refs/heads/concourse-staging from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8661b1e ] GEODE-5709: Use external IP for winrm packer communication > Create pipeline job to build windows image > -- > > Key: GEODE-5709 > URL: https://issues.apache.org/jira/browse/GEODE-5709 > Project: Geode > Issue Type: Task > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5628) CI Failure: WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
[
https://issues.apache.org/jira/browse/GEODE-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610961#comment-16610961
]
ASF subversion and git services commented on GEODE-5628:
Commit e586c841c98e4f7f27217ede42e6059771f673cf in geode's branch
refs/heads/concourse-staging from [~mcmellawatt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e586c84 ]
GEODE-5628: Getting two random ports at once and fixing formatting (#2441)
* GEODE-5628: Getting two random ports at once and fixing formatting
Co-authored-by: Ryan McMahon
Co-authored-by: Sai Boorlagadda
> CI Failure: WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
> --
>
> Key: GEODE-5628
> URL: https://issues.apache.org/jira/browse/GEODE-5628
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Sai Boorlagadda
>Assignee: Ryan McMahon
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 40m
> Remaining Estimate: 0h
>
> CI Run: https://concourse.apachegeode-ci.info/builds/20378
> Build artifacts:
> http://files.apachegeode-ci.info/builds/geode-pr-2357/test-results/upgradeTest/1535044814/
> {code:java}
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo
> > EventProcessingMixedSiteOneOldSiteTwo[from_v150] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo$$Lambda$41/436821547.run
> in VM 4 running on Host 460446c8f083 with 7 VMs with version 150
> at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.EventProcessingMixedSiteOneOldSiteTwo(WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.java:68)
> Caused by:
> java.net.BindException: Failed to create server socket on
> null[25,312]
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:752)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:709)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:675)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.initializeServerSocket(TcpServer.java:240)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.startServerThread(TcpServer.java:224)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:219)
> at
> org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:485)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:542)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:305)
> at
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocator(WANRollingUpgradeDUnitTest.java:103)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocator(WANRollingUpgradeDUnitTest.java:95)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.lambda$EventProcessingMixedSiteOneOldSiteTwo$67afc7f8$1(WANRollingUpgradeEventProcessingMixedSiteOneOldSiteTwo.java:68)
> Caused by:
> java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
> at java.net.ServerSocket.bind(ServerSocket.java:375)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:748)
> ... 13 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5724) Fix javadocs for cache.util.ObjectSizer
Karen Smoler Miller created GEODE-5724:
--
Summary: Fix javadocs for cache.util.ObjectSizer
Key: GEODE-5724
URL: https://issues.apache.org/jira/browse/GEODE-5724
Project: Geode
Issue Type: Bug
Reporter: Karen Smoler Miller
The javadocs description for org.apache.geode.cache.util.ObjectSizer look like
this:
{{public interface ObjectSizer
The sizer interface defines a method that when called returns the size of the
object passed in. Implementations may return hardcoded values for object size
if the implementation knows the object size for all objects that are likely to
be cached. You should use a sizer with a
EvictionAttributes.createLRUHeapAttributes(ObjectSizer) or
EvictionAttributes.createLRUMemoryAttributes(ObjectSizer) if you want to use a
faster or more accurate method of sizing than provided by the default object
sizer, which is {#link SIZE_CLASS_ONCE}}
Notice that the last part of the description is not right. It needs to be
fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5724) Fix javadocs for cache.util.ObjectSizer
[
https://issues.apache.org/jira/browse/GEODE-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-5724:
---
Description:
The javadocs description for org.apache.geode.cache.util.ObjectSizer look like
this:
{{public interface ObjectSizer}}
{{ The sizer interface defines a method that when called returns the size of
the object passed in. Implementations may return hardcoded values for object
size if the implementation knows the object size for all objects that are
likely to be cached. You should use a sizer with a
EvictionAttributes.createLRUHeapAttributes(ObjectSizer) or
EvictionAttributes.createLRUMemoryAttributes(ObjectSizer) if you want to use a
faster or more accurate method of sizing than provided by the default object
sizer, which is {#link SIZE_CLASS_ONCE}}
Notice that the last part of the description is not right. It needs to be fixed.
was:
The javadocs description for org.apache.geode.cache.util.ObjectSizer look like
this:
{{public interface ObjectSizer
The sizer interface defines a method that when called returns the size of the
object passed in. Implementations may return hardcoded values for object size
if the implementation knows the object size for all objects that are likely to
be cached. You should use a sizer with a
EvictionAttributes.createLRUHeapAttributes(ObjectSizer) or
EvictionAttributes.createLRUMemoryAttributes(ObjectSizer) if you want to use a
faster or more accurate method of sizing than provided by the default object
sizer, which is {#link SIZE_CLASS_ONCE}}
Notice that the last part of the description is not right. It needs to be
fixed.
> Fix javadocs for cache.util.ObjectSizer
> ---
>
> Key: GEODE-5724
> URL: https://issues.apache.org/jira/browse/GEODE-5724
> Project: Geode
> Issue Type: Bug
>Reporter: Karen Smoler Miller
>Priority: Major
>
> The javadocs description for org.apache.geode.cache.util.ObjectSizer look
> like this:
> {{public interface ObjectSizer}}
> {{ The sizer interface defines a method that when called returns the size of
> the object passed in. Implementations may return hardcoded values for object
> size if the implementation knows the object size for all objects that are
> likely to be cached. You should use a sizer with a
> EvictionAttributes.createLRUHeapAttributes(ObjectSizer) or
> EvictionAttributes.createLRUMemoryAttributes(ObjectSizer) if you want to use
> a faster or more accurate method of sizing than provided by the default
> object sizer, which is {#link SIZE_CLASS_ONCE}}
> Notice that the last part of the description is not right. It needs to be
> fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5724) Fix javadocs for cache.util.ObjectSizer
[
https://issues.apache.org/jira/browse/GEODE-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-5724:
---
Priority: Minor (was: Major)
Description:
The javadocs description for org.apache.geode.cache.util.ObjectSizer look like
this:
{{public interface ObjectSizer}}
{{The sizer interface defines a method that when called returns the size of the
object passed in. Implementations may return hardcoded values for object size
if the implementation knows the object size for all objects that are likely to
be cached. You should use a sizer with a
EvictionAttributes.createLRUHeapAttributes(ObjectSizer) or
EvictionAttributes.createLRUMemoryAttributes(ObjectSizer) if you want to use a
faster or more accurate method of sizing than provided by the default object
sizer, which is {#link SIZE_CLASS_ONCE}}
Notice that the last part of the description is not right. It needs to be fixed.
was:
The javadocs description for org.apache.geode.cache.util.ObjectSizer look like
this:
{{public interface ObjectSizer}}
{{ The sizer interface defines a method that when called returns the size of
the object passed in. Implementations may return hardcoded values for object
size if the implementation knows the object size for all objects that are
likely to be cached. You should use a sizer with a
EvictionAttributes.createLRUHeapAttributes(ObjectSizer) or
EvictionAttributes.createLRUMemoryAttributes(ObjectSizer) if you want to use a
faster or more accurate method of sizing than provided by the default object
sizer, which is {#link SIZE_CLASS_ONCE}}
Notice that the last part of the description is not right. It needs to be fixed.
> Fix javadocs for cache.util.ObjectSizer
> ---
>
> Key: GEODE-5724
> URL: https://issues.apache.org/jira/browse/GEODE-5724
> Project: Geode
> Issue Type: Bug
>Reporter: Karen Smoler Miller
>Priority: Minor
>
> The javadocs description for org.apache.geode.cache.util.ObjectSizer look
> like this:
> {{public interface ObjectSizer}}
> {{The sizer interface defines a method that when called returns the size of
> the object passed in. Implementations may return hardcoded values for object
> size if the implementation knows the object size for all objects that are
> likely to be cached. You should use a sizer with a
> EvictionAttributes.createLRUHeapAttributes(ObjectSizer) or
> EvictionAttributes.createLRUMemoryAttributes(ObjectSizer) if you want to use
> a faster or more accurate method of sizing than provided by the default
> object sizer, which is {#link SIZE_CLASS_ONCE}}
> Notice that the last part of the description is not right. It needs to be
> fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5725) Many WAN DUnit tests with off-heap enabled aren't actually exercising off-heap
Ryan McMahon created GEODE-5725: --- Summary: Many WAN DUnit tests with off-heap enabled aren't actually exercising off-heap Key: GEODE-5725 URL: https://issues.apache.org/jira/browse/GEODE-5725 Project: Geode Issue Type: Bug Components: offheap, wan Reporter: Ryan McMahon Fix For: 1.8.0 Many of the WAN DUnit tests are run with both off-heap disabled and enabled. However, there is an optimization in the off-heap implementation where if the entry value is less than 8-bytes, off-heap is bypassed and the value is put on the heap. This is due to the value being equal to or less than the size of the off-heap address that would have been used. It is therefore pointless to use off-heap if the value itself is less than the size of the address. In many WAN tests we are using longs as values, which will bypass off-heap in this way. However, it is expected that off-heap is being exercised. We should instead use another data type (strings) as values to be sure that the off-heap feature is actually being exercised. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5694) Remove zip distribution
[ https://issues.apache.org/jira/browse/GEODE-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610998#comment-16610998 ] ASF subversion and git services commented on GEODE-5694: Commit 518717a50a404642b28751fbbaeb4438111c169a in geode's branch refs/heads/develop from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=518717a ] GEODE-5694 Do not create or publish zip distributions (#2424) * Zip archive is removed from publication list. * Geode uses the maven-publish plugin which has better control of publication tasks. Prefer using it instead. * Fully disable distZip and distSrcZip, even when specified on commandline Co-Authored-by: Sean Goller Co-Authored-by: Robert Houghton > Remove zip distribution > --- > > Key: GEODE-5694 > URL: https://issues.apache.org/jira/browse/GEODE-5694 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > This causes build times to be longer than necessary, and produces a redundant > artifact. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5726) CI Failure.AsyncEventListenerDistributedTest > testReplicatedSerialAsyncEventQueueWithPersistenceEnabled_Restart
[
https://issues.apache.org/jira/browse/GEODE-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5726:
-
Labels: swat (was: )
> CI Failure.AsyncEventListenerDistributedTest >
> testReplicatedSerialAsyncEventQueueWithPersistenceEnabled_Restart
>
>
> Key: GEODE-5726
> URL: https://issues.apache.org/jira/browse/GEODE-5726
> Project: Geode
> Issue Type: Improvement
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
>
> This test failed in multiple CI runs recently.
> https://concourse.apachegeode-ci.info/teams/main/pipelines/concourse-staging/jobs/DistributedTest/builds/96
> http://files.apachegeode-ci.info/builds/1.8.0-build.1/test-results/distributedTest/1536506408/
> {noformat}
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDistributedTest
> >
> testReplicatedSerialAsyncEventQueueWithPersistenceEnabled_Restart[dispatcherThreadCount=1]
> FAILED
>
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDistributedTest$$Lambda$132/352914586.run
> in VM 0 running on Host 58887cf96a8a with 4 VMs
>
> at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
>
> at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
>
> at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
>
> at
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDistributedTest.testReplicatedSerialAsyncEventQueueWithPersistenceEnabled_Restart(AsyncEventListenerDistributedTest.java:283)
>
>
> Caused by:
>
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDistributedTest
>
>
> Expected size:<1000> but was:<900> in:
>
> <{100=100, 101=101, 102=102, 103=103, 104=104, 105=105, 106=106,
> 107=107, 108=108, 109=109, 110=110, 111=111, 112=112, 113=113, 114=114,
> 115=115, 116=116, 117=117, 118=118, 119=119, 120=120, 121=121, 122=122,
> 123=123, 124=124, 125=125, 126=126, 127=127, 128=128, 129=129, 130=130,
> 131=131, 132=132, 133=133, 134=134, 135=135, 136=136, 137=137, 138=138,
> 139=139, 140=140, 141=141, 142=142, 143=143, 144=144, 145=145, 146=146,
> 147=147, 148=148, 149=149, 150=150, 151=151, 152=152, 153=153, 154=154,
> 155=155, 156=156, 157=157, 158=158, 159=159, 160=160, 161=161, 162=162,
> 163=163, 164=164, 165=165, 166=166, 167=167, 168=168, 169=169, 170=170,
> 171=171, 172=172, 173=173, 174=174, 175=175, 176=176, 177=177, 178=178,
> 179=179, 180=180, 181=181, 182=182, 183=183, 184=184, 185=185, 186=186,
> 187=187, 188=188, 189=189, 190=190, 191=191, 192=192, 193=193, 194=194,
> 195=195, 196=196, 197=197, 198=198, 199=199, 200=200, 201=201, 202=202,
> 203=203, 204=204, 205=205, 206=206, 207=207, 208=208, 209=209, 210=210,
> 211=211, 212=212, 213=213, 214=214, 215=215, 216=216, 217=217, 218=218,
> 219=219, 220=220, 221=221, 222=222, 223=223, 224=224, 225=225, 226=226,
> 227=227, 228=228, 229=229, 230=230, 231=231, 232=232, 233=233, 234=234,
> 235=235, 236=236, 237=237, 238=238, 239=239, 240=240, 241=241, 242=242,
> 243=243, 244=244, 245=245, 246=246, 247=247, 248=248, 249=249, 250=250,
> 251=251, 252=252, 253=253, 254=254, 255=255, 256=256, 257=257, 258=258,
> 259=259, 260=260, 261=261, 262=262, 263=263, 264=264, 265=265, 266=266,
> 267=267, 268=268, 269=269, 270=270, 271=271, 272=272, 273=273, 274=274,
> 275=275, 276=276, 277=277, 278=278, 279=279, 280=280, 281=281, 282=282,
> 283=283, 284=284, 285=285, 286=286, 287=287, 288=288, 289=289, 290=290,
> 291=291, 292=292, 293=293, 294=294, 295=295, 296=296, 297=297, 298=298,
> 299=299, 300=300, 301=301, 302=302, 303=303, 304=304, 305=305, 306=306,
> 307=307, 308=308, 309=309, 310=310, 311=311, 312=312, 313=313, 314=314,
> 315=315, 316=316, 317=317, 318=318, 319=319, 320=320, 321=321, 322=322,
> 323=323, 324=324, 325=325, 326=326, 327=327, 328=328, 329=329, 330=330,
> 331=331, 332=332, 333=333, 334=334, 335=335, 336=336, 337=337, 338=338,
> 339=339, 340=340, 341=341, 342=342, 343=343, 344=344, 345=345, 346=346,
> 347=347, 348=348, 349=349, 350=350, 351=351, 352=352, 353=353, 354=354,
> 355=355, 356=356, 357=357, 358=358, 359=359, 360=360, 361=361, 362=362,
> 363=363, 364=364, 365=365, 366=366, 367=367, 368=368, 369=369, 370=370,
> 371=371, 372=372, 373=373, 374=374, 375=375, 376=376, 377=377, 378=378,
> 379=379, 380=380, 381=381, 382=382, 383=383, 384=384, 385=385, 386=386,
> 387=387, 388=388, 389=389, 390=390, 391=391, 392=392, 393=393, 394=394,
> 395=395, 396=396, 397=397, 398=398, 399=399, 400=400, 401=401,
[jira] [Created] (GEODE-5726) CI Failure.AsyncEventListenerDistributedTest > testReplicatedSerialAsyncEventQueueWithPersistenceEnabled_Restart
Dan Smith created GEODE-5726:
Summary: CI Failure.AsyncEventListenerDistributedTest >
testReplicatedSerialAsyncEventQueueWithPersistenceEnabled_Restart
Key: GEODE-5726
URL: https://issues.apache.org/jira/browse/GEODE-5726
Project: Geode
Issue Type: Improvement
Reporter: Dan Smith
This test failed in multiple CI runs recently.
https://concourse.apachegeode-ci.info/teams/main/pipelines/concourse-staging/jobs/DistributedTest/builds/96
http://files.apachegeode-ci.info/builds/1.8.0-build.1/test-results/distributedTest/1536506408/
{noformat}
org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDistributedTest
>
testReplicatedSerialAsyncEventQueueWithPersistenceEnabled_Restart[dispatcherThreadCount=1]
FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDistributedTest$$Lambda$132/352914586.run
in VM 0 running on Host 58887cf96a8a with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
at
org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDistributedTest.testReplicatedSerialAsyncEventQueueWithPersistenceEnabled_Restart(AsyncEventListenerDistributedTest.java:283)
Caused by:
org.awaitility.core.ConditionTimeoutException: Assertion condition
defined as a lambda expression in
org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventListenerDistributedTest
Expected size:<1000> but was:<900> in:
<{100=100, 101=101, 102=102, 103=103, 104=104, 105=105, 106=106,
107=107, 108=108, 109=109, 110=110, 111=111, 112=112, 113=113, 114=114,
115=115, 116=116, 117=117, 118=118, 119=119, 120=120, 121=121, 122=122,
123=123, 124=124, 125=125, 126=126, 127=127, 128=128, 129=129, 130=130,
131=131, 132=132, 133=133, 134=134, 135=135, 136=136, 137=137, 138=138,
139=139, 140=140, 141=141, 142=142, 143=143, 144=144, 145=145, 146=146,
147=147, 148=148, 149=149, 150=150, 151=151, 152=152, 153=153, 154=154,
155=155, 156=156, 157=157, 158=158, 159=159, 160=160, 161=161, 162=162,
163=163, 164=164, 165=165, 166=166, 167=167, 168=168, 169=169, 170=170,
171=171, 172=172, 173=173, 174=174, 175=175, 176=176, 177=177, 178=178,
179=179, 180=180, 181=181, 182=182, 183=183, 184=184, 185=185, 186=186,
187=187, 188=188, 189=189, 190=190, 191=191, 192=192, 193=193, 194=194,
195=195, 196=196, 197=197, 198=198, 199=199, 200=200, 201=201, 202=202,
203=203, 204=204, 205=205, 206=206, 207=207, 208=208, 209=209, 210=210,
211=211, 212=212, 213=213, 214=214, 215=215, 216=216, 217=217, 218=218,
219=219, 220=220, 221=221, 222=222, 223=223, 224=224, 225=225, 226=226,
227=227, 228=228, 229=229, 230=230, 231=231, 232=232, 233=233, 234=234,
235=235, 236=236, 237=237, 238=238, 239=239, 240=240, 241=241, 242=242,
243=243, 244=244, 245=245, 246=246, 247=247, 248=248, 249=249, 250=250,
251=251, 252=252, 253=253, 254=254, 255=255, 256=256, 257=257, 258=258,
259=259, 260=260, 261=261, 262=262, 263=263, 264=264, 265=265, 266=266,
267=267, 268=268, 269=269, 270=270, 271=271, 272=272, 273=273, 274=274,
275=275, 276=276, 277=277, 278=278, 279=279, 280=280, 281=281, 282=282,
283=283, 284=284, 285=285, 286=286, 287=287, 288=288, 289=289, 290=290,
291=291, 292=292, 293=293, 294=294, 295=295, 296=296, 297=297, 298=298,
299=299, 300=300, 301=301, 302=302, 303=303, 304=304, 305=305, 306=306,
307=307, 308=308, 309=309, 310=310, 311=311, 312=312, 313=313, 314=314,
315=315, 316=316, 317=317, 318=318, 319=319, 320=320, 321=321, 322=322,
323=323, 324=324, 325=325, 326=326, 327=327, 328=328, 329=329, 330=330,
331=331, 332=332, 333=333, 334=334, 335=335, 336=336, 337=337, 338=338,
339=339, 340=340, 341=341, 342=342, 343=343, 344=344, 345=345, 346=346,
347=347, 348=348, 349=349, 350=350, 351=351, 352=352, 353=353, 354=354,
355=355, 356=356, 357=357, 358=358, 359=359, 360=360, 361=361, 362=362,
363=363, 364=364, 365=365, 366=366, 367=367, 368=368, 369=369, 370=370,
371=371, 372=372, 373=373, 374=374, 375=375, 376=376, 377=377, 378=378,
379=379, 380=380, 381=381, 382=382, 383=383, 384=384, 385=385, 386=386,
387=387, 388=388, 389=389, 390=390, 391=391, 392=392, 393=393, 394=394,
395=395, 396=396, 397=397, 398=398, 399=399, 400=400, 401=401, 402=402,
403=403, 404=404, 405=405, 406=406, 407=407, 408=408, 409=409, 410=410,
411=411, 412=412, 413=413, 414=414, 415=415, 416=416, 417=417, 418=418,
419=419, 420=420, 421=421, 422=422, 423=423, 424=424, 425=425, 426=426,
427=427, 428=428, 429=429, 430=430, 431=431, 432=432, 433=433, 434=434,
435=435, 436=436, 437=437, 438=438, 439=439, 440=440, 441=441, 442=442,
443=443, 444=444, 445=445, 446=446, 447=447, 448=448,
[jira] [Created] (GEODE-5727) Export cluster-configuration does not work filename only
Bradford D. Boyle created GEODE-5727:
Summary: Export cluster-configuration does not work filename only
Key: GEODE-5727
URL: https://issues.apache.org/jira/browse/GEODE-5727
Project: Geode
Issue Type: Bug
Components: gfsh
Reporter: Bradford D. Boyle
Fix For: 1.7.0
Using the latest Geode snapshot (aaac1e5cefe6ad7ca533a7ca87eef9dd779912e4),
exporting cluster config with only a filename (no path) results in an error:
{code}
gfsh> start locator
gfsh> start server
gfsh> create region --name=test --type=PARTITION
gfsh> export cluster-configuration --zip-file-name=cluster-config.zip
Could not process command due to error. null
{code}
It does (sort of) work if you use a path:
{code}
gfsh> start locator
gfsh> start server
gfsh> create region --name=test --type=PARTITION
gfsh> export cluster-configuration --zip-file-name=./cluster-config.zip
{code}
However, it appears that the cluster config file is written to both the
specified path and the current working directory.
{code}
gfsh > export cluster-configuration --zip-file-name=/tmp/cluster-config.zip
{code}
{code}
$ md5 /tmp/cluster-config.zip cluster-config.zip
MD5 (/tmp/cluster-config.zip) = 50022493fa54f54da700adfc1a8f709c
MD5 (cluster-config.zip) = 50022493fa54f54da700adfc1a8f709c
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5728) Suspect string (NullPointerException) found in LocatorDUnitTest.testStartTwoLocators
Kenneth Howe created GEODE-5728:
---
Summary: Suspect string (NullPointerException) found in
LocatorDUnitTest.testStartTwoLocators
Key: GEODE-5728
URL: https://issues.apache.org/jira/browse/GEODE-5728
Project: Geode
Issue Type: Bug
Components: swat
Reporter: Kenneth Howe
DistributedTest failure in
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/379
{code}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1241
[fatal 2018/09/11 00:04:32.409 UTC tid=0x676]
Exception in processing request from 172.17.0.20
java.lang.NullPointerException
at
org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.processFindCoordinatorRequest(GMSLocator.java:309)
at
org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.processRequest(GMSLocator.java:205)
at
org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1194)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.processOneConnection(TcpServer.java:484)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:378)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
The test doesn't have a history of (flaky) failures that I've discovered, and I
haven't gotten it to fail locally.
The NPE comes from a null return from {{v.getCoordinator()}}.
{code}
synchronized (registrants) {
if (isCoordinator) {
coordinator = localAddress;
if (v != null && !v.getCoordinator().equals(localAddress)) {
logger.info("This member is becoming coordinator since view {}", v);
v = null;
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5728) Suspect string (NullPointerException) found in LocatorDUnitTest.testStartTwoLocators
[
https://issues.apache.org/jira/browse/GEODE-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Howe updated GEODE-5728:
Component/s: membership
> Suspect string (NullPointerException) found in
> LocatorDUnitTest.testStartTwoLocators
>
>
> Key: GEODE-5728
> URL: https://issues.apache.org/jira/browse/GEODE-5728
> Project: Geode
> Issue Type: Bug
> Components: membership, swat
>Reporter: Kenneth Howe
>Priority: Major
>
> DistributedTest failure in
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/379
> {code}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1241
> [fatal 2018/09/11 00:04:32.409 UTC tid=0x676]
> Exception in processing request from 172.17.0.20
> java.lang.NullPointerException
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.processFindCoordinatorRequest(GMSLocator.java:309)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.processRequest(GMSLocator.java:205)
> at
> org.apache.geode.distributed.internal.InternalLocator$PrimaryHandler.processRequest(InternalLocator.java:1194)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.processOneConnection(TcpServer.java:484)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:378)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> The test doesn't have a history of (flaky) failures that I've discovered, and
> I haven't gotten it to fail locally.
> The NPE comes from a null return from {{v.getCoordinator()}}.
> {code}
> synchronized (registrants) {
> if (isCoordinator) {
> coordinator = localAddress;
> if (v != null && !v.getCoordinator().equals(localAddress)) {
> logger.info("This member is becoming coordinator since view {}", v);
> v = null;
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5709) Create pipeline job to build windows image
[ https://issues.apache.org/jira/browse/GEODE-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611205#comment-16611205 ] ASF subversion and git services commented on GEODE-5709: Commit fe4afe393ff2bfbecf1f6a02b0082df8541675c0 in geode's branch refs/heads/develop from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fe4afe3 ] GEODE-5709: Avoid interactive prompting > Create pipeline job to build windows image > -- > > Key: GEODE-5709 > URL: https://issues.apache.org/jira/browse/GEODE-5709 > Project: Geode > Issue Type: Task > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (GEODE-5501) CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates
[
https://issues.apache.org/jira/browse/GEODE-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Helena Bales updated GEODE-5501:
Comment: was deleted
(was:
{code:java}
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest$14.run in VM 0
running on Host 33a3f4695006 with 4 VMs at
org.apache.geode.test.dunit.VM.invoke(VM.java:450) at
org.apache.geode.test.dunit.VM.invoke(VM.java:419) at
org.apache.geode.test.dunit.VM.invoke(VM.java:362) at
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.createReplicate(NetSearchMessagingDUnitTest.java:425)
at
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.testOneMessageWithReplicates(NetSearchMessagingDUnitTest.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at
org.junit.rules.RunRules.evaluate(RunRules.java:20) at
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:155)
at
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:137)
at
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at
java.util.concurren
[jira] [Commented] (GEODE-5501) CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates
[
https://issues.apache.org/jira/browse/GEODE-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611284#comment-16611284
]
Helena Bales commented on GEODE-5501:
-
{code:java}
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest$14.run in VM 0
running on Host 33a3f4695006 with 4 VMs at
org.apache.geode.test.dunit.VM.invoke(VM.java:450) at
org.apache.geode.test.dunit.VM.invoke(VM.java:419) at
org.apache.geode.test.dunit.VM.invoke(VM.java:362) at
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.createReplicate(NetSearchMessagingDUnitTest.java:425)
at
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.testOneMessageWithReplicates(NetSearchMessagingDUnitTest.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at
org.junit.rules.RunRules.evaluate(RunRules.java:20) at
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at
org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:155)
at
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:137)
at
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46
[jira] [Created] (GEODE-5729) when DistributedCacheOperation needs 2 messages, should let the notifyOnly message to trigger callback
xiaojian zhou created GEODE-5729: Summary: when DistributedCacheOperation needs 2 messages, should let the notifyOnly message to trigger callback Key: GEODE-5729 URL: https://issues.apache.org/jira/browse/GEODE-5729 Project: Geode Issue Type: Bug Reporter: xiaojian zhou When one of the secondary bucket is still initializing (in middle of GII), the primary member call adviseRequiresTwoMessages() will return not null, i.e. PutAll will send both PutAllMessage and PutAllPRMessage(notifyOnly==true) to that member. Then it might cause to send the same event 2 times to the secondary serial gateway queue. There's race that the primary serial gateway queue finished processing the event before one of (or all of) the 2 duplicated events at secondary serial gateway queue, the one was enqueued after the processing primary event will be replayed. When considering the fix, we have to keep the twoMessage design, and we cannot guarantee that when the PutAllPRMessage(notifyOnly==true) is sent, the secondary bucket will be ready. I find a work around: The reason we need to send both PutAllMessage and PutAllPRMessage to the member is: we need the PutAllMessage to do apply distribution if region is ready, and also trigger call back if region is ready. But the PutAllPRMessage will trigger callbacks anyway even region is not ready So when I detect there're overlap in the 2 sets of recipients, I can set event to be inhibitAllNotifications for PutAllMessage to let it only apply distribution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5729) when DistributedCacheOperation needs 2 messages, should let the notifyOnly message to trigger callback
[ https://issues.apache.org/jira/browse/GEODE-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiaojian zhou reassigned GEODE-5729: Assignee: xiaojian zhou > when DistributedCacheOperation needs 2 messages, should let the notifyOnly > message to trigger callback > -- > > Key: GEODE-5729 > URL: https://issues.apache.org/jira/browse/GEODE-5729 > Project: Geode > Issue Type: Bug >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > > When one of the secondary bucket is still initializing (in middle of GII), > the primary member call adviseRequiresTwoMessages() will return not null, > i.e. PutAll will send both PutAllMessage and > PutAllPRMessage(notifyOnly==true) to that member. > Then it might cause to send the same event 2 times to the secondary serial > gateway queue. There's race that the primary serial gateway queue finished > processing the event before one of (or all of) the 2 duplicated events at > secondary serial gateway queue, the one was enqueued after the processing > primary event will be replayed. > When considering the fix, we have to keep the twoMessage design, and we > cannot guarantee that when the PutAllPRMessage(notifyOnly==true) is sent, the > secondary bucket will be ready. > I find a work around: > The reason we need to send both PutAllMessage and PutAllPRMessage to the > member is: we need the PutAllMessage to do apply distribution if region is > ready, and also trigger call back if region is ready. But the PutAllPRMessage > will trigger callbacks anyway even region is not ready > So when I detect there're overlap in the 2 sets of recipients, I can set > event to be inhibitAllNotifications for PutAllMessage to let it only apply > distribution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5729) when DistributedCacheOperation needs 2 messages, should let the notifyOnly message to trigger callback
[ https://issues.apache.org/jira/browse/GEODE-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611333#comment-16611333 ] xiaojian zhou commented on GEODE-5729: -- Another issue is: CacheOperationMessage's toData() will pack bits via computeCompressedShort(bits), pack extendedBits via computeCompressedExtBits(extendedBits), which will save inhibitAllNotifications. But computeCompressedShort() also saved inhibitAllNotifications, which will be interpreted as hasDelta() if it's set. > when DistributedCacheOperation needs 2 messages, should let the notifyOnly > message to trigger callback > -- > > Key: GEODE-5729 > URL: https://issues.apache.org/jira/browse/GEODE-5729 > Project: Geode > Issue Type: Bug >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > > When one of the secondary bucket is still initializing (in middle of GII), > the primary member call adviseRequiresTwoMessages() will return not null, > i.e. PutAll will send both PutAllMessage and > PutAllPRMessage(notifyOnly==true) to that member. > Then it might cause to send the same event 2 times to the secondary serial > gateway queue. There's race that the primary serial gateway queue finished > processing the event before one of (or all of) the 2 duplicated events at > secondary serial gateway queue, the one was enqueued after the processing > primary event will be replayed. > When considering the fix, we have to keep the twoMessage design, and we > cannot guarantee that when the PutAllPRMessage(notifyOnly==true) is sent, the > secondary bucket will be ready. > I find a work around: > The reason we need to send both PutAllMessage and PutAllPRMessage to the > member is: we need the PutAllMessage to do apply distribution if region is > ready, and also trigger call back if region is ready. But the PutAllPRMessage > will trigger callbacks anyway even region is not ready > So when I detect there're overlap in the 2 sets of recipients, I can set > event to be inhibitAllNotifications for PutAllMessage to let it only apply > distribution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5501) CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates
[
https://issues.apache.org/jira/browse/GEODE-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Helena Bales reassigned GEODE-5501:
---
Assignee: Helena Bales
> CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates
>
>
> Key: GEODE-5501
> URL: https://issues.apache.org/jira/browse/GEODE-5501
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Helena Bales
>Priority: Major
> Labels: swat
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.NetSearchMessagingDUnitTest$14.run in VM 0
> running on Host 4fad81dffa5f with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
> at
> org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.createReplicate(NetSearchMessagingDUnitTest.java:425)
> at
> org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.testOneMessageWithReplicates(NetSearchMessagingDUnitTest.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy1.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at ja
[jira] [Commented] (GEODE-5723) Only publish maven artifacts for SNAPSHOT versions.
[ https://issues.apache.org/jira/browse/GEODE-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611356#comment-16611356 ] ASF subversion and git services commented on GEODE-5723: Commit 4e099fe1ab6fbe09973e2387b3e751949c9260ac in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e099fe ] GEODE-5723: Don't publish to maven repo unless SNAPSHOT. (#2453) Co-authored-by: Dick Cavender Co-authored-by: Jacob Barrett > Only publish maven artifacts for SNAPSHOT versions. > --- > > Key: GEODE-5723 > URL: https://issues.apache.org/jira/browse/GEODE-5723 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5723) Only publish maven artifacts for SNAPSHOT versions.
[ https://issues.apache.org/jira/browse/GEODE-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611358#comment-16611358 ] ASF subversion and git services commented on GEODE-5723: Commit c637193aa61abdfd236ae36b6d9a228fc1e84bcd in geode's branch refs/heads/release/1.7.0 from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c637193 ] GEODE-5723: Don't publish to maven repo unless SNAPSHOT. (#2453) Co-authored-by: Dick Cavender Co-authored-by: Jacob Barrett > Only publish maven artifacts for SNAPSHOT versions. > --- > > Key: GEODE-5723 > URL: https://issues.apache.org/jira/browse/GEODE-5723 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5729) when DistributedCacheOperation needs 2 messages, should let the notifyOnly message to trigger callback
[ https://issues.apache.org/jira/browse/GEODE-5729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5729: -- Labels: pull-request-available (was: ) > when DistributedCacheOperation needs 2 messages, should let the notifyOnly > message to trigger callback > -- > > Key: GEODE-5729 > URL: https://issues.apache.org/jira/browse/GEODE-5729 > Project: Geode > Issue Type: Bug >Reporter: xiaojian zhou >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > > When one of the secondary bucket is still initializing (in middle of GII), > the primary member call adviseRequiresTwoMessages() will return not null, > i.e. PutAll will send both PutAllMessage and > PutAllPRMessage(notifyOnly==true) to that member. > Then it might cause to send the same event 2 times to the secondary serial > gateway queue. There's race that the primary serial gateway queue finished > processing the event before one of (or all of) the 2 duplicated events at > secondary serial gateway queue, the one was enqueued after the processing > primary event will be replayed. > When considering the fix, we have to keep the twoMessage design, and we > cannot guarantee that when the PutAllPRMessage(notifyOnly==true) is sent, the > secondary bucket will be ready. > I find a work around: > The reason we need to send both PutAllMessage and PutAllPRMessage to the > member is: we need the PutAllMessage to do apply distribution if region is > ready, and also trigger call back if region is ready. But the PutAllPRMessage > will trigger callbacks anyway even region is not ready > So when I detect there're overlap in the 2 sets of recipients, I can set > event to be inhibitAllNotifications for PutAllMessage to let it only apply > distribution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5698) Fix google-readability-redundant-smartptr-get
[ https://issues.apache.org/jira/browse/GEODE-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5698: -- Labels: pull-request-available (was: ) > Fix google-readability-redundant-smartptr-get > - > > Key: GEODE-5698 > URL: https://issues.apache.org/jira/browse/GEODE-5698 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5707) Tx in permanent illegal state, not cleaned.
[ https://issues.apache.org/jira/browse/GEODE-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611377#comment-16611377 ] Jacob S. Barrett commented on GEODE-5707: - [~vaijira] awesome test! What SHA of the source were you able to reproduce this issue on? I'd like to make certain the "fix" was intentional. ;) > Tx in permanent illegal state, not cleaned. > --- > > Key: GEODE-5707 > URL: https://issues.apache.org/jira/browse/GEODE-5707 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jorge Perez Burgos >Priority: Major > Labels: pull-request-available > Attachments: > fix-tx-clean-geode-21224839d03aa9a9c502bbfab0bf40d1c9bd5ae9.patch > > Time Spent: 20m > Remaining Estimate: 0h > > The c++ native client doesn't clean the tx properly in partitioned regions > when an error happens. You can reproduce this forcing a > commitconflictexception and after that the every following tx you try to do > in the client fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4881) handle concurrent lucene indexing (after region created) with rebalance
[
https://issues.apache.org/jira/browse/GEODE-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun updated GEODE-4881:
---
Issue Type: Sub-task (was: New Feature)
Parent: GEODE-3924
> handle concurrent lucene indexing (after region created) with rebalance
> ---
>
> Key: GEODE-4881
> URL: https://issues.apache.org/jira/browse/GEODE-4881
> Project: Geode
> Issue Type: Sub-task
> Components: lucene
>Reporter: Shelley Lynn Hughes-Godfrey
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> {noformat}
> While adding a Lucene index to a region with data, if a rebalance is
> triggered during re-indexing, the index should complete successfully and
> match the region data.
> If I add a Lucene index while a rebalance is in progress, the index should
> successfully complete and match the region data. (*)
> (*) Note: It may be acceptable to detect a rebalance in progress before
> starting and wait for it to finish before adding the Lucene index.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5709) Create pipeline job to build windows image
[ https://issues.apache.org/jira/browse/GEODE-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611401#comment-16611401 ] ASF subversion and git services commented on GEODE-5709: Commit 8661b1e0347cbd4574fbb26c8e0999a646b4bd7f in geode's branch refs/heads/feature/Micrometer from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8661b1e ] GEODE-5709: Use external IP for winrm packer communication > Create pipeline job to build windows image > -- > > Key: GEODE-5709 > URL: https://issues.apache.org/jira/browse/GEODE-5709 > Project: Geode > Issue Type: Task > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5716) Improve GfshRule to allow easy debugging of the processes started
[ https://issues.apache.org/jira/browse/GEODE-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611400#comment-16611400 ] ASF subversion and git services commented on GEODE-5716: Commit b9587c24f3a3097e811b0072d7586aaa8c39 in geode's branch refs/heads/feature/Micrometer from jinmeiliao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b9587c2 ] GEODE-5716: add debug capability to the processes started using GfshRule (#2446) > Improve GfshRule to allow easy debugging of the processes started > - > > Key: GEODE-5716 > URL: https://issues.apache.org/jira/browse/GEODE-5716 > Project: Geode > Issue Type: Improvement > Components: configuration >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently GfshRule started processes for gfsh and locator/servers started, > it's hard to debug into these processes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5694) Remove zip distribution
[ https://issues.apache.org/jira/browse/GEODE-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611402#comment-16611402 ] ASF subversion and git services commented on GEODE-5694: Commit 518717a50a404642b28751fbbaeb4438111c169a in geode's branch refs/heads/feature/Micrometer from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=518717a ] GEODE-5694 Do not create or publish zip distributions (#2424) * Zip archive is removed from publication list. * Geode uses the maven-publish plugin which has better control of publication tasks. Prefer using it instead. * Fully disable distZip and distSrcZip, even when specified on commandline Co-Authored-by: Sean Goller Co-Authored-by: Robert Houghton > Remove zip distribution > --- > > Key: GEODE-5694 > URL: https://issues.apache.org/jira/browse/GEODE-5694 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > This causes build times to be longer than necessary, and produces a redundant > artifact. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5697) SingleThreadJTAExecutor.cleanup method should ignore exception thrown during cache close
[
https://issues.apache.org/jira/browse/GEODE-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611399#comment-16611399
]
ASF subversion and git services commented on GEODE-5697:
Commit 7f605494e4cfe87c168215bb54ffaeb9c2fe9503 in geode's branch
refs/heads/feature/Micrometer from pivotal-eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7f60549 ]
GEODE-5697: Handle CacheClosedException when performing beforeCompletion and
afterCompletion. (#2448)
> SingleThreadJTAExecutor.cleanup method should ignore exception thrown during
> cache close
>
>
> Key: GEODE-5697
> URL: https://issues.apache.org/jira/browse/GEODE-5697
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.7.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following exception cause some of the TXState is not being cleaned up due
> to the following exception.
> {noformat}
> org.apache.geode.cache.CacheClosedException: The cache is closed.
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:1563)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.AfterCompletion.waitForCondition(AfterCompletion.java:65)
> at
> org.apache.geode.internal.cache.AfterCompletion.waitUntilFinished(AfterCompletion.java:89)
> at
> org.apache.geode.internal.cache.AfterCompletion.signalAndWaitForDoOp(AfterCompletion.java:82)
> at
> org.apache.geode.internal.cache.AfterCompletion.cancel(AfterCompletion.java:94)
> at
> org.apache.geode.internal.cache.SingleThreadJTAExecutor.cleanup(SingleThreadJTAExecutor.java:65)
> at org.apache.geode.internal.cache.TXState.cleanup(TXState.java:875)
> at org.apache.geode.internal.cache.TXState.close(TXState.java:863)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.close(TXStateProxyImpl.java:925)
> at
> org.apache.geode.internal.cache.TXManagerImpl.close(TXManagerImpl.java:663)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2408)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1372)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1022)
> at hydra.RemoteTestModule$3.run(RemoteTestModule.java:416)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5723) Only publish maven artifacts for SNAPSHOT versions.
[ https://issues.apache.org/jira/browse/GEODE-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611404#comment-16611404 ] ASF subversion and git services commented on GEODE-5723: Commit 4e099fe1ab6fbe09973e2387b3e751949c9260ac in geode's branch refs/heads/feature/Micrometer from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e099fe ] GEODE-5723: Don't publish to maven repo unless SNAPSHOT. (#2453) Co-authored-by: Dick Cavender Co-authored-by: Jacob Barrett > Only publish maven artifacts for SNAPSHOT versions. > --- > > Key: GEODE-5723 > URL: https://issues.apache.org/jira/browse/GEODE-5723 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5709) Create pipeline job to build windows image
[ https://issues.apache.org/jira/browse/GEODE-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611403#comment-16611403 ] ASF subversion and git services commented on GEODE-5709: Commit fe4afe393ff2bfbecf1f6a02b0082df8541675c0 in geode's branch refs/heads/feature/Micrometer from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fe4afe3 ] GEODE-5709: Avoid interactive prompting > Create pipeline job to build windows image > -- > > Key: GEODE-5709 > URL: https://issues.apache.org/jira/browse/GEODE-5709 > Project: Geode > Issue Type: Task > Components: build >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5698) Fix google-readability-redundant-smartptr-get
[ https://issues.apache.org/jira/browse/GEODE-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett reassigned GEODE-5698: --- Assignee: Jacob S. Barrett > Fix google-readability-redundant-smartptr-get > - > > Key: GEODE-5698 > URL: https://issues.apache.org/jira/browse/GEODE-5698 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5730) Fix google-explicit-constructor clang-tidy warning
Jacob S. Barrett created GEODE-5730: --- Summary: Fix google-explicit-constructor clang-tidy warning Key: GEODE-5730 URL: https://issues.apache.org/jira/browse/GEODE-5730 Project: Geode Issue Type: Sub-task Components: native client Reporter: Jacob S. Barrett -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5691) Fix google-build-using-namespace clang-tidy warning
[ https://issues.apache.org/jira/browse/GEODE-5691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-5691. - Resolution: Fixed > Fix google-build-using-namespace clang-tidy warning > --- > > Key: GEODE-5691 > URL: https://issues.apache.org/jira/browse/GEODE-5691 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Fix `google-build-using-namespace` warning from `clang-tidy`. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5730) Fix google-explicit-constructor clang-tidy warning
[ https://issues.apache.org/jira/browse/GEODE-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett reassigned GEODE-5730: --- Assignee: Jacob S. Barrett > Fix google-explicit-constructor clang-tidy warning > -- > > Key: GEODE-5730 > URL: https://issues.apache.org/jira/browse/GEODE-5730 > Project: Geode > Issue Type: Sub-task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5707) Tx in permanent illegal state, not cleaned.
[ https://issues.apache.org/jira/browse/GEODE-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611626#comment-16611626 ] Jorge Perez Burgos commented on GEODE-5707: --- It happens in premodernization release code, when adapting to latest driver code i thought the problem was still there but it seems it doesnt. BR > Tx in permanent illegal state, not cleaned. > --- > > Key: GEODE-5707 > URL: https://issues.apache.org/jira/browse/GEODE-5707 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Jorge Perez Burgos >Priority: Major > Labels: pull-request-available > Attachments: > fix-tx-clean-geode-21224839d03aa9a9c502bbfab0bf40d1c9bd5ae9.patch > > Time Spent: 20m > Remaining Estimate: 0h > > The c++ native client doesn't clean the tx properly in partitioned regions > when an error happens. You can reproduce this forcing a > commitconflictexception and after that the every following tx you try to do > in the client fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
