[jira] [Resolved] (GEODE-5771) Geode should not allow user to configure pdx persistence on a client
[ https://issues.apache.org/jira/browse/GEODE-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan José Ramos Cassella resolved GEODE-5771. - Resolution: Fixed Fix Version/s: 1.8.0 Merged into develop through commit [fbb132f|https://github.com/apache/geode/commit/fbb132f227e81fa8aa79367d0394098eb967359d]. > Geode should not allow user to configure pdx persistence on a client > > > Key: GEODE-5771 > URL: https://issues.apache.org/jira/browse/GEODE-5771 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Juan José Ramos Cassella >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Geode currently does not support persistence of PDX data on the client side. > This is to avoid dealing with issues that might arise if the client's PDX > data is inconsistent with the server side. > However, the client side API and XSD still allow the user to set pdx to be > persistent. It appears that this setting is simply ignored: > See ClientCacheFactory.setPdxPersistent and cache-1.0.xsd (the client-cache > element embeds a pdx element which has a persistence flag. > These methods should be deprecated or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5771) Geode should not allow user to configure pdx persistence on a client
[ https://issues.apache.org/jira/browse/GEODE-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631578#comment-16631578 ] ASF subversion and git services commented on GEODE-5771: Commit fbb132f227e81fa8aa79367d0394098eb967359d in geode's branch refs/heads/develop from Juan José Ramos [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fbb132f ] Merge pull request #2515 from jujoramos/feature/GEODE-5771 GEODE-5771: Deprecate PDX Persistence on Client Currently, even when set, the PDX metadata is not persisted on the client side (to avoid dealing with problems that might arise if the client's PDX data is inconsistent with the server). - Methods `setPdxPersistent` and `setPdxDiskStore` from `ClientCacheFactory` have been deprecated. - Attributes `persistent` and `disk-store-name` from the element `pdx` have been deprecated (new complex type `client-pdx-type` has been added to avoid messing with the pdx definition used for non-clients). - A `warning` message will now be logged when creating the cache if we detect that PDX persistence has been configured for a client cache. - Added test methods to `ClientCacheFactoryJUnitTest`, also replaced the usage of `junit.Assert` by `assertj`, and manual file manipulation/cleanup by `TemporaryFolder` rule. > Geode should not allow user to configure pdx persistence on a client > > > Key: GEODE-5771 > URL: https://issues.apache.org/jira/browse/GEODE-5771 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Juan José Ramos Cassella >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Geode currently does not support persistence of PDX data on the client side. > This is to avoid dealing with issues that might arise if the client's PDX > data is inconsistent with the server side. > However, the client side API and XSD still allow the user to set pdx to be > persistent. It appears that this setting is simply ignored: > See ClientCacheFactory.setPdxPersistent and cache-1.0.xsd (the client-cache > element embeds a pdx element which has a persistence flag. > These methods should be deprecated or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5771) Geode should not allow user to configure pdx persistence on a client
[ https://issues.apache.org/jira/browse/GEODE-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631577#comment-16631577 ] ASF subversion and git services commented on GEODE-5771: Commit fbb132f227e81fa8aa79367d0394098eb967359d in geode's branch refs/heads/develop from Juan José Ramos [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fbb132f ] Merge pull request #2515 from jujoramos/feature/GEODE-5771 GEODE-5771: Deprecate PDX Persistence on Client Currently, even when set, the PDX metadata is not persisted on the client side (to avoid dealing with problems that might arise if the client's PDX data is inconsistent with the server). - Methods `setPdxPersistent` and `setPdxDiskStore` from `ClientCacheFactory` have been deprecated. - Attributes `persistent` and `disk-store-name` from the element `pdx` have been deprecated (new complex type `client-pdx-type` has been added to avoid messing with the pdx definition used for non-clients). - A `warning` message will now be logged when creating the cache if we detect that PDX persistence has been configured for a client cache. - Added test methods to `ClientCacheFactoryJUnitTest`, also replaced the usage of `junit.Assert` by `assertj`, and manual file manipulation/cleanup by `TemporaryFolder` rule. > Geode should not allow user to configure pdx persistence on a client > > > Key: GEODE-5771 > URL: https://issues.apache.org/jira/browse/GEODE-5771 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Juan José Ramos Cassella >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Geode currently does not support persistence of PDX data on the client side. > This is to avoid dealing with issues that might arise if the client's PDX > data is inconsistent with the server side. > However, the client side API and XSD still allow the user to set pdx to be > persistent. It appears that this setting is simply ignored: > See ClientCacheFactory.setPdxPersistent and cache-1.0.xsd (the client-cache > element embeds a pdx element which has a persistence flag. > These methods should be deprecated or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5771) Geode should not allow user to configure pdx persistence on a client
[ https://issues.apache.org/jira/browse/GEODE-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631576#comment-16631576 ] ASF subversion and git services commented on GEODE-5771: Commit 1cb5fe5ae460c72ab7e9fda3d9ed22fd2d3d3768 in geode's branch refs/heads/develop from Juan Jose Ramos Cassella [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1cb5fe5 ] GEODE-5771: Deprecate PDX Persistence on Client Currently, even when set, the PDX metadata is not persisted on the client side (to avoid dealing with problems that might arise if the client's PDX data is inconsistent with the server). - Methods `setPdxPersistent` and `setPdxDiskStore` from `ClientCacheFactory` have been deprecated. - Attributes `persistent` and `disk-store-name` from the element `pdx` have been deprecated (new complex type `client-pdx-type` has been added to avoid messing with the pdx definition used for non-clients). - A `warning` message will now be logged when creating the cache if we detect that PDX persistence has been configured for a client cache. - Added test methods to `ClientCacheFactoryJUnitTest`, also replaced the usage of `junit.Assert` by `assertj`, and manual file manipulation/cleanup by `TemporaryFolder` rule. > Geode should not allow user to configure pdx persistence on a client > > > Key: GEODE-5771 > URL: https://issues.apache.org/jira/browse/GEODE-5771 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Juan José Ramos Cassella >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Geode currently does not support persistence of PDX data on the client side. > This is to avoid dealing with issues that might arise if the client's PDX > data is inconsistent with the server side. > However, the client side API and XSD still allow the user to set pdx to be > persistent. It appears that this setting is simply ignored: > See ClientCacheFactory.setPdxPersistent and cache-1.0.xsd (the client-cache > element embeds a pdx element which has a persistence flag. > These methods should be deprecated or removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5794) windows - failing JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainLocatorAndCrashServer
[ https://issues.apache.org/jira/browse/GEODE-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631931#comment-16631931 ] ASF subversion and git services commented on GEODE-5794: Commit 6c08f91e4a17ecfc779c5c231cfcf98a70726b6f in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6c08f91 ] GEODE-5794: ignore JMXMBeanRecommentDUnitTest on windows (#2530) These tests are failing and causing CI job to hang. So ignoring them until they are fixed. > windows - failing > JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainLocatorAndCrashServer > -- > > Key: GEODE-5794 > URL: https://issues.apache.org/jira/browse/GEODE-5794 > Project: Geode > Issue Type: Bug > Components: ci >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] [Created] (GEODE-5795) User Guide built from sources has incorrect Geode version string
Dave Barnes created GEODE-5795: -- Summary: User Guide built from sources has incorrect Geode version string Key: GEODE-5795 URL: https://issues.apache.org/jira/browse/GEODE-5795 Project: Geode Issue Type: Bug Components: docs Reporter: Dave Barnes The config files for the v1.7 user guide source build, /geode-book/config.sys and ../redirects.rb, specify the Geode version as 1.8. The build succeeds, but the version number in the text and in the URLs appears as 1.8. Workaround: Before generating the user guide, edit config.sys and redirects.rb, changing "1.8" and "18" to "1.7" and "17", respectively. Real solution: Replace the two config files in the source distribution with corrected ones. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5795) User Guide built from sources has incorrect Geode version string
[ https://issues.apache.org/jira/browse/GEODE-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-5795: --- Priority: Minor (was: Major) > User Guide built from sources has incorrect Geode version string > > > Key: GEODE-5795 > URL: https://issues.apache.org/jira/browse/GEODE-5795 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Priority: Minor > > The config files for the v1.7 user guide source build, > /geode-book/config.sys and ../redirects.rb, specify the Geode > version as 1.8. > The build succeeds, but the version number in the text and in the URLs > appears as 1.8. > Workaround: Before generating the user guide, edit config.sys and > redirects.rb, changing "1.8" and "18" to "1.7" and "17", respectively. > Real solution: Replace the two config files in the source distribution with > corrected ones. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5795) User Guide built from sources has incorrect Geode version string
[ https://issues.apache.org/jira/browse/GEODE-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes reassigned GEODE-5795: -- Assignee: Dave Barnes > User Guide built from sources has incorrect Geode version string > > > Key: GEODE-5795 > URL: https://issues.apache.org/jira/browse/GEODE-5795 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > The config files for the v1.7 user guide source build, > /geode-book/config.sys and ../redirects.rb, specify the Geode > version as 1.8. > The build succeeds, but the version number in the text and in the URLs > appears as 1.8. > Workaround: Before generating the user guide, edit config.sys and > redirects.rb, changing "1.8" and "18" to "1.7" and "17", respectively. > Real solution: Replace the two config files in the source distribution with > corrected ones. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5795) User Guide built from sources has incorrect Geode version string
[ https://issues.apache.org/jira/browse/GEODE-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632105#comment-16632105 ] Dave Barnes commented on GEODE-5795: Pull request submitted as a placeholder, just in case there's a new version of 1.7.x in the future. > User Guide built from sources has incorrect Geode version string > > > Key: GEODE-5795 > URL: https://issues.apache.org/jira/browse/GEODE-5795 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > The config files for the v1.7 user guide source build, > /geode-book/config.sys and ../redirects.rb, specify the Geode > version as 1.8. > The build succeeds, but the version number in the text and in the URLs > appears as 1.8. > Workaround: Before generating the user guide, edit config.sys and > redirects.rb, changing "1.8" and "18" to "1.7" and "17", respectively. > Real solution: Replace the two config files in the source distribution with > corrected ones. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-5795) User Guide built from sources has incorrect Geode version string
[ https://issues.apache.org/jira/browse/GEODE-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632105#comment-16632105 ] Dave Barnes edited comment on GEODE-5795 at 9/28/18 4:38 PM: - Pull request submitted as a placeholder, to be left in place in case we generate a new release of 1.7.x in the future. If v1.8 comes out before v1.7 is re-issued, this ticket becomes irrelevant and can be dismissed as "will not fix". was (Author: dbarnes97): Pull request submitted as a placeholder, just in case there's a new version of 1.7.x in the future. > User Guide built from sources has incorrect Geode version string > > > Key: GEODE-5795 > URL: https://issues.apache.org/jira/browse/GEODE-5795 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > The config files for the v1.7 user guide source build, > /geode-book/config.sys and ../redirects.rb, specify the Geode > version as 1.8. > The build succeeds, but the version number in the text and in the URLs > appears as 1.8. > Workaround: Before generating the user guide, edit config.sys and > redirects.rb, changing "1.8" and "18" to "1.7" and "17", respectively. > Real solution: Replace the two config files in the source distribution with > corrected ones. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (GEODE-5795) User Guide built from sources has incorrect Geode version string
[ https://issues.apache.org/jira/browse/GEODE-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632105#comment-16632105 ] Dave Barnes edited comment on GEODE-5795 at 9/28/18 4:40 PM: - Pull request submitted as a placeholder, to be left in place in case we generate a new release of 1.7.x in the future. If v1.8 comes out before v1.7 is re-issued, this ticket becomes irrelevant and can be dismissed as "won't fix". was (Author: dbarnes97): Pull request submitted as a placeholder, to be left in place in case we generate a new release of 1.7.x in the future. If v1.8 comes out before v1.7 is re-issued, this ticket becomes irrelevant and can be dismissed as "will not fix". > User Guide built from sources has incorrect Geode version string > > > Key: GEODE-5795 > URL: https://issues.apache.org/jira/browse/GEODE-5795 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Minor > > The config files for the v1.7 user guide source build, > /geode-book/config.sys and ../redirects.rb, specify the Geode > version as 1.8. > The build succeeds, but the version number in the text and in the URLs > appears as 1.8. > Workaround: Before generating the user guide, edit config.sys and > redirects.rb, changing "1.8" and "18" to "1.7" and "17", respectively. > Real solution: Replace the two config files in the source distribution with > corrected ones. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5796) Build scripts removes out scripts from the ci folder.
nabarun created GEODE-5796:
--
Summary: Build scripts removes out scripts from the ci folder.
Key: GEODE-5796
URL: https://issues.apache.org/jira/browse/GEODE-5796
Project: Geode
Issue Type: Bug
Components: ci
Reporter: nabarun
*+Issue+*:
In geode-assemble/build.gradle we ignore
{code:java}
**/out/**{code}
in the source distribution creation. However, in ci project, we need scripts
named out.sh which cannot be renamed as these are required parameters for
Concourse. So, in the release process, these scripts are left out and we have a
source file difference the git branch and the source distribution.
The out.sh files are located in
{code:java}
ci/resource-types/gce-instances-resource/out
ci/resource-types/concourse-metadata-resource/files/out
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5796) Build scripts removes out scripts from the ci folder.
[
https://issues.apache.org/jira/browse/GEODE-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun reassigned GEODE-5796:
--
Assignee: Dick Cavender (was: nabarun)
> Build scripts removes out scripts from the ci folder.
> -
>
> Key: GEODE-5796
> URL: https://issues.apache.org/jira/browse/GEODE-5796
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: nabarun
>Assignee: Dick Cavender
>Priority: Major
>
> *+Issue+*:
> In geode-assemble/build.gradle we ignore
> {code:java}
> **/out/**{code}
> in the source distribution creation. However, in ci project, we need scripts
> named out.sh which cannot be renamed as these are required parameters for
> Concourse. So, in the release process, these scripts are left out and we have
> a source file difference the git branch and the source distribution.
> The out.sh files are located in
>
> {code:java}
> ci/resource-types/gce-instances-resource/out
> ci/resource-types/concourse-metadata-resource/files/out
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5796) Build scripts removes out scripts from the ci folder.
[
https://issues.apache.org/jira/browse/GEODE-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun reassigned GEODE-5796:
--
Assignee: nabarun
> Build scripts removes out scripts from the ci folder.
> -
>
> Key: GEODE-5796
> URL: https://issues.apache.org/jira/browse/GEODE-5796
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: nabarun
>Assignee: nabarun
>Priority: Major
>
> *+Issue+*:
> In geode-assemble/build.gradle we ignore
> {code:java}
> **/out/**{code}
> in the source distribution creation. However, in ci project, we need scripts
> named out.sh which cannot be renamed as these are required parameters for
> Concourse. So, in the release process, these scripts are left out and we have
> a source file difference the git branch and the source distribution.
> The out.sh files are located in
>
> {code:java}
> ci/resource-types/gce-instances-resource/out
> ci/resource-types/concourse-metadata-resource/files/out
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5783) geode should use a single class to create instances of ThreadFactory
[ https://issues.apache.org/jira/browse/GEODE-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-5783: --- Assignee: Darrel Schneider > geode should use a single class to create instances of ThreadFactory > > > Key: GEODE-5783 > URL: https://issues.apache.org/jira/browse/GEODE-5783 > Project: Geode > Issue Type: Improvement > Components: core >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > > Geode creates a large number of ThreadFactory instances. Most of these are > created with anonymous inner classes. In most cases the ThreadFactory > instance is passed on to a thread pool. Since thread pools are finalizable > they will keep alive anything they reference until finalization takes place. > Most JVM garbage collectors delay doing finalization as long as possible. > Since an anonymous inner class always has a references to the outer class > instance, a number of places will end up having a reference to our single > GemFireCacheImpl which can end up preventing a large amount of heap from > being garbage collected. > For the above reasons, and also to avoid code duplication, it would be better > if we had a single utility class that took care of creating ThreadFactory > instances. We already have one such class in geode named GemFireCacheHelper > that is only used from one class. Also google guava has ThreadFactoryBuilder > which could be used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2644) Provide ability to configure Geode appenders in log4j2.xml
[ https://issues.apache.org/jira/browse/GEODE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632196#comment-16632196 ] ASF subversion and git services commented on GEODE-2644: Commit 8c7a7396f992d96e8086d6492e25c97c2092a3da in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8c7a739 ] GEODE-2644: Cleanup LogService (#2533) * Rename LogService getConfigInformation to getConfigurationInfo. * Rename variables, remove SuppressWarnings, remove unused code. > Provide ability to configure Geode appenders in log4j2.xml > -- > > Key: GEODE-2644 > URL: https://issues.apache.org/jira/browse/GEODE-2644 > Project: Geode > Issue Type: Improvement > Components: configuration, logging >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: AlertAppender, Log4j2, LogWriterAppender, log4j2.xml, > pull-request-available > Time Spent: 4h 20m > Remaining Estimate: 0h > > Presently Geode dynamically creates, adds and removes AlertAppender and > LogWriterAppender by manipulating log4j2 core API. We should move the bulk of > the Appender functionality to internal classes and just leave the Appenders > registered with log4j2 during the life of the JVM. > This allows us to enable and configure our Appenders via log4j2.xml and > control the Cache-controlled lifecycle internally without having to add and > remove custom Appender instances. > The code would then become simpler, we could avoid invoking log4j2 core APIs, > and users would have control over configuring our use of log4j2 completely > within the .xml file. Presently, a user cannot configure our AlertAppender or > LogWriterAppender in log4j2.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5797) CI failure: ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
[
https://issues.apache.org/jira/browse/GEODE-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Galen O'Sullivan updated GEODE-5797:
Labels: swat (was: )
> CI failure:
> ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
> -
>
> Key: GEODE-5797
> URL: https://issues.apache.org/jira/browse/GEODE-5797
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Galen O'Sullivan
>Priority: Major
> Labels: swat
>
> at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/29
> {noformat}
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> > testPartitionedParallelPropagationHA FAILED
>
> 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 5853
>
>
> [error 2018/09/28 09:42:18.421 UTC
> tid=0x692] Unexpected exception during bucket recovery
>
> java.lang.IllegalStateException: Region specified in 'colocated-with'
> (/testPartitionedParallelPropagationHA_PR) for region
> /ln_PARALLEL_GATEWAY_SENDER_QUEUE does not exist. It should be created before
> setting 'colocated-with' attribute for this region.
>
> at
> org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
>
> at
> org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
>
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:134)
>
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:114)
>
> at
> org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1587)
>
> at
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58)
>
> at
> org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:141)
>
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5797) CI failure: ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
[
https://issues.apache.org/jira/browse/GEODE-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Galen O'Sullivan updated GEODE-5797:
Component/s: wan
> CI failure:
> ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
> -
>
> Key: GEODE-5797
> URL: https://issues.apache.org/jira/browse/GEODE-5797
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Galen O'Sullivan
>Priority: Major
> Labels: swat
>
> at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/29
> {noformat}
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> > testPartitionedParallelPropagationHA FAILED
>
> 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 5853
>
>
> [error 2018/09/28 09:42:18.421 UTC
> tid=0x692] Unexpected exception during bucket recovery
>
> java.lang.IllegalStateException: Region specified in 'colocated-with'
> (/testPartitionedParallelPropagationHA_PR) for region
> /ln_PARALLEL_GATEWAY_SENDER_QUEUE does not exist. It should be created before
> setting 'colocated-with' attribute for this region.
>
> at
> org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
>
> at
> org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
>
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:134)
>
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:114)
>
> at
> org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1587)
>
> at
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58)
>
> at
> org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:141)
>
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>
> 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)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5797) CI failure: ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
Galen O'Sullivan created GEODE-5797:
---
Summary: CI failure:
ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
Key: GEODE-5797
URL: https://issues.apache.org/jira/browse/GEODE-5797
Project: Geode
Issue Type: Bug
Reporter: Galen O'Sullivan
at
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/29
{noformat}
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> testPartitionedParallelPropagationHA FAILED
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 5853
[error 2018/09/28 09:42:18.421 UTC
tid=0x692] Unexpected exception during bucket recovery
java.lang.IllegalStateException: Region specified in 'colocated-with'
(/testPartitionedParallelPropagationHA_PR) for region
/ln_PARALLEL_GATEWAY_SENDER_QUEUE does not exist. It should be created before
setting 'colocated-with' attribute for this region.
at
org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
at
org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
at
org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:134)
at
org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:114)
at
org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1587)
at
org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58)
at
org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:141)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
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)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5797) CI failure: ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
[
https://issues.apache.org/jira/browse/GEODE-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Galen O'Sullivan updated GEODE-5797:
Description:
at
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/29
artifacts at
http://files.apachegeode-ci.info/builds/1.8.0-build.1482/test-artifacts/1538129994/distributedtestfiles-1.8.0-build.1482.tgz
{noformat}
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> testPartitionedParallelPropagationHA FAILED
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 5853
[error 2018/09/28 09:42:18.421 UTC
tid=0x692] Unexpected exception during bucket recovery
java.lang.IllegalStateException: Region specified in 'colocated-with'
(/testPartitionedParallelPropagationHA_PR) for region
/ln_PARALLEL_GATEWAY_SENDER_QUEUE does not exist. It should be created before
setting 'colocated-with' attribute for this region.
at
org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
at
org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
at
org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:134)
at
org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:114)
at
org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1587)
at
org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58)
at
org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:141)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
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)
{noformat}
was:
at
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/29
{noformat}
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> testPartitionedParallelPropagationHA FAILED
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 5853
[error 2018/09/28 09:42:18.421 UTC
tid=0x692] Unexpected exception during bucket recovery
java.lang.IllegalStateException: Region specified in 'colocated-with'
(/testPartitionedParallelPropagationHA_PR) for region
/ln_PARALLEL_GATEWAY_SENDER_QUEUE does not exist. It should be created before
setting 'colocated-with' attribute for this region.
at
org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
at
org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
at
org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:134)
at
org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:114)
at
org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1587)
at
org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58)
at
org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:141)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[jira] [Commented] (GEODE-5764) CI failure: ParallelAsyncEventListenerWithOffHeapDistributedTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching[dispatcherThreadCount=3]
[
https://issues.apache.org/jira/browse/GEODE-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632208#comment-16632208
]
Galen O'Sullivan commented on GEODE-5764:
-
failed again in a slightly different test class in
https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1-7-0/jobs/DistributedTest/builds/4
> CI failure:
> ParallelAsyncEventListenerWithOffHeapDistributedTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching[dispatcherThreadCount=3]
> -
>
> Key: GEODE-5764
> URL: https://issues.apache.org/jira/browse/GEODE-5764
> Project: Geode
> Issue Type: Bug
>Reporter: Dale Emery
>Priority: Major
> Labels: swat
>
> [http://files.apachegeode-ci.info/builds/geode-pr-2461/test-results/distributedTest/1537481968/classes/org.apache.geode.internal.cache.wan.asyncqueue.ParallelAsyncEventListenerWithOffHeapDistributedTest.html#testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching[dispatcherThreadCount=3]]
>
> {code:java}
> org.junit.ComparisonFailure: expected:<...05,
> 106,
> 107[,
> 108,
> 109,
> 110,
> 111,
> 112]]> but was:<...05,
> 106,
> 107[]]>
> 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.internal.cache.wan.asyncqueue.ParallelAsyncEventListenerDistributedTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching(ParallelAsyncEventListenerDistributedTest.java:777)
> 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.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:60)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:60)
> at
> org.apache.geode.test.dunit.rules.AbstractDistributedRule$1.evaluate(AbstractDistributedRule.java:60)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> 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.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> 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.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.testi
[jira] [Assigned] (GEODE-5798) Rat should ignore bin directories created by IDE
[ https://issues.apache.org/jira/browse/GEODE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5798: Assignee: Kirk Lund > Rat should ignore bin directories created by IDE > > > Key: GEODE-5798 > URL: https://issues.apache.org/jira/browse/GEODE-5798 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Rat should ignore bin directories created by IDE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5798) Rat should ignore bin directories created by IDE
Kirk Lund created GEODE-5798: Summary: Rat should ignore bin directories created by IDE Key: GEODE-5798 URL: https://issues.apache.org/jira/browse/GEODE-5798 Project: Geode Issue Type: Bug Components: build Reporter: Kirk Lund Rat should ignore bin directories created by IDE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5798) Rat should ignore bin directories created by IDE
[ https://issues.apache.org/jira/browse/GEODE-5798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5798: -- Labels: pull-request-available (was: ) > Rat should ignore bin directories created by IDE > > > Key: GEODE-5798 > URL: https://issues.apache.org/jira/browse/GEODE-5798 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > > Rat should ignore bin directories created by IDE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2644) Provide ability to configure Geode appenders in log4j2.xml
[ https://issues.apache.org/jira/browse/GEODE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632235#comment-16632235 ] ASF subversion and git services commented on GEODE-2644: Commit 076fff86683d3f2ed14c978dd5ba4c3031ae6a64 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=076fff8 ] GEODE-2644: Improve GfshParserAutoCompletionTest assertions (#2534) Improve assertions so that failures in this test can be diagnosed without using the IDE debugger. > Provide ability to configure Geode appenders in log4j2.xml > -- > > Key: GEODE-2644 > URL: https://issues.apache.org/jira/browse/GEODE-2644 > Project: Geode > Issue Type: Improvement > Components: configuration, logging >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: AlertAppender, Log4j2, LogWriterAppender, log4j2.xml, > pull-request-available > Time Spent: 4.5h > Remaining Estimate: 0h > > Presently Geode dynamically creates, adds and removes AlertAppender and > LogWriterAppender by manipulating log4j2 core API. We should move the bulk of > the Appender functionality to internal classes and just leave the Appenders > registered with log4j2 during the life of the JVM. > This allows us to enable and configure our Appenders via log4j2.xml and > control the Cache-controlled lifecycle internally without having to add and > remove custom Appender instances. > The code would then become simpler, we could avoid invoking log4j2 core APIs, > and users would have control over configuring our use of log4j2 completely > within the .xml file. Presently, a user cannot configure our AlertAppender or > LogWriterAppender in log4j2.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2644) Provide ability to configure Geode appenders in log4j2.xml
[ https://issues.apache.org/jira/browse/GEODE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632236#comment-16632236 ] ASF subversion and git services commented on GEODE-2644: Commit 65725eb7e466be85260b215cf3a0917f931a21c5 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=65725eb ] GEODE-2644: Cleanup logging tests (#2519) > Provide ability to configure Geode appenders in log4j2.xml > -- > > Key: GEODE-2644 > URL: https://issues.apache.org/jira/browse/GEODE-2644 > Project: Geode > Issue Type: Improvement > Components: configuration, logging >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: AlertAppender, Log4j2, LogWriterAppender, log4j2.xml, > pull-request-available > Time Spent: 4h 40m > Remaining Estimate: 0h > > Presently Geode dynamically creates, adds and removes AlertAppender and > LogWriterAppender by manipulating log4j2 core API. We should move the bulk of > the Appender functionality to internal classes and just leave the Appenders > registered with log4j2 during the life of the JVM. > This allows us to enable and configure our Appenders via log4j2.xml and > control the Cache-controlled lifecycle internally without having to add and > remove custom Appender instances. > The code would then become simpler, we could avoid invoking log4j2 core APIs, > and users would have control over configuring our use of log4j2 completely > within the .xml file. Presently, a user cannot configure our AlertAppender or > LogWriterAppender in log4j2.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2644) Provide ability to configure Geode appenders in log4j2.xml
[ https://issues.apache.org/jira/browse/GEODE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632238#comment-16632238 ] ASF subversion and git services commented on GEODE-2644: Commit 78c4aac8dc18e43f26b14013e106e2c8a7b4c982 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=78c4aac ] GEODE-2644: Use LINE_SEPARATOR in logging classes (#2525) Use org.apache.commons.lang.SystemUtils.LINE_SEPARATOR instead of \n. > Provide ability to configure Geode appenders in log4j2.xml > -- > > Key: GEODE-2644 > URL: https://issues.apache.org/jira/browse/GEODE-2644 > Project: Geode > Issue Type: Improvement > Components: configuration, logging >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: AlertAppender, Log4j2, LogWriterAppender, log4j2.xml, > pull-request-available > Time Spent: 4h 50m > Remaining Estimate: 0h > > Presently Geode dynamically creates, adds and removes AlertAppender and > LogWriterAppender by manipulating log4j2 core API. We should move the bulk of > the Appender functionality to internal classes and just leave the Appenders > registered with log4j2 during the life of the JVM. > This allows us to enable and configure our Appenders via log4j2.xml and > control the Cache-controlled lifecycle internally without having to add and > remove custom Appender instances. > The code would then become simpler, we could avoid invoking log4j2 core APIs, > and users would have control over configuring our use of log4j2 completely > within the .xml file. Presently, a user cannot configure our AlertAppender or > LogWriterAppender in log4j2.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5212) Many distributedTest and integrationTest failures on windows
[ https://issues.apache.org/jira/browse/GEODE-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632525#comment-16632525 ] ASF subversion and git services commented on GEODE-5212: Commit 821c8e1aced91b2b532a90433f8672be853dd84d in geode's branch refs/heads/develop from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=821c8e1 ] GEODE-5212: Also use the host's canonical (fully qualified) name as a SAN in the certificate (#2536) > Many distributedTest and integrationTest failures on windows > > > Key: GEODE-5212 > URL: https://issues.apache.org/jira/browse/GEODE-5212 > Project: Geode > Issue Type: Task > Components: general, gfsh >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available, windows > Time Spent: 9h 50m > Remaining Estimate: 0h > > Windows regressions currently fail spectacularly. The primary culprits > appear to be based around filesystem I/O and passing the current working > directory to members started by our testing framework. > > The scope of this ticket will be defined by "refactors" as children tickets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5785) Add file permissions support to LogWriter appender
[ https://issues.apache.org/jira/browse/GEODE-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-5785: - Priority: Minor (was: Major) > Add file permissions support to LogWriter appender > -- > > Key: GEODE-5785 > URL: https://issues.apache.org/jira/browse/GEODE-5785 > Project: Geode > Issue Type: New Feature > Components: logging >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > > Log4J2 FileAppender supports specifying file permissions during > configuration. It may be valuable to provide similar support for LogWriter > appender, especially the SecurityLogWriter. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5776) Console log statements show thread id in decimal format
[ https://issues.apache.org/jira/browse/GEODE-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5776. -- Resolution: Fixed Fix Version/s: 1.8.0 > Console log statements show thread id in decimal format > --- > > Key: GEODE-5776 > URL: https://issues.apache.org/jira/browse/GEODE-5776 > Project: Geode > Issue Type: Bug > Components: logging >Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, > 1.4.0, 1.5.0, 1.6.0 >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The console log statements for stdout should show thread id in hex format, > but they are now showing it in decimal format. > Geode contains ThreadIdPatternConverter which formats the tid in hex format. > Log4j2 introduced its own ThreadIdPatternConverter in 2.6 and because the > Plugin name and ConverterKeys are the same, it's now being used instead of > the one in Geode. > The fix will require us to rename our Plugin and ConverterKeys. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5799) Change log4j2.xml StatusLogger level to WARN
Kirk Lund created GEODE-5799: Summary: Change log4j2.xml StatusLogger level to WARN Key: GEODE-5799 URL: https://issues.apache.org/jira/browse/GEODE-5799 Project: Geode Issue Type: Improvement Components: logging Reporter: Kirk Lund Now that Geode is using HexThreadIdPatternConverter with unique plugin metadata, we can change the log4j2.xml configuration files in product and tests to have StatusLogger level of WARN instead of FATAL. This will allow us to see any new problems with our custom PatternConverters and Appenders earlier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5799) Change log4j2.xml StatusLogger level to WARN
[ https://issues.apache.org/jira/browse/GEODE-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5799: Assignee: Kirk Lund > Change log4j2.xml StatusLogger level to WARN > > > Key: GEODE-5799 > URL: https://issues.apache.org/jira/browse/GEODE-5799 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Now that Geode is using HexThreadIdPatternConverter with unique plugin > metadata, we can change the log4j2.xml configuration files in product and > tests to have StatusLogger level of WARN instead of FATAL. This will allow us > to see any new problems with our custom PatternConverters and Appenders > earlier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5799) Change log4j2.xml StatusLogger level to WARN
[ https://issues.apache.org/jira/browse/GEODE-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5799: -- Labels: pull-request-available (was: ) > Change log4j2.xml StatusLogger level to WARN > > > Key: GEODE-5799 > URL: https://issues.apache.org/jira/browse/GEODE-5799 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > > Now that Geode is using HexThreadIdPatternConverter with unique plugin > metadata, we can change the log4j2.xml configuration files in product and > tests to have StatusLogger level of WARN instead of FATAL. This will allow us > to see any new problems with our custom PatternConverters and Appenders > earlier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5523) Remove DefaultHashMap
[
https://issues.apache.org/jira/browse/GEODE-5523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632573#comment-16632573
]
ASF subversion and git services commented on GEODE-5523:
Commit d4d9f7f83f7ae10fb82d36eeca39b929d99d068e in geode's branch
refs/heads/develop from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d4d9f7f ]
GEODE-5523: Fixed NPE by converting remaining getOrDefault calls (#2539)
> Remove DefaultHashMap
> -
>
> Key: GEODE-5523
> URL: https://issues.apache.org/jira/browse/GEODE-5523
> Project: Geode
> Issue Type: Improvement
> Components: general, jmx, statistics
>Reporter: Juan José Ramos Cassella
>Assignee: Juan José Ramos Cassella
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The class {{MBeanStatsMonitor}} exposes the static class {{DefaultHashMap}},
> which is basically a wrapper of a simple {{java.util.Map}} that returns a
> default value ({{0}}) when the requested key doesn't exist.
> {code}
> public static class DefaultHashMap { // TODO: delete this class
> private Map internalMap = new HashMap<>();
> public DefaultHashMap() {}
> public Number get(final String key) {
> return internalMap.get(key) != null ? internalMap.get(key) : 0;
> }
> public void put(final String key, final Number value) {
> internalMap.put(key, value);
> }
> public void clear() {
> internalMap.clear();
> }
> /**
> * For testing only
> */
> Map getInternalMap() {
> return this.internalMap;
> }
> }
> {code}
> The containing class, {{MBeanStatsMonitor}}, also has a method that prevents
> {{null}} values from being returned when accessing the {{Map}}, which is
> redundant:
> {code}
> public Number getStatistic(final String statName) {
> Number value = statsMap.get(statName);
> return value != null ? value : 0;
> }
> {code}
> The class {{DefaultHashMap}} should be eliminated, and the method
> {{getStatistic}} should be refactored to use {{Map.getOrDefault(Object key, V
> defaultValue)}} instead of executing the logic manually.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5794) windows - failing JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainLocatorAndCrashServer
[ https://issues.apache.org/jira/browse/GEODE-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632592#comment-16632592 ] ASF subversion and git services commented on GEODE-5794: Commit 92a02d869b3d02cef3a23caca6b519a3068801ff in geode's branch refs/heads/feature/GEODE-5794-fix from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=92a02d8 ] GEODE-5794: fix failing JMXMBeanReconnectDUnitTest Signed-off-by: Jens Deppe > windows - failing > JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainLocatorAndCrashServer > -- > > Key: GEODE-5794 > URL: https://issues.apache.org/jira/browse/GEODE-5794 > Project: Geode > Issue Type: Bug > Components: ci >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] [Commented] (GEODE-5787) Support graceful bouncing DUnit VMs on windows
[ https://issues.apache.org/jira/browse/GEODE-5787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632596#comment-16632596 ] ASF subversion and git services commented on GEODE-5787: Commit 7f0c15619e71e2afc563a96be6a2dcfb268b0342 in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7f0c156 ] GEODE-5787: deleted deprecated RepeatableRunnable (#2522) > Support graceful bouncing DUnit VMs on windows > -- > > Key: GEODE-5787 > URL: https://issues.apache.org/jira/browse/GEODE-5787 > Project: Geode > Issue Type: New Feature > Components: tests >Reporter: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Process.destroy is not graceful on windows and causes distributed system to > get into suspect processing and network partition when used in DUnit to > restart VMs. > There were existing JDK > [bugs|https://bugs.openjdk.java.net/browse/JDK-8056139] open requesting for > supporting graceful destroy for Windows. > Underlying native implementation on Linux can take advantage of SIGTERM vs > SIGKILL and JDK support process.destroy and process.destroyForcibly, where as > on Windows this differentiation is not possible so its unlikely that we will > see JDK support for graceful destroy. > A better approach would be to invoke 'System.exit( n )' using VM.invoke. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5212) Many distributedTest and integrationTest failures on windows
[ https://issues.apache.org/jira/browse/GEODE-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632603#comment-16632603 ] ASF subversion and git services commented on GEODE-5212: Commit 9f083537c3cab993ecb6a36f76bff27723d740c4 in geode's branch refs/heads/develop from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9f08353 ] GEODE-5212: Make paths platform agnostic > Many distributedTest and integrationTest failures on windows > > > Key: GEODE-5212 > URL: https://issues.apache.org/jira/browse/GEODE-5212 > Project: Geode > Issue Type: Task > Components: general, gfsh >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available, windows > Time Spent: 9h 50m > Remaining Estimate: 0h > > Windows regressions currently fail spectacularly. The primary culprits > appear to be based around filesystem I/O and passing the current working > directory to members started by our testing framework. > > The scope of this ticket will be defined by "refactors" as children tickets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5776) Console log statements show thread id in decimal format
[ https://issues.apache.org/jira/browse/GEODE-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632620#comment-16632620 ] ASF subversion and git services commented on GEODE-5776: Commit 18c47cf8089f8950d5fba3fa824c4e6aefa05e66 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=18c47cf ] GEODE-5776: Use HexThreadIdPatternConverter in tests (#2541) > Console log statements show thread id in decimal format > --- > > Key: GEODE-5776 > URL: https://issues.apache.org/jira/browse/GEODE-5776 > Project: Geode > Issue Type: Bug > Components: logging >Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, > 1.4.0, 1.5.0, 1.6.0 >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The console log statements for stdout should show thread id in hex format, > but they are now showing it in decimal format. > Geode contains ThreadIdPatternConverter which formats the tid in hex format. > Log4j2 introduced its own ThreadIdPatternConverter in 2.6 and because the > Plugin name and ConverterKeys are the same, it's now being used instead of > the one in Geode. > The fix will require us to rename our Plugin and ConverterKeys. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5703) CI Failure: AlterRuntimeCommandDUnitTest > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true)
[
https://issues.apache.org/jira/browse/GEODE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632629#comment-16632629
]
Brian Rowe commented on GEODE-5703:
---
So, I've spent far too long on this for how rare the failure is and am going to
put this down to focus on more pressing issues. Some observations from my
debugging so far:
This failure seems to occur when this test (or similar tests, such as when run
as part of a full AlterRuntimeCommandDUnitTest run) is run multiple times in a
particular set of VMs. I was able to reproduce this by repeatedly running the
test in IntelliJ (took several hundred test runs), but was unable to get it to
fail in an isolated run of a single instance (with over 20,000 attempts).
The failure is due to being unable to connect to the locator, which can be seen
either when starting a server, or in the locator startup itself (when joining
the distributed system immediately after starting the locator). In the
specific case where I was able to add some additional logging and drill down
into this (which was a locator startup failure), what I specifically saw was
that the GMSMembershipManager.join got back a false when invoking
GMSJoinLeave.join. This in turn was caused by the GMSJoinLeave.findCoordinator
returning false, which was caused by
tcpClientWrapper.sendCoordinatorFindRequest throwing an IOException containing
"Unknown header byte: 0." That exception string only appears in the
InternalDataSerializer.basicReadObject, which indicates that this exception was
thrown when reading the request object, or an object nested within the request.
Either way, the server had successfully read a gossip version and object
header byte off the stream before encountering an invalid 0 byte (so the entire
stream couldn't have been corrupted). Looking through the serialization code,
there were no obvious places we could have written this incorrectly.
Because the server-side socket is visible to only a single thread (we believe),
it seems unlikely that the stream is being corrupted on the server-side (e.g.
by two server-side threads reading from the same socket concurrently). Perhaps
the client is actually writing a 0 in the wrong place? But the client too,
creates a single-use socket, visible only to one thread (we believe), so
contention there would be unlikely. That doesn't rule out simply broken
single-threaded logic.
Of course, the fact that this only shows up in repeated runs on a particular VM
suggests there's some deeper issue contributing to this as well.
> CI Failure: AlterRuntimeCommandDUnitTest >
> alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true)
>
>
> Key: GEODE-5703
> URL: https://issues.apache.org/jira/browse/GEODE-5703
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Assignee: Brian Rowe
>Priority: Major
> Labels: swat
>
> CI Failure can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/363
> Failed with Stack Trace:
> {code:java}
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest
> > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true) [0]
> FAILED
>
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/1318057984.call
> in VM 0 running on Host fca019e1fb13 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:385)
>
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:198)
>
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:191)
>
> at
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest.alterStatArchiveFileWithMember_updatesSelectedServerConfigs(AlterRuntimeCommandDUnitTest.java:466)
>
>
> Caused by:
>
> org.apache.geode.GemFireConfigException: Unable to join the
> distributed system. Operation either timed out, was stopped or Locator does
> not exist.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5703) CI Failure: AlterRuntimeCommandDUnitTest > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true)
[
https://issues.apache.org/jira/browse/GEODE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Rowe updated GEODE-5703:
--
Attachment: TestResultsPage.htm
> CI Failure: AlterRuntimeCommandDUnitTest >
> alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true)
>
>
> Key: GEODE-5703
> URL: https://issues.apache.org/jira/browse/GEODE-5703
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Assignee: Brian Rowe
>Priority: Major
> Labels: swat
> Attachments: TestResultsPage.htm
>
>
> CI Failure can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/363
> Failed with Stack Trace:
> {code:java}
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest
> > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true) [0]
> FAILED
>
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/1318057984.call
> in VM 0 running on Host fca019e1fb13 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:385)
>
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:198)
>
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:191)
>
> at
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest.alterStatArchiveFileWithMember_updatesSelectedServerConfigs(AlterRuntimeCommandDUnitTest.java:466)
>
>
> Caused by:
>
> org.apache.geode.GemFireConfigException: Unable to join the
> distributed system. Operation either timed out, was stopped or Locator does
> not exist.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5703) CI Failure: AlterRuntimeCommandDUnitTest > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true)
[
https://issues.apache.org/jira/browse/GEODE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Rowe reassigned GEODE-5703:
-
Assignee: (was: Brian Rowe)
> CI Failure: AlterRuntimeCommandDUnitTest >
> alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true)
>
>
> Key: GEODE-5703
> URL: https://issues.apache.org/jira/browse/GEODE-5703
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Priority: Major
> Labels: swat
> Attachments: TestResultsPage.htm
>
>
> CI Failure can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/363
> Failed with Stack Trace:
> {code:java}
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest
> > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true) [0]
> FAILED
>
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/1318057984.call
> in VM 0 running on Host fca019e1fb13 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:385)
>
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:198)
>
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:191)
>
> at
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest.alterStatArchiveFileWithMember_updatesSelectedServerConfigs(AlterRuntimeCommandDUnitTest.java:466)
>
>
> Caused by:
>
> org.apache.geode.GemFireConfigException: Unable to join the
> distributed system. Operation either timed out, was stopped or Locator does
> not exist.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5703) CI Failure: AlterRuntimeCommandDUnitTest > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true)
[
https://issues.apache.org/jira/browse/GEODE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632634#comment-16632634
]
Brian Rowe commented on GEODE-5703:
---
Also, uploading the test results page linked from the course run in the
description, as that run is longer available.
> CI Failure: AlterRuntimeCommandDUnitTest >
> alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true)
>
>
> Key: GEODE-5703
> URL: https://issues.apache.org/jira/browse/GEODE-5703
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Assignee: Brian Rowe
>Priority: Major
> Labels: swat
> Attachments: TestResultsPage.htm
>
>
> CI Failure can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/363
> Failed with Stack Trace:
> {code:java}
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest
> > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true) [0]
> FAILED
>
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/1318057984.call
> in VM 0 running on Host fca019e1fb13 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:385)
>
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:198)
>
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:191)
>
> at
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest.alterStatArchiveFileWithMember_updatesSelectedServerConfigs(AlterRuntimeCommandDUnitTest.java:466)
>
>
> Caused by:
>
> org.apache.geode.GemFireConfigException: Unable to join the
> distributed system. Operation either timed out, was stopped or Locator does
> not exist.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5787) Support graceful bouncing DUnit VMs on windows
[ https://issues.apache.org/jira/browse/GEODE-5787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632642#comment-16632642 ] ASF subversion and git services commented on GEODE-5787: Commit 239bc29c2b995860be0bfa242d87905e6920a84a in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=239bc29 ] GEODE-5787: delete unused LocalVM (#2521) > Support graceful bouncing DUnit VMs on windows > -- > > Key: GEODE-5787 > URL: https://issues.apache.org/jira/browse/GEODE-5787 > Project: Geode > Issue Type: New Feature > Components: tests >Reporter: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Process.destroy is not graceful on windows and causes distributed system to > get into suspect processing and network partition when used in DUnit to > restart VMs. > There were existing JDK > [bugs|https://bugs.openjdk.java.net/browse/JDK-8056139] open requesting for > supporting graceful destroy for Windows. > Underlying native implementation on Linux can take advantage of SIGTERM vs > SIGKILL and JDK support process.destroy and process.destroyForcibly, where as > on Windows this differentiation is not possible so its unlikely that we will > see JDK support for graceful destroy. > A better approach would be to invoke 'System.exit( n )' using VM.invoke. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
