[jira] [Updated] (GEODE-5918) Geode function security should be dynamically determined by function arguments
[
https://issues.apache.org/jira/browse/GEODE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ivorzhou updated GEODE-5918:
Issue Type: Improvement (was: New Feature)
> Geode function security should be dynamically determined by function arguments
> --
>
> Key: GEODE-5918
> URL: https://issues.apache.org/jira/browse/GEODE-5918
> Project: Geode
> Issue Type: Improvement
> Components: functions, security
>Reporter: ivorzhou
>Priority: Critical
>
> Now in Function interface there is a method
> default Collection getRequiredPermissions(String
> regionName) {
> return Collections.singletonList(ResourcePermissions.DATA_WRITE);
> }
>
> Which only support statically security determination in design
> time(regionName is not enough).
> In some situation,we require determining security on function arguments.
>
> I think add a method in this interface like
> default Collection getRequiredPermissions(String
> regionName,Object args) {
> return getRequiredPermissions(regionName);
> }
>
> and in server side command,call the new method with regionName and arguments
> together.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5918) Geode function security should be dynamically determined by function arguments
[
https://issues.apache.org/jira/browse/GEODE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ivorzhou updated GEODE-5918:
Issue Type: New Feature (was: Improvement)
> Geode function security should be dynamically determined by function arguments
> --
>
> Key: GEODE-5918
> URL: https://issues.apache.org/jira/browse/GEODE-5918
> Project: Geode
> Issue Type: New Feature
> Components: functions, security
>Reporter: ivorzhou
>Priority: Critical
>
> Now in Function interface there is a method
> default Collection getRequiredPermissions(String
> regionName) {
> return Collections.singletonList(ResourcePermissions.DATA_WRITE);
> }
>
> Which only support statically security determination in design
> time(regionName is not enough).
> In some situation,we require determining security on function arguments.
>
> I think add a method in this interface like
> default Collection getRequiredPermissions(String
> regionName,Object args) {
> return getRequiredPermissions(regionName);
> }
>
> and in server side command,call the new method with regionName and arguments
> together.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5919) Fix Documentation Bugs in Native Client public APIs
Michael Martell created GEODE-5919: -- Summary: Fix Documentation Bugs in Native Client public APIs Key: GEODE-5919 URL: https://issues.apache.org/jira/browse/GEODE-5919 Project: Geode Issue Type: Bug Components: native client Reporter: Michael Martell This ticket is to fix documentation bugs in the cppcache portion of the native client API. Specifically, comments for the following classes need to be fixed. apache::geode::client::CacheableUndefined (uncommented) apache::geode::client::CacheTransactionManager (uncommented) apache::geode::client::PdxSerializable (uncommented) apache::geode::client::TypeRegistry (uncommented) apache::geode::client::CacheableEnum (comment in wrong place, not picked up) apache::geode::client::CacheableObjectArray (comment in wrong place, not picked up) apache::geode::client::CacheableFileName (comment in wrong place, not picked up) apache::geode::client::Delta (comment in wrong place, not picked up) apache::geode::client::EntryEvent (comment in wrong place, not picked up) apache::geode::client::AuthenticatedView (wrong comment, called Cache class) DataSerializableFixedId_t (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializableInternal (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializablePrimitive (uncommented, but is exported, but is internal so maybe shouldn't be exported) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5919) Fix Documentation Bugs in Geode Native public APIs
[ https://issues.apache.org/jira/browse/GEODE-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-5919: --- Description: This ticket is to fix documentation bugs in the cppcache portion of the geode native API. Specifically, comments for the following classes need to be fixed. These are doxygen fixes. apache::geode::client::CacheableUndefined (uncommented) apache::geode::client::CacheTransactionManager (uncommented) apache::geode::client::PdxSerializable (uncommented) apache::geode::client::TypeRegistry (uncommented) apache::geode::client::CacheableEnum (comment in wrong place, not picked up) apache::geode::client::CacheableObjectArray (comment in wrong place, not picked up) apache::geode::client::CacheableFileName (comment in wrong place, not picked up) apache::geode::client::Delta (comment in wrong place, not picked up) apache::geode::client::EntryEvent (comment in wrong place, not picked up) apache::geode::client::AuthenticatedView (wrong comment, called Cache class) DataSerializableFixedId_t (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializableInternal (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializablePrimitive (uncommented, but is exported, but is internal so maybe shouldn't be exported) was: This ticket is to fix documentation bugs in the cppcache portion of the native client API. Specifically, comments for the following classes need to be fixed. apache::geode::client::CacheableUndefined (uncommented) apache::geode::client::CacheTransactionManager (uncommented) apache::geode::client::PdxSerializable (uncommented) apache::geode::client::TypeRegistry (uncommented) apache::geode::client::CacheableEnum (comment in wrong place, not picked up) apache::geode::client::CacheableObjectArray (comment in wrong place, not picked up) apache::geode::client::CacheableFileName (comment in wrong place, not picked up) apache::geode::client::Delta (comment in wrong place, not picked up) apache::geode::client::EntryEvent (comment in wrong place, not picked up) apache::geode::client::AuthenticatedView (wrong comment, called Cache class) DataSerializableFixedId_t (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializableInternal (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializablePrimitive (uncommented, but is exported, but is internal so maybe shouldn't be exported) > Fix Documentation Bugs in Geode Native public APIs > -- > > Key: GEODE-5919 > URL: https://issues.apache.org/jira/browse/GEODE-5919 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > > This ticket is to fix documentation bugs in the cppcache portion of the geode > native API. Specifically, comments for the following classes need to be > fixed. These are doxygen fixes. > apache::geode::client::CacheableUndefined (uncommented) > apache::geode::client::CacheTransactionManager (uncommented) > apache::geode::client::PdxSerializable (uncommented) > apache::geode::client::TypeRegistry (uncommented) > apache::geode::client::CacheableEnum (comment in wrong place, not picked up) > apache::geode::client::CacheableObjectArray (comment in wrong place, not > picked up) > apache::geode::client::CacheableFileName (comment in wrong place, not picked > up) > apache::geode::client::Delta (comment in wrong place, not picked up) > apache::geode::client::EntryEvent (comment in wrong place, not picked up) > apache::geode::client::AuthenticatedView (wrong comment, called Cache class) > DataSerializableFixedId_t (uncommented, but is exported, but is internal so > maybe shouldn't be exported) > DataSerializableInternal (uncommented, but is exported, but is internal so > maybe shouldn't be exported) > DataSerializablePrimitive (uncommented, but is exported, but is internal so > maybe shouldn't be exported) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5919) Fix Documentation Bugs in Geode Native public APIs
[ https://issues.apache.org/jira/browse/GEODE-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison updated GEODE-5919: --- Summary: Fix Documentation Bugs in Geode Native public APIs (was: Fix Documentation Bugs in Native Client public APIs) > Fix Documentation Bugs in Geode Native public APIs > -- > > Key: GEODE-5919 > URL: https://issues.apache.org/jira/browse/GEODE-5919 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > > This ticket is to fix documentation bugs in the cppcache portion of the > native client API. Specifically, comments for the following classes need to > be fixed. > apache::geode::client::CacheableUndefined (uncommented) > apache::geode::client::CacheTransactionManager (uncommented) > apache::geode::client::PdxSerializable (uncommented) > apache::geode::client::TypeRegistry (uncommented) > apache::geode::client::CacheableEnum (comment in wrong place, not picked up) > apache::geode::client::CacheableObjectArray (comment in wrong place, not > picked up) > apache::geode::client::CacheableFileName (comment in wrong place, not picked > up) > apache::geode::client::Delta (comment in wrong place, not picked up) > apache::geode::client::EntryEvent (comment in wrong place, not picked up) > apache::geode::client::AuthenticatedView (wrong comment, called Cache class) > DataSerializableFixedId_t (uncommented, but is exported, but is internal so > maybe shouldn't be exported) > DataSerializableInternal (uncommented, but is exported, but is internal so > maybe shouldn't be exported) > DataSerializablePrimitive (uncommented, but is exported, but is internal so > maybe shouldn't be exported) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3506) LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails intermittently with IllegalStateException: Failed to read status file
[
https://issues.apache.org/jira/browse/GEODE-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662518#comment-16662518
]
Darrel Schneider commented on GEODE-3506:
-
Saw this today which seems related:
org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest >
startDeletesStaleControlFiles FAILED
[ |https://concourse.apachegeode-ci.info/builds/8557#L5bcbc7f3:665]
java.lang.IllegalStateException: Status file
'/tmp/junit1574730945400887391/vf.gf.locator.status' is blank
> LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails
> intermittently with IllegalStateException: Failed to read status file
> --
>
> Key: GEODE-3506
> URL: https://issues.apache.org/jira/browse/GEODE-3506
> Project: Geode
> Issue Type: Bug
> Components: gfsh, management
>Reporter: Kirk Lund
>Priority: Major
> Labels: CI
>
> {noformat}
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest >
> startDeletesStaleControlFiles FAILED
> java.lang.IllegalStateException: Failed to read status file
> {noformat}
> Full stack trace:
> {noformat}
> java.lang.IllegalStateException: Failed to read status file
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at
> org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:940)
> at
> org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:868)
> at
> org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(LocatorLauncherRemoteIntegrationTestCase.java:196)
> at
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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] [Comment Edited] (GEODE-3506) LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails intermittently with IllegalStateException: Failed to read status file
[
https://issues.apache.org/jira/browse/GEODE-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662518#comment-16662518
]
Darrel Schneider edited comment on GEODE-3506 at 10/24/18 4:43 PM:
---
Saw this today which seems related:
org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest >
startDeletesStaleControlFiles FAILED
[ |https://concourse.apachegeode-ci.info/builds/8557#L5bcbc7f3:665]
java.lang.IllegalStateException: Status file
'/tmp/junit1574730945400887391/vf.gf.locator.status' is blank
In this pull request run: https://concourse.apachegeode-ci.info/builds/8557
was (Author: dschneider):
Saw this today which seems related:
org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest >
startDeletesStaleControlFiles FAILED
[ |https://concourse.apachegeode-ci.info/builds/8557#L5bcbc7f3:665]
java.lang.IllegalStateException: Status file
'/tmp/junit1574730945400887391/vf.gf.locator.status' is blank
> LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails
> intermittently with IllegalStateException: Failed to read status file
> --
>
> Key: GEODE-3506
> URL: https://issues.apache.org/jira/browse/GEODE-3506
> Project: Geode
> Issue Type: Bug
> Components: gfsh, management
>Reporter: Kirk Lund
>Priority: Major
> Labels: CI
>
> {noformat}
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest >
> startDeletesStaleControlFiles FAILED
> java.lang.IllegalStateException: Failed to read status file
> {noformat}
> Full stack trace:
> {noformat}
> java.lang.IllegalStateException: Failed to read status file
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at
> org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:940)
> at
> org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:868)
> at
> org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(LocatorLauncherRemoteIntegrationTestCase.java:196)
> at
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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] [Resolved] (GEODE-2606) Source distribution needs missing files
[
https://issues.apache.org/jira/browse/GEODE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Addison resolved GEODE-2606.
Resolution: Fixed
> Source distribution needs missing files
> ---
>
> Key: GEODE-2606
> URL: https://issues.apache.org/jira/browse/GEODE-2606
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
>
> The source distribution generated by
> {{cpack --config CPackSourceConfig.cmake}}
> only includes files from the {{src}} directory. It should include all files
> from the root directory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GEODE-2606) Source distribution needs missing files
[
https://issues.apache.org/jira/browse/GEODE-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Addison closed GEODE-2606.
--
> Source distribution needs missing files
> ---
>
> Key: GEODE-2606
> URL: https://issues.apache.org/jira/browse/GEODE-2606
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
>
> The source distribution generated by
> {{cpack --config CPackSourceConfig.cmake}}
> only includes files from the {{src}} directory. It should include all files
> from the root directory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5841) Update the versions of tomcat that are tested and supported.
[ https://issues.apache.org/jira/browse/GEODE-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662567#comment-16662567 ] ASF subversion and git services commented on GEODE-5841: Commit 0c082e598c0bce260993e690cda77adb647ec0d6 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0c082e5 ] GEODE-5841: Adding Tomcat 9 support * GEODE-5841: Adding Tomcat 9 support Adding a separate tomcat-9 module and testing that session replication works with tomcat 9. Deprecating Tomcat 6 support. > Update the versions of tomcat that are tested and supported. > > > Key: GEODE-5841 > URL: https://issues.apache.org/jira/browse/GEODE-5841 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Tomcat 6 has been in end of life since 2016. We should deprecate > Tomcat6DeltaSessionManager and plan on removing that in a later release. > Tomcat 9 has been out for a year. We should add tests that use Tomcat 9 and > start supporting that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5841) Update the versions of tomcat that are tested and supported.
[ https://issues.apache.org/jira/browse/GEODE-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662568#comment-16662568 ] ASF subversion and git services commented on GEODE-5841: Commit 0c082e598c0bce260993e690cda77adb647ec0d6 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0c082e5 ] GEODE-5841: Adding Tomcat 9 support * GEODE-5841: Adding Tomcat 9 support Adding a separate tomcat-9 module and testing that session replication works with tomcat 9. Deprecating Tomcat 6 support. > Update the versions of tomcat that are tested and supported. > > > Key: GEODE-5841 > URL: https://issues.apache.org/jira/browse/GEODE-5841 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Tomcat 6 has been in end of life since 2016. We should deprecate > Tomcat6DeltaSessionManager and plan on removing that in a later release. > Tomcat 9 has been out for a year. We should add tests that use Tomcat 9 and > start supporting that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5841) Update the versions of tomcat that are tested and supported.
[ https://issues.apache.org/jira/browse/GEODE-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5841. -- Resolution: Fixed Fix Version/s: 1.8.0 > Update the versions of tomcat that are tested and supported. > > > Key: GEODE-5841 > URL: https://issues.apache.org/jira/browse/GEODE-5841 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Tomcat 6 has been in end of life since 2016. We should deprecate > Tomcat6DeltaSessionManager and plan on removing that in a later release. > Tomcat 9 has been out for a year. We should add tests that use Tomcat 9 and > start supporting that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2607) Improve release artifacts
[
https://issues.apache.org/jira/browse/GEODE-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender resolved GEODE-2607.
-
Resolution: Fixed
> Improve release artifacts
> -
>
> Key: GEODE-2607
> URL: https://issues.apache.org/jira/browse/GEODE-2607
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
>
> The geode-native release artifacts for the source and binary distributions
> should include:
> - archive
> - SHA-256 hash
> - GPG signatures for archive
> In addition, the top-level directory in the archives should include the
> version (e.g. {{apache-geode-native-1.2.0-source}}.
> The process for generating the release artifacts should be documented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-2607) Improve release artifacts
[
https://issues.apache.org/jira/browse/GEODE-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662572#comment-16662572
]
Blake Bender commented on GEODE-2607:
-
We don't currently generate the GPG signature file, but this can be done
manually. The SHA512 is now generated alongside build artifacts via cpack.
> Improve release artifacts
> -
>
> Key: GEODE-2607
> URL: https://issues.apache.org/jira/browse/GEODE-2607
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
>
> The geode-native release artifacts for the source and binary distributions
> should include:
> - archive
> - SHA-256 hash
> - GPG signatures for archive
> In addition, the top-level directory in the archives should include the
> version (e.g. {{apache-geode-native-1.2.0-source}}.
> The process for generating the release artifacts should be documented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GEODE-2607) Improve release artifacts
[
https://issues.apache.org/jira/browse/GEODE-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender closed GEODE-2607.
---
> Improve release artifacts
> -
>
> Key: GEODE-2607
> URL: https://issues.apache.org/jira/browse/GEODE-2607
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
>
> The geode-native release artifacts for the source and binary distributions
> should include:
> - archive
> - SHA-256 hash
> - GPG signatures for archive
> In addition, the top-level directory in the archives should include the
> version (e.g. {{apache-geode-native-1.2.0-source}}.
> The process for generating the release artifacts should be documented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-2608) Source release should not require git repo
[
https://issues.apache.org/jira/browse/GEODE-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662573#comment-16662573
]
Blake Bender commented on GEODE-2608:
-
Yep, this was fixed some time ago and the associated Jira item was not updated.
> Source release should not require git repo
> --
>
> Key: GEODE-2608
> URL: https://issues.apache.org/jira/browse/GEODE-2608
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
>
> The source archive for geode-native requires a git repo (see
> {{src/cppcache/src/version.cmake.in}}). That will not be present for a
> source release, see [1].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-2608) Source release should not require git repo
[
https://issues.apache.org/jira/browse/GEODE-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender resolved GEODE-2608.
-
Resolution: Fixed
> Source release should not require git repo
> --
>
> Key: GEODE-2608
> URL: https://issues.apache.org/jira/browse/GEODE-2608
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
>
> The source archive for geode-native requires a git repo (see
> {{src/cppcache/src/version.cmake.in}}). That will not be present for a
> source release, see [1].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (GEODE-2608) Source release should not require git repo
[
https://issues.apache.org/jira/browse/GEODE-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender closed GEODE-2608.
---
> Source release should not require git repo
> --
>
> Key: GEODE-2608
> URL: https://issues.apache.org/jira/browse/GEODE-2608
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
>
> The source archive for geode-native requires a git repo (see
> {{src/cppcache/src/version.cmake.in}}). That will not be present for a
> source release, see [1].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5251) Parameterize assembly info
[
https://issues.apache.org/jira/browse/GEODE-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-5251:
-
Issue Type: Improvement (was: Sub-task)
Parent: (was: GEODE-1416)
> Parameterize assembly info
> --
>
> Key: GEODE-5251
> URL: https://issues.apache.org/jira/browse/GEODE-5251
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Anthony Baker
>Priority: Major
>
> Some of the fields in
> {{[clicache/src/impl/AssemblyInfo.cpp.in|https://github.com/apache/geode-native/pull/297/files/aa52e2fa7969ee7082794940530e45ee1042366a#diff-2ba30c65953794a80be3c9f17447aed8]}}
> should be filled in by CMake vars when creating the assembly. See PR #297.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5920) Security Service documentation should indicate reliance Cluster Configuration Service
Patrick Rhomberg created GEODE-5920:
---
Summary: Security Service documentation should indicate reliance
Cluster Configuration Service
Key: GEODE-5920
URL: https://issues.apache.org/jira/browse/GEODE-5920
Project: Geode
Issue Type: Improvement
Components: docs, security
Reporter: Patrick Rhomberg
In the documentation pace [Enable Security with Property
Definitions|http://geode.apache.org/docs/guide/17/managing/security/enable_security.html],
we indicate
{noformat}
If you must specify the security-manager property for servers (neither
necessary nor recommended) make sure its value is exactly identical to that
specified for the first locator.
{noformat}
I believe this is only accurate while the Cluster Configuration Service is
active. While use of this service is highly recommended elsewhere, it should
be clarified and/or reiterated here to avoid any possible confusion,
particularly given the paramount importance of security.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5911) Improve SSL warning to indicate specific to GEODE; reference related property
[
https://issues.apache.org/jira/browse/GEODE-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662614#comment-16662614
]
ASF subversion and git services commented on GEODE-5911:
Commit de2aed4a8032fc0e0bc1f8399ce985fae7e3cb85 in geode's branch
refs/heads/develop from ladyVader
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=de2aed4 ]
GEODE-5911: Improve SSL warning to indicate specific to GEODE; reference
related property
* Added Apache GEODE to SSL hostname validation warning
* Added ssl-endpoint-identification-enabled property to same
> Improve SSL warning to indicate specific to GEODE; reference related property
> -
>
> Key: GEODE-5911
> URL: https://issues.apache.org/jira/browse/GEODE-5911
> Project: Geode
> Issue Type: Bug
> Components: security
>Affects Versions: 1.8.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We currently log this warning in the system log if
> ssl-endpoint-identification-enabled
> {noformat}
> Your SSL configuration disables hostname validation. Future releases will
> mandate hostname validation.
> {noformat}
> This can be mis-interpreted as a JVM warning, so updating the message to show
> it is Apache GEODE related ... and include the property to enable hostname
> validation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5921) Update URL for schema
Ernest Burghardt created GEODE-5921: --- Summary: Update URL for schema Key: GEODE-5921 URL: https://issues.apache.org/jira/browse/GEODE-5921 Project: Geode Issue Type: Task Components: native client Reporter: Ernest Burghardt current schema file is found at: http://geode.apache.org/schema/cpp-cache/cpp-cache-1.0.xsd -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5819) Handshake fails on Java11
[
https://issues.apache.org/jira/browse/GEODE-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662651#comment-16662651
]
ASF subversion and git services commented on GEODE-5819:
Commit a1bbe9074b05a9945e2f8cc4e7c915bd13bc8c02 in geode's branch
refs/heads/develop from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a1bbe90 ]
GEODE-5819: use cipher suites supported across jdk versions (#2677)
> Handshake fails on Java11
> -
>
> Key: GEODE-5819
> URL: https://issues.apache.org/jira/browse/GEODE-5819
> Project: Geode
> Issue Type: Sub-task
>Reporter: Jinmei Liao
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> *
> [RestAPIsWithSSLDUnitTest|http://files.apachegeode-ci.info/builds/1.8.0-build.5/test-results/distributedTest/1538508591/classes/org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.html].
>
> [testSSLWithMultipleCipherSuite|http://files.apachegeode-ci.info/builds/1.8.0-build.5/test-results/distributedTest/1538508591/classes/org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.html#testSSLWithMultipleCipherSuite]
> *
> [RestAPIsWithSSLDUnitTest|http://files.apachegeode-ci.info/builds/1.8.0-build.5/test-results/distributedTest/1538508591/classes/org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.html].
>
> [testSSLWithMultipleCipherSuiteLegacy|http://files.apachegeode-ci.info/builds/1.8.0-build.5/test-results/distributedTest/1538508591/classes/org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.html#testSSLWithMultipleCipherSuiteLegacy]
> {noformat}
> java.lang.RuntimeException: unexpected exception
> at
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.validateConnection(RestAPIsWithSSLDUnitTest.java:512)
> at
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithMultipleCipherSuite(RestAPIsWithSSLDUnitTest.java:701)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 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
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:6
[jira] [Resolved] (GEODE-5907) better fix for windows
[ https://issues.apache.org/jira/browse/GEODE-5907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-5907. - Resolution: Fixed Fix Version/s: 1.8.0 > better fix for windows > -- > > Key: GEODE-5907 > URL: https://issues.apache.org/jira/browse/GEODE-5907 > Project: Geode > Issue Type: Sub-task >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5915) ManagementListener.handleEvent logs a warning anytime a system Alert occurs
[
https://issues.apache.org/jira/browse/GEODE-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662728#comment-16662728
]
ASF subversion and git services commented on GEODE-5915:
Commit 1c55639a2081233e5bf0cee3c0def74ad97ccce6 in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1c55639 ]
GEODE-5915: Fix IllegalMonitorStateException logged for Alerts
* Prevent IllegalMonitorStateException in ManagementListener.
* Pass in InternalDistributedSystem to prevent singleton fetches.
* Create unit tests for ManagementListener.
> ManagementListener.handleEvent logs a warning anytime a system Alert occurs
> ---
>
> Key: GEODE-5915
> URL: https://issues.apache.org/jira/browse/GEODE-5915
> Project: Geode
> Issue Type: Test
> Components: management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The IllegalMonitorStateException is being thrown because the read lock is
> acquired only if the ResourceEvent type is not SYSTEM_ALERT, but the code
> tries to unlock it unconditionally:
> Lock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().lock();
> } else if (event != ResourceEvent.SYSTEM_ALERT) {
> readWriteLock.readLock().lock();
> }
> {noformat}
> Unlock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().unlock();
> } else {
> readWriteLock.readLock().unlock();
> }
> {noformat}
> {noformat}
> [vm0] [warn 2018/10/23 12:51:35.339 PDT
> tid=0x58] attempt to unlock read lock, not locked by current thread
> [vm0] java.lang.IllegalMonitorStateException: attempt to unlock read lock,
> not locked by current thread
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428)
> [vm0] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881)
> [vm0] at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:232)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2219)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:595)
> [vm0] at
> org.apache.geode.internal.admin.remote.AlertListenerMessage.process(AlertListenerMessage.java:106)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:954)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.doProcessingThread(ClusterDistributionManager.java:820)
> [vm0] at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5915) ManagementListener.handleEvent logs a warning anytime a system Alert occurs
[
https://issues.apache.org/jira/browse/GEODE-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-5915.
--
Resolution: Fixed
Fix Version/s: 1.8.0
> ManagementListener.handleEvent logs a warning anytime a system Alert occurs
> ---
>
> Key: GEODE-5915
> URL: https://issues.apache.org/jira/browse/GEODE-5915
> Project: Geode
> Issue Type: Test
> Components: management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The IllegalMonitorStateException is being thrown because the read lock is
> acquired only if the ResourceEvent type is not SYSTEM_ALERT, but the code
> tries to unlock it unconditionally:
> Lock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().lock();
> } else if (event != ResourceEvent.SYSTEM_ALERT) {
> readWriteLock.readLock().lock();
> }
> {noformat}
> Unlock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().unlock();
> } else {
> readWriteLock.readLock().unlock();
> }
> {noformat}
> {noformat}
> [vm0] [warn 2018/10/23 12:51:35.339 PDT
> tid=0x58] attempt to unlock read lock, not locked by current thread
> [vm0] java.lang.IllegalMonitorStateException: attempt to unlock read lock,
> not locked by current thread
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428)
> [vm0] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881)
> [vm0] at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:232)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2219)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:595)
> [vm0] at
> org.apache.geode.internal.admin.remote.AlertListenerMessage.process(AlertListenerMessage.java:106)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:954)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.doProcessingThread(ClusterDistributionManager.java:820)
> [vm0] at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5915) ManagementListener.handleEvent logs a warning anytime a system Alert occurs
[
https://issues.apache.org/jira/browse/GEODE-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662727#comment-16662727
]
ASF subversion and git services commented on GEODE-5915:
Commit 02d7d1b3caec51c2805a78aa814b97642061e79d in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=02d7d1b ]
GEODE-5915: Cleanup DistributedSystemDUnitTest
* Remove unnecessary this qualifiers.
* Minor whitespace changes.
> ManagementListener.handleEvent logs a warning anytime a system Alert occurs
> ---
>
> Key: GEODE-5915
> URL: https://issues.apache.org/jira/browse/GEODE-5915
> Project: Geode
> Issue Type: Test
> Components: management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The IllegalMonitorStateException is being thrown because the read lock is
> acquired only if the ResourceEvent type is not SYSTEM_ALERT, but the code
> tries to unlock it unconditionally:
> Lock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().lock();
> } else if (event != ResourceEvent.SYSTEM_ALERT) {
> readWriteLock.readLock().lock();
> }
> {noformat}
> Unlock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().unlock();
> } else {
> readWriteLock.readLock().unlock();
> }
> {noformat}
> {noformat}
> [vm0] [warn 2018/10/23 12:51:35.339 PDT
> tid=0x58] attempt to unlock read lock, not locked by current thread
> [vm0] java.lang.IllegalMonitorStateException: attempt to unlock read lock,
> not locked by current thread
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428)
> [vm0] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881)
> [vm0] at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:232)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2219)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:595)
> [vm0] at
> org.apache.geode.internal.admin.remote.AlertListenerMessage.process(AlertListenerMessage.java:106)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:954)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.doProcessingThread(ClusterDistributionManager.java:820)
> [vm0] at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5922) SerialGatewaySenderQueue concurrency is poorly implemented
Bruce Schuchardt created GEODE-5922: --- Summary: SerialGatewaySenderQueue concurrency is poorly implemented Key: GEODE-5922 URL: https://issues.apache.org/jira/browse/GEODE-5922 Project: Geode Issue Type: Improvement Components: wan Reporter: Bruce Schuchardt This class uses synchronization on the queue to limit access to one put at a time. Synchronization isn't a fair locking mechanism so threads can be blocked trying to add events to the queue while other more recent events get the lock and insert their events. This causes inconsistent latency which I've observed being as long as 30 seconds, causing client connections to be shut down by the ClientHealthMonitor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16662815#comment-16662815 ] ASF subversion and git services commented on GEODE-5783: Commit aaf1ec318ca87ed5df882885774cced6401edaa7 in geode's branch refs/heads/feature/GEODE-5783b from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=aaf1ec3 ] GEODE-5783: have a single source for ThreadFactory Use the keepalive parameter when initializing the thread factory. I also made some logging changes while debugging the problems this missing setting was causing. > 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 > Fix For: 1.8.0 > > > 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] [Updated] (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 ] ASF GitHub Bot updated GEODE-5783: -- Labels: pull-request-available (was: ) > 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 > Labels: pull-request-available > Fix For: 1.8.0 > > > 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] [Updated] (GEODE-5827) DUnit suspect string setUp is generating ERROR messages
[
https://issues.apache.org/jira/browse/GEODE-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5827:
--
Labels: pull-request-available (was: )
> DUnit suspect string setUp is generating ERROR messages
> ---
>
> Key: GEODE-5827
> URL: https://issues.apache.org/jira/browse/GEODE-5827
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Trivial
> Labels: pull-request-available
>
> The ERROR messages are generated because hexTid is a custom PatternConverter.
> DUnit is programmatically adding an Appender for suspect string detection and
> there doesn't seem to be a way to add custom PatternConverter. We'll probably
> have to use tid instead of hexTid for the suspect string detection appender.
> {noformat}
> [vm0] 2018-10-03 09:57:53,227 main ERROR Unrecognized format specifier
> [hexTid]
> [vm0] 2018-10-03 09:57:53,227 main ERROR Unrecognized conversion specifier
> [hexTid] starting at position 78 in conversion pattern.
> [vm1] 2018-10-03 09:57:53,243 main ERROR Unrecognized format specifier
> [hexTid]
> [vm1] 2018-10-03 09:57:53,243 main ERROR Unrecognized conversion specifier
> [hexTid] starting at position 78 in conversion pattern.
> [vm2] 2018-10-03 09:57:53,274 main ERROR Unrecognized format specifier
> [hexTid]
> [vm2] 2018-10-03 09:57:53,274 main ERROR Unrecognized conversion specifier
> [hexTid] starting at position 78 in conversion pattern.
> [vm3] 2018-10-03 09:57:53,274 main ERROR Unrecognized format specifier
> [hexTid]
> [vm3] 2018-10-03 09:57:53,274 main ERROR Unrecognized conversion specifier
> [hexTid] starting at position 78 in conversion pattern.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-717) CI failure: RedisDistDUnitTest.testConcCreateDestroy
[ https://issues.apache.org/jira/browse/GEODE-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662821#comment-16662821 ] Mark Hanson commented on GEODE-717: --- http://files.apachegeode-ci.info/builds/mhansonp-pipeline-main/1.8.0-build.1/test-results/distributedTest/1540408469/ > CI failure: RedisDistDUnitTest.testConcCreateDestroy > > > Key: GEODE-717 > URL: https://issues.apache.org/jira/browse/GEODE-717 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Jianxia Chen >Priority: Major > Labels: CI, Flaky, swat > > Failed 1 times in the last 30 runs. Stability: 96 % > Error Message > dunit.RMIException: While invoking > com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call in VM 1 running on Host > kuwait.gemstone.com with 4 VMs > Stacktrace > dunit.RMIException: While invoking > com.gemstone.gemfire.redis.RedisDistDUnitTest$1.call in VM 1 running on Host > kuwait.gemstone.com with 4 VMs > at dunit.VM.invoke(VM.java:369) > at dunit.VM.invoke(VM.java:312) > at dunit.VM.invoke(VM.java:280) > at > com.gemstone.gemfire.redis.RedisDistDUnitTest.setUp(RedisDistDUnitTest.java:94) > at junit.framework.TestCase.runBare(TestCase.java:139) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50) > at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.messaging.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:106) > at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54) > at > org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: Could not start Server > at > com.gemstone.gemfire.redis.GemFireRedisServer.start(GemFireRedisServer.java:387) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.startRedisServer(GemFireCacheImpl.java:1243) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.init(GemFireCacheImpl.java:1167) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:774) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:794) > at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:179) > at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:226)
[jira] [Created] (GEODE-5923) JMX manager does not receive locally generated Alerts
Kirk Lund created GEODE-5923: Summary: JMX manager does not receive locally generated Alerts Key: GEODE-5923 URL: https://issues.apache.org/jira/browse/GEODE-5923 Project: Geode Issue Type: Bug Components: management Reporter: Kirk Lund The JMX manager does not receive locally generated Alerts. It only receives remotely generated Alerts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5923) JMX manager does not receive locally generated Alerts
[ https://issues.apache.org/jira/browse/GEODE-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5923: Assignee: Kirk Lund > JMX manager does not receive locally generated Alerts > - > > Key: GEODE-5923 > URL: https://issues.apache.org/jira/browse/GEODE-5923 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > The JMX manager does not receive locally generated Alerts. It only receives > remotely generated Alerts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3506) LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails intermittently with IllegalStateException: Failed to read status file
[
https://issues.apache.org/jira/browse/GEODE-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662828#comment-16662828
]
Helena Bales commented on GEODE-3506:
-
Failed again on 'develop' CI Pipeline:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/39]
Download the log files here:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.8.0-build.40/test-results/integrationTest/1540410916/
> LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles fails
> intermittently with IllegalStateException: Failed to read status file
> --
>
> Key: GEODE-3506
> URL: https://issues.apache.org/jira/browse/GEODE-3506
> Project: Geode
> Issue Type: Bug
> Components: gfsh, management
>Reporter: Kirk Lund
>Priority: Major
> Labels: CI
>
> {noformat}
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest >
> startDeletesStaleControlFiles FAILED
> java.lang.IllegalStateException: Failed to read status file
> {noformat}
> Full stack trace:
> {noformat}
> java.lang.IllegalStateException: Failed to read status file
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at
> org.apache.geode.distributed.LocatorLauncher.statusWithWorkingDirectory(LocatorLauncher.java:940)
> at
> org.apache.geode.distributed.LocatorLauncher.status(LocatorLauncher.java:868)
> at
> org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(LocatorLauncherRemoteIntegrationTestCase.java:196)
> at
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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] [Assigned] (GEODE-5924) JMX manager may fail to register for Alerts with all members
[ https://issues.apache.org/jira/browse/GEODE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5924: Assignee: Kirk Lund > JMX manager may fail to register for Alerts with all members > > > Key: GEODE-5924 > URL: https://issues.apache.org/jira/browse/GEODE-5924 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > JMX manager may fail to register for Alerts with all members. > Invoking DistributedSystemMXBean.changeAlertLevel(String alertLevel) seems to > work around the problem. > Hosting the JMX manager within a Locator also seems to work around this which > suggests there is a race condition involving ManagerStartupMessage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5923) JMX manager does not receive locally generated Alerts
[ https://issues.apache.org/jira/browse/GEODE-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-5923: - Affects Version/s: 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 1.7.0 > JMX manager does not receive locally generated Alerts > - > > Key: GEODE-5923 > URL: https://issues.apache.org/jira/browse/GEODE-5923 > Project: Geode > Issue Type: Bug > Components: management >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, 1.7.0 >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > The JMX manager does not receive locally generated Alerts. It only receives > remotely generated Alerts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5924) JMX manager may fail to register for Alerts with all members
Kirk Lund created GEODE-5924: Summary: JMX manager may fail to register for Alerts with all members Key: GEODE-5924 URL: https://issues.apache.org/jira/browse/GEODE-5924 Project: Geode Issue Type: Bug Components: management Reporter: Kirk Lund JMX manager may fail to register for Alerts with all members. Invoking DistributedSystemMXBean.changeAlertLevel(String alertLevel) seems to work around the problem. Hosting the JMX manager within a Locator also seems to work around this which suggests there is a race condition involving ManagerStartupMessage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5924) JMX manager may fail to register for Alerts with all members
[ https://issues.apache.org/jira/browse/GEODE-5924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-5924: - Affects Version/s: 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 1.7.0 > JMX manager may fail to register for Alerts with all members > > > Key: GEODE-5924 > URL: https://issues.apache.org/jira/browse/GEODE-5924 > Project: Geode > Issue Type: Bug > Components: management >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, 1.7.0 >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > JMX manager may fail to register for Alerts with all members. > Invoking DistributedSystemMXBean.changeAlertLevel(String alertLevel) seems to > work around the problem. > Hosting the JMX manager within a Locator also seems to work around this which > suggests there is a race condition involving ManagerStartupMessage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5925) Server shutdown delays election of new primary bucket owners
Bruce Schuchardt created GEODE-5925: --- Summary: Server shutdown delays election of new primary bucket owners Key: GEODE-5925 URL: https://issues.apache.org/jira/browse/GEODE-5925 Project: Geode Issue Type: Improvement Components: regions Reporter: Bruce Schuchardt The distributed lock service is configured to avoid releasing locks while the cache is closing. If the cache that is closing has any primary bucket locks this can delay cache operations on those buckets until the cache is completely closed and the DistributedSystem is disconnected. I've seen this take over 30 seconds, causing client connections to be timed out on the server-side and clients failing over from one server to another only to be blocked by the same issue in those servers. Another thing I observed at the same time is that AcceptorImpl is sending profile updates for all partitioned regions. Those profile updates take as long as 2 seconds apiece to process. This also delays election of new primary bucket owners and it's unnecessary since DestroyPartitionRegion messages are later sent that remove the profiles in other servers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5922) SerialGatewaySenderQueue concurrency is poorly implemented
[ https://issues.apache.org/jira/browse/GEODE-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reassigned GEODE-5922: --- Assignee: Bruce Schuchardt > SerialGatewaySenderQueue concurrency is poorly implemented > -- > > Key: GEODE-5922 > URL: https://issues.apache.org/jira/browse/GEODE-5922 > Project: Geode > Issue Type: Improvement > Components: wan >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > > This class uses synchronization on the queue to limit access to one put at a > time. Synchronization isn't a fair locking mechanism so threads can be > blocked trying to add events to the queue while other more recent events get > the lock and insert their events. This causes inconsistent latency which > I've observed being as long as 30 seconds, causing client connections to be > shut down by the ClientHealthMonitor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5925) Server shutdown delays election of new primary bucket owners
[ https://issues.apache.org/jira/browse/GEODE-5925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt reassigned GEODE-5925: --- Assignee: Bruce Schuchardt > Server shutdown delays election of new primary bucket owners > > > Key: GEODE-5925 > URL: https://issues.apache.org/jira/browse/GEODE-5925 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > > The distributed lock service is configured to avoid releasing locks while the > cache is closing. If the cache that is closing has any primary bucket locks > this can delay cache operations on those buckets until the cache is > completely closed and the DistributedSystem is disconnected. > I've seen this take over 30 seconds, causing client connections to be timed > out on the server-side and clients failing over from one server to another > only to be blocked by the same issue in those servers. > Another thing I observed at the same time is that AcceptorImpl is sending > profile updates for all partitioned regions. Those profile updates take as > long as 2 seconds apiece to process. This also delays election of new > primary bucket owners and it's unnecessary since > DestroyPartitionRegion messages are later sent that remove the profiles in > other servers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5922) SerialGatewaySenderQueue concurrency is poorly implemented
[ https://issues.apache.org/jira/browse/GEODE-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662839#comment-16662839 ] ASF subversion and git services commented on GEODE-5922: Commit 7b7fed861903d9a9660e1f5b1c4d778d14f5eca5 in geode's branch refs/heads/feature/GEODE-5922 from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7b7fed8 ] GEODE-5922 SerialGatewaySenderQueue concurrency is poorly implemented Replaced simple synchronization with a fair write-lock. The use of sync to enforce serial queueing wasn't fair and caused inconsistent latency. I observed one thread that was blocked trying to get the sync for over 30 seconds while other subsequent threads were able to get the sync and queue their events. > SerialGatewaySenderQueue concurrency is poorly implemented > -- > > Key: GEODE-5922 > URL: https://issues.apache.org/jira/browse/GEODE-5922 > Project: Geode > Issue Type: Improvement > Components: wan >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > > This class uses synchronization on the queue to limit access to one put at a > time. Synchronization isn't a fair locking mechanism so threads can be > blocked trying to add events to the queue while other more recent events get > the lock and insert their events. This causes inconsistent latency which > I've observed being as long as 30 seconds, causing client connections to be > shut down by the ClientHealthMonitor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5922) SerialGatewaySenderQueue concurrency is poorly implemented
[ https://issues.apache.org/jira/browse/GEODE-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5922: -- Labels: pull-request-available (was: ) > SerialGatewaySenderQueue concurrency is poorly implemented > -- > > Key: GEODE-5922 > URL: https://issues.apache.org/jira/browse/GEODE-5922 > Project: Geode > Issue Type: Improvement > Components: wan >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > > This class uses synchronization on the queue to limit access to one put at a > time. Synchronization isn't a fair locking mechanism so threads can be > blocked trying to add events to the queue while other more recent events get > the lock and insert their events. This causes inconsistent latency which > I've observed being as long as 30 seconds, causing client connections to be > shut down by the ClientHealthMonitor. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5861) JDBC Connector should use gfsh jndi-binding instead of jdbc-connection
[
https://issues.apache.org/jira/browse/GEODE-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662851#comment-16662851
]
ASF subversion and git services commented on GEODE-5861:
Commit 404c64d827e23faf7c95de291bf5782ac53e07ad in geode's branch
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=404c64d ]
GEODE-5861: change jdbc connector to use jndi binding (#2650)
The jdbc connector now uses the existing "jndi-binding" xml/gfsh instead of
adding "jdbc-connection" xml/gfsh. All the old "jdbc-connection" commands have
been removed.
The create jndi-binding command has been changed in the following ways:
* the driver-class-name gfsh parameter is now optional.
* --url can be used as a replacement for --connnection-url
* the --type now defaults to SIMPLE (it used to not have a default).
* the --type=POOLED now defaults to creating a Hikari pool and an SPI exists to
customize the class
that implements the pool.
New External APIS:
DataSourceFactoryTest: this is the SPI users can implement for the POOLED
type.
Co-authored-by: @BenjaminPerryRoss
> JDBC Connector should use gfsh jndi-binding instead of jdbc-connection
> --
>
> Key: GEODE-5861
> URL: https://issues.apache.org/jira/browse/GEODE-5861
> Project: Geode
> Issue Type: Improvement
> Components: extensions
>Reporter: Jianxia Chen
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> In Geode there are two {{gfsh}} commands {{create jndi-binding}} and {{create
> jdbc-connection}} which try to accomplish the same goal. We should:
> * Change JDBC Connector to use the JNDI binding, instead of the JDBC
> Connection
> * Remove the {{create jdbc-connection}} command.
> * Remove the {{destroy jdbc-connection}} command
> * Remove the {{list jdbc-connection}} command.
> * Remove the {{describe jdbc-connection}} command
> * Remove the {{alter jdbc-connnection}} command
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5861) JDBC Connector should use gfsh jndi-binding instead of jdbc-connection
[
https://issues.apache.org/jira/browse/GEODE-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider resolved GEODE-5861.
-
Resolution: Fixed
> JDBC Connector should use gfsh jndi-binding instead of jdbc-connection
> --
>
> Key: GEODE-5861
> URL: https://issues.apache.org/jira/browse/GEODE-5861
> Project: Geode
> Issue Type: Improvement
> Components: extensions
>Reporter: Jianxia Chen
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> In Geode there are two {{gfsh}} commands {{create jndi-binding}} and {{create
> jdbc-connection}} which try to accomplish the same goal. We should:
> * Change JDBC Connector to use the JNDI binding, instead of the JDBC
> Connection
> * Remove the {{create jdbc-connection}} command.
> * Remove the {{destroy jdbc-connection}} command
> * Remove the {{list jdbc-connection}} command.
> * Remove the {{describe jdbc-connection}} command
> * Remove the {{alter jdbc-connnection}} command
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5861) JDBC Connector should use gfsh jndi-binding instead of jdbc-connection
[
https://issues.apache.org/jira/browse/GEODE-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662872#comment-16662872
]
ASF subversion and git services commented on GEODE-5861:
Commit 404c64d827e23faf7c95de291bf5782ac53e07ad in geode's branch
refs/heads/feature/GEODE-5897 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=404c64d ]
GEODE-5861: change jdbc connector to use jndi binding (#2650)
The jdbc connector now uses the existing "jndi-binding" xml/gfsh instead of
adding "jdbc-connection" xml/gfsh. All the old "jdbc-connection" commands have
been removed.
The create jndi-binding command has been changed in the following ways:
* the driver-class-name gfsh parameter is now optional.
* --url can be used as a replacement for --connnection-url
* the --type now defaults to SIMPLE (it used to not have a default).
* the --type=POOLED now defaults to creating a Hikari pool and an SPI exists to
customize the class
that implements the pool.
New External APIS:
DataSourceFactoryTest: this is the SPI users can implement for the POOLED
type.
Co-authored-by: @BenjaminPerryRoss
> JDBC Connector should use gfsh jndi-binding instead of jdbc-connection
> --
>
> Key: GEODE-5861
> URL: https://issues.apache.org/jira/browse/GEODE-5861
> Project: Geode
> Issue Type: Improvement
> Components: extensions
>Reporter: Jianxia Chen
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> In Geode there are two {{gfsh}} commands {{create jndi-binding}} and {{create
> jdbc-connection}} which try to accomplish the same goal. We should:
> * Change JDBC Connector to use the JNDI binding, instead of the JDBC
> Connection
> * Remove the {{create jdbc-connection}} command.
> * Remove the {{destroy jdbc-connection}} command
> * Remove the {{list jdbc-connection}} command.
> * Remove the {{describe jdbc-connection}} command
> * Remove the {{alter jdbc-connnection}} command
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5916) deploying examples pipeline is broken
[ https://issues.apache.org/jira/browse/GEODE-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662864#comment-16662864 ] ASF subversion and git services commented on GEODE-5916: Commit a76ff07e458ba254e1a9cf4e2c1c55fa0b4ccb36 in geode's branch refs/heads/feature/GEODE-5897 from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a76ff07 ] GEODE-5916: Indentation. (#2700) Co-authored-by: Sean Goller Co-authored-by: Dick Cavender Co-authored-by: Patrick Rhomberg > deploying examples pipeline is broken > - > > Key: GEODE-5916 > URL: https://issues.apache.org/jira/browse/GEODE-5916 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 4h > Remaining Estimate: 0h > > The meta job that deploys the examples pipeline is broken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5915) ManagementListener.handleEvent logs a warning anytime a system Alert occurs
[
https://issues.apache.org/jira/browse/GEODE-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662870#comment-16662870
]
ASF subversion and git services commented on GEODE-5915:
Commit 02d7d1b3caec51c2805a78aa814b97642061e79d in geode's branch
refs/heads/feature/GEODE-5897 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=02d7d1b ]
GEODE-5915: Cleanup DistributedSystemDUnitTest
* Remove unnecessary this qualifiers.
* Minor whitespace changes.
> ManagementListener.handleEvent logs a warning anytime a system Alert occurs
> ---
>
> Key: GEODE-5915
> URL: https://issues.apache.org/jira/browse/GEODE-5915
> Project: Geode
> Issue Type: Test
> Components: management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The IllegalMonitorStateException is being thrown because the read lock is
> acquired only if the ResourceEvent type is not SYSTEM_ALERT, but the code
> tries to unlock it unconditionally:
> Lock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().lock();
> } else if (event != ResourceEvent.SYSTEM_ALERT) {
> readWriteLock.readLock().lock();
> }
> {noformat}
> Unlock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().unlock();
> } else {
> readWriteLock.readLock().unlock();
> }
> {noformat}
> {noformat}
> [vm0] [warn 2018/10/23 12:51:35.339 PDT
> tid=0x58] attempt to unlock read lock, not locked by current thread
> [vm0] java.lang.IllegalMonitorStateException: attempt to unlock read lock,
> not locked by current thread
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428)
> [vm0] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881)
> [vm0] at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:232)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2219)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:595)
> [vm0] at
> org.apache.geode.internal.admin.remote.AlertListenerMessage.process(AlertListenerMessage.java:106)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:954)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.doProcessingThread(ClusterDistributionManager.java:820)
> [vm0] at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5841) Update the versions of tomcat that are tested and supported.
[ https://issues.apache.org/jira/browse/GEODE-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662866#comment-16662866 ] ASF subversion and git services commented on GEODE-5841: Commit 0c082e598c0bce260993e690cda77adb647ec0d6 in geode's branch refs/heads/feature/GEODE-5897 from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0c082e5 ] GEODE-5841: Adding Tomcat 9 support * GEODE-5841: Adding Tomcat 9 support Adding a separate tomcat-9 module and testing that session replication works with tomcat 9. Deprecating Tomcat 6 support. > Update the versions of tomcat that are tested and supported. > > > Key: GEODE-5841 > URL: https://issues.apache.org/jira/browse/GEODE-5841 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Tomcat 6 has been in end of life since 2016. We should deprecate > Tomcat6DeltaSessionManager and plan on removing that in a later release. > Tomcat 9 has been out for a year. We should add tests that use Tomcat 9 and > start supporting that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5915) ManagementListener.handleEvent logs a warning anytime a system Alert occurs
[
https://issues.apache.org/jira/browse/GEODE-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662871#comment-16662871
]
ASF subversion and git services commented on GEODE-5915:
Commit 1c55639a2081233e5bf0cee3c0def74ad97ccce6 in geode's branch
refs/heads/feature/GEODE-5897 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1c55639 ]
GEODE-5915: Fix IllegalMonitorStateException logged for Alerts
* Prevent IllegalMonitorStateException in ManagementListener.
* Pass in InternalDistributedSystem to prevent singleton fetches.
* Create unit tests for ManagementListener.
> ManagementListener.handleEvent logs a warning anytime a system Alert occurs
> ---
>
> Key: GEODE-5915
> URL: https://issues.apache.org/jira/browse/GEODE-5915
> Project: Geode
> Issue Type: Test
> Components: management
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The IllegalMonitorStateException is being thrown because the read lock is
> acquired only if the ResourceEvent type is not SYSTEM_ALERT, but the code
> tries to unlock it unconditionally:
> Lock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().lock();
> } else if (event != ResourceEvent.SYSTEM_ALERT) {
> readWriteLock.readLock().lock();
> }
> {noformat}
> Unlock:
> {noformat}
> if (event == ResourceEvent.CACHE_CREATE || event ==
> ResourceEvent.CACHE_REMOVE) {
> readWriteLock.writeLock().unlock();
> } else {
> readWriteLock.readLock().unlock();
> }
> {noformat}
> {noformat}
> [vm0] [warn 2018/10/23 12:51:35.339 PDT
> tid=0x58] attempt to unlock read lock, not locked by current thread
> [vm0] java.lang.IllegalMonitorStateException: attempt to unlock read lock,
> not locked by current thread
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.unmatchedUnlockException(ReentrantReadWriteLock.java:444)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryReleaseShared(ReentrantReadWriteLock.java:428)
> [vm0] at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1341)
> [vm0] at
> java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.unlock(ReentrantReadWriteLock.java:881)
> [vm0] at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:232)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2219)
> [vm0] at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:595)
> [vm0] at
> org.apache.geode.internal.admin.remote.AlertListenerMessage.process(AlertListenerMessage.java:106)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> [vm0] at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:954)
> [vm0] at
> org.apache.geode.distributed.internal.ClusterDistributionManager.doProcessingThread(ClusterDistributionManager.java:820)
> [vm0] at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5916) deploying examples pipeline is broken
[ https://issues.apache.org/jira/browse/GEODE-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662865#comment-16662865 ] ASF subversion and git services commented on GEODE-5916: Commit 2a4d4c54f7caaba5c521b42462f521ff77fa3d99 in geode's branch refs/heads/feature/GEODE-5897 from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2a4d4c5 ] GEODE-5916: INDENTATION! (#2701) Co-authored-by: Sean Goller Co-authored-by: Dick Cavender Co-authored-by: Patrick Rhomberg > deploying examples pipeline is broken > - > > Key: GEODE-5916 > URL: https://issues.apache.org/jira/browse/GEODE-5916 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 4h > Remaining Estimate: 0h > > The meta job that deploys the examples pipeline is broken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5911) Improve SSL warning to indicate specific to GEODE; reference related property
[
https://issues.apache.org/jira/browse/GEODE-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662868#comment-16662868
]
ASF subversion and git services commented on GEODE-5911:
Commit de2aed4a8032fc0e0bc1f8399ce985fae7e3cb85 in geode's branch
refs/heads/feature/GEODE-5897 from ladyVader
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=de2aed4 ]
GEODE-5911: Improve SSL warning to indicate specific to GEODE; reference
related property
* Added Apache GEODE to SSL hostname validation warning
* Added ssl-endpoint-identification-enabled property to same
> Improve SSL warning to indicate specific to GEODE; reference related property
> -
>
> Key: GEODE-5911
> URL: https://issues.apache.org/jira/browse/GEODE-5911
> Project: Geode
> Issue Type: Bug
> Components: security
>Affects Versions: 1.8.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Shelley Lynn Hughes-Godfrey
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We currently log this warning in the system log if
> ssl-endpoint-identification-enabled
> {noformat}
> Your SSL configuration disables hostname validation. Future releases will
> mandate hostname validation.
> {noformat}
> This can be mis-interpreted as a JVM warning, so updating the message to show
> it is Apache GEODE related ... and include the property to enable hostname
> validation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5819) Handshake fails on Java11
[
https://issues.apache.org/jira/browse/GEODE-5819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662869#comment-16662869
]
ASF subversion and git services commented on GEODE-5819:
Commit a1bbe9074b05a9945e2f8cc4e7c915bd13bc8c02 in geode's branch
refs/heads/feature/GEODE-5897 from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a1bbe90 ]
GEODE-5819: use cipher suites supported across jdk versions (#2677)
> Handshake fails on Java11
> -
>
> Key: GEODE-5819
> URL: https://issues.apache.org/jira/browse/GEODE-5819
> Project: Geode
> Issue Type: Sub-task
>Reporter: Jinmei Liao
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> *
> [RestAPIsWithSSLDUnitTest|http://files.apachegeode-ci.info/builds/1.8.0-build.5/test-results/distributedTest/1538508591/classes/org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.html].
>
> [testSSLWithMultipleCipherSuite|http://files.apachegeode-ci.info/builds/1.8.0-build.5/test-results/distributedTest/1538508591/classes/org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.html#testSSLWithMultipleCipherSuite]
> *
> [RestAPIsWithSSLDUnitTest|http://files.apachegeode-ci.info/builds/1.8.0-build.5/test-results/distributedTest/1538508591/classes/org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.html].
>
> [testSSLWithMultipleCipherSuiteLegacy|http://files.apachegeode-ci.info/builds/1.8.0-build.5/test-results/distributedTest/1538508591/classes/org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.html#testSSLWithMultipleCipherSuiteLegacy]
> {noformat}
> java.lang.RuntimeException: unexpected exception
> at
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.validateConnection(RestAPIsWithSSLDUnitTest.java:512)
> at
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithMultipleCipherSuite(RestAPIsWithSSLDUnitTest.java:701)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 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
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
[jira] [Commented] (GEODE-5897) create jndi-binding gfsh command does not report errors
[
https://issues.apache.org/jira/browse/GEODE-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662873#comment-16662873
]
ASF subversion and git services commented on GEODE-5897:
Commit b2bb98e2e9760983159aa2468b07a20501396a66 in geode's branch
refs/heads/feature/GEODE-5897 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b2bb98e ]
Merge branch 'develop' into feature/GEODE-5897
> create jndi-binding gfsh command does not report errors
> ---
>
> Key: GEODE-5897
> URL: https://issues.apache.org/jira/browse/GEODE-5897
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The command succeeds even if there was an error on the server. I would expect
> the command to fail if the url has a typo, the credentials are incorrect, the
> driver class was not found on the classpath etc.
> E.g.
> {noformat}
> gfsh>create jndi-binding --connection-url=lcoalsthag --name=ds2
> --jdbc-driver-class="asdffii" --type=SIMPLE --username=foo
> Password: *
> Member | Status | Message
> -- | -- |
> ---
> serv1 | OK | Initiated jndi binding "ds2" on "serv1". See server logs to
> verify.
> Changes to configuration for group 'cluster' are persisted.
> {noformat}
> But the server has an error in the logs:
> {noformat}
> [error 2018/10/18 11:26:27.385 PDT serv1
> tid=0x48] An Exception was caught while trying to load the driver. asdffii
> java.lang.ClassNotFoundException: asdffii
> at
> org.apache.geode.internal.ClassPathLoader.forName(ClassPathLoader.java:170)
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.loadDriver(GemFireBasicDataSource.java:130)
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.(GemFireBasicDataSource.java:68)
> at
> org.apache.geode.internal.datasource.DataSourceFactory.getSimpleDataSource(DataSourceFactory.java:75)
> at
> org.apache.geode.internal.jndi.JNDIInvoker.mapDatasource(JNDIInvoker.java:340)
> at
> org.apache.geode.management.internal.cli.functions.CreateJndiBindingFunction.executeFunction(CreateJndiBindingFunction.java:39)
> at org.apache.geode.management.cli.CliFunction.execute(CliFunction.java:32)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:193)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:949)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.doFunctionExecutionThread(ClusterDistributionManager.java:803)
> at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> at java.lang.Thread.run(Thread.java:745)
> [error 2018/10/18 11:26:27.386 PDT serv1
> tid=0x48] DataSourceFactory::getSimpleDataSource:Exception while creating
> GemfireBasicDataSource.Exception String=An Exception was caught while trying
> to load the driver. asdffii
> java.sql.SQLException: An Exception was caught while trying to load the
> driver. asdffii
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.loadDriver(GemFireBasicDataSource.java:137)
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.(GemFireBasicDataSource.java:68)
> at
> org.apache.geode.internal.datasource.DataSourceFactory.getSimpleDataSource(DataSourceFactory.java:75)
> at
> org.apache.geode.internal.jndi.JNDIInvoker.mapDatasource(JNDIInvoker.java:340)
> at
> org.apache.geode.management.internal.cli.functions.CreateJndiBindingFunction.executeFunction(CreateJndiBindingFunction.java:39)
> at org.apache.geode.management.cli.CliFunction.execute(CliFunction.java:32)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:193)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolE
[jira] [Commented] (GEODE-5841) Update the versions of tomcat that are tested and supported.
[ https://issues.apache.org/jira/browse/GEODE-5841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662867#comment-16662867 ] ASF subversion and git services commented on GEODE-5841: Commit 0c082e598c0bce260993e690cda77adb647ec0d6 in geode's branch refs/heads/feature/GEODE-5897 from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0c082e5 ] GEODE-5841: Adding Tomcat 9 support * GEODE-5841: Adding Tomcat 9 support Adding a separate tomcat-9 module and testing that session replication works with tomcat 9. Deprecating Tomcat 6 support. > Update the versions of tomcat that are tested and supported. > > > Key: GEODE-5841 > URL: https://issues.apache.org/jira/browse/GEODE-5841 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Tomcat 6 has been in end of life since 2016. We should deprecate > Tomcat6DeltaSessionManager and plan on removing that in a later release. > Tomcat 9 has been out for a year. We should add tests that use Tomcat 9 and > start supporting that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5916) deploying examples pipeline is broken
[ https://issues.apache.org/jira/browse/GEODE-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662863#comment-16662863 ] ASF subversion and git services commented on GEODE-5916: Commit 991aa22cab52cbfaa88a8ab73942fe9b030951f4 in geode's branch refs/heads/feature/GEODE-5897 from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=991aa22 ] GEODE-5916: stop instance after we are done. (#2699) Co-authored-by: Sean Goller Co-authored-by: Dick Cavender Co-authored-by: Patrick Rhomberg > deploying examples pipeline is broken > - > > Key: GEODE-5916 > URL: https://issues.apache.org/jira/browse/GEODE-5916 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 4h > Remaining Estimate: 0h > > The meta job that deploys the examples pipeline is broken. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5926) use jinja to reduce duplicated code in metrics pipeline
Owen Nichols created GEODE-5926: --- Summary: use jinja to reduce duplicated code in metrics pipeline Key: GEODE-5926 URL: https://issues.apache.org/jira/browse/GEODE-5926 Project: Geode Issue Type: Bug Components: ci Reporter: Owen Nichols the current pipeline code has been duplicated 18 times for each job. using a jinja loop this could be reduced by 18x. also it is pointing to the wrong pipeline, should be apache-develop-main instead of develop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5927) add a way for create jndi-binding --type=POOLED to pass vendor specific attributes to the pool provider
[ https://issues.apache.org/jira/browse/GEODE-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-5927: --- Assignee: Darrel Schneider > add a way for create jndi-binding --type=POOLED to pass vendor specific > attributes to the pool provider > --- > > Key: GEODE-5927 > URL: https://issues.apache.org/jira/browse/GEODE-5927 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > > The new create jndi-binding --type=POOLED does not provide a way to configure > the pool. > The pool can now be implemented by a user implemented class so we can not > know in advance the different configuration options it may have. So we want > to provide a way that the gfsh create jndi-binding command can pass key:value > string pairs to the pool implementation. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5927) add a way for create jndi-binding --type=POOLED to pass vendor specific attributes to the pool provider
Darrel Schneider created GEODE-5927: --- Summary: add a way for create jndi-binding --type=POOLED to pass vendor specific attributes to the pool provider Key: GEODE-5927 URL: https://issues.apache.org/jira/browse/GEODE-5927 Project: Geode Issue Type: Improvement Components: gfsh Reporter: Darrel Schneider The new create jndi-binding --type=POOLED does not provide a way to configure the pool. The pool can now be implemented by a user implemented class so we can not know in advance the different configuration options it may have. So we want to provide a way that the gfsh create jndi-binding command can pass key:value string pairs to the pool implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-2610) Host schema on geode.apache.org
[
https://issues.apache.org/jira/browse/GEODE-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-2610:
--
Labels: pull-request-available (was: )
> Host schema on geode.apache.org
> ---
>
> Key: GEODE-2610
> URL: https://issues.apache.org/jira/browse/GEODE-2610
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
> Labels: pull-request-available
>
> We need to move gfcpp-cache-9.0.xsd to http://geode.apache.org/schema and
> change the definition:
> {noformat}
> http://schema.pivotal.io/gemfire/gfcpp-cache";
> xmlns:nc="http://schema.pivotal.io/gemfire/gfcpp-cache";
> elementFormDefault="qualified" attributeFormDefault="unqualified"
> targetNamespace="http://schema.pivotal.io/gemfire/gfcpp-cache";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; version="9.0">
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-2610) Host schema on geode.apache.org
[
https://issues.apache.org/jira/browse/GEODE-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662918#comment-16662918
]
Blake Bender commented on GEODE-2610:
-
Schema is now hosted at
[http://geode.apache.org/schema/cpp-cache/cpp-cache-1.0.xsd.] References in
the source tree should all be fixed up now.
> Host schema on geode.apache.org
> ---
>
> Key: GEODE-2610
> URL: https://issues.apache.org/jira/browse/GEODE-2610
> Project: Geode
> Issue Type: Sub-task
> Components: build, native client
>Reporter: Anthony Baker
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We need to move gfcpp-cache-9.0.xsd to http://geode.apache.org/schema and
> change the definition:
> {noformat}
> http://schema.pivotal.io/gemfire/gfcpp-cache";
> xmlns:nc="http://schema.pivotal.io/gemfire/gfcpp-cache";
> elementFormDefault="qualified" attributeFormDefault="unqualified"
> targetNamespace="http://schema.pivotal.io/gemfire/gfcpp-cache";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; version="9.0">
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5928) Code Cleanup: Refactor WANSSLDunitTest to not extend TestBase classes
Patrick Rhomberg created GEODE-5928: --- Summary: Code Cleanup: Refactor WANSSLDunitTest to not extend TestBase classes Key: GEODE-5928 URL: https://issues.apache.org/jira/browse/GEODE-5928 Project: Geode Issue Type: Improvement Reporter: Patrick Rhomberg It is very difficult to reason about a test's behavior when the majority of it is obfuscated behind test inheritance. This ticket represents refactoring done in pursuit of GEODE-5819. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5928) Code Cleanup: Refactor WANSSLDunitTest to not extend TestBase classes
[ https://issues.apache.org/jira/browse/GEODE-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5928: -- Labels: pull-request-available (was: ) > Code Cleanup: Refactor WANSSLDunitTest to not extend TestBase classes > - > > Key: GEODE-5928 > URL: https://issues.apache.org/jira/browse/GEODE-5928 > Project: Geode > Issue Type: Improvement >Reporter: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > > It is very difficult to reason about a test's behavior when the majority of > it is obfuscated behind test inheritance. This ticket represents refactoring > done in pursuit of GEODE-5819. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5864) Streamline and parameterize concourse environment
[ https://issues.apache.org/jira/browse/GEODE-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662944#comment-16662944 ] ASF subversion and git services commented on GEODE-5864: Commit 7d9858ee882f6bf06a7658b39911aac4fe72e4e1 in geode's branch refs/heads/develop from [~smgoller] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7d9858e ] GEODE-5864 Refactor pipeline deployment. (#2707) * deploy_meta.sh now looks at the file meta.properties for defaults * Users should create meta.properties.local file and override values there. A common customization is to override GEODE_FORK with your personal geode repository. * GRADLE_GLOBAL_ARGS is a string of gradle arguments that will be passed to every invocation of gradle. * Change "start_instance.sh" to "create_instance.sh" * Change "stop_instance.sh" to "delete_instance.sh" * Remove unnecessary gcloud delete invocation * Add on_failure block to rsync_code_up job to delete the instance. * Make on_failure call a do block to be consistent with other on_failures. * Add system property for excluding individual test classes. * Adjust excludeTests to handle multiple tests * Add maven snapshot bucket for storing published artifacts. * Make GCP_PROJECT a property instead of deriving it. * Make deploy_meta.sh more user-friendly by displaying values and offering the option to abort. * Forks should no longer be hard-coded. * Remove UpdatePassingRef job. * Remove unused scripts. Co-authored-by: Sean Goller Co-authored-by: Jacob Barrett Co-authored-by: Dick Cavender > Streamline and parameterize concourse environment > - > > Key: GEODE-5864 > URL: https://issues.apache.org/jira/browse/GEODE-5864 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 9h 40m > Remaining Estimate: 0h > > In order to simplify stamping out multiple CI environments such as for > developer use, parameterize infrastructure-specific variables and remove > unnecessary vault usage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5926) use jinja to reduce duplicated code in metrics pipeline
[ https://issues.apache.org/jira/browse/GEODE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5926: -- Labels: pull-request-available (was: ) > use jinja to reduce duplicated code in metrics pipeline > --- > > Key: GEODE-5926 > URL: https://issues.apache.org/jira/browse/GEODE-5926 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > the current pipeline code has been duplicated 18 times for each job. using a > jinja loop this could be reduced by 18x. also it is pointing to the wrong > pipeline, should be apache-develop-main instead of develop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5926) use jinja to reduce duplicated code in metrics pipeline
[ https://issues.apache.org/jira/browse/GEODE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662959#comment-16662959 ] ASF subversion and git services commented on GEODE-5926: Commit 35d122686e6ccc8b23c4e42d104e3d489f96b85a in geode's branch refs/heads/develop from [~onichols-pivotal] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=35d1226 ] GEODE-5926 parameterize metrics pipeline (#2708) > use jinja to reduce duplicated code in metrics pipeline > --- > > Key: GEODE-5926 > URL: https://issues.apache.org/jira/browse/GEODE-5926 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > the current pipeline code has been duplicated 18 times for each job. using a > jinja loop this could be reduced by 18x. also it is pointing to the wrong > pipeline, should be apache-develop-main instead of develop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5674) Stop picking ports randomly for tests
[ https://issues.apache.org/jira/browse/GEODE-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Rowe reassigned GEODE-5674: - Assignee: Brian Rowe > Stop picking ports randomly for tests > - > > Key: GEODE-5674 > URL: https://issues.apache.org/jira/browse/GEODE-5674 > Project: Geode > Issue Type: Improvement >Reporter: Dan Smith >Assignee: Brian Rowe >Priority: Major > Labels: swat > > Our tests currently use AvailablePortHelper and AvailablePort to find a > random port that is not in use. > However, this can lead to port collisions because after the port is returned, > it is available until something binds to that socket. In the mean time, other > calls to getAvailablePort can return the same port, with around 0.01% chance, > since the range is 1 ports. > If we did not pick ports randomly, but instead iterated over a pool of ports, > we would not return the same port twice until exhaust the pool. We therefore > not get the same port twice in a test. > We would need to handle the fact that dunit tests have multiple VMs, so we > need either a central available port service or a unique pool of ports for > each process or something like that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5764) CI failure: ParallelAsyncEventListenerWithOffHeapDistributedTest.testParallelAsyncEventQueueMoveBucketAndMoveItBackDuringDispatching[dispatcherThreadCount=3]
[
https://issues.apache.org/jira/browse/GEODE-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5764:
--
Labels: pull-request-available swat (was: swat)
> 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
>Assignee: Dale Emery
>Priority: Major
> Labels: pull-request-available, 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.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
>
[jira] [Updated] (GEODE-5923) JMX manager does not receive locally generated Alerts
[ https://issues.apache.org/jira/browse/GEODE-5923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5923: -- Labels: pull-request-available (was: ) > JMX manager does not receive locally generated Alerts > - > > Key: GEODE-5923 > URL: https://issues.apache.org/jira/browse/GEODE-5923 > Project: Geode > Issue Type: Bug > Components: management >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, 1.7.0 >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > > The JMX manager does not receive locally generated Alerts. It only receives > remotely generated Alerts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5926) use jinja to reduce duplicated code in metrics pipeline
[ https://issues.apache.org/jira/browse/GEODE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-5926. - Resolution: Fixed Fix Version/s: 1.8.0 > use jinja to reduce duplicated code in metrics pipeline > --- > > Key: GEODE-5926 > URL: https://issues.apache.org/jira/browse/GEODE-5926 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > the current pipeline code has been duplicated 18 times for each job. using a > jinja loop this could be reduced by 18x. also it is pointing to the wrong > pipeline, should be apache-develop-main instead of develop -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5929) concourse workers do not need java
Owen Nichols created GEODE-5929: --- Summary: concourse workers do not need java Key: GEODE-5929 URL: https://issues.apache.org/jira/browse/GEODE-5929 Project: Geode Issue Type: Bug Components: ci Reporter: Owen Nichols all java is done in heavy-lifters now, so we can use an even lighter weight alpine base image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5927) add a way for create jndi-binding --type=POOLED to pass vendor specific attributes to the pool provider
[ https://issues.apache.org/jira/browse/GEODE-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5927: -- Labels: pull-request-available (was: ) > add a way for create jndi-binding --type=POOLED to pass vendor specific > attributes to the pool provider > --- > > Key: GEODE-5927 > URL: https://issues.apache.org/jira/browse/GEODE-5927 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > The new create jndi-binding --type=POOLED does not provide a way to configure > the pool. > The pool can now be implemented by a user implemented class so we can not > know in advance the different configuration options it may have. So we want > to provide a way that the gfsh create jndi-binding command can pass key:value > string pairs to the pool implementation. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5886) Make extension module dependencies explicit.
[ https://issues.apache.org/jira/browse/GEODE-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662969#comment-16662969 ] ASF subversion and git services commented on GEODE-5886: Commit 01dc9db9ca334087f1edec31c5739710eef3d06b in geode's branch refs/heads/develop from [~prhomberg] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=01dc9db ] GEODE-5886: Make dependencies explicit in extensions modules. (#2674) * GEODE-5886: Make dependencies explicit in extensions modules. * javax.servlet:servlet-api is identified as a dependency, but causes classpath conflicts to occur in Tomcat testing. Additional investigation required. Co-authored-by: Patrick Rhomberg Co-authored-by: Robert Houghton > Make extension module dependencies explicit. > > > Key: GEODE-5886 > URL: https://issues.apache.org/jira/browse/GEODE-5886 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5886) Make extension module dependencies explicit.
[ https://issues.apache.org/jira/browse/GEODE-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662970#comment-16662970 ] ASF subversion and git services commented on GEODE-5886: Commit 01dc9db9ca334087f1edec31c5739710eef3d06b in geode's branch refs/heads/develop from [~prhomberg] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=01dc9db ] GEODE-5886: Make dependencies explicit in extensions modules. (#2674) * GEODE-5886: Make dependencies explicit in extensions modules. * javax.servlet:servlet-api is identified as a dependency, but causes classpath conflicts to occur in Tomcat testing. Additional investigation required. Co-authored-by: Patrick Rhomberg Co-authored-by: Robert Houghton > Make extension module dependencies explicit. > > > Key: GEODE-5886 > URL: https://issues.apache.org/jira/browse/GEODE-5886 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5929) concourse workers do not need java
[ https://issues.apache.org/jira/browse/GEODE-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5929: -- Labels: pull-request-available (was: ) > concourse workers do not need java > -- > > Key: GEODE-5929 > URL: https://issues.apache.org/jira/browse/GEODE-5929 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > all java is done in heavy-lifters now, so we can use an even lighter weight > alpine base image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5897) create jndi-binding gfsh command does not report errors
[
https://issues.apache.org/jira/browse/GEODE-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider resolved GEODE-5897.
-
Resolution: Fixed
Fix Version/s: 1.8.0
> create jndi-binding gfsh command does not report errors
> ---
>
> Key: GEODE-5897
> URL: https://issues.apache.org/jira/browse/GEODE-5897
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The command succeeds even if there was an error on the server. I would expect
> the command to fail if the url has a typo, the credentials are incorrect, the
> driver class was not found on the classpath etc.
> E.g.
> {noformat}
> gfsh>create jndi-binding --connection-url=lcoalsthag --name=ds2
> --jdbc-driver-class="asdffii" --type=SIMPLE --username=foo
> Password: *
> Member | Status | Message
> -- | -- |
> ---
> serv1 | OK | Initiated jndi binding "ds2" on "serv1". See server logs to
> verify.
> Changes to configuration for group 'cluster' are persisted.
> {noformat}
> But the server has an error in the logs:
> {noformat}
> [error 2018/10/18 11:26:27.385 PDT serv1
> tid=0x48] An Exception was caught while trying to load the driver. asdffii
> java.lang.ClassNotFoundException: asdffii
> at
> org.apache.geode.internal.ClassPathLoader.forName(ClassPathLoader.java:170)
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.loadDriver(GemFireBasicDataSource.java:130)
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.(GemFireBasicDataSource.java:68)
> at
> org.apache.geode.internal.datasource.DataSourceFactory.getSimpleDataSource(DataSourceFactory.java:75)
> at
> org.apache.geode.internal.jndi.JNDIInvoker.mapDatasource(JNDIInvoker.java:340)
> at
> org.apache.geode.management.internal.cli.functions.CreateJndiBindingFunction.executeFunction(CreateJndiBindingFunction.java:39)
> at org.apache.geode.management.cli.CliFunction.execute(CliFunction.java:32)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:193)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:949)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.doFunctionExecutionThread(ClusterDistributionManager.java:803)
> at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> at java.lang.Thread.run(Thread.java:745)
> [error 2018/10/18 11:26:27.386 PDT serv1
> tid=0x48] DataSourceFactory::getSimpleDataSource:Exception while creating
> GemfireBasicDataSource.Exception String=An Exception was caught while trying
> to load the driver. asdffii
> java.sql.SQLException: An Exception was caught while trying to load the
> driver. asdffii
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.loadDriver(GemFireBasicDataSource.java:137)
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.(GemFireBasicDataSource.java:68)
> at
> org.apache.geode.internal.datasource.DataSourceFactory.getSimpleDataSource(DataSourceFactory.java:75)
> at
> org.apache.geode.internal.jndi.JNDIInvoker.mapDatasource(JNDIInvoker.java:340)
> at
> org.apache.geode.management.internal.cli.functions.CreateJndiBindingFunction.executeFunction(CreateJndiBindingFunction.java:39)
> at org.apache.geode.management.cli.CliFunction.execute(CliFunction.java:32)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:193)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> {noformat}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5919) Fix Documentation Bugs in Geode Native public APIs
[ https://issues.apache.org/jira/browse/GEODE-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Martell updated GEODE-5919: --- Description: This ticket is to fix documentation bugs in the cppcache portion of the native client API. Specifically, comments for the following classes need to be fixed. *CPPCACHE* apache::geode::client::CacheableUndefined (uncommented) apache::geode::client::CacheTransactionManager (uncommented) apache::geode::client::PdxSerializable (uncommented) apache::geode::client::TypeRegistry (uncommented) apache::geode::client::CacheableEnum (comment in wrong place, not picked up) apache::geode::client::CacheableObjectArray (comment in wrong place, not picked up) apache::geode::client::CacheableFileName (comment in wrong place, not picked up) apache::geode::client::Delta (comment in wrong place, not picked up) apache::geode::client::EntryEvent (comment in wrong place, not picked up) apache::geode::client::AuthenticatedView (wrong comment, called Cache class) DataSerializableFixedId_t (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializableInternal (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializablePrimitive (uncommented, but is exported, but is internal so maybe shouldn't be exported) *CLICACHE* Apache::Geode::Client::IDataSerializable Apache::Geode::Client::TypeRegistry was: This ticket is to fix documentation bugs in the cppcache portion of the geode native API. Specifically, comments for the following classes need to be fixed. These are doxygen fixes. apache::geode::client::CacheableUndefined (uncommented) apache::geode::client::CacheTransactionManager (uncommented) apache::geode::client::PdxSerializable (uncommented) apache::geode::client::TypeRegistry (uncommented) apache::geode::client::CacheableEnum (comment in wrong place, not picked up) apache::geode::client::CacheableObjectArray (comment in wrong place, not picked up) apache::geode::client::CacheableFileName (comment in wrong place, not picked up) apache::geode::client::Delta (comment in wrong place, not picked up) apache::geode::client::EntryEvent (comment in wrong place, not picked up) apache::geode::client::AuthenticatedView (wrong comment, called Cache class) DataSerializableFixedId_t (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializableInternal (uncommented, but is exported, but is internal so maybe shouldn't be exported) DataSerializablePrimitive (uncommented, but is exported, but is internal so maybe shouldn't be exported) > Fix Documentation Bugs in Geode Native public APIs > -- > > Key: GEODE-5919 > URL: https://issues.apache.org/jira/browse/GEODE-5919 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Michael Martell >Priority: Major > > This ticket is to fix documentation bugs in the cppcache portion of the > native client API. Specifically, comments for the following classes need to > be fixed. > *CPPCACHE* > apache::geode::client::CacheableUndefined (uncommented) > apache::geode::client::CacheTransactionManager (uncommented) > apache::geode::client::PdxSerializable (uncommented) > apache::geode::client::TypeRegistry (uncommented) > apache::geode::client::CacheableEnum (comment in wrong place, not picked up) > apache::geode::client::CacheableObjectArray (comment in wrong place, not > picked up) > apache::geode::client::CacheableFileName (comment in wrong place, not picked > up) > apache::geode::client::Delta (comment in wrong place, not picked up) > apache::geode::client::EntryEvent (comment in wrong place, not picked up) > apache::geode::client::AuthenticatedView (wrong comment, called Cache class) > DataSerializableFixedId_t (uncommented, but is exported, but is internal so > maybe shouldn't be exported) > DataSerializableInternal (uncommented, but is exported, but is internal so > maybe shouldn't be exported) > DataSerializablePrimitive (uncommented, but is exported, but is internal so > maybe shouldn't be exported) > *CLICACHE* > Apache::Geode::Client::IDataSerializable > Apache::Geode::Client::TypeRegistry -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5886) Make extension module dependencies explicit.
[ https://issues.apache.org/jira/browse/GEODE-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg resolved GEODE-5886. - Resolution: Fixed Fix Version/s: 1.8.0 > Make extension module dependencies explicit. > > > Key: GEODE-5886 > URL: https://issues.apache.org/jira/browse/GEODE-5886 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5930) clean up dangling outputs in concourse
Owen Nichols created GEODE-5930: --- Summary: clean up dangling outputs in concourse Key: GEODE-5930 URL: https://issues.apache.org/jira/browse/GEODE-5930 Project: Geode Issue Type: Bug Components: ci Reporter: Owen Nichols due to a typo, every job is needlessly showing a "concourse metadata" output -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5897) create jndi-binding gfsh command does not report errors
[
https://issues.apache.org/jira/browse/GEODE-5897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662975#comment-16662975
]
ASF subversion and git services commented on GEODE-5897:
Commit bf7981f591de3e1bf16c808bf112f3d473178914 in geode's branch
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=bf7981f5 ]
GEODE-5897: change create jndi-binding to fail on an exception (#2680)
Create jndi-binding will now fail if an exception occurs during the create.
Also the data-source is now validated by asking it for a connection when the
jndi-binding is created.
If a connection can not be obtained, the create fails and the data-source is
closed.
Previously if an exception occurred when creating a jndi-binding an info
message was logged.
Now, as the docs state, a warning is logged.
The problem was caused by an exception being caught, logged, and not rethrown.
Now the gfsh function will get the thrown exception and pass a failure back
to gfsh. For backwards compatibility, the XML parser still logs a warning if
the jndi-binding can not be created, instead of having it cause the cache not
to start.
> create jndi-binding gfsh command does not report errors
> ---
>
> Key: GEODE-5897
> URL: https://issues.apache.org/jira/browse/GEODE-5897
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The command succeeds even if there was an error on the server. I would expect
> the command to fail if the url has a typo, the credentials are incorrect, the
> driver class was not found on the classpath etc.
> E.g.
> {noformat}
> gfsh>create jndi-binding --connection-url=lcoalsthag --name=ds2
> --jdbc-driver-class="asdffii" --type=SIMPLE --username=foo
> Password: *
> Member | Status | Message
> -- | -- |
> ---
> serv1 | OK | Initiated jndi binding "ds2" on "serv1". See server logs to
> verify.
> Changes to configuration for group 'cluster' are persisted.
> {noformat}
> But the server has an error in the logs:
> {noformat}
> [error 2018/10/18 11:26:27.385 PDT serv1
> tid=0x48] An Exception was caught while trying to load the driver. asdffii
> java.lang.ClassNotFoundException: asdffii
> at
> org.apache.geode.internal.ClassPathLoader.forName(ClassPathLoader.java:170)
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.loadDriver(GemFireBasicDataSource.java:130)
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.(GemFireBasicDataSource.java:68)
> at
> org.apache.geode.internal.datasource.DataSourceFactory.getSimpleDataSource(DataSourceFactory.java:75)
> at
> org.apache.geode.internal.jndi.JNDIInvoker.mapDatasource(JNDIInvoker.java:340)
> at
> org.apache.geode.management.internal.cli.functions.CreateJndiBindingFunction.executeFunction(CreateJndiBindingFunction.java:39)
> at org.apache.geode.management.cli.CliFunction.execute(CliFunction.java:32)
> at
> org.apache.geode.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:193)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:367)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:432)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:949)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.doFunctionExecutionThread(ClusterDistributionManager.java:803)
> at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> at java.lang.Thread.run(Thread.java:745)
> [error 2018/10/18 11:26:27.386 PDT serv1
> tid=0x48] DataSourceFactory::getSimpleDataSource:Exception while creating
> GemfireBasicDataSource.Exception String=An Exception was caught while trying
> to load the driver. asdffii
> java.sql.SQLException: An Exception was caught while trying to load the
> driver. asdffii
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.loadDriver(GemFireBasicDataSource.java:137)
> at
> org.apache.geode.internal.datasource.GemFireBasicDataSource.(GemFireBasicDataSource.java:68)
> at
> org.apache.geode.internal.datasource.DataSourceFactory.getSimpleDataSource(DataSourceFactory.java:75
[jira] [Resolved] (GEODE-5885) Add geode-core exclusion from all geode-junit and geode-dunit dependencies
[ https://issues.apache.org/jira/browse/GEODE-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg resolved GEODE-5885. - Resolution: Fixed Fix Version/s: 1.8.0 > Add geode-core exclusion from all geode-junit and geode-dunit dependencies > -- > > Key: GEODE-5885 > URL: https://issues.apache.org/jira/browse/GEODE-5885 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Failing to exclude geode-core causes the Nebula dependency linter to object > to what appear to be circular dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5899) Make dependencies explicit in geode-lucene, *-old-client-support
[ https://issues.apache.org/jira/browse/GEODE-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662977#comment-16662977 ] Patrick Rhomberg commented on GEODE-5899: - Moved *-web, and *-web-api to a separate ticket. > Make dependencies explicit in geode-lucene, *-old-client-support > > > Key: GEODE-5899 > URL: https://issues.apache.org/jira/browse/GEODE-5899 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5899) Make dependencies explicit in geode-lucene, *-old-client-support
[ https://issues.apache.org/jira/browse/GEODE-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg resolved GEODE-5899. - Resolution: Fixed Fix Version/s: 1.8.0 > Make dependencies explicit in geode-lucene, *-old-client-support > > > Key: GEODE-5899 > URL: https://issues.apache.org/jira/browse/GEODE-5899 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5899) Make dependencies explicit in geode-lucene, *-old-client-support
[ https://issues.apache.org/jira/browse/GEODE-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Rhomberg updated GEODE-5899: Summary: Make dependencies explicit in geode-lucene, *-old-client-support (was: Make dependencies explicit in geode-lucene, *-old-client-support, *-web, and *-web-api) > Make dependencies explicit in geode-lucene, *-old-client-support > > > Key: GEODE-5899 > URL: https://issues.apache.org/jira/browse/GEODE-5899 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5930) clean up dangling outputs in concourse
[ https://issues.apache.org/jira/browse/GEODE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5930: -- Labels: pull-request-available (was: ) > clean up dangling outputs in concourse > -- > > Key: GEODE-5930 > URL: https://issues.apache.org/jira/browse/GEODE-5930 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > due to a typo, every job is needlessly showing a "concourse metadata" output -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5931) Make dependencies explicit in geode-pulse
Patrick Rhomberg created GEODE-5931: --- Summary: Make dependencies explicit in geode-pulse Key: GEODE-5931 URL: https://issues.apache.org/jira/browse/GEODE-5931 Project: Geode Issue Type: Sub-task Reporter: Patrick Rhomberg -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5749) DeprecatedCacheServerLauncherIntegrationTest.testServerPortNoCacheServer
[ https://issues.apache.org/jira/browse/GEODE-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663005#comment-16663005 ] Helena Bales commented on GEODE-5749: - Failed again in geode-develop CI Pipeline: [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/41] Download the log files here: http://files.apachegeode-ci.info/builds/apache-develop-main/1.8.0-build.42/test-results/integrationTest/1540423109/ > DeprecatedCacheServerLauncherIntegrationTest.testServerPortNoCacheServer > > > Key: GEODE-5749 > URL: https://issues.apache.org/jira/browse/GEODE-5749 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Mark Hanson >Priority: Major > Labels: swat > Attachments: run.log > > > PR-Develop failed with this error in > https://concourse.apachegeode-ci.info/teams/main/pipelines/pr-develop/jobs/IntegrationTest/builds/1078 > java.lang.AssertionError: Timed out waiting for output "CacheServer pid: \d+ > status: running" after 12 ms. Output: Starting CacheServer with pid: 0 at > org.junit.Assert.fail(Assert.java:88) at > org.apache.geode.test.process.ProcessWrapper.waitForOutputToMatch(ProcessWrapper.java:238) > at > org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.execAndValidate(DeprecatedCacheServerLauncherIntegrationTest.java:439) > at > org.apache.geode.internal.cache.DeprecatedCacheServerLauncherIntegrationTest.testServerPortNoCacheServer(DeprecatedCacheServerLauncherIntegrationTest.java:367) > 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.ExternalResource$1.evaluate(ExternalResource.java:48) 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.RunAfters.evaluate(RunAfters.java:27) > 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
[jira] [Commented] (GEODE-5899) Make dependencies explicit in geode-lucene, *-old-client-support
[ https://issues.apache.org/jira/browse/GEODE-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663006#comment-16663006 ] ASF subversion and git services commented on GEODE-5899: Commit 861abf4497d5c8644e31757b7f741e0da6ca0717 in geode's branch refs/heads/develop from [~prhomberg] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=861abf4 ] GEODE-5899: Make dependencies explicit in old-client and lucene* modules. (#2675) Co-authored-by: Robert Houghton Co-authored-by: Patrick Rhomberg > Make dependencies explicit in geode-lucene, *-old-client-support > > > Key: GEODE-5899 > URL: https://issues.apache.org/jira/browse/GEODE-5899 > Project: Geode > Issue Type: Sub-task >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5909) Code Cleanup: remove dead code and irrelevant snippets, most importantly that causing compile warnings.
[
https://issues.apache.org/jira/browse/GEODE-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663010#comment-16663010
]
ASF subversion and git services commented on GEODE-5909:
Commit 1a2725c7bfe95b81db1c813be276348a54a003a2 in geode's branch
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1a2725c ]
GEODE-5909: Remove unknown tag causing compile warning. (#2678)
* Also cleanup various pieces of dead code or now-inapplicable comments.
> Code Cleanup: remove dead code and irrelevant snippets, most importantly that
> causing compile warnings.
> ---
>
> Key: GEODE-5909
> URL: https://issues.apache.org/jira/browse/GEODE-5909
> Project: Geode
> Issue Type: Improvement
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As part of our build, we see:
> {noformat}
> > Task :geode-junit:javadoc
> /home/geode/geode/geode-junit/src/main/java/org/apache/geode/management/model/SubOrder.java:20:
> warning - @rishim is an unknown tag.
> {noformat}
> The offending tag is an otherwise empty javadoc. Remove this and any other
> easily identifiable dead code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5932) Add task to linter to ensure that all dependencies listed are consumed. Remove those unused version declarations.
Patrick Rhomberg created GEODE-5932:
---
Summary: Add task to linter to ensure that all dependencies listed
are consumed. Remove those unused version declarations.
Key: GEODE-5932
URL: https://issues.apache.org/jira/browse/GEODE-5932
Project: Geode
Issue Type: Sub-task
Reporter: Patrick Rhomberg
At time of writing, the following command and output is found:
{noformat}
$> for v in $(grep -vE "^#"
/Users/prhomberg/workspace/just-geode/gradle/dependency-versions.properties |
grep -vE "^ *$" | cut -d"=" -f1) ; do git grep ${v} "*.gradle" &> /dev/null ||
echo $v ; done
commons-exec.version
dom4j.version
google-gson.version
javassist.version
open-json.version
{noformat}
suggesting that these dependencies have been removed and are not consumed as
properties anywhere in our gradle build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5933) fix deploy_meta to again allow pipelines for personal forks
Owen Nichols created GEODE-5933: --- Summary: fix deploy_meta to again allow pipelines for personal forks Key: GEODE-5933 URL: https://issues.apache.org/jira/browse/GEODE-5933 Project: Geode Issue Type: Bug Components: ci Reporter: Owen Nichols also make it easier for user to know what to do to make a personal fork pipeline -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5933) fix deploy_meta to again allow pipelines for personal forks
[ https://issues.apache.org/jira/browse/GEODE-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5933: -- Labels: pull-request-available (was: ) > fix deploy_meta to again allow pipelines for personal forks > --- > > Key: GEODE-5933 > URL: https://issues.apache.org/jira/browse/GEODE-5933 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > also make it easier for user to know what to do to make a personal fork > pipeline -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5933) fix deploy_meta to again allow pipelines for personal forks
[ https://issues.apache.org/jira/browse/GEODE-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663029#comment-16663029 ] ASF subversion and git services commented on GEODE-5933: Commit 46fa876178faabb70428925f598176ccbd355cb4 in geode's branch refs/heads/develop from [~onichols-pivotal] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=46fa876 ] GEODE-5933 make it easier to use deploy_meta with forks (#2715) > fix deploy_meta to again allow pipelines for personal forks > --- > > Key: GEODE-5933 > URL: https://issues.apache.org/jira/browse/GEODE-5933 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > also make it easier for user to know what to do to make a personal fork > pipeline -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5929) concourse workers do not need java
[ https://issues.apache.org/jira/browse/GEODE-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663031#comment-16663031 ] ASF subversion and git services commented on GEODE-5929: Commit 6556b0fee9b82b4448760123473f232418d3d361 in geode's branch refs/heads/develop from [~onichols-pivotal] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6556b0f ] GEODE-5929 concourse workers no longer need java (#2712) > concourse workers do not need java > -- > > Key: GEODE-5929 > URL: https://issues.apache.org/jira/browse/GEODE-5929 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > all java is done in heavy-lifters now, so we can use an even lighter weight > alpine base image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5930) clean up dangling outputs in concourse
[ https://issues.apache.org/jira/browse/GEODE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663030#comment-16663030 ] ASF subversion and git services commented on GEODE-5930: Commit 5503d5cd1e48f9810c85c2a0a05e730157d13211 in geode's branch refs/heads/develop from [~onichols-pivotal] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5503d5c ] GEODE-5930 clean up dangling outputs in concourse (#2713) > clean up dangling outputs in concourse > -- > > Key: GEODE-5930 > URL: https://issues.apache.org/jira/browse/GEODE-5930 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > due to a typo, every job is needlessly showing a "concourse metadata" output -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5930) clean up dangling outputs in concourse
[ https://issues.apache.org/jira/browse/GEODE-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-5930. - Resolution: Fixed Fix Version/s: 1.8.0 > clean up dangling outputs in concourse > -- > > Key: GEODE-5930 > URL: https://issues.apache.org/jira/browse/GEODE-5930 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > due to a typo, every job is needlessly showing a "concourse metadata" output -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5933) fix deploy_meta to again allow pipelines for personal forks
[ https://issues.apache.org/jira/browse/GEODE-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-5933. - Resolution: Fixed Fix Version/s: 1.8.0 > fix deploy_meta to again allow pipelines for personal forks > --- > > Key: GEODE-5933 > URL: https://issues.apache.org/jira/browse/GEODE-5933 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > also make it easier for user to know what to do to make a personal fork > pipeline -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5929) concourse workers do not need java
[ https://issues.apache.org/jira/browse/GEODE-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-5929. - Resolution: Fixed Fix Version/s: 1.8.0 > concourse workers do not need java > -- > > Key: GEODE-5929 > URL: https://issues.apache.org/jira/browse/GEODE-5929 > Project: Geode > Issue Type: Bug > Components: ci >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > all java is done in heavy-lifters now, so we can use an even lighter weight > alpine base image -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5934) fix examples pipeline
Owen Nichols created GEODE-5934: --- Summary: fix examples pipeline Key: GEODE-5934 URL: https://issues.apache.org/jira/browse/GEODE-5934 Project: Geode Issue Type: Bug Reporter: Owen Nichols looks like this pipeline got missed in the refactoring -- This message was sent by Atlassian JIRA (v7.6.3#76005)
