[jira] [Assigned] (GEODE-6070) CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
[
https://issues.apache.org/jira/browse/GEODE-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Lindsey reassigned GEODE-6070:
Assignee: (was: Aaron Lindsey)
> CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
> --
>
> Key: GEODE-6070
> URL: https://issues.apache.org/jira/browse/GEODE-6070
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Priority: Major
> Labels: GeodeCommons
>
> Failed with stacktrace:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest
> > testShutdownAll FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 302
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.3(server-1:496):41002 started at Thu Nov
> 15 19:47:58 UTC 2018: Message distribution has terminated
> {noformat}
> Test results can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-results/distributedTest/1542315851/classes/org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest.html#testShutdownAll
>
> Test Artifacts can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-artifacts/1542315851/distributedtestfiles-OpenJDK8-1.9.0-build.158.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7257) Minimize test usage of log4j-core and log4j-core:tests
[ https://issues.apache.org/jira/browse/GEODE-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942374#comment-16942374 ] ASF subversion and git services commented on GEODE-7257: Commit f452b9b96010eb1eabbc301de7c43268b9066f86 in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f452b9b ] GEODE-7257: Remove unnecessary uses of log4j-core (#4098) Reimplement tests without using log4j-core: * ManagementRequestLoggingDistributedTest * GfshParserAutoCompletionIntegrationTest * GoldenTestCase Remove log4j-core and log4j-core:tests dependencies from: * geode-assembly * geode-junit * geode-pulse * geode-serialization > Minimize test usage of log4j-core and log4j-core:tests > -- > > Key: GEODE-7257 > URL: https://issues.apache.org/jira/browse/GEODE-7257 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The following test classes use log4j-core and log4j-core:tests but could > easily be reimplemented to not depend on log4j-core: > * ManagementRequestLoggingDUnitTest > * GfshParserAutoCompletionTest > * GoldenTestCase > These geode modules declare dependency on log4j-core and log4j-core:tests but > could remove it if the above files are changed: > * geode-junit > * geode-pulse > * geode-serialization > * geode-assembly -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942304#comment-16942304
]
Barrett Oglesby commented on GEODE-7258:
The function doesn't have to do anything, but it requires optimizeForWrite
returning true.
I used this function in my tests.
{noformat}
import org.apache.geode.cache.Declarable;
import org.apache.geode.cache.execute.Function;
import org.apache.geode.cache.execute.FunctionContext;
public class TestFunction implements Function, Declarable {
public void execute(FunctionContext context) {
context.getResultSender().lastResult(true);
}
public String getId() {
return getClass().getSimpleName();
}
public boolean optimizeForWrite() {
return true;
}
}
{noformat}
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> --
>
> Key: GEODE-7258
> URL: https://issues.apache.org/jira/browse/GEODE-7258
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Attachments: runsWithFineLevelLogging.zip
>
>
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> This test is failing repeatedly. The logs do not to my eyes indicate what is
> the source of the problem.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1112]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1113]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-results/upgradeTest/1569861659/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-artifacts/1569861659/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0169.tgz
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-results/upgradeTest/1569863814/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-artifacts/1569863814/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0170.tgz
>
> {noformat}
> Task :geode-lucene:upgradeTest
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated$$Lambda$172/0x0008407b2440.run
> in VM 3 running on Host 38006782570a with 4 VMs with version 1.10.0
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> java.lang.reflect.InvocationTargetException
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:381)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.lambda$test$c93719d5$2(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create a
> new connection to server 38006782570a:24478
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:209)
> at
>
[jira] [Commented] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942303#comment-16942303
]
Barrett Oglesby commented on GEODE-7258:
I've seen it fail in both of these ways:
{noformat}
Exception in thread "main" org.apache.geode.cache.execute.FunctionException:
org.apache.geode.cache.client.ServerConnectivityException: Could not create a
new connection to server 192.168.1.4:57095
at
org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:231)
at
org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:179)
at
org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:377)
Caused by: org.apache.geode.cache.client.ServerConnectivityException: Could not
create a new connection to server 192.168.1.4:57095
at
org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:324)
at
org.apache.geode.cache.client.internal.pooling.ConnectionManagerImpl.borrowConnection(ConnectionManagerImpl.java:70)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:326)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOn(OpExecutorImpl.java:300)
at
org.apache.geode.cache.client.internal.PoolImpl.executeOn(PoolImpl.java:814)
at
org.apache.geode.cache.client.internal.SingleHopOperationCallable.call(SingleHopOperationCallable.java:52)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
{noformat}
{noformat}
Exception in thread "main" org.apache.geode.cache.execute.FunctionException:
org.apache.geode.cache.client.ServerConnectivityException: Pool unexpected
closed socket on server connection=Pooled Connection to 192.168.1.4:57539:
Connection[DESTROYED]). Server unreachable: could not connect after 1 attempts
at
org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:231)
at
org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:179)
at
org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:377)
Caused by: org.apache.geode.cache.client.ServerConnectivityException: Pool
unexpected closed socket on server connection=Pooled Connection to
192.168.1.4:57539: Connection[DESTROYED]). Server unreachable: could not
connect after 1 attempts
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:331)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOn(OpExecutorImpl.java:300)
at
org.apache.geode.cache.client.internal.PoolImpl.executeOn(PoolImpl.java:813)
at
org.apache.geode.cache.client.internal.SingleHopOperationCallable.call(SingleHopOperationCallable.java:52)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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.io.EOFException: The connection has been reset while reading
the header
at
org.apache.geode.internal.cache.tier.sockets.Message.fetchHeader(Message.java:832)
at
org.apache.geode.internal.cache.tier.sockets.ChunkedMessage.readHeader(ChunkedMessage.java:197)
at
org.apache.geode.cache.client.internal.ExecuteRegionFunctionSingleHopOp$ExecuteRegionFunctionSingleHopOpImpl.processResponse(ExecuteRegionFunctionSingleHopOp.java:261)
at
org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:222)
at
org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:195)
at
org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:382)
at
org.apache.geode.cache.client.internal.AbstractOpWithTimeout.attempt(AbstractOpWithTimeout.java:45)
at
org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263)
at
org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:353)
[jira] [Commented] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942302#comment-16942302
]
Barrett Oglesby commented on GEODE-7258:
I ran a few tests on this issue as well. This issue can be reproduced without
any rolling behavior with a test like:
- start 2 servers with a PARTITION_REDUNDANT region
- run a client that:
- does a put into each bucket
- executes onRegion function
- sleeps
- executes onRegion function
Stop one of the servers during the client sleep, and the second onRegion
function will fail.
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> --
>
> Key: GEODE-7258
> URL: https://issues.apache.org/jira/browse/GEODE-7258
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Attachments: runsWithFineLevelLogging.zip
>
>
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> This test is failing repeatedly. The logs do not to my eyes indicate what is
> the source of the problem.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1112]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1113]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-results/upgradeTest/1569861659/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-artifacts/1569861659/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0169.tgz
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-results/upgradeTest/1569863814/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-artifacts/1569863814/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0170.tgz
>
> {noformat}
> Task :geode-lucene:upgradeTest
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated$$Lambda$172/0x0008407b2440.run
> in VM 3 running on Host 38006782570a with 4 VMs with version 1.10.0
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> java.lang.reflect.InvocationTargetException
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:381)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.lambda$test$c93719d5$2(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create a
> new connection to server 38006782570a:24478
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:209)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:152)
> at
>
[jira] [Assigned] (GEODE-6070) CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
[
https://issues.apache.org/jira/browse/GEODE-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Lindsey reassigned GEODE-6070:
Assignee: Aaron Lindsey
> CI Failure: ShutdownCommandOverHttpDUnitTest > testShutdownAll
> --
>
> Key: GEODE-6070
> URL: https://issues.apache.org/jira/browse/GEODE-6070
> Project: Geode
> Issue Type: Bug
>Reporter: Helena Bales
>Assignee: Aaron Lindsey
>Priority: Major
> Labels: GeodeCommons
>
> Failed with stacktrace:
> {noformat}
> org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest
> > testShutdownAll FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 302
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.3(server-1:496):41002 started at Thu Nov
> 15 19:47:58 UTC 2018: Message distribution has terminated
> {noformat}
> Test results can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-results/distributedTest/1542315851/classes/org.apache.geode.management.internal.cli.commands.ShutdownCommandOverHttpDUnitTest.html#testShutdownAll
>
> Test Artifacts can be found here:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.158/test-artifacts/1542315851/distributedtestfiles-OpenJDK8-1.9.0-build.158.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7260) Publish latest version of documentation in web
[
https://issues.apache.org/jira/browse/GEODE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942245#comment-16942245
]
Joey McAllister commented on GEODE-7260:
That's a great catch, Alberto. I agree that that is unclear and should be
corrected, but I think the correction should be to change the wording in the
README, rather than following the current wording by publishing documentation
that does not yet have a release associated with it. Doing that would create a
lot of maintenance (and potential for breakage) between the website and the
documentation.
If we agreed to publish pre-release documentation to the website, that would
require anyone who ever made a change to the documentation to manually push to
the website. (Updating the website is a manual activity.) If they forgot or
just didn't do it, then the pre-release docs on the website would fall behind
the actual pre-release docs.
Currently, anyone can build the pre-release documentation locally and, so long
as they have pulled all the latest check-ins from the repo, they can be sure
that they're seeing the latest documentation. This is similar to how the code
part of the product works, and I think it makes sense to keep it that way.
I definitely think we should more clearly state in the geode-book README that
what is built and published to the website ("latest") is the documentation for
the most recent release, rather than unfinished documentation (which is still
available to build locally). What do you think about that as a fix?
> Publish latest version of documentation in web
> --
>
> Key: GEODE-7260
> URL: https://issues.apache.org/jira/browse/GEODE-7260
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Alberto Bustamante Reyes
>Priority: Major
>
> Following sentence is stated in [README file of
> geode-book|https://github.com/apache/geode/tree/develop/geode-book] :
> {code}
> The latest check-ins to {geode-project-dir}/geode-docs on the develop branch
> are regularly built and published to http://geode.apache.org/docs/.
> {code}
> Currently in the web page there are only links to the documentation of
> official releases.
> I think it would be useful to publish the latest version of documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7263) Geode Native: Dockerfile for building the user guide needs updating
Dave Barnes created GEODE-7263: -- Summary: Geode Native: Dockerfile for building the user guide needs updating Key: GEODE-7263 URL: https://issues.apache.org/jira/browse/GEODE-7263 Project: Geode Issue Type: Bug Components: docs, native client Reporter: Dave Barnes We provide a Docker file for building the Native Client User Guide ( geode-native/docs/docker ). When I follow README instructions, I get errors regarding unrecognized addresses and out-of-date components. A sample: gpg: directory '/root/.gnupg' created gpg: keybox '/root/.gnupg/pubring.kbx' created gpg: keyserver receive failed: Cannot assign requested address gpg: keyserver receive failed: No data gpg: key 105BD0E739499BDB: 7 signatures not checked due to missing keys gpg: /root/.gnupg/trustdb.gpg: trustdb created gpg: key 105BD0E739499BDB: public key "Piotr Kuczynski " imported gpg: key 3804BB82D39DC0E3: 106 signatures not checked due to missing keys gpg: key 3804BB82D39DC0E3: public key "Michal Papis (RVM signing) " imported gpg: no ultimately trusted keys found gpg: Total number processed: 2 gpg: imported: 2 ... Step 6/13 : RUN /bin/bash -l -c "rvm requirements" ---> Running in 10c01ef4a95e mesg: ttyname failed: Inappropriate ioctl for device ... Please be aware that you just installed a ruby that requires 3 patches just to be compiled on an up to date linux system. This may have known and unaccounted for security vulnerabilities. Please consider upgrading to ruby-2.6.5 which will have all of the latest security patches. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt updated GEODE-7258:
--
Attachment: runsWithFineLevelLogging.zip
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> --
>
> Key: GEODE-7258
> URL: https://issues.apache.org/jira/browse/GEODE-7258
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Attachments: runsWithFineLevelLogging.zip
>
>
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> This test is failing repeatedly. The logs do not to my eyes indicate what is
> the source of the problem.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1112]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1113]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-results/upgradeTest/1569861659/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-artifacts/1569861659/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0169.tgz
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-results/upgradeTest/1569863814/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-artifacts/1569863814/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0170.tgz
>
> {noformat}
> Task :geode-lucene:upgradeTest
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated$$Lambda$172/0x0008407b2440.run
> in VM 3 running on Host 38006782570a with 4 VMs with version 1.10.0
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> java.lang.reflect.InvocationTargetException
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:381)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.lambda$test$c93719d5$2(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create a
> new connection to server 38006782570a:24478
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:209)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:152)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:379)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.waitUntilFlushed(LuceneServiceImpl.java:658)
> ... 6 more
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create
> a new connection to server 38006782570a:24478
> 108 tests completed, 1 failed
> > Task :geode-lucene:upgradeTest
[jira] [Commented] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942236#comment-16942236
]
Bruce J Schuchardt commented on GEODE-7258:
---
I ran this test with 1.9.1 and 1.10.0 with fine-level logging and observed a
change in behavior in the client cache. There was some refactoring done this
summer in client function execution and that may be the cause of this failure.
In 1.9.1 the client invoked waitUntilFlushed and the single-hop function op
tried to send it to two servers. One of the servers was shut down and
connection formation failed. The client waited for the other server to respond
and then returned to the caller without throwing an exception.
In 1.10.0 the client invoked waitUntilFlushed and the single-hop function op
tried to send it to two servers. As in 1.9.1 one of the servers was shut down
and connection formation failed. In 1.10.0, though, the client did not wait
for the other server to respond. Instead it immediately threw a
FunctionException with ServerConnectivityException as the cause.
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> --
>
> Key: GEODE-7258
> URL: https://issues.apache.org/jira/browse/GEODE-7258
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Attachments: runsWithFineLevelLogging.zip
>
>
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> This test is failing repeatedly. The logs do not to my eyes indicate what is
> the source of the problem.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1112]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1113]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-results/upgradeTest/1569861659/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-artifacts/1569861659/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0169.tgz
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-results/upgradeTest/1569863814/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-artifacts/1569863814/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0170.tgz
>
> {noformat}
> Task :geode-lucene:upgradeTest
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated$$Lambda$172/0x0008407b2440.run
> in VM 3 running on Host 38006782570a with 4 VMs with version 1.10.0
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> java.lang.reflect.InvocationTargetException
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:381)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.lambda$test$c93719d5$2(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
>
[jira] [Updated] (GEODE-7262) Geode Native Client guide: Split into language-specific editions
[ https://issues.apache.org/jira/browse/GEODE-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes updated GEODE-7262: --- Component/s: native client > Geode Native Client guide: Split into language-specific editions > > > Key: GEODE-7262 > URL: https://issues.apache.org/jira/browse/GEODE-7262 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Reporter: Dave Barnes >Priority: Major > > The Geode Native Client User Guide, in its current form, describes two APIs: > C++ and .NET. > The Guide would be easier to read if it could be split into two editions, one > for each language. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7262) Geode Native Client guide: Split into language-specific editions
Dave Barnes created GEODE-7262: -- Summary: Geode Native Client guide: Split into language-specific editions Key: GEODE-7262 URL: https://issues.apache.org/jira/browse/GEODE-7262 Project: Geode Issue Type: Improvement Components: docs Reporter: Dave Barnes The Geode Native Client User Guide, in its current form, describes two APIs: C++ and .NET. The Guide would be easier to read if it could be split into two editions, one for each language. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6945) geode-managment should create its own set of configuration objects for IndexConfiguration
[ https://issues.apache.org/jira/browse/GEODE-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942204#comment-16942204 ] ASF subversion and git services commented on GEODE-6945: Commit 70eaacce372cf03f53feec51a9bd4bea81c048f4 in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=70eaacc ] GEODE-6945: use LEGACY instead of UNSUPPORTED (#4106) > geode-managment should create its own set of configuration objects for > IndexConfiguration > - > > Key: GEODE-6945 > URL: https://issues.apache.org/jira/browse/GEODE-6945 > Project: Geode > Issue Type: Sub-task > Components: management >Reporter: Jinmei Liao >Priority: Major > Fix For: 1.11.0 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > IndexConfiguration > only add the supported attributes > modify the implementation of ConfigurationManager to do the bridging between > the configuration objects and xml domain objects -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7258) RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated > test[from_v1.10.0, with reindex=true] FAILED
[
https://issues.apache.org/jira/browse/GEODE-7258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-7258:
--
Assignee: Xiaojian Zhou (was: Mark Hanson)
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> --
>
> Key: GEODE-7258
> URL: https://issues.apache.org/jira/browse/GEODE-7258
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
>
> RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> This test is failing repeatedly. The logs do not to my eyes indicate what is
> the source of the problem.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1112]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK11/builds/1113]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-results/upgradeTest/1569861659/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0169/test-artifacts/1569861659/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0169.tgz
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-results/upgradeTest/1569863814/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0170/test-artifacts/1569863814/upgradetestfiles-OpenJDK11-1.11.0-SNAPSHOT.0170.tgz
>
> {noformat}
> Task :geode-lucene:upgradeTest
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated
> > test[from_v1.10.0, with reindex=true] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated$$Lambda$172/0x0008407b2440.run
> in VM 3 running on Host 38006782570a with 4 VMs with version 1.10.0
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.test(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> java.lang.reflect.InvocationTargetException
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.geode.cache.lucene.LuceneSearchWithRollingUpgradeDUnit.verifyLuceneQueryResults(LuceneSearchWithRollingUpgradeDUnit.java:381)
> at
> org.apache.geode.cache.lucene.RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.lambda$test$c93719d5$2(RollingUpgradeQueryReturnsCorrectResultsAfterClientAndServersAreRolledOverAllBucketsCreated.java:111)
> Caused by:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create a
> new connection to server 38006782570a:24478
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:209)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:152)
> at
> org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.execute(ServerRegionFunctionExecutor.java:379)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.waitUntilFlushed(LuceneServiceImpl.java:658)
> ... 6 more
> Caused by:
> org.apache.geode.cache.client.ServerConnectivityException: Could not create
> a new connection to server 38006782570a:24478
> 108 tests completed, 1 failed
> > Task :geode-lucene:upgradeTest FAILED {noformat}
>
--
This message was sent by
[jira] [Assigned] (GEODE-6987) Implement RegexBasedMethodAuthorizer
[ https://issues.apache.org/jira/browse/GEODE-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Ramos reassigned GEODE-6987: - Assignee: Juan Ramos > Implement RegexBasedMethodAuthorizer > > > Key: GEODE-6987 > URL: https://issues.apache.org/jira/browse/GEODE-6987 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Juan Ramos >Assignee: Juan Ramos >Priority: Major > Labels: GeodeCommons > > Implement the [RegexBasedMethodAuthorizer > |https://cwiki.apache.org/confluence/display/GEODE/OQL+Method+Invocation+Security#OQLMethodInvocationSecurity-RegexBasedMethodAuthorizer] > class. > * Make sure the class is immutable and thread safe. > * Implement unit tests for the class and all of its methods. > * Add comprehensive and clear documentation to the class and all its public > methods so customers can use it without leaving their IDE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7261) Geode V1 admin rest does not start with Spring 5.x jars on the classpath
[
https://issues.apache.org/jira/browse/GEODE-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe updated GEODE-7261:
--
Description:
The geode-web war includes several spring jars, but does not include
{{spring-core}}. With Jetty debug logging enabled we can see the following
error:
{noformat}
[vm0] 07:30:50.469 [RMI TCP Connection(1)-127.0.0.1] DEBUG
org.eclipse.jetty.servlet.ServletHandler - EXCEPTION
[vm0] java.lang.NoClassDefFoundError: org/springframework/core/ErrorCoded
[vm0] at java.lang.ClassLoader.defineClass1(Native Method)
[vm0] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
[vm0] at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
[vm0] at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
[vm0] at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
[vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
[vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
{noformat}
In addition, the war file also include {{commons-logging}} which causes the war
logging to be redirected to stderr.
was:
The geode-web war includes several spring jars, but does not include
{{spring-core}}. With Jetty debug logging enabled we can see the following
error:
{noformat}
[vm0] 07:30:50.469 [RMI TCP Connection(1)-127.0.0.1] DEBUG
org.eclipse.jetty.servlet.ServletHandler - EXCEPTION
[vm0] java.lang.NoClassDefFoundError: org/springframework/core/ErrorCoded
[vm0] at java.lang.ClassLoader.defineClass1(Native Method)
[vm0] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
[vm0] at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
[vm0] at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
[vm0] at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
[vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
[vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
{noformat}
In addition, the war file also include {{commons-logging}} which causes the war
logging to be redirected to stderr when various slf4j bridging libraries are
also on the classpath (pulled in transitively through spring-geode-starter).
> Geode V1 admin rest does not start with Spring 5.x jars on the classpath
>
>
> Key: GEODE-7261
> URL: https://issues.apache.org/jira/browse/GEODE-7261
> Project: Geode
> Issue Type: Bug
> Components: rest (admin)
>Affects Versions: 1.9.0, 1.9.1
>Reporter: Jens Deppe
>Priority: Major
>
> The geode-web war includes several spring jars, but does not include
> {{spring-core}}. With Jetty debug logging enabled we can see the following
> error:
> {noformat}
> [vm0] 07:30:50.469 [RMI TCP Connection(1)-127.0.0.1] DEBUG
> org.eclipse.jetty.servlet.ServletHandler - EXCEPTION
> [vm0] java.lang.NoClassDefFoundError: org/springframework/core/ErrorCoded
> [vm0] at java.lang.ClassLoader.defineClass1(Native Method)
> [vm0] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> [vm0] at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> [vm0] at
> java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
> [vm0] at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> [vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> [vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> {noformat}
> In addition, the war file also include {{commons-logging}} which causes the
> war logging to be redirected to stderr.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-6989) Use Caching for Already Authorized Methods
[
https://issues.apache.org/jira/browse/GEODE-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Ramos updated GEODE-6989:
--
Description:
We already
[cache|https://github.com/apache/geode/blob/rel/v1.9.0/geode-core/src/main/java/org/apache/geode/cache/query/internal/CompiledOperation.java#L267-L285]
created instances of {{MethodDispatch}} to avoid creating them for every
query. Modify the {{MethodDispatch}} class to remember whether the method was
allowed by a previous invocation, preventing further calls to the respective
{{authorizer}} if it was. We also
[cache|https://github.com/apache/geode/blob/rel/v1.9.0/geode-core/src/main/java/org/apache/geode/cache/query/internal/AttributeDescriptor.java#L148-L170]
within the {{AttributeDescriptor}} class the member already read by reflection
for a particular attribute to avoid doing it again and again in every query.
Modify the {{AttributeDescriptor}} class to remember whether the accessor
method was allowed by a previous invocation, preventing further calls to the
respective {{authorizer}} if it was.
Currently this internal caching is done statically through a static
{{ConcurrentMap}}, we want something to store this information within the
{{QueryExecutionContext}} so the authorization logic is executed once per query.
was:
We already
[cache|https://github.com/apache/geode/blob/rel/v1.9.0/geode-core/src/main/java/org/apache/geode/cache/query/internal/CompiledOperation.java#L267-L285]
created instances of {{MethodDispatch}} to avoid creating them for every
query. Modify the {{MethodDispatch}} class to remember whether the method was
allowed by a previous invocation, preventing further calls to the respective
{{authorizer}} if it was.
We also
[cache|https://github.com/apache/geode/blob/rel/v1.9.0/geode-core/src/main/java/org/apache/geode/cache/query/internal/AttributeDescriptor.java#L148-L170]
within the {{AttributeDescriptor}} class the member already read by reflection
for a particular attribute to avoid doing it again and again in every query.
Modify the {{AttributeDescriptor}} class to remember whether the accessor
method was allowed by a previous invocation, preventing further calls to the
respective {{authorizer}} if it was.
> Use Caching for Already Authorized Methods
> --
>
> Key: GEODE-6989
> URL: https://issues.apache.org/jira/browse/GEODE-6989
> Project: Geode
> Issue Type: New Feature
> Components: querying
>Reporter: Juan Ramos
>Priority: Major
> Labels: GeodeCommons
>
> We already
> [cache|https://github.com/apache/geode/blob/rel/v1.9.0/geode-core/src/main/java/org/apache/geode/cache/query/internal/CompiledOperation.java#L267-L285]
> created instances of {{MethodDispatch}} to avoid creating them for every
> query. Modify the {{MethodDispatch}} class to remember whether the method was
> allowed by a previous invocation, preventing further calls to the respective
> {{authorizer}} if it was. We also
> [cache|https://github.com/apache/geode/blob/rel/v1.9.0/geode-core/src/main/java/org/apache/geode/cache/query/internal/AttributeDescriptor.java#L148-L170]
> within the {{AttributeDescriptor}} class the member already read by
> reflection for a particular attribute to avoid doing it again and again in
> every query. Modify the {{AttributeDescriptor}} class to remember whether the
> accessor method was allowed by a previous invocation, preventing further
> calls to the respective {{authorizer}} if it was.
> Currently this internal caching is done statically through a static
> {{ConcurrentMap}}, we want something to store this information within the
> {{QueryExecutionContext}} so the authorization logic is executed once per
> query.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7261) Geode V1 admin rest does not start with Spring 5.x jars on the classpath
[
https://issues.apache.org/jira/browse/GEODE-7261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe updated GEODE-7261:
--
Affects Version/s: 1.9.0
1.9.1
> Geode V1 admin rest does not start with Spring 5.x jars on the classpath
>
>
> Key: GEODE-7261
> URL: https://issues.apache.org/jira/browse/GEODE-7261
> Project: Geode
> Issue Type: Bug
> Components: rest (admin)
>Affects Versions: 1.9.0, 1.9.1
>Reporter: Jens Deppe
>Priority: Major
>
> The geode-web war includes several spring jars, but does not include
> {{spring-core}}. With Jetty debug logging enabled we can see the following
> error:
> {noformat}
> [vm0] 07:30:50.469 [RMI TCP Connection(1)-127.0.0.1] DEBUG
> org.eclipse.jetty.servlet.ServletHandler - EXCEPTION
> [vm0] java.lang.NoClassDefFoundError: org/springframework/core/ErrorCoded
> [vm0] at java.lang.ClassLoader.defineClass1(Native Method)
> [vm0] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> [vm0] at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> [vm0] at
> java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
> [vm0] at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> [vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> [vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> {noformat}
> In addition, the war file also include {{commons-logging}} which causes the
> war logging to be redirected to stderr when various slf4j bridging libraries
> are also on the classpath (pulled in transitively through
> spring-geode-starter).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7261) Geode V1 admin rest does not start with Spring 5.x jars on the classpath
Jens Deppe created GEODE-7261:
-
Summary: Geode V1 admin rest does not start with Spring 5.x jars
on the classpath
Key: GEODE-7261
URL: https://issues.apache.org/jira/browse/GEODE-7261
Project: Geode
Issue Type: Bug
Components: rest (admin)
Reporter: Jens Deppe
The geode-web war includes several spring jars, but does not include
{{spring-core}}. With Jetty debug logging enabled we can see the following
error:
{noformat}
[vm0] 07:30:50.469 [RMI TCP Connection(1)-127.0.0.1] DEBUG
org.eclipse.jetty.servlet.ServletHandler - EXCEPTION
[vm0] java.lang.NoClassDefFoundError: org/springframework/core/ErrorCoded
[vm0] at java.lang.ClassLoader.defineClass1(Native Method)
[vm0] at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
[vm0] at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
[vm0] at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
[vm0] at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
[vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
[vm0] at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
{noformat}
In addition, the war file also include {{commons-logging}} which causes the war
logging to be redirected to stderr when various slf4j bridging libraries are
also on the classpath (pulled in transitively through spring-geode-starter).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7260) Publish latest version of documentation in web
Alberto Bustamante Reyes created GEODE-7260:
---
Summary: Publish latest version of documentation in web
Key: GEODE-7260
URL: https://issues.apache.org/jira/browse/GEODE-7260
Project: Geode
Issue Type: Improvement
Components: docs
Reporter: Alberto Bustamante Reyes
Following sentence is stated in [README file of
geode-book|https://github.com/apache/geode/tree/develop/geode-book] :
{code}
The latest check-ins to {geode-project-dir}/geode-docs on the develop branch
are regularly built and published to http://geode.apache.org/docs/.
{code}
Currently in the web page there are only links to the documentation of official
releases.
I think it would be useful to publish the latest version of documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7259) Function Execution Through REST API Limitation
Juan Ramos created GEODE-7259:
-
Summary: Function Execution Through REST API Limitation
Key: GEODE-7259
URL: https://issues.apache.org/jira/browse/GEODE-7259
Project: Geode
Issue Type: Bug
Components: docs, rest (dev)
Reporter: Juan Ramos
Function execution through the {{REST API}} doesn't support nested collections
as part of the parameters, this is an undocumented limitation.
We basically try to convert the {{JSON}} parameters into a {{Map}} and
afterwards, based on the {{Map}} contents and the {{@type}} value within the
JSON string, convert that into the actual {{Object[]}} parameters expected by
the function. If any of those objects contain an inner collection ([] as JSON)
or object ({} as JSON), the initial parsing will always fail:
{code:title=AbstractBaseController.java|borderStyle=solid}
private Map convertJsonToMap(final String jsonString) {
Map map = new HashMap();
// convert JSON string to Map
try {
map = objectMapper.readValue(jsonString, new
TypeReference>() {});
} catch (JsonParseException e) {
throw new MalformedJsonException(
"Bind params specified as JSON document in the request is
incorrect!", e);
} catch (JsonMappingException e) {
throw new MalformedJsonException(
"Server unable to process bind params specified as JSON document in
the request!", e);
} catch (IOException e) {
throw new GemfireRestException("Server has encountered error while
process this request!", e);
}
return map;
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
