[jira] [Commented] (GEODE-10299) Creating Regions Dynamically Example in User's Guide is Broken
[ https://issues.apache.org/jira/browse/GEODE-10299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538533#comment-17538533 ] ASF subversion and git services commented on GEODE-10299: - Commit 5aada08049d67782130d8cff04b03ccf677d80b4 in geode's branch refs/heads/support/1.14 from Max Hufnagel [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5aada08049 ] GEODE-10299: update examples for creating dynamic regions (#7681) > Creating Regions Dynamically Example in User's Guide is Broken > -- > > Key: GEODE-10299 > URL: https://issues.apache.org/jira/browse/GEODE-10299 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Max Hufnagel >Assignee: Max Hufnagel >Priority: Major > Labels: pull-request-available > Fix For: 1.14.5, 1.15.0, 1.16.0 > > Attachments: CreateRegionCacheListener.java, CreateRegionFunction.java > > > The example on > [https://geode.apache.org/docs/guide/114/developing/region_options/dynamic_region_creation.html] > no longer works. The RegionAttributesImpl class was made not Serializable in > Geode 1.11 ([GEODE-7090|https://issues.apache.org/jira/browse/GEODE-7090]), > so instances can no longer be passed from the client to the server making > this function unusable from a client. > Barry Oglesby has created updated versions of the two classes (see attached). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10299) Creating Regions Dynamically Example in User's Guide is Broken
[ https://issues.apache.org/jira/browse/GEODE-10299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10299. - Fix Version/s: 1.14.5 1.15.0 1.16.0 Resolution: Fixed > Creating Regions Dynamically Example in User's Guide is Broken > -- > > Key: GEODE-10299 > URL: https://issues.apache.org/jira/browse/GEODE-10299 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Max Hufnagel >Assignee: Max Hufnagel >Priority: Major > Labels: pull-request-available > Fix For: 1.14.5, 1.15.0, 1.16.0 > > Attachments: CreateRegionCacheListener.java, CreateRegionFunction.java > > > The example on > [https://geode.apache.org/docs/guide/114/developing/region_options/dynamic_region_creation.html] > no longer works. The RegionAttributesImpl class was made not Serializable in > Geode 1.11 ([GEODE-7090|https://issues.apache.org/jira/browse/GEODE-7090]), > so instances can no longer be passed from the client to the server making > this function unusable from a client. > Barry Oglesby has created updated versions of the two classes (see attached). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10299) Creating Regions Dynamically Example in User's Guide is Broken
[ https://issues.apache.org/jira/browse/GEODE-10299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538530#comment-17538530 ] ASF subversion and git services commented on GEODE-10299: - Commit 53cbccaeb5bcf2bfa6773481ff98e47f27704e86 in geode's branch refs/heads/support/1.15 from Max Hufnagel [ https://gitbox.apache.org/repos/asf?p=geode.git;h=53cbccaeb5 ] GEODE-10299: update examples for creating dynamic regions (#7681) > Creating Regions Dynamically Example in User's Guide is Broken > -- > > Key: GEODE-10299 > URL: https://issues.apache.org/jira/browse/GEODE-10299 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Max Hufnagel >Assignee: Max Hufnagel >Priority: Major > Labels: pull-request-available > Attachments: CreateRegionCacheListener.java, CreateRegionFunction.java > > > The example on > [https://geode.apache.org/docs/guide/114/developing/region_options/dynamic_region_creation.html] > no longer works. The RegionAttributesImpl class was made not Serializable in > Geode 1.11 ([GEODE-7090|https://issues.apache.org/jira/browse/GEODE-7090]), > so instances can no longer be passed from the client to the server making > this function unusable from a client. > Barry Oglesby has created updated versions of the two classes (see attached). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10316) Convert the rest APIs to use plain spring rather than Spring Boot.
[ https://issues.apache.org/jira/browse/GEODE-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538512#comment-17538512 ] Patrick Johnsn commented on GEODE-10316: I've got it working without Spring Boot, but only by changing the `v1` in the URLs to `v3` because swagger-ui is trying to fetch configuration from `/geode/v3/api-docs/swagger-config` instead of `/geode/v1/api-docs/swagger-config`. This SHOULD be configurable with `springdoc.swagger-ui.configUrl`, but it doesn't seem to be having any effect. Changing `v1` to `v3` isn't ideal, so I'm going to continue looking for a way to make it use `v1`. I have a rough PR: https://github.com/apache/geode/pull/7701 > Convert the rest APIs to use plain spring rather than Spring Boot. > -- > > Key: GEODE-10316 > URL: https://issues.apache.org/jira/browse/GEODE-10316 > Project: Geode > Issue Type: Task > Components: rest (admin), rest (dev) >Affects Versions: 1.15.0 >Reporter: Patrick Johnsn >Assignee: Patrick Johnsn >Priority: Major > > Related to https://issues.apache.org/jira/browse/GEODE-10282, where Boot was > introduced. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-7739) JMX managers may fail to federate mbeans for other members
[ https://issues.apache.org/jira/browse/GEODE-7739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538509#comment-17538509 ] Geode Integration commented on GEODE-7739: -- Seen in [distributed-test-openjdk8 #367|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/367] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0222/test-results/distributedTest/1652752021/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.16.0-build.0222/test-artifacts/1652752021/distributedtestfiles-openjdk8-1.16.0-build.0222.tgz]. > JMX managers may fail to federate mbeans for other members > -- > > Key: GEODE-7739 > URL: https://issues.apache.org/jira/browse/GEODE-7739 > Project: Geode > Issue Type: Bug > Components: jmx >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > JMX Manager may fail to federate one or more MXBeans for other members > because of a race condition during startup. When ManagementCacheListener is > first constructed, it is in a state that will ignore all callbacks because > the field readyForEvents is false. > > Debugging with JMXMBeanReconnectDUnitTest revealed this bug. > The test starts two locators with jmx manager configured and started. > Locator1 always has all of locator2's mbeans, but locator2 is intermittently > missing the personal mbeans of locator1. > I think this is caused by some sort of race condition in the code that > creates the monitoring regions for other members in locator2. > It's possible that the jmx manager that hits this bug might fail to have > mbeans for servers as well as other locators but I haven't seen a test case > for this scenario. > The exposure of this bug means that a user running more than one locator > might have a locator that is missing one or more mbeans for the cluster. > > Studying the JMX code also reveals the existence of *GEODE-8012*. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10316) Convert the rest APIs to use plain spring rather than Spring Boot.
Patrick Johnsn created GEODE-10316: -- Summary: Convert the rest APIs to use plain spring rather than Spring Boot. Key: GEODE-10316 URL: https://issues.apache.org/jira/browse/GEODE-10316 Project: Geode Issue Type: Task Components: rest (admin), rest (dev) Affects Versions: 1.15.0 Reporter: Patrick Johnsn Related to https://issues.apache.org/jira/browse/GEODE-10282, where Boot was introduced. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10316) Convert the rest APIs to use plain spring rather than Spring Boot.
[ https://issues.apache.org/jira/browse/GEODE-10316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Johnsn reassigned GEODE-10316: -- Assignee: Patrick Johnsn > Convert the rest APIs to use plain spring rather than Spring Boot. > -- > > Key: GEODE-10316 > URL: https://issues.apache.org/jira/browse/GEODE-10316 > Project: Geode > Issue Type: Task > Components: rest (admin), rest (dev) >Affects Versions: 1.15.0 >Reporter: Patrick Johnsn >Assignee: Patrick Johnsn >Priority: Major > > Related to https://issues.apache.org/jira/browse/GEODE-10282, where Boot was > introduced. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-8254) JSONFormatter cannot parse JSON Arrays
[ https://issues.apache.org/jira/browse/GEODE-8254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Blum updated GEODE-8254: - Description: The Apache Geode [JSONFormatter|https://geode.apache.org/releases/latest/javadoc/org/apache/geode/pdx/JSONFormatter.html] class is not capable of parsing/processing JSON Arrays, making it less than adequate to process JSON documents and content. This leaves the responsibility and burden on the user, which requires the user to inspect the individual array elements. A test case reproducing this issue can be found [here|https://github.com/spring-projects/spring-boot-data-geode/blob/1.3.0.RELEASE/spring-geode/src/test/java/org/springframework/geode/data/json/JsonCacheDataImporterExporterIntegrationTests.java#L518-L543]. The matching JSON document is [here|https://github.com/spring-projects/spring-boot-data-geode/blob/1.3.0.RELEASE/spring-geode/src/test/resources/data-example-doefamily.json]. JSON Arrays are a very common JSON data type, as [specified|https://www.json.org/json-en.html]. was: The Apache Geode [JSONFormatter|https://geode.apache.org/releases/latest/javadoc/org/apache/geode/pdx/JSONFormatter.html] class is not capable of parsing/processing JSON Arrays, making it less than adequate to process JSON documents and content. This leaves the responsibility and burden on the user, which requires the user to inspect the individual array elements. A test case reproducing this issue can be found [here|https://geode.apache.org/releases/latest/javadoc/org/apache/geode/pdx/JSONFormatter.html]. The matching JSON document is [here|https://github.com/spring-projects/spring-boot-data-geode/blob/1.3.0.RELEASE/spring-geode/src/test/resources/data-example-doefamily.json]. JSON Arrays are a very common JSON data type, as [specified|https://www.json.org/json-en.html]. > JSONFormatter cannot parse JSON Arrays > -- > > Key: GEODE-8254 > URL: https://issues.apache.org/jira/browse/GEODE-8254 > Project: Geode > Issue Type: Bug > Components: serialization >Affects Versions: 1.9.2, 1.10.0, 1.11.0, 1.12.0 >Reporter: John Blum >Priority: Major > Labels: JSON-PDX > > The Apache Geode > [JSONFormatter|https://geode.apache.org/releases/latest/javadoc/org/apache/geode/pdx/JSONFormatter.html] > class is not capable of parsing/processing JSON Arrays, making it less than > adequate to process JSON documents and content. > This leaves the responsibility and burden on the user, which requires the > user to inspect the individual array elements. > A test case reproducing this issue can be found > [here|https://github.com/spring-projects/spring-boot-data-geode/blob/1.3.0.RELEASE/spring-geode/src/test/java/org/springframework/geode/data/json/JsonCacheDataImporterExporterIntegrationTests.java#L518-L543]. > The matching JSON document is > [here|https://github.com/spring-projects/spring-boot-data-geode/blob/1.3.0.RELEASE/spring-geode/src/test/resources/data-example-doefamily.json]. > JSON Arrays are a very common JSON data type, as > [specified|https://www.json.org/json-en.html]. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10287) DistributedRegion.distributedRegionCleanup logic looks wrong
[ https://issues.apache.org/jira/browse/GEODE-10287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-10287: -- Labels: (was: needsTriage) > DistributedRegion.distributedRegionCleanup logic looks wrong > > > Key: GEODE-10287 > URL: https://issues.apache.org/jira/browse/GEODE-10287 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Darrel Schneider >Assignee: Jinmei Liao >Priority: Major > > DistributedRegion.distributedRegionCleanup does this: distAdvisor.close(). > Then a few lines later it calls "waitForCurrentOperations()". But > waitForCurrentOperations uses the closed distAdvisor. Maybe it is okay to > uses a closed distAdvisor but it seems better to call wait first and then > close distAdvisor. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent
[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538333#comment-17538333 ] Nabarun Nag commented on GEODE-10294: - Backported to 1.15.0 > Need to consider invalid token when comparing value during putIfAbsent > -- > > Key: GEODE-10294 > URL: https://issues.apache.org/jira/browse/GEODE-10294 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.15.0, 1.16.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.15.0, 1.16.0 > > > During retry of putIfAbsent, there is a possibility that value has been > created by the initial operation. Geode treats this as a successful > operation, so that client initiated the operation will also create the entry > in its local cache. However, putIfAbsent of null is a special case, as an > Invalid Token is created instead of null value being put into the region > entry. Need to handle this special case for above value comparison. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent
[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-10294: Fix Version/s: 1.15.0 > Need to consider invalid token when comparing value during putIfAbsent > -- > > Key: GEODE-10294 > URL: https://issues.apache.org/jira/browse/GEODE-10294 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.15.0, 1.16.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.15.0, 1.16.0 > > > During retry of putIfAbsent, there is a possibility that value has been > created by the initial operation. Geode treats this as a successful > operation, so that client initiated the operation will also create the entry > in its local cache. However, putIfAbsent of null is a special case, as an > Invalid Token is created instead of null value being put into the region > entry. Need to handle this special case for above value comparison. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent
[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538332#comment-17538332 ] ASF subversion and git services commented on GEODE-10294: - Commit 1613857913ec3a10cfa1cdd816ff2f28f9fde3e1 in geode's branch refs/heads/support/1.15 from Eric Shu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1613857913 ] GEODE-10294: Compare invalid token during putIfAbsent retry. (#7679) * During putIfAbsent retry, comparing invalid token value when putIfAbsent of a null value instead. (cherry picked from commit 4f4af2a303142729708a951cc8a93f562c3de8bc) > Need to consider invalid token when comparing value during putIfAbsent > -- > > Key: GEODE-10294 > URL: https://issues.apache.org/jira/browse/GEODE-10294 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.15.0, 1.16.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.16.0 > > > During retry of putIfAbsent, there is a possibility that value has been > created by the initial operation. Geode treats this as a successful > operation, so that client initiated the operation will also create the entry > in its local cache. However, putIfAbsent of null is a special case, as an > Invalid Token is created instead of null value being put into the region > entry. Need to handle this special case for above value comparison. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent
[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nabarun Nag updated GEODE-10294: Affects Version/s: 1.15.0 1.16.0 > Need to consider invalid token when comparing value during putIfAbsent > -- > > Key: GEODE-10294 > URL: https://issues.apache.org/jira/browse/GEODE-10294 > Project: Geode > Issue Type: Bug > Components: regions >Affects Versions: 1.15.0, 1.16.0 >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: blocks-1.15.0, pull-request-available > Fix For: 1.16.0 > > > During retry of putIfAbsent, there is a possibility that value has been > created by the initial operation. Geode treats this as a successful > operation, so that client initiated the operation will also create the entry > in its local cache. However, putIfAbsent of null is a special case, as an > Invalid Token is created instead of null value being put into the region > entry. Need to handle this special case for above value comparison. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10306) CacheServerImpl should stop the acceptor immediately after stop is called
[
https://issues.apache.org/jira/browse/GEODE-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson resolved GEODE-10306.
-
Fix Version/s: 1.16.0
Resolution: Fixed
Moved up the acceptor close
> CacheServerImpl should stop the acceptor immediately after stop is called
> -
>
> Key: GEODE-10306
> URL: https://issues.apache.org/jira/browse/GEODE-10306
> Project: Geode
> Issue Type: Bug
>Reporter: Mark Hanson
>Assignee: Mark Hanson
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> Currently, after cache server stop is called, it takes a while for the
> acceptor to stop taking new data, which can be a problem because the bigger
> the window of time, the greater the risk of data loss.
>
> {noformat}
> public synchronized void stop() {
> if (!isRunning()) {
> return;
> }
> RuntimeException firstException = null;
> try {
> if (loadMonitor != null) {
> loadMonitor.stop();
> }
> } catch (RuntimeException e) {
> logger.warn("CacheServer - Error closing load monitor", e);
> firstException = e;
> }
> try {
> if (advisor != null) {
> advisor.close();
> }
> } catch (RuntimeException e) {
> logger.warn("CacheServer - Error closing advisor", e);
> firstException = e;
> }
> PROBLEM -> try {
> if (acceptor != null) {
> acceptor.close();
> }
> } catch (RuntimeException e) {
> logger.warn("CacheServer - Error closing acceptor monitor", e);
> if (firstException != null) {
> firstException = e;
> }
> } {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10308) CI Failure: Tomcat8SessionsClientServerDUnitTest.testSessionExpiration1 failed
[
https://issues.apache.org/jira/browse/GEODE-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-10308:
--
Affects Version/s: 1.16.0
> CI Failure: Tomcat8SessionsClientServerDUnitTest.testSessionExpiration1 failed
> --
>
> Key: GEODE-10308
> URL: https://issues.apache.org/jira/browse/GEODE-10308
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.16.0
>Reporter: Eric Shu
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> org.apache.geode.cache.CacheClosedException: The cache is closed.
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5207)
> at
> org.apache.geode.internal.cache.LocalRegion$Stopper.generateCancelledException(LocalRegion.java:11342)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:87)
> at
> org.apache.geode.internal.cache.execute.InternalFunctionExecutionServiceImpl.onRegion(InternalFunctionExecutionServiceImpl.java:122)
> at
> org.apache.geode.cache.execute.FunctionService.onRegion(FunctionService.java:79)
> at
> org.apache.geode.modules.session.catalina.ClientServerSessionCache.getExecutionForFunctionOnRegionWithFilter(ClientServerSessionCache.java:283)
> at
> org.apache.geode.modules.session.catalina.ClientServerSessionCache.touchSessions(ClientServerSessionCache.java:101)
> at
> org.apache.geode.modules.session.catalina.DeltaSessionManager$1.run(DeltaSessionManager.java:534)
> at java.util.TimerThread.mainLoop(Timer.java:556)
> at java.util.TimerThread.run(Timer.java:506)
> {noformat}
> Artifacts can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk11/builds/334
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10305) CI Failure: TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest failed
[
https://issues.apache.org/jira/browse/GEODE-10305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-10305:
--
Affects Version/s: 1.16.0
> CI Failure:
> TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest
> failed
> -
>
> Key: GEODE-10305
> URL: https://issues.apache.org/jira/browse/GEODE-10305
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.16.0
>Reporter: Eric Shu
>Priority: Major
> Labels: needsTriage
>
> {noformat}
> org.gradle.internal.exceptions.DefaultMultiCauseException: Multiple Failures
> (2 failures)
> org.opentest4j.AssertionFailedError: [The Cache Server process
> terminated unexpectedly with exit status 1. Please refer to the log file in
> /tmp/junit439159077415808630/server for full details.
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/tmp/geode_container_install8549633813411705254/cargo_containers/Tomcat8AndCurrentModules/tomcat-8.5.66/apache-tomcat-8.5.66/lib/slf4j-jdk14-1.7.32.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/home/geode/geode/geode-assembly/build/install/apache-geode/lib/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.JDK14LoggerFactory]
> {noformat}
> This is caused by ForcedDisconnectException during cache creation.
> {noformat}
> Exception in thread "main"
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on
> heavy-lifter-e2fd6dd2-c530-54ef-ab7c-b95e0e8cca34(server:240126):41036
> started at Thu May 05 21:36:30 UTC 2022: Member isn't responding to heartbeat
> requests, caused by org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:2899)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:1183)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:5201)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.cache.query.cq.internal.CqServiceImpl.(CqServiceImpl.java:166)
> at
> org.apache.geode.cache.query.cq.internal.CqServiceFactoryImpl.create(CqServiceFactoryImpl.java:59)
> at
> org.apache.geode.cache.query.internal.cq.CqServiceProvider.create(CqServiceProvider.java:63)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:1004)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:864)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52)
> at
> org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:913)
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:814)
> at
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:740)
> at
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:259)
> Caused by: org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.DistributionImpl$LifecycleListenerImpl.forcedDisconnect(DistributionImpl.java:941)
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$uncleanShutdownDS$0(GMSMembership.java:1792)
> at java.lang.Thread.run(Thread.java:750)
> {noformat}
> Artifacts can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/upgrade-test-openjdk8/builds/331
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (GEODE-10315) remove unneeded add-opens from MemberJvmOptions
[ https://issues.apache.org/jira/browse/GEODE-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10315: --- Labels: Java17 pull-request-available (was: Java17) > remove unneeded add-opens from MemberJvmOptions > --- > > Key: GEODE-10315 > URL: https://issues.apache.org/jira/browse/GEODE-10315 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: Java17, pull-request-available > > Currently when gfsh starts a locator or server it will do an add-opens of > java.management/sun.management=ALL-UNNAMED. It turns out geode does not need > this package to be opened so this one should be removed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10315) remove unneeded add-opens from MemberJvmOptions
[ https://issues.apache.org/jira/browse/GEODE-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-10315: - Affects Version/s: 1.15.0 > remove unneeded add-opens from MemberJvmOptions > --- > > Key: GEODE-10315 > URL: https://issues.apache.org/jira/browse/GEODE-10315 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.15.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: Java17 > > Currently when gfsh starts a locator or server it will do an add-opens of > java.management/sun.management=ALL-UNNAMED. It turns out geode does not need > this package to be opened so this one should be removed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (GEODE-10315) remove unneeded add-opens from MemberJvmOptions
[ https://issues.apache.org/jira/browse/GEODE-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-10315: Assignee: Darrel Schneider > remove unneeded add-opens from MemberJvmOptions > --- > > Key: GEODE-10315 > URL: https://issues.apache.org/jira/browse/GEODE-10315 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: Java17 > > Currently when gfsh starts a locator or server it will do an add-opens of > java.management/sun.management=ALL-UNNAMED. It turns out geode does not need > this package to be opened so this one should be removed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10315) remove unneeded add-opens from MemberJvmOptions
[ https://issues.apache.org/jira/browse/GEODE-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-10315: - Labels: Java17 (was: needsTriage) > remove unneeded add-opens from MemberJvmOptions > --- > > Key: GEODE-10315 > URL: https://issues.apache.org/jira/browse/GEODE-10315 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Darrel Schneider >Priority: Major > Labels: Java17 > > Currently when gfsh starts a locator or server it will do an add-opens of > java.management/sun.management=ALL-UNNAMED. It turns out geode does not need > this package to be opened so this one should be removed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10315) remove unneeded add-opens from MemberJvmOptions
[ https://issues.apache.org/jira/browse/GEODE-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10315: -- Labels: needsTriage (was: ) > remove unneeded add-opens from MemberJvmOptions > --- > > Key: GEODE-10315 > URL: https://issues.apache.org/jira/browse/GEODE-10315 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Darrel Schneider >Priority: Major > Labels: needsTriage > > Currently when gfsh starts a locator or server it will do an add-opens of > java.management/sun.management=ALL-UNNAMED. It turns out geode does not need > this package to be opened so this one should be removed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GEODE-10315) remove unneeded add-opens from MemberJvmOptions
Darrel Schneider created GEODE-10315: Summary: remove unneeded add-opens from MemberJvmOptions Key: GEODE-10315 URL: https://issues.apache.org/jira/browse/GEODE-10315 Project: Geode Issue Type: Bug Components: gfsh Reporter: Darrel Schneider Currently when gfsh starts a locator or server it will do an add-opens of java.management/sun.management=ALL-UNNAMED. It turns out geode does not need this package to be opened so this one should be removed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (GEODE-10313) User Guide: Add javadocs template variable
[ https://issues.apache.org/jira/browse/GEODE-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-10313. - Fix Version/s: 1.15.0 1.16.0 Resolution: Fixed > User Guide: Add javadocs template variable > -- > > Key: GEODE-10313 > URL: https://issues.apache.org/jira/browse/GEODE-10313 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0, 1.16.0 > > > Improve User Guide publishing flexibility by incorporating a 'javadocs' > template variable in place of hard-coded path to the API docs. > Affected files: > geode-book/config.yml > geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb > geode-docs/developing/gemfire_data_serialization.html.md.erb > geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb > geode-docs/developing/events/implementing_write_behind_event_handler.html.md.erb > geode-docs/developing/function_exec/function_execution.html.md.erb > geode-docs/developing/query_additional/using_query_bind_parameters.html.md.erb > geode-docs/developing/query_index/maintaining_indexes.html.md.erb > geode-docs/developing/query_select/the_select_statement.html.md.erb > geode-docs/developing/querying_basics/querying_partitioned_regions.html.md.erb > geode-docs/developing/querying_basics/running_a_query.html.md.erb > geode-docs/getting_started/querying_quick_reference.html.md.erb -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10313) User Guide: Add javadocs template variable
[ https://issues.apache.org/jira/browse/GEODE-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538297#comment-17538297 ] ASF subversion and git services commented on GEODE-10313: - Commit 4d5356665868d46a0417a5bbd9902de047b3f07d in geode's branch refs/heads/support/1.15 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4d53566658 ] GEODE-10313: User Guide: Add javadocs template variable (#7696) > User Guide: Add javadocs template variable > -- > > Key: GEODE-10313 > URL: https://issues.apache.org/jira/browse/GEODE-10313 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Improve User Guide publishing flexibility by incorporating a 'javadocs' > template variable in place of hard-coded path to the API docs. > Affected files: > geode-book/config.yml > geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb > geode-docs/developing/gemfire_data_serialization.html.md.erb > geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb > geode-docs/developing/events/implementing_write_behind_event_handler.html.md.erb > geode-docs/developing/function_exec/function_execution.html.md.erb > geode-docs/developing/query_additional/using_query_bind_parameters.html.md.erb > geode-docs/developing/query_index/maintaining_indexes.html.md.erb > geode-docs/developing/query_select/the_select_statement.html.md.erb > geode-docs/developing/querying_basics/querying_partitioned_regions.html.md.erb > geode-docs/developing/querying_basics/running_a_query.html.md.erb > geode-docs/getting_started/querying_quick_reference.html.md.erb -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GEODE-10312) Remove SpringBootApplication In SwaggerConfig
[
https://issues.apache.org/jira/browse/GEODE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538218#comment-17538218
]
Juan Ramos commented on GEODE-10312:
Another side effect of the change is that the automatically generated
{{swagger}} docs are not "sorted" anymore. Not a deal breaker, sure, but it
might cause headaches for customers interacting with the REST API using clients
automatically generated (through the {{swagger-codegen-cli}} as an example).
I've done some local tests and adding the configuration property
[writer-with-order-by-keys|https://springdoc.org/index.html#springdoc-openapi-core-properties],
both to
[geode-web-api/src/main/resources/swagger.properties|https://github.com/apache/geode/blob/develop/geode-web-api/src/main/resources/swagger.properties]
and
[geode-web-management/src/main/resources/swagger-management.properties|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/resources/swagger-management.properties],
seems to fix this.
> Remove SpringBootApplication In SwaggerConfig
> -
>
> Key: GEODE-10312
> URL: https://issues.apache.org/jira/browse/GEODE-10312
> Project: Geode
> Issue Type: Bug
> Components: locator, rest (admin), rest (dev)
>Affects Versions: 1.15.0
>Reporter: Juan Ramos
>Priority: Major
> Labels: blocks-1.15.0
> Attachments: GEODE-10312.zip
>
>
> The issue was introduced by GEODE-10282. As part of commit
> [41305de1405c2125142e6b337c3f1704f736fca4|https://github.com/apache/geode/commit/41305de1405c2125142e6b337c3f1704f736fca4],
> {{SwaggerConfig}} classes used to start and configure the internal
> {{geode-web-management}} and {{geode-web-api}} services use the
> {{@SpringBootApplication}} annotation. This annotation automatically enables
> other spring annotations (like {{@EnableAutoConfiguration}} and
> {{@ComponentScan}}) which, in turn, might cause critical issues during
> startup as {{spring}} tries to automatically configure several services based
> on classes and interfaces found within the member's class path.
> ---
> I'm attaching a small scenario that reproduces the problem; the
> {{reproduce.sh}} script simply starts a locator making sure that the
> {{spring-jdbc-5.3.20.jar}} is part of the class path. When using any commit
> after
> [41305de1405c2125142e6b337c3f1704f736fca4|https://github.com/apache/geode/commit/41305de1405c2125142e6b337c3f1704f736fca4]
> the logs will contain the following:
> {noformat}
> [info 2022/05/16 15:54:38.997 IST locator0 tid=0x1] Adding webapp
> /management
> [info 2022/05/16 15:54:39.610 IST locator0 tid=0x1] Initializing
> Servlet 'management'
> [info 2022/05/16 15:54:42.124 IST locator0 tid=0x1] Will secure any
> request with
> [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@33ed6546,
>
> org.springframework.security.web.context.SecurityContextPersistenceFilter@5a503cf0,
> org.springframework.security.web.header.HeaderWriterFilter@5b04224a,
> org.springframework.security.web.authentication.logout.LogoutFilter@17db90a7,
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter@6f78c132,
>
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@42f9b425,
>
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter@54d62c35,
> org.springframework.security.web.session.SessionManagementFilter@78907a46,
> org.springframework.security.web.access.ExceptionTranslationFilter@eaf3dd0,
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor@7cd6b76a]
> [warn 2022/05/16 15:54:42.975 IST locator0 tid=0x1] Exception
> encountered during context initialization - cancelling refresh attempt:
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'dataSource' defined in class path resource
> [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]:
> Unsatisfied dependency expressed through method 'dataSource' parameter 0;
> nested exception is org.springframework.beans.factory.BeanCreationException:
> Error creating bean with name
> 'spring.datasource-org.springframework.boot.autoconfigure.jdbc.DataSourceProperties':
> Invocation of init method failed; nested exception is
> java.lang.NoClassDefFoundError: org/springframework/dao/DataAccessException
> [error 2022/05/16 15:54:42.980 IST locator0 tid=0x1] Context
> initialization failed
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'dataSource' defined in class path resource
> [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]:
> Unsatisfied dependency expressed through method 'dataSource' parameter 0;
>
[jira] (GEODE-10312) Remove SpringBootApplication In SwaggerConfig
[ https://issues.apache.org/jira/browse/GEODE-10312 ]
Juan Ramos deleted comment on GEODE-10312:
was (Author: jujoramos):
Another side effect of the change is that the automatically generated
{{swagger}} docs are not "sorted" anymore. Not a deal breaker, sure, but it
might cause headaches for customers interacting with the REST API using clients
automatically generated (through the {{swagger-codegen-cli}} as an example).
I've done some local tests and adding the configuration property
[writer-with-order-by-keys|https://springdoc.org/index.html#springdoc-openapi-core-properties],
both to
[geode-web-api/src/main/resources/swagger.properties|https://github.com/apache/geode/blob/develop/geode-web-api/src/main/resources/swagger.properties]
and
[geode-web-management/src/main/resources/swagger-management.properties|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/resources/swagger-management.properties],
seems to fix this.
> Remove SpringBootApplication In SwaggerConfig
> -
>
> Key: GEODE-10312
> URL: https://issues.apache.org/jira/browse/GEODE-10312
> Project: Geode
> Issue Type: Bug
> Components: locator, rest (admin), rest (dev)
>Affects Versions: 1.15.0
>Reporter: Juan Ramos
>Priority: Major
> Labels: blocks-1.15.0
> Attachments: GEODE-10312.zip
>
>
> The issue was introduced by GEODE-10282. As part of commit
> [41305de1405c2125142e6b337c3f1704f736fca4|https://github.com/apache/geode/commit/41305de1405c2125142e6b337c3f1704f736fca4],
> {{SwaggerConfig}} classes used to start and configure the internal
> {{geode-web-management}} and {{geode-web-api}} services use the
> {{@SpringBootApplication}} annotation. This annotation automatically enables
> other spring annotations (like {{@EnableAutoConfiguration}} and
> {{@ComponentScan}}) which, in turn, might cause critical issues during
> startup as {{spring}} tries to automatically configure several services based
> on classes and interfaces found within the member's class path.
> ---
> I'm attaching a small scenario that reproduces the problem; the
> {{reproduce.sh}} script simply starts a locator making sure that the
> {{spring-jdbc-5.3.20.jar}} is part of the class path. When using any commit
> after
> [41305de1405c2125142e6b337c3f1704f736fca4|https://github.com/apache/geode/commit/41305de1405c2125142e6b337c3f1704f736fca4]
> the logs will contain the following:
> {noformat}
> [info 2022/05/16 15:54:38.997 IST locator0 tid=0x1] Adding webapp
> /management
> [info 2022/05/16 15:54:39.610 IST locator0 tid=0x1] Initializing
> Servlet 'management'
> [info 2022/05/16 15:54:42.124 IST locator0 tid=0x1] Will secure any
> request with
> [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@33ed6546,
>
> org.springframework.security.web.context.SecurityContextPersistenceFilter@5a503cf0,
> org.springframework.security.web.header.HeaderWriterFilter@5b04224a,
> org.springframework.security.web.authentication.logout.LogoutFilter@17db90a7,
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter@6f78c132,
>
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@42f9b425,
>
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter@54d62c35,
> org.springframework.security.web.session.SessionManagementFilter@78907a46,
> org.springframework.security.web.access.ExceptionTranslationFilter@eaf3dd0,
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor@7cd6b76a]
> [warn 2022/05/16 15:54:42.975 IST locator0 tid=0x1] Exception
> encountered during context initialization - cancelling refresh attempt:
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'dataSource' defined in class path resource
> [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]:
> Unsatisfied dependency expressed through method 'dataSource' parameter 0;
> nested exception is org.springframework.beans.factory.BeanCreationException:
> Error creating bean with name
> 'spring.datasource-org.springframework.boot.autoconfigure.jdbc.DataSourceProperties':
> Invocation of init method failed; nested exception is
> java.lang.NoClassDefFoundError: org/springframework/dao/DataAccessException
> [error 2022/05/16 15:54:42.980 IST locator0 tid=0x1] Context
> initialization failed
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'dataSource' defined in class path resource
> [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]:
> Unsatisfied dependency expressed through method 'dataSource' parameter 0;
> nested exception is
[jira] [Commented] (GEODE-10312) Remove SpringBootApplication In SwaggerConfig
[
https://issues.apache.org/jira/browse/GEODE-10312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538208#comment-17538208
]
Juan Ramos commented on GEODE-10312:
Another side effect of the change is that the automatically generated
{{swagger}} docs are not "sorted" anymore. Not a deal breaker, sure, but it
might cause headaches for customers interacting with the REST API using clients
automatically generated (through the {{swagger-codegen-cli}} as an example).
I've done some local tests and adding the configuration property
[writer-with-order-by-keys|https://springdoc.org/index.html#springdoc-openapi-core-properties],
both to
[geode-web-api/src/main/resources/swagger.properties|https://github.com/apache/geode/blob/develop/geode-web-api/src/main/resources/swagger.properties]
and
[geode-web-management/src/main/resources/swagger-management.properties|https://github.com/apache/geode/blob/develop/geode-web-management/src/main/resources/swagger-management.properties],
seems to fix this.
> Remove SpringBootApplication In SwaggerConfig
> -
>
> Key: GEODE-10312
> URL: https://issues.apache.org/jira/browse/GEODE-10312
> Project: Geode
> Issue Type: Bug
> Components: locator, rest (admin), rest (dev)
>Affects Versions: 1.15.0
>Reporter: Juan Ramos
>Priority: Major
> Labels: blocks-1.15.0
> Attachments: GEODE-10312.zip
>
>
> The issue was introduced by GEODE-10282. As part of commit
> [41305de1405c2125142e6b337c3f1704f736fca4|https://github.com/apache/geode/commit/41305de1405c2125142e6b337c3f1704f736fca4],
> {{SwaggerConfig}} classes used to start and configure the internal
> {{geode-web-management}} and {{geode-web-api}} services use the
> {{@SpringBootApplication}} annotation. This annotation automatically enables
> other spring annotations (like {{@EnableAutoConfiguration}} and
> {{@ComponentScan}}) which, in turn, might cause critical issues during
> startup as {{spring}} tries to automatically configure several services based
> on classes and interfaces found within the member's class path.
> ---
> I'm attaching a small scenario that reproduces the problem; the
> {{reproduce.sh}} script simply starts a locator making sure that the
> {{spring-jdbc-5.3.20.jar}} is part of the class path. When using any commit
> after
> [41305de1405c2125142e6b337c3f1704f736fca4|https://github.com/apache/geode/commit/41305de1405c2125142e6b337c3f1704f736fca4]
> the logs will contain the following:
> {noformat}
> [info 2022/05/16 15:54:38.997 IST locator0 tid=0x1] Adding webapp
> /management
> [info 2022/05/16 15:54:39.610 IST locator0 tid=0x1] Initializing
> Servlet 'management'
> [info 2022/05/16 15:54:42.124 IST locator0 tid=0x1] Will secure any
> request with
> [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@33ed6546,
>
> org.springframework.security.web.context.SecurityContextPersistenceFilter@5a503cf0,
> org.springframework.security.web.header.HeaderWriterFilter@5b04224a,
> org.springframework.security.web.authentication.logout.LogoutFilter@17db90a7,
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter@6f78c132,
>
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@42f9b425,
>
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter@54d62c35,
> org.springframework.security.web.session.SessionManagementFilter@78907a46,
> org.springframework.security.web.access.ExceptionTranslationFilter@eaf3dd0,
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor@7cd6b76a]
> [warn 2022/05/16 15:54:42.975 IST locator0 tid=0x1] Exception
> encountered during context initialization - cancelling refresh attempt:
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'dataSource' defined in class path resource
> [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]:
> Unsatisfied dependency expressed through method 'dataSource' parameter 0;
> nested exception is org.springframework.beans.factory.BeanCreationException:
> Error creating bean with name
> 'spring.datasource-org.springframework.boot.autoconfigure.jdbc.DataSourceProperties':
> Invocation of init method failed; nested exception is
> java.lang.NoClassDefFoundError: org/springframework/dao/DataAccessException
> [error 2022/05/16 15:54:42.980 IST locator0 tid=0x1] Context
> initialization failed
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'dataSource' defined in class path resource
> [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]:
> Unsatisfied dependency expressed through method 'dataSource' parameter 0;
>
[jira] [Commented] (GEODE-10313) User Guide: Add javadocs template variable
[ https://issues.apache.org/jira/browse/GEODE-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17538203#comment-17538203 ] ASF subversion and git services commented on GEODE-10313: - Commit cbd8795bc30dd595b6956b957301167f2f0ac5d5 in geode's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=cbd8795bc3 ] GEODE-10313: User Guide: Add javadocs template variable (#7696) > User Guide: Add javadocs template variable > -- > > Key: GEODE-10313 > URL: https://issues.apache.org/jira/browse/GEODE-10313 > Project: Geode > Issue Type: Improvement > Components: docs >Affects Versions: 1.14.4 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Improve User Guide publishing flexibility by incorporating a 'javadocs' > template variable in place of hard-coded path to the API docs. > Affected files: > geode-book/config.yml > geode-docs/developing/data_serialization/extending_the_autoserializer.html.md.erb > geode-docs/developing/gemfire_data_serialization.html.md.erb > geode-docs/developing/events/configuring_gateway_concurrency_levels.html.md.erb > geode-docs/developing/events/implementing_write_behind_event_handler.html.md.erb > geode-docs/developing/function_exec/function_execution.html.md.erb > geode-docs/developing/query_additional/using_query_bind_parameters.html.md.erb > geode-docs/developing/query_index/maintaining_indexes.html.md.erb > geode-docs/developing/query_select/the_select_statement.html.md.erb > geode-docs/developing/querying_basics/querying_partitioned_regions.html.md.erb > geode-docs/developing/querying_basics/running_a_query.html.md.erb > geode-docs/getting_started/querying_quick_reference.html.md.erb -- This message was sent by Atlassian Jira (v8.20.7#820007)
