[jira] [Assigned] (GEODE-1470) Upgrade log4j to 2.6
[ https://issues.apache.org/jira/browse/GEODE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1470: --- Assignee: Kevin Duling > Upgrade log4j to 2.6 > > > Key: GEODE-1470 > URL: https://issues.apache.org/jira/browse/GEODE-1470 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > > The new version of log4j (2.6) has made improvements to make it "garbage > free" (source: https://www.infoq.com/news/2016/05/log4j-garbage-free). We > should upgrade to this version to reap the benefits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH
[
https://issues.apache.org/jira/browse/GEODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319711#comment-15319711
]
Kevin Duling commented on GEODE-744:
I saw a problem with the queries and consulted [~huynhja]. After talking with
him, I've a followup change. The issue is that there are more varieties of
count than simply * within the count(). Specifically, one can do:
{{count(distinct(field))}} or {{count(field)}}
This makes checking for only {{count( * )}} incorrect. My proposed solution is
to search for {{" count("}} like we now search for {{" limit"}}
> Incorrect use of APP_FETCH_SIZE in GFSH
> ---
>
> Key: GEODE-744
> URL: https://issues.apache.org/jira/browse/GEODE-744
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Attachments: workspace (1).zip
>
>
> A customer is facing an easily reproducible issue when executing queries from
> GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the
> query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X.
> Attached to the TRAC is the reproducible scenario, steps to reproduce:
> Uncompress the file.
> Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt.
> Execute "./start_cluster.sh".
> Exceute "./run.sh". This script inserts 1500 entries in the region and,
> afterwards, executes two queries, one using lower case and other using upper
> case. You can see from the console that ouput is different, one returns the
> actual size (1500) and the other one returns the default APP_FETCH_SIZE
> (1000).
> Exceute "./stop_cluster.sh".
> The fix seems pretty easy to implement, the method "addLimit" of the inner
> class "SelectExecStep?" in "DataCommandFunction?" class should be modified to
> compare strings without using the actual word case. Is not enough to add more
> "or" to the comparison like we are currently doing with since keywords like
> "Count" or "coUn" will still break the functionallity. We should compare
> everything using lower case or upper case, it doesn't matter which one, or at
> least make sure that gfsh converts the query to upper/lower case before
> actually executing them.
> The actual code with the problem is below:
> {noformat}
> private String addLimit(String query) {
> boolean containsLimitOrAggregate = query.contains(" limit")
> query.contains(" LIMIT") query.contains("count(*)");
> if (!containsLimitOrAggregate){
> String limitQuery = query + " limit " + getFetchSize();
> return limitQuery;
> } else {
> return query;
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH
[
https://issues.apache.org/jira/browse/GEODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reassigned GEODE-744:
--
Assignee: Kevin Duling
> Incorrect use of APP_FETCH_SIZE in GFSH
> ---
>
> Key: GEODE-744
> URL: https://issues.apache.org/jira/browse/GEODE-744
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Attachments: workspace (1).zip
>
>
> A customer is facing an easily reproducible issue when executing queries from
> GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the
> query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X.
> Attached to the TRAC is the reproducible scenario, steps to reproduce:
> Uncompress the file.
> Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt.
> Execute "./start_cluster.sh".
> Exceute "./run.sh". This script inserts 1500 entries in the region and,
> afterwards, executes two queries, one using lower case and other using upper
> case. You can see from the console that ouput is different, one returns the
> actual size (1500) and the other one returns the default APP_FETCH_SIZE
> (1000).
> Exceute "./stop_cluster.sh".
> The fix seems pretty easy to implement, the method "addLimit" of the inner
> class "SelectExecStep?" in "DataCommandFunction?" class should be modified to
> compare strings without using the actual word case. Is not enough to add more
> "or" to the comparison like we are currently doing with since keywords like
> "Count" or "coUn" will still break the functionallity. We should compare
> everything using lower case or upper case, it doesn't matter which one, or at
> least make sure that gfsh converts the query to upper/lower case before
> actually executing them.
> The actual code with the problem is below:
> {noformat}
> private String addLimit(String query) {
> boolean containsLimitOrAggregate = query.contains(" limit")
> query.contains(" LIMIT") query.contains("count(*)");
> if (!containsLimitOrAggregate){
> String limitQuery = query + " limit " + getFetchSize();
> return limitQuery;
> } else {
> return query;
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available
[
https://issues.apache.org/jira/browse/GEODE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319675#comment-15319675
]
Kevin Duling commented on GEODE-68:
---
[~markito] can you comment on this? When you refer to the hostname, are you
expecting the name of the box or the name of the dominant network interface?
> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
> Labels: gfsh
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- |
> --
> APP_COLLECTION_LIMIT | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER | basic
> SYS_CLASSPATH |
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME | wmarkito
> SYS_JAVA_VERSION | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR |
> SYS_USER | wmarkito
> SYS_USER_HOME | /Users/wmarkito
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-308) Separate hydra from dunit and junit tests in gemfire-core
[ https://issues.apache.org/jira/browse/GEODE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-308: --- Assignee: (was: Kevin Duling) > Separate hydra from dunit and junit tests in gemfire-core > - > > Key: GEODE-308 > URL: https://issues.apache.org/jira/browse/GEODE-308 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund > Labels: hydra > > Usage of Hydra needs to be removed from dunit and junit tests in gemfire-core > and any other project. > The following hydra classes in gemfire-core should be removed (and replaced > if needed by dunit/junit tests): > src/test/java/hydra/GsRandom.java > src/test/java/hydra/HydraRuntimeException.java > src/test/java/hydra/Log.java > src/test/java/hydra/LogVersionHelper.java > src/test/java/hydra/MethExecutor.java > src/test/java/hydra/MethExecutorResult.java > src/test/java/hydra/SchedulingOrder.java > src/test/java/hydra/log/AnyLogWriter.java > src/test/java/hydra/log/CircularOutputStream.java > The following are also not com.gemstone packages and should be removed if > they're specific to Hydra (or Hydra tests) or repackaged if they're actually > used in dunit/junit tests: > src/test/java/batterytest/greplogs/ExpectedStrings.java > src/test/java/batterytest/greplogs/LogConsumer.java > src/test/java/cacheRunner/Portfolio.java > src/test/java/cacheRunner/Position.java > src/test/java/parReg/query/unittest/NewPortfolio.java > src/test/java/parReg/query/unittest/Position.java > src/test/java/perffmwk/Formatter.java > src/test/java/templates/security/DummyAuthenticator.java > src/test/java/templates/security/DummyAuthorization.java > src/test/java/templates/security/FunctionSecurityPrmsHolder.java > src/test/java/templates/security/LdapUserAuthenticator.java > src/test/java/templates/security/PKCSAuthenticator.java > src/test/java/templates/security/PKCSAuthInt.java > src/test/java/templates/security/PKCSPrincipal.java > src/test/java/templates/security/UsernamePrincipal.java > src/test/java/templates.security/UserPasswordAuthInit.java > src/test/java/templates.security/XmlAuthorization.java > src/test/java/templates.security/XmlErrorHandler.java > src/test/java/util/TestException.java > The following are Hydra-related resources in src/test/resources that also > need to be removed: > src/test/resources/jta/cachejta.xml > src/test/resources/ssl/trusted.keystore > src/test/resources/templates/security/authz5_5.dtd > src/test/resources/templates/security/authz6_0.dtd -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH
[
https://issues.apache.org/jira/browse/GEODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-744.
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3
Resolving this ticket as is. Opening another for the {{count(*)}} issue.
> Incorrect use of APP_FETCH_SIZE in GFSH
> ---
>
> Key: GEODE-744
> URL: https://issues.apache.org/jira/browse/GEODE-744
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
> Attachments: workspace (1).zip
>
>
> A customer is facing an easily reproducible issue when executing queries from
> GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the
> query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X.
> Attached to the TRAC is the reproducible scenario, steps to reproduce:
> Uncompress the file.
> Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt.
> Execute "./start_cluster.sh".
> Exceute "./run.sh". This script inserts 1500 entries in the region and,
> afterwards, executes two queries, one using lower case and other using upper
> case. You can see from the console that ouput is different, one returns the
> actual size (1500) and the other one returns the default APP_FETCH_SIZE
> (1000).
> Exceute "./stop_cluster.sh".
> The fix seems pretty easy to implement, the method "addLimit" of the inner
> class "SelectExecStep?" in "DataCommandFunction?" class should be modified to
> compare strings without using the actual word case. Is not enough to add more
> "or" to the comparison like we are currently doing with since keywords like
> "Count" or "coUn" will still break the functionallity. We should compare
> everything using lower case or upper case, it doesn't matter which one, or at
> least make sure that gfsh converts the query to upper/lower case before
> actually executing them.
> The actual code with the problem is below:
> {noformat}
> private String addLimit(String query) {
> boolean containsLimitOrAggregate = query.contains(" limit")
> query.contains(" LIMIT") query.contains("count(*)");
> if (!containsLimitOrAggregate){
> String limitQuery = query + " limit " + getFetchSize();
> return limitQuery;
> } else {
> return query;
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available
[
https://issues.apache.org/jira/browse/GEODE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323081#comment-15323081
]
Kevin Duling commented on GEODE-68:
---
Requesting comments [~amb] [~bschuchardt]
Testing by forcing a DNS timeout, I've found that the response could take as
long as 75 seconds. Clearly, that's too long. So there are a couple of
alternatives.
* Start a background thread when gfish first starts up to collect and cache the
hostname so that if there is a DNS timeout, avoid exposing it to the user.
* Adopt the suggestion posted on many, many stacktrace.com threads. This is
the controversial {{System.exec("hostname")}} command.
There are several good reasons to do this.
* hostname exists on Windows (c:\Windows\System32\hostname.exe) as well as
Linux, *nix, Solaris, and Mac (/usr/bin/hostname)
* Takes approximately 20ms to process.
* Will return the POSIX name of the system as [~markito] requested, not the
name of a NIC.
* It can be the fallback if the appropriate environment variable is not set.
Below is a test program I've done to validate the behavior and get some
timings. I've also tested this by calling "hostnme" instead of "hostname" and
verified the behavior if the command doesn't exist, defaulting to 'unknown'.
{code}
import java.io.IOException;
import java.io.InputStream;
import java.util.Scanner;
public class Host {
public static void main(String[] args) throws IOException {
long mark = System.currentTimeMillis();
String hostname;
hostname = System.getenv("COMPUTERNAME"); // Windows
if (hostname == null) {
hostname = System.getenv("HOSTNAME"); // Unix / Mac / Cygwin sometimes
has this set
}
if (hostname == null) {
try
{
hostname = execReadToString("hostname"); // Unix / Mac / Windows /
Cygwin
}
catch (IOException io) // happens if hostname binary is not found.
{
hostname = "unknown";
}
}
if (hostname == null) // if it still isn't set, default it.
{
hostname = "unknown";
}
System.out.println(hostname + " " + (System.currentTimeMillis() - mark) +
"ms");
}
private static String execReadToString(String execCommand) throws IOException
{
Process proc = Runtime.getRuntime().exec(execCommand);
try (InputStream stream = proc.getInputStream()) {
try (Scanner s = new Scanner(stream).useDelimiter("\\A")) {
return s.hasNext() ? s.next() : "";
}
}
}
}
{code}
> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
> Labels: gfsh
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- |
> --
> APP_COLLECTION_LIMIT | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER | basic
> SYS_CLASSPATH |
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME | wmarkito
> SYS_JAVA_VERSION | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR |
> SYS_USER | wmarkito
> SYS_USER_HOME | /Users/wmarkito
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1331) gfsh.bat on Windows is incorrect
[
https://issues.apache.org/jira/browse/GEODE-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reassigned GEODE-1331:
---
Assignee: Kevin Duling
> gfsh.bat on Windows is incorrect
>
>
> Key: GEODE-1331
> URL: https://issues.apache.org/jira/browse/GEODE-1331
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> Initial report:
> {noformat}
> I am doing testing in windows STS. I am not adding these dependencies jars,
> gfsh.bat is what doing this.
>
> C:\DEV\Pivotal\GemFire_v82014\bin\gfsh.bat has below code, which is setting
> gemfire, antlr, gfsh-dependencies and pulse-dependencies jars in classpath.
> Line 26 to 29
> @set
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> @if defined CLASSPATH (
> @set GEMFIRE_JARS=%GEMFIRE_JARS%;%CLASSPATH%
> )
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\antlr.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\pulse-dependencies.jar
>
> Unix C:\DEV\Pivotal\GemFire_v82014\bin script, does not set these jars in
> classpath.
>
>
> Another observation is that, if I pass --include-system-classpath to gfsh
> start server command, then it is prepending
> gemfire.jar and gfsh-dependencies.jar to the system classpath and adding that
> to the server, that is what is shown in logs
> Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar
>
> ………..
> C:\Program Files\Java\jdk1.7.0_67\lib\tools.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>
> start server \
> --name=${NAME} --server-port=${PORT} \
> --properties-file=${GEMFIRE_PWD}/resources/cache.properties \
> --J=-Dgemfire.distributed-system-id=${DISTRIBUTED_SYSTEM_ID} \
> --J=-Dgemfire.bind-address=${HOST_NAME}
> --J=-Dgemfire.server-bind-address=${HOST_NAME} \
> --J=-Dgemfire.locators=${HOST_NAME}[${LOCATOR_PORT}] \
> --J=-Dgemfire.OSProcess.ENABLE_OUTPUT_REDIRECTION=true \
> --include-system-classpath
>
> If I don’t pass this parameter, then it does not add gfsh-dependencies
> Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>
> I am trying to do testing without using –include-system-classpath instead add
> jars in to the start server –classpath as a work around.
> {noformat}
> And a subsequent reply from John Blum:
> {noformat}
> My apologies. I was not aware that you were launching your GemFire process
> (e.g. Server) using Gfsh, and specifically with gfsh.bat on Windows.
> I just confirmed the line(s) you were looking at in gfsh.bat, and indeed the
> BAT file is wrong! Specifically, the classpath for the GemFire process
> is being constructed from the following lines...
> @set
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> ...
> @set GFSH_JARS=;%GEMFIRE%\lib\gfsh-dependencies.jar
> @set CLASSPATH=%GFSH_JARS%;%GEMFIRE_JARS%
> The Windows BAT file is also inconsistent with the Bash shell version (gfsh),
> which rightfully only contains...
> GEMFIRE_JARS=$GEMFIRE/lib/gfsh-dependencies.jar
> if [ "x$CLASSPATH" != "x" ]; then
> GEMFIRE_JARS=$GEMFIRE_JARS:$CLASSPATH
> fi
> CLASSPATH=$GEMFIRE_JARS
> In addition, the Bash shell version launches the Gfsh process using the java
> -classpath option...
> "$GF_JAVA" -Dgfsh=true
> -Dlog4j.configurationFile=/com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml
> ${JLINE_TERMINAL} -classpath "${CLASSPATH}" $JAVA_ARGS $LAUNCHER "$@"
> Which does not "export", or rather, set the global System CLASSPATH
> environment variable. Here it is only setting the Java System property
> to the Java process, where as, I believe, the Window BAT file is actually
> setting the System CLASSPATH environment variable, since there is no
> java -classpath option present in the command to launch Gfsh...
> @"%GF_JAVA%" -Dgfsh=true
> -Dlog4j.configurationFile=/com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml
> %JAVA_ARGS% %LAUNCHER% %*
> Regarding...
> > I think we need Pivotal Engineering team to look into gfsh.bat and
> > –include-system-classpath behavior.
> Not exactly. --include-system-classpath basically functions such that it
> appends the value of the System CLASSPATH environment variable
> to the forked GemFire process launched from Gfsh if the user has set the
> global variable per environment and wishes to use it.
> In a nutshell, GemFire documentation use to erroneously recommend users to
> set
[jira] [Reopened] (GEODE-1470) Upgrade log4j to 2.6
[ https://issues.apache.org/jira/browse/GEODE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reopened GEODE-1470: - > Upgrade log4j to 2.6 > > > Key: GEODE-1470 > URL: https://issues.apache.org/jira/browse/GEODE-1470 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > > The new version of log4j (2.6) has made improvements to make it "garbage > free" (source: https://www.infoq.com/news/2016/05/log4j-garbage-free). We > should upgrade to this version to reap the benefits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available
[
https://issues.apache.org/jira/browse/GEODE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-68.
---
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3
> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
> Labels: gfsh
> Fix For: 1.0.0-incubating.M3
>
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- |
> --
> APP_COLLECTION_LIMIT | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER | basic
> SYS_CLASSPATH |
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME | wmarkito
> SYS_JAVA_VERSION | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR |
> SYS_USER | wmarkito
> SYS_USER_HOME | /Users/wmarkito
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-1470) Upgrade log4j to 2.6
[ https://issues.apache.org/jira/browse/GEODE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1470. - Resolution: Fixed Pull request accepted. > Upgrade log4j to 2.6 > > > Key: GEODE-1470 > URL: https://issues.apache.org/jira/browse/GEODE-1470 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > > The new version of log4j (2.6) has made improvements to make it "garbage > free" (source: https://www.infoq.com/news/2016/05/log4j-garbage-free). We > should upgrade to this version to reap the benefits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1521) APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
[
https://issues.apache.org/jira/browse/GEODE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-1521.
-
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3
> APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
> -
>
> Key: GEODE-1521
> URL: https://issues.apache.org/jira/browse/GEODE-1521
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> There are more varieties of count than simply * within the count().
> Specifically, one can do: {{count(distinct(field))}} or {{count(field)}}
> This makes checking for only {{count( * )}} incorrect. Instead, the search
> to apply the limt should look for {{" count("}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-1470) Upgrade log4j to 2.6
[ https://issues.apache.org/jira/browse/GEODE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1470. - Resolution: Fixed Fix Version/s: 1.0.0-incubating.M3 > Upgrade log4j to 2.6 > > > Key: GEODE-1470 > URL: https://issues.apache.org/jira/browse/GEODE-1470 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > > The new version of log4j (2.6) has made improvements to make it "garbage > free" (source: https://www.infoq.com/news/2016/05/log4j-garbage-free). We > should upgrade to this version to reap the benefits. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-68) GFSH SYS_HOST_NAME variable have value
[
https://issues.apache.org/jira/browse/GEODE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reassigned GEODE-68:
-
Assignee: Kevin Duling (was: Tushar Khairnar)
> GFSH SYS_HOST_NAME variable have value
> --
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
> Labels: gfsh
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- |
> --
> APP_COLLECTION_LIMIT | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER | basic
> SYS_CLASSPATH |
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME | wmarkito
> SYS_JAVA_VERSION | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR |
> SYS_USER | wmarkito
> SYS_USER_HOME | /Users/wmarkito
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available
[
https://issues.apache.org/jira/browse/GEODE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-68:
--
Summary: GFSH SYS_HOST_NAME variable should report hostname if available
(was: GFSH SYS_HOST_NAME variable have value)
> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
> Labels: gfsh
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- |
> --
> APP_COLLECTION_LIMIT | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER | basic
> SYS_CLASSPATH |
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME | wmarkito
> SYS_JAVA_VERSION | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR |
> SYS_USER | wmarkito
> SYS_USER_HOME | /Users/wmarkito
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-748) Unexpected version string returned from gfsh
[
https://issues.apache.org/jira/browse/GEODE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-748.
Resolution: Resolved
Fix Version/s: 1.0.0-incubating.M3
> Unexpected version string returned from gfsh
>
>
> Key: GEODE-748
> URL: https://issues.apache.org/jira/browse/GEODE-748
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> {{gfsh version}} returns a version number with a prepended 'v'. This is
> inconsistent with the actual versioning which never includes a 'v'.
> The {{v}} should be removed from the specific gfsh command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-308) Separate hydra from dunit and junit tests in gemfire-core
[ https://issues.apache.org/jira/browse/GEODE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-308: -- Assignee: Kevin Duling (was: Kirk Lund) > Separate hydra from dunit and junit tests in gemfire-core > - > > Key: GEODE-308 > URL: https://issues.apache.org/jira/browse/GEODE-308 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kevin Duling > Labels: hydra > > Usage of Hydra needs to be removed from dunit and junit tests in gemfire-core > and any other project. > The following hydra classes in gemfire-core should be removed (and replaced > if needed by dunit/junit tests): > src/test/java/hydra/GsRandom.java > src/test/java/hydra/HydraRuntimeException.java > src/test/java/hydra/Log.java > src/test/java/hydra/LogVersionHelper.java > src/test/java/hydra/MethExecutor.java > src/test/java/hydra/MethExecutorResult.java > src/test/java/hydra/SchedulingOrder.java > src/test/java/hydra/log/AnyLogWriter.java > src/test/java/hydra/log/CircularOutputStream.java > The following are also not com.gemstone packages and should be removed if > they're specific to Hydra (or Hydra tests) or repackaged if they're actually > used in dunit/junit tests: > src/test/java/batterytest/greplogs/ExpectedStrings.java > src/test/java/batterytest/greplogs/LogConsumer.java > src/test/java/cacheRunner/Portfolio.java > src/test/java/cacheRunner/Position.java > src/test/java/parReg/query/unittest/NewPortfolio.java > src/test/java/parReg/query/unittest/Position.java > src/test/java/perffmwk/Formatter.java > src/test/java/templates/security/DummyAuthenticator.java > src/test/java/templates/security/DummyAuthorization.java > src/test/java/templates/security/FunctionSecurityPrmsHolder.java > src/test/java/templates/security/LdapUserAuthenticator.java > src/test/java/templates/security/PKCSAuthenticator.java > src/test/java/templates/security/PKCSAuthInt.java > src/test/java/templates/security/PKCSPrincipal.java > src/test/java/templates/security/UsernamePrincipal.java > src/test/java/templates.security/UserPasswordAuthInit.java > src/test/java/templates.security/XmlAuthorization.java > src/test/java/templates.security/XmlErrorHandler.java > src/test/java/util/TestException.java > The following are Hydra-related resources in src/test/resources that also > need to be removed: > src/test/resources/jta/cachejta.xml > src/test/resources/ssl/trusted.keystore > src/test/resources/templates/security/authz5_5.dtd > src/test/resources/templates/security/authz6_0.dtd -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-308) Separate hydra from dunit and junit tests in gemfire-core
[ https://issues.apache.org/jira/browse/GEODE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310797#comment-15310797 ] Kevin Duling commented on GEODE-308: Removed several classes. * src/test/java/hydra/GsRandom.java * src/test/java/hydra/HydraRuntimeException.java * src/test/java/hydra/Log.java * src/test/java/hydra/LogVersionHelper.java * src/test/java/hydra/log/AnyLogWriter.java * src/test/java/hydra/log/CircularOutputStream.java These classes need more work to extract them. * src/test/java/hydra/MethExecutor.java * src/test/java/hydra/MethExecutorResult.java * src/test/java/hydra/SchedulingOrder.java > Separate hydra from dunit and junit tests in gemfire-core > - > > Key: GEODE-308 > URL: https://issues.apache.org/jira/browse/GEODE-308 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kevin Duling > Labels: hydra > > Usage of Hydra needs to be removed from dunit and junit tests in gemfire-core > and any other project. > The following hydra classes in gemfire-core should be removed (and replaced > if needed by dunit/junit tests): > src/test/java/hydra/GsRandom.java > src/test/java/hydra/HydraRuntimeException.java > src/test/java/hydra/Log.java > src/test/java/hydra/LogVersionHelper.java > src/test/java/hydra/MethExecutor.java > src/test/java/hydra/MethExecutorResult.java > src/test/java/hydra/SchedulingOrder.java > src/test/java/hydra/log/AnyLogWriter.java > src/test/java/hydra/log/CircularOutputStream.java > The following are also not com.gemstone packages and should be removed if > they're specific to Hydra (or Hydra tests) or repackaged if they're actually > used in dunit/junit tests: > src/test/java/batterytest/greplogs/ExpectedStrings.java > src/test/java/batterytest/greplogs/LogConsumer.java > src/test/java/cacheRunner/Portfolio.java > src/test/java/cacheRunner/Position.java > src/test/java/parReg/query/unittest/NewPortfolio.java > src/test/java/parReg/query/unittest/Position.java > src/test/java/perffmwk/Formatter.java > src/test/java/templates/security/DummyAuthenticator.java > src/test/java/templates/security/DummyAuthorization.java > src/test/java/templates/security/FunctionSecurityPrmsHolder.java > src/test/java/templates/security/LdapUserAuthenticator.java > src/test/java/templates/security/PKCSAuthenticator.java > src/test/java/templates/security/PKCSAuthInt.java > src/test/java/templates/security/PKCSPrincipal.java > src/test/java/templates/security/UsernamePrincipal.java > src/test/java/templates.security/UserPasswordAuthInit.java > src/test/java/templates.security/XmlAuthorization.java > src/test/java/templates.security/XmlErrorHandler.java > src/test/java/util/TestException.java > The following are Hydra-related resources in src/test/resources that also > need to be removed: > src/test/resources/jta/cachejta.xml > src/test/resources/ssl/trusted.keystore > src/test/resources/templates/security/authz5_5.dtd > src/test/resources/templates/security/authz6_0.dtd -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1521) APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
[
https://issues.apache.org/jira/browse/GEODE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-1521.
-
Resolution: Fixed
Delivered
> APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
> -
>
> Key: GEODE-1521
> URL: https://issues.apache.org/jira/browse/GEODE-1521
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> There are more varieties of count than simply * within the count().
> Specifically, one can do: {{count(distinct(field))}} or {{count(field)}}
> This makes checking for only {{count( * )}} incorrect. Instead, the search
> to apply the limt should look for {{" count("}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH
[
https://issues.apache.org/jira/browse/GEODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-744.
Resolution: Fixed
> Incorrect use of APP_FETCH_SIZE in GFSH
> ---
>
> Key: GEODE-744
> URL: https://issues.apache.org/jira/browse/GEODE-744
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
> Attachments: workspace (1).zip
>
>
> A customer is facing an easily reproducible issue when executing queries from
> GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the
> query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X.
> Attached to the TRAC is the reproducible scenario, steps to reproduce:
> Uncompress the file.
> Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt.
> Execute "./start_cluster.sh".
> Exceute "./run.sh". This script inserts 1500 entries in the region and,
> afterwards, executes two queries, one using lower case and other using upper
> case. You can see from the console that ouput is different, one returns the
> actual size (1500) and the other one returns the default APP_FETCH_SIZE
> (1000).
> Exceute "./stop_cluster.sh".
> The fix seems pretty easy to implement, the method "addLimit" of the inner
> class "SelectExecStep?" in "DataCommandFunction?" class should be modified to
> compare strings without using the actual word case. Is not enough to add more
> "or" to the comparison like we are currently doing with since keywords like
> "Count" or "coUn" will still break the functionallity. We should compare
> everything using lower case or upper case, it doesn't matter which one, or at
> least make sure that gfsh converts the query to upper/lower case before
> actually executing them.
> The actual code with the problem is below:
> {noformat}
> private String addLimit(String query) {
> boolean containsLimitOrAggregate = query.contains(" limit")
> query.contains(" LIMIT") query.contains("count(*)");
> if (!containsLimitOrAggregate){
> String limitQuery = query + " limit " + getFetchSize();
> return limitQuery;
> } else {
> return query;
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available
[
https://issues.apache.org/jira/browse/GEODE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-68.
---
Resolution: Fixed
Delivered
> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
> Labels: gfsh
> Fix For: 1.0.0-incubating.M3
>
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- |
> --
> APP_COLLECTION_LIMIT | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER | basic
> SYS_CLASSPATH |
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME | wmarkito
> SYS_JAVA_VERSION | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR |
> SYS_USER | wmarkito
> SYS_USER_HOME | /Users/wmarkito
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-117) gfsh put ignores --skip-if-exists flag
[ https://issues.apache.org/jira/browse/GEODE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-117. Resolution: Fixed Fix Version/s: 1.0.0-incubating.M3 Fixed test, which erroneously reported that the --skip-if-exists flag is honored. Implemented check for flag within the put operation. > gfsh put ignores --skip-if-exists flag > -- > > Key: GEODE-117 > URL: https://issues.apache.org/jira/browse/GEODE-117 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dan Smith >Assignee: Kevin Duling > Labels: gfsh, starter > Fix For: 1.0.0-incubating.M3 > > > Someone hit this on a forum post: > https://support.pivotal.io/hc/communities/public/questions/204414098-put-in-gfsh-doesn-t-honor-skip-if-exists-true-flag-?flash_digest=f2441b8a96ac363d6da205c6f90a62035b1a3c21 > I looked into the code, and it looks like the flag gets lost somewhere along > the way. If you look at DataCommandFunction.put, it has a putIfAbsent flag, > but that flag is not used; the function just does a normal put. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[
https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-1575.
-
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M3
Added a catch clause for the exception.
Now the error message reads:
{panel:title=gfsh}
(2) Executing - create region --name=replicatedRegion --type=REPLICATE
--cache-loader=com.example.TestCacheLoader
Member | Status
- |
---
host1-server1 | ERROR: Could not find class "com.example.TestCacheLoader"
specified for "cache-loader".
{panel}
> Unhandled NoClassDefFound Exception when creating regions
> -
>
> Key: GEODE-1575
> URL: https://issues.apache.org/jira/browse/GEODE-1575
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> {panel:title=gfsh}
> Executing - create region --name=replicatedRegion --type=REPLICATE
> --cache-loader=com.example.TestCacheLoader
> Could not process command due to GemFire error.
> java.lang.ClassNotFoundException cannot be cast to
> com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult
> {panel}
> {panel:title=server.log}
> [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13
> from null with exception com.gemstone.gemfire.distributed.internal.ReplyE
> xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> com.gemstone.gemfire.distributed.internal.ReplyException:
> java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89)
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
> at
> com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384)
> ... 15 more
> {panel}
> The wrong error message is being displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[
https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reopened GEODE-1575:
-
> Unhandled NoClassDefFound Exception when creating regions
> -
>
> Key: GEODE-1575
> URL: https://issues.apache.org/jira/browse/GEODE-1575
> Project: Geode
> Issue Type: Bug
> Components: configuration, gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> The wrong error message is being displayed when encountering a
> {{NoClassDefFoundError}}
> {panel:title=gfsh}
> {noformat}
> Executing - create region --name=replicatedRegion --type=REPLICATE
> --cache-loader=com.example.TestCacheLoader
> Could not process command due to GemFire error.
> java.lang.ClassNotFoundException cannot be cast to
> com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult
> {noformat}
> {panel}
> {panel:title=server.log}
> {noformat}
> [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13
> from null with exception
> com.gemstone.gemfire.distributed.internal.ReplyException:
> java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> com.gemstone.gemfire.distributed.internal.ReplyException:
> java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89)
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
> at
> com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384)
> ... 15 more
> {noformat}
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
Kevin Duling created GEODE-1575:
---
Summary: Unhandled NoClassDefFound Exception when creating regions
Key: GEODE-1575
URL: https://issues.apache.org/jira/browse/GEODE-1575
Project: Geode
Issue Type: Bug
Components: configuration
Reporter: Kevin Duling
{panel:title=gfsh}
Executing - create region --name=replicatedRegion --type=REPLICATE
--cache-loader=com.example.TestCacheLoader
Could not process command due to GemFire error.
java.lang.ClassNotFoundException cannot be cast to
com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult
{panel}
{panel:title=server.log}
[fine 2016/06/21 10:02:02.745 PDT host1-server1
tid=0x41] Replying with exception: ReplyMessage processorId=13 from null with
exception com.gemstone.gemfire.distributed.internal.ReplyE
xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
com.gemstone.gemfire.distributed.internal.ReplyException:
java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at
com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
at
com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at
io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at
com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408)
at
com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386)
at
com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312)
at
com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89)
at
com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
... 7 more
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
at
com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568)
at
com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413)
at
com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389)
at
com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384)
... 15 more
{panel}
The wrong error message is being displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[
https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reassigned GEODE-1575:
---
Assignee: Kevin Duling
> Unhandled NoClassDefFound Exception when creating regions
> -
>
> Key: GEODE-1575
> URL: https://issues.apache.org/jira/browse/GEODE-1575
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> {panel:title=gfsh}
> Executing - create region --name=replicatedRegion --type=REPLICATE
> --cache-loader=com.example.TestCacheLoader
> Could not process command due to GemFire error.
> java.lang.ClassNotFoundException cannot be cast to
> com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult
> {panel}
> {panel:title=server.log}
> [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13
> from null with exception com.gemstone.gemfire.distributed.internal.ReplyE
> xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> com.gemstone.gemfire.distributed.internal.ReplyException:
> java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89)
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
> at
> com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384)
> ... 15 more
> {panel}
> The wrong error message is being displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[
https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342192#comment-15342192
]
Kevin Duling edited comment on GEODE-1575 at 6/21/16 5:07 PM:
--
Added a catch clause for the exception.
Now the error message reads:
{panel:title=gfsh}
{noformat}
(2) Executing - create region --name=replicatedRegion --type=REPLICATE
--cache-loader=com.example.TestCacheLoader
Member | Status
- |
---
host1-server1 | ERROR: Could not find class "com.example.TestCacheLoader"
specified for "cache-loader".
{noformat}
{panel}
was (Author: kduling):
Added a catch clause for the exception.
Now the error message reads:
{panel:title=gfsh}
(2) Executing - create region --name=replicatedRegion --type=REPLICATE
--cache-loader=com.example.TestCacheLoader
Member | Status
- |
---
host1-server1 | ERROR: Could not find class "com.example.TestCacheLoader"
specified for "cache-loader".
{panel}
> Unhandled NoClassDefFound Exception when creating regions
> -
>
> Key: GEODE-1575
> URL: https://issues.apache.org/jira/browse/GEODE-1575
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> {panel:title=gfsh}
> Executing - create region --name=replicatedRegion --type=REPLICATE
> --cache-loader=com.example.TestCacheLoader
> Could not process command due to GemFire error.
> java.lang.ClassNotFoundException cannot be cast to
> com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult
> {panel}
> {panel:title=server.log}
> [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13
> from null with exception com.gemstone.gemfire.distributed.internal.ReplyE
> xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> com.gemstone.gemfire.distributed.internal.ReplyException:
> java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89)
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
> at
> com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384)
> ... 15 more
> {panel}
> The wrong error message is being displayed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[
https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1575:
Component/s: gfsh
> Unhandled NoClassDefFound Exception when creating regions
> -
>
> Key: GEODE-1575
> URL: https://issues.apache.org/jira/browse/GEODE-1575
> Project: Geode
> Issue Type: Bug
> Components: configuration, gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> The wrong error message is being displayed when encountering a
> {{NoClassDefFoundError}}
> {panel:title=gfsh}
> {noformat}
> Executing - create region --name=replicatedRegion --type=REPLICATE
> --cache-loader=com.example.TestCacheLoader
> Could not process command due to GemFire error.
> java.lang.ClassNotFoundException cannot be cast to
> com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult
> {noformat}
> {panel}
> {panel:title=server.log}
> {noformat}
> [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13
> from null with exception
> com.gemstone.gemfire.distributed.internal.ReplyException:
> java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> com.gemstone.gemfire.distributed.internal.ReplyException:
> java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89)
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
> at
> com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384)
> ... 15 more
> {noformat}
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[
https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1575:
Description:
The wrong error message is being displayed when encountering a
{{NoClassDefFoundError}}
{panel:title=gfsh}
{noformat}
Executing - create region --name=replicatedRegion --type=REPLICATE
--cache-loader=com.example.TestCacheLoader
Could not process command due to GemFire error.
java.lang.ClassNotFoundException cannot be cast to
com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult
{noformat}
{panel}
{panel:title=server.log}
{noformat}
[fine 2016/06/21 10:02:02.745 PDT host1-server1
tid=0x41] Replying with exception: ReplyMessage processorId=13 from null with
exception com.gemstone.gemfire.distributed.internal.ReplyException:
java.lang.NoClassDefFoundError: org/apache/log4j/Logger
com.gemstone.gemfire.distributed.internal.ReplyException:
java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at
com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
at
com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at
io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at
com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408)
at
com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386)
at
com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312)
at
com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89)
at
com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
... 7 more
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
at
com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568)
at
com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413)
at
com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389)
at
com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384)
... 15 more
{noformat}
{panel}
was:
{panel:title=gfsh}
Executing - create region --name=replicatedRegion --type=REPLICATE
--cache-loader=com.example.TestCacheLoader
Could not process command due to GemFire error.
java.lang.ClassNotFoundException cannot be cast to
com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult
{panel}
{panel:title=server.log}
[fine 2016/06/21 10:02:02.745 PDT host1-server1
tid=0x41] Replying with exception: ReplyMessage processorId=13 from null with
exception com.gemstone.gemfire.distributed.internal.ReplyE
xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
com.gemstone.gemfire.distributed.internal.ReplyException:
java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at
com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
at
com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
at
com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at
io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14)
at java.lang.Class.forName0(Native Method)
at
[jira] [Resolved] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[
https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-1575.
-
Resolution: Fixed
> Unhandled NoClassDefFound Exception when creating regions
> -
>
> Key: GEODE-1575
> URL: https://issues.apache.org/jira/browse/GEODE-1575
> Project: Geode
> Issue Type: Bug
> Components: configuration, gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> The wrong error message is being displayed when encountering a
> {{NoClassDefFoundError}}
> {panel:title=gfsh}
> {noformat}
> Executing - create region --name=replicatedRegion --type=REPLICATE
> --cache-loader=com.example.TestCacheLoader
> Could not process command due to GemFire error.
> java.lang.ClassNotFoundException cannot be cast to
> com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult
> {noformat}
> {panel}
> {panel:title=server.log}
> {noformat}
> [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13
> from null with exception
> com.gemstone.gemfire.distributed.internal.ReplyException:
> java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> com.gemstone.gemfire.distributed.internal.ReplyException:
> java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at
> io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312)
> at
> com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89)
> at
> com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194)
> ... 7 more
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
> at
> com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389)
> at
> com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384)
> ... 15 more
> {noformat}
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (GEODE-1521) APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
[
https://issues.apache.org/jira/browse/GEODE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1521:
Comment: was deleted
(was: Re-opening so it can be added to Pivotal Tracker.)
> APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
> -
>
> Key: GEODE-1521
> URL: https://issues.apache.org/jira/browse/GEODE-1521
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> There are more varieties of count than simply * within the count().
> Specifically, one can do: {{count(distinct(field))}} or {{count(field)}}
> This makes checking for only {{count( * )}} incorrect. Instead, the search
> to apply the limt should look for {{" count("}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH
[
https://issues.apache.org/jira/browse/GEODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-744:
---
Comment: was deleted
(was: Re-opening so it can be added to Pivotal Tracker.)
> Incorrect use of APP_FETCH_SIZE in GFSH
> ---
>
> Key: GEODE-744
> URL: https://issues.apache.org/jira/browse/GEODE-744
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
> Attachments: workspace (1).zip
>
>
> A customer is facing an easily reproducible issue when executing queries from
> GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the
> query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X.
> Attached to the TRAC is the reproducible scenario, steps to reproduce:
> Uncompress the file.
> Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt.
> Execute "./start_cluster.sh".
> Exceute "./run.sh". This script inserts 1500 entries in the region and,
> afterwards, executes two queries, one using lower case and other using upper
> case. You can see from the console that ouput is different, one returns the
> actual size (1500) and the other one returns the default APP_FETCH_SIZE
> (1000).
> Exceute "./stop_cluster.sh".
> The fix seems pretty easy to implement, the method "addLimit" of the inner
> class "SelectExecStep?" in "DataCommandFunction?" class should be modified to
> compare strings without using the actual word case. Is not enough to add more
> "or" to the comparison like we are currently doing with since keywords like
> "Count" or "coUn" will still break the functionallity. We should compare
> everything using lower case or upper case, it doesn't matter which one, or at
> least make sure that gfsh converts the query to upper/lower case before
> actually executing them.
> The actual code with the problem is below:
> {noformat}
> private String addLimit(String query) {
> boolean containsLimitOrAggregate = query.contains(" limit")
> query.contains(" LIMIT") query.contains("count(*)");
> if (!containsLimitOrAggregate){
> String limitQuery = query + " limit " + getFetchSize();
> return limitQuery;
> } else {
> return query;
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (GEODE-748) Unexpected version string returned from gfsh
[
https://issues.apache.org/jira/browse/GEODE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reopened GEODE-748:
> Unexpected version string returned from gfsh
>
>
> Key: GEODE-748
> URL: https://issues.apache.org/jira/browse/GEODE-748
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> {{gfsh version}} returns a version number with a prepended 'v'. This is
> inconsistent with the actual versioning which never includes a 'v'.
> The {{v}} should be removed from the specific gfsh command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-748) Unexpected version string returned from gfsh
[
https://issues.apache.org/jira/browse/GEODE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-748.
Resolution: Fixed
> Unexpected version string returned from gfsh
>
>
> Key: GEODE-748
> URL: https://issues.apache.org/jira/browse/GEODE-748
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> {{gfsh version}} returns a version number with a prepended 'v'. This is
> inconsistent with the actual versioning which never includes a 'v'.
> The {{v}} should be removed from the specific gfsh command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH
[
https://issues.apache.org/jira/browse/GEODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reopened GEODE-744:
Re-opening so it can be added to Pivotal Tracker.
> Incorrect use of APP_FETCH_SIZE in GFSH
> ---
>
> Key: GEODE-744
> URL: https://issues.apache.org/jira/browse/GEODE-744
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
> Attachments: workspace (1).zip
>
>
> A customer is facing an easily reproducible issue when executing queries from
> GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the
> query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X.
> Attached to the TRAC is the reproducible scenario, steps to reproduce:
> Uncompress the file.
> Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt.
> Execute "./start_cluster.sh".
> Exceute "./run.sh". This script inserts 1500 entries in the region and,
> afterwards, executes two queries, one using lower case and other using upper
> case. You can see from the console that ouput is different, one returns the
> actual size (1500) and the other one returns the default APP_FETCH_SIZE
> (1000).
> Exceute "./stop_cluster.sh".
> The fix seems pretty easy to implement, the method "addLimit" of the inner
> class "SelectExecStep?" in "DataCommandFunction?" class should be modified to
> compare strings without using the actual word case. Is not enough to add more
> "or" to the comparison like we are currently doing with since keywords like
> "Count" or "coUn" will still break the functionallity. We should compare
> everything using lower case or upper case, it doesn't matter which one, or at
> least make sure that gfsh converts the query to upper/lower case before
> actually executing them.
> The actual code with the problem is below:
> {noformat}
> private String addLimit(String query) {
> boolean containsLimitOrAggregate = query.contains(" limit")
> query.contains(" LIMIT") query.contains("count(*)");
> if (!containsLimitOrAggregate){
> String limitQuery = query + " limit " + getFetchSize();
> return limitQuery;
> } else {
> return query;
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available
[
https://issues.apache.org/jira/browse/GEODE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reopened GEODE-68:
---
Re-opening so it can be added to Pivotal Tracker.
> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
> Labels: gfsh
> Fix For: 1.0.0-incubating.M3
>
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- |
> --
> APP_COLLECTION_LIMIT | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER | basic
> SYS_CLASSPATH |
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME | wmarkito
> SYS_JAVA_VERSION | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR |
> SYS_USER | wmarkito
> SYS_USER_HOME | /Users/wmarkito
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1548) jmx-manager-hostname-for-clients not honored
[
https://issues.apache.org/jira/browse/GEODE-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reassigned GEODE-1548:
---
Assignee: Kevin Duling
> jmx-manager-hostname-for-clients not honored
>
>
> Key: GEODE-1548
> URL: https://issues.apache.org/jira/browse/GEODE-1548
> Project: Geode
> Issue Type: Bug
> Components: gfsh, management
>Reporter: Swapnil Bawaskar
>Assignee: Kevin Duling
>
> While running Geode on AWS, found that {{jmx-manager-hostname-for-clients}}
> is not being honored resulting in not being able to connect to gfsh from
> outside AWS.
> I started a locator in AWS with the following command:
> {noformat}
> gfsh>start locator --name=locator
> --J=-Dgemfire.jmx-manager-hostname-for-clients=
> --hostname-for-clients=
> {noformat}
> When trying to connect to this locator from my laptop I get the following
> error:
> {noformat}
> gfsh>connect --locator=52.41.104.182[10334]
> Connecting to Locator at [host=52.41.104.182, port=10334] ..
> Connecting to Manager at
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099] ..
> Could not connect to :
> [host=ec2-52-41-104-182.us-west-2.compute.amazonaws.com, port=1099]. Failed
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root
> exception is java.rmi.ConnectIOException: error during JRMP connection
> establishment; nested exception is:
> java.net.SocketException: Connection reset]
> {noformat}
> Note that gfsh is trying to connect to the public dns for the instance, not
> using the {{jmx-manager-hostname-for-clients}} property provided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (GEODE-1521) APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
[
https://issues.apache.org/jira/browse/GEODE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reopened GEODE-1521:
-
Re-opening so it can be added to Pivotal Tracker.
> APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
> -
>
> Key: GEODE-1521
> URL: https://issues.apache.org/jira/browse/GEODE-1521
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Kevin Duling
>Assignee: Kevin Duling
> Fix For: 1.0.0-incubating.M3
>
>
> There are more varieties of count than simply * within the count().
> Specifically, one can do: {{count(distinct(field))}} or {{count(field)}}
> This makes checking for only {{count( * )}} incorrect. Instead, the search
> to apply the limt should look for {{" count("}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available
[
https://issues.apache.org/jira/browse/GEODE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-68:
--
Comment: was deleted
(was: Re-opening so it can be added to Pivotal Tracker.)
> GFSH SYS_HOST_NAME variable should report hostname if available
> ---
>
> Key: GEODE-68
> URL: https://issues.apache.org/jira/browse/GEODE-68
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: William Markito Oliveira
>Assignee: Kevin Duling
>Priority: Minor
> Labels: gfsh
> Fix For: 1.0.0-incubating.M3
>
>
> SYS_HOST_NAME is actually displaying SYS_USER_HOME.
> This is very useful for automation scripts.
> {code}
> gfsh>echo --string=$*
>Property| Value
> -- |
> --
> APP_COLLECTION_LIMIT | 20
> APP_FETCH_SIZE | 1000
> APP_LAST_EXIT_STATUS | 0
> APP_LOGGING_ENABLED| false
> APP_LOG_FILE | /Users/wmarkito/gfsh-%u_%g.log
> APP_NAME | gfsh
> APP_PWD| /Users/wmarkito
> APP_QUERY_RESULTS_DISPLAY_MODE | table
> APP_QUIET_EXECUTION| false
> APP_RESULT_VIEWER | basic
> SYS_CLASSPATH |
> /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar
> SYS_GEMFIRE_DIR| /Users/wmarkito/...
> SYS_HOST_NAME | wmarkito
> SYS_JAVA_VERSION | 1.7.0_72
> SYS_OS | Mac OS X
> SYS_OS_LINE_SEPARATOR |
> SYS_USER | wmarkito
> SYS_USER_HOME | /Users/wmarkito
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-117) gfsh put ignores --skip-if-exists flag
[ https://issues.apache.org/jira/browse/GEODE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-117: -- Assignee: Kevin Duling (was: Srikanth Manvi) > gfsh put ignores --skip-if-exists flag > -- > > Key: GEODE-117 > URL: https://issues.apache.org/jira/browse/GEODE-117 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dan Smith >Assignee: Kevin Duling > Labels: gfsh, starter > > Someone hit this on a forum post: > https://support.pivotal.io/hc/communities/public/questions/204414098-put-in-gfsh-doesn-t-honor-skip-if-exists-true-flag-?flash_digest=f2441b8a96ac363d6da205c6f90a62035b1a3c21 > I looked into the code, and it looks like the flag gets lost somewhere along > the way. If you look at DataCommandFunction.put, it has a putIfAbsent flag, > but that flag is not used; the function just does a normal put. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-748) Unexpected version string returned from gfsh
[
https://issues.apache.org/jira/browse/GEODE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reassigned GEODE-748:
--
Assignee: Kevin Duling
> Unexpected version string returned from gfsh
>
>
> Key: GEODE-748
> URL: https://issues.apache.org/jira/browse/GEODE-748
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
>
> {{gfsh version}} returns a version number with a prepended 'v'. This is
> inconsistent with the actual versioning which never includes a 'v'.
> The {{v}} should be removed from the specific gfsh command.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
[
https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377423#comment-15377423
]
Kevin Duling commented on GEODE-746:
Grace and I tracked the first part of this down to a problem in
{{LauncherLifecycleCommands}}:
{{String locatorHostName =
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(),
getLocalHost());}}
We've changed this to look instead at the bind address first:
{code}
String locatorHostName;
InetAddress bindAddr = locatorLauncher.getBindAddress();
if (bindAddr != null){
locatorHostName = bindAddr.getCanonicalHostName();
} else {
locatorHostName =
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(),
getLocalHost());
}
{code}
This improved things a little. The system will now connect: {{gfsh start
locator --name=locator1 --port=19991 --bind-address=192.168.1.187}}
{noformat}
Listening for transport dt_socket at address: 3
...
Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is
currently online.
Process ID: 2765
Uptime: 1 minute 23 seconds
GemFire Version: 1.0.0-incubating-SNAPSHOT
Java Version: 1.8.0_92
Log File: /gemfire/open/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=2
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path:
/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
Successfully connected to: [host=pdx2-office-dhcp9.eng.vmware.com, port=1099]
Cluster configuration service is up and running.
{noformat}
But now the successfully connected message is showing the wrong IP address.
Looking at netstat, we can see that the listener is correctly bound to the IP
address specified:
{noformat}
$ netstat -an | grep 19991
tcp4 0 0 192.168.1.187.19991*.*LISTEN
{noformat}
Yet the hostname actually resolves to a different NIC: {{ping
pdx2-office-dhcp9.eng.vmware.com}}
{noformat}
PING pdx2-office-dhcp9.eng.vmware.com (10.118.33.209): 56 data bytes
{noformat}
Both NICs exist on this machine, just one is being erroneously reported:
{{nestat -rn}}
{noformat}
Routing tables
Internet:
DestinationGatewayFlagsRefs Use Netif Expire
default10.118.33.253 UGSc 3600 en4
default192.168.1.253 UGScI 350 en0
{noformat}
Tracing this down, it appears to be an incorrect response from the locator in
{{ShellCommands.connectToLocator(String host, int port, int timeout,
Map props)}}
{code}
JmxManagerLocatorResponse locatorResponse = JmxManagerLocatorRequest.send(host,
port, timeout, props);
// locatorResponse: “JmxManagerLocatorResponse [host=10.118.33.209, port=1099,
ssl=false, ex=null]”
// host: “192.168.1.187”
// port: 19991
// timeout: 15000
// props: size = 0
{code}
> When starting a locator using --bind-address, gfsh prints incorrect connect
> message
> ---
>
> Key: GEODE-746
> URL: https://issues.apache.org/jira/browse/GEODE-746
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
>
> When starting my locator with {{gfsh start locator --name=locator1
> --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like
> this:
> {noformat}
> ..
> Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1
> is currently online.
> Process ID: 2666
> Uptime: 15 seconds
> GemFire Version: 8.2.0.Beta
> Java Version: 1.7.0_72
> Log File: /Users/jdeppe/debug/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path:
> /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar
> Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the
> locator.
> Failed to connect; unknown cause: Connection refused
> {noformat}
> The connect string shown is just displaying my host address and not the bind
> address.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
[
https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377423#comment-15377423
]
Kevin Duling edited comment on GEODE-746 at 7/14/16 10:45 PM:
--
Grace and I tracked the first part of this down to a problem in
{{LauncherLifecycleCommands}}:
{{String locatorHostName =
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(),
getLocalHost());}}
We've changed this to look instead at the bind address first:
{code}
String locatorHostName;
InetAddress bindAddr = locatorLauncher.getBindAddress();
if (bindAddr != null){
locatorHostName = bindAddr.getCanonicalHostName();
} else {
locatorHostName =
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(),
getLocalHost());
}
{code}
This resolved the problem. The system will now connect: {{gfsh start locator
--name=locator1 --port=19991 --bind-address=192.168.1.187}}
{noformat}
Listening for transport dt_socket at address: 3
...
Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is
currently online.
Process ID: 2765
Uptime: 1 minute 23 seconds
GemFire Version: 1.0.0-incubating-SNAPSHOT
Java Version: 1.8.0_92
Log File: /gemfire/open/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=2
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path:
/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
Successfully connected to: [host=pdx2-office-dhcp9.eng.vmware.com, port=1099]
Cluster configuration service is up and running.
{noformat}
The successfully connected message appears to be showing the wrong IP address.
Looking at netstat, we can see that the listener is correctly bound to the IP
address specified:
{noformat}
$ netstat -an | grep 19991
tcp4 0 0 192.168.1.187.19991*.*LISTEN
{noformat}
The "successfully connected" hostname reports a different NIC: {{ping
pdx2-office-dhcp9.eng.vmware.com}}
{noformat}
PING pdx2-office-dhcp9.eng.vmware.com (10.118.33.209): 56 data bytes
{noformat}
Both NICs exist on this machine: {{nestat -rn}}
{noformat}
Routing tables
Internet:
DestinationGatewayFlagsRefs Use Netif Expire
default10.118.33.253 UGSc 3600 en4
default192.168.1.253 UGScI 350 en0
{noformat}
Tracing this down, the address is coming from this line in
{{ShellCommands.connectToLocator(String host, int port, int timeout,
Map props)}}
{code}
JmxManagerLocatorResponse locatorResponse = JmxManagerLocatorRequest.send(host,
port, timeout, props);
// locatorResponse: “JmxManagerLocatorResponse [host=10.118.33.209, port=1099,
ssl=false, ex=null]”
// host: “192.168.1.187”
// port: 19991
// timeout: 15000
// props: size = 0
{code}
So the confusion here now is that this is the JMX address, not the locator
address. The formatting of this message lends one to believe it's supposed to
be the locator. Yet, if you look at the original response from the system, it
correctly reports the Locator's address:
{noformat}
Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is
currently online.
{noformat}
I've added JMX to the "successfully connected" message to reduce confusion.
was (Author: kduling):
Grace and I tracked the first part of this down to a problem in
{{LauncherLifecycleCommands}}:
{{String locatorHostName =
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(),
getLocalHost());}}
We've changed this to look instead at the bind address first:
{code}
String locatorHostName;
InetAddress bindAddr = locatorLauncher.getBindAddress();
if (bindAddr != null){
locatorHostName = bindAddr.getCanonicalHostName();
} else {
locatorHostName =
StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(),
getLocalHost());
}
{code}
This improved things a little. The system will now connect: {{gfsh start
locator --name=locator1 --port=19991 --bind-address=192.168.1.187}}
{noformat}
Listening for transport dt_socket at address: 3
...
Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is
currently online.
Process ID: 2765
Uptime: 1 minute 23 seconds
GemFire Version: 1.0.0-incubating-SNAPSHOT
Java Version: 1.8.0_92
Log File: /gemfire/open/locator1/locator1.log
JVM Arguments: -Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false
[jira] [Resolved] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
[
https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-746.
Resolution: Fixed
> When starting a locator using --bind-address, gfsh prints incorrect connect
> message
> ---
>
> Key: GEODE-746
> URL: https://issues.apache.org/jira/browse/GEODE-746
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
>
> When starting my locator with {{gfsh start locator --name=locator1
> --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like
> this:
> {noformat}
> ..
> Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1
> is currently online.
> Process ID: 2666
> Uptime: 15 seconds
> GemFire Version: 8.2.0.Beta
> Java Version: 1.7.0_72
> Log File: /Users/jdeppe/debug/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path:
> /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar
> Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the
> locator.
> Failed to connect; unknown cause: Connection refused
> {noformat}
> The connect string shown is just displaying my host address and not the bind
> address.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1706) miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Kevin Duling created GEODE-1706:
---
Summary:
miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Key: GEODE-1706
URL: https://issues.apache.org/jira/browse/GEODE-1706
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3411:
{noformat}
Error Message
java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the
shell to disconnect!
Stacktrace
java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the
shell to disconnect!
at org.junit.Assert.fail(Assert.java:88)
at com.gemstone.gemfire.test.dunit.Wait.waitForCriterion(Wait.java:185)
at
com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.testShutDownWithoutTimeout(MiscellaneousCommandsDUnitTest.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
[jira] [Created] (GEODE-1704) FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore
Kevin Duling created GEODE-1704:
---
Summary:
FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore
Key: GEODE-1704
URL: https://issues.apache.org/jira/browse/GEODE-1704
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3414:
{noformat}
Error Message
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run
in VM 3 running on Host japan.gemstone.com with 4 VMs
Stacktrace
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run
in VM 3 running on Host japan.gemstone.com with 4 VMs
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
at
com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore(FixedPartitioningDUnitTest.java:1029)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
[jira] [Created] (GEODE-1705) DurableClientCommandsDUnitTest.testCloseDurableCQ
Kevin Duling created GEODE-1705:
---
Summary: DurableClientCommandsDUnitTest.testCloseDurableCQ
Key: GEODE-1705
URL: https://issues.apache.org/jira/browse/GEODE-1705
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3414:
{noformat}
Error Message
java.lang.AssertionError
Stacktrace
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
com.gemstone.gemfire.management.internal.cli.commands.DurableClientCommandsDUnitTest.testCloseDurableCQ(DurableClientCommandsDUnitTest.java:138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.GeneratedMethodAccessor377.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor376.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
[jira] [Updated] (GEODE-1706) miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1706:
Labels: ci (was: )
> miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
>
>
> Key: GEODE-1706
> URL: https://issues.apache.org/jira/browse/GEODE-1706
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: ci
>
> In Geode_develop_DistributedTests/3411:
> {noformat}
> Error Message
> java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the
> shell to disconnect!
> Stacktrace
> java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the
> shell to disconnect!
> at org.junit.Assert.fail(Assert.java:88)
> at com.gemstone.gemfire.test.dunit.Wait.waitForCriterion(Wait.java:185)
> at
> com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.testShutDownWithoutTimeout(MiscellaneousCommandsDUnitTest.java:245)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
>
[jira] [Created] (GEODE-1708) CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
Kevin Duling created GEODE-1708:
---
Summary:
CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
Key: GEODE-1708
URL: https://issues.apache.org/jira/browse/GEODE-1708
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3423:
{noformat}
Error Message
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1
running on Host cc2-rh6.gemstone.com with 4 VMs
Stacktrace
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1
running on Host cc2-rh6.gemstone.com with 4 VMs
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
at
com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults(CompiledInDUnitTest.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
[jira] [Updated] (GEODE-1708) CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
[
https://issues.apache.org/jira/browse/GEODE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1708:
Labels: CI (was: )
> CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
> -
>
> Key: GEODE-1708
> URL: https://issues.apache.org/jira/browse/GEODE-1708
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: CI
>
> In Geode_develop_DistributedTests/3423:
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1
> running on Host cc2-rh6.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1
> running on Host cc2-rh6.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
> at
> com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults(CompiledInDUnitTest.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Updated] (GEODE-1710) CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
[
https://issues.apache.org/jira/browse/GEODE-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1710:
Labels: CI (was: )
> CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
> --
>
> Key: GEODE-1710
> URL: https://issues.apache.org/jira/browse/GEODE-1710
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: CI
>
> In Geode_develop_DistributedTests/3430:
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1
> running on Host kuwait.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1
> running on Host kuwait.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
> at
> com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults(CompiledInDUnitTest.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
>
[jira] [Created] (GEODE-1710) CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
Kevin Duling created GEODE-1710:
---
Summary:
CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
Key: GEODE-1710
URL: https://issues.apache.org/jira/browse/GEODE-1710
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3430:
{noformat}
Error Message
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1
running on Host kuwait.gemstone.com with 4 VMs
Stacktrace
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1
running on Host kuwait.gemstone.com with 4 VMs
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
at
com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults(CompiledInDUnitTest.java:236)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at
[jira] [Updated] (GEODE-1704) FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore
[
https://issues.apache.org/jira/browse/GEODE-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1704:
Labels: ci (was: )
> FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore
> --
>
> Key: GEODE-1704
> URL: https://issues.apache.org/jira/browse/GEODE-1704
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: ci
>
> In Geode_develop_DistributedTests/3414:
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run
> in VM 3 running on Host japan.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run
> in VM 3 running on Host japan.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
> at
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore(FixedPartitioningDUnitTest.java:1029)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
[jira] [Updated] (GEODE-1705) DurableClientCommandsDUnitTest.testCloseDurableCQ
[
https://issues.apache.org/jira/browse/GEODE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1705:
Labels: ci (was: )
> DurableClientCommandsDUnitTest.testCloseDurableCQ
> -
>
> Key: GEODE-1705
> URL: https://issues.apache.org/jira/browse/GEODE-1705
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: ci
>
> In Geode_develop_DistributedTests/3414:
> {noformat}
> Error Message
> java.lang.AssertionError
> Stacktrace
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> com.gemstone.gemfire.management.internal.cli.commands.DurableClientCommandsDUnitTest.testCloseDurableCQ(DurableClientCommandsDUnitTest.java:138)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.GeneratedMethodAccessor377.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.GeneratedMethodAccessor376.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Created] (GEODE-1709) LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound
Kevin Duling created GEODE-1709:
---
Summary:
LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound
Key: GEODE-1709
URL: https://issues.apache.org/jira/browse/GEODE-1709
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3421:
{noformat}
Error Message
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
venezuela.gemstone.com with 4 VMs
Stacktrace
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
venezuela.gemstone.com with 4 VMs
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308)
at
com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:125)
at
com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:118)
at
com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:109)
at
com.gemstone.gemfire.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.createJMXManager(LuceneIndexCommandsDUnitTest.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
[jira] [Updated] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1467: Component/s: docs > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: docs, rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1467: --- Assignee: Kevin Duling > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reopened GEODE-1467: - > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15397847#comment-15397847 ] Kevin Duling edited comment on GEODE-1467 at 7/28/16 5:34 PM: -- Added the servlets to Jetty twice as a temporary solution in order to support both contexts for a period of time. Updated DUnit tests to test both URL endpoints. gemfire-api became geode gemfire became geode-mgmt was (Author: kduling): Added the servlets to Jetty twice as a temporary solution in order to support both contexts for a period of time. Updated DUnit tests to test both URL endpoints. > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: docs, rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1699) LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused
Kevin Duling created GEODE-1699:
---
Summary:
LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused
Key: GEODE-1699
URL: https://issues.apache.org/jira/browse/GEODE-1699
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3402:
{noformat}
Error Message
java.lang.AssertionError
Stacktrace
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
com.gemstone.gemfire.cache.lucene.LuceneQueriesPRBase.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused(LuceneQueriesPRBase.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Standard Output
Previously run tests:
[jira] [Updated] (GEODE-1699) LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused
[
https://issues.apache.org/jira/browse/GEODE-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1699:
Labels: ci (was: )
> LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused
> --
>
> Key: GEODE-1699
> URL: https://issues.apache.org/jira/browse/GEODE-1699
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: ci
>
> In Geode_develop_DistributedTests/3402:
> {noformat}
> Error Message
> java.lang.AssertionError
> Stacktrace
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> com.gemstone.gemfire.cache.lucene.LuceneQueriesPRBase.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused(LuceneQueriesPRBase.java:120)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
>
[jira] [Updated] (GEODE-1697) RedisDistDUnitTest.testConcOps
[
https://issues.apache.org/jira/browse/GEODE-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1697:
Labels: ci (was: )
> RedisDistDUnitTest.testConcOps
> --
>
> Key: GEODE-1697
> URL: https://issues.apache.org/jira/browse/GEODE-1697
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: ci
>
> In Geode_develop_DistributedTests/3405:
> {noformat}
> Error Message
> java.lang.AssertionError: An exception occurred during asynchronous
> invocation.
> Stacktrace
> java.lang.AssertionError: An exception occurred during asynchronous
> invocation.
> at
> com.gemstone.gemfire.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:155)
> at
> com.gemstone.gemfire.test.dunit.AsyncInvocation.getResult(AsyncInvocation.java:178)
> at
> org.apache.geode.redis.RedisDistDUnitTest.testConcOps(RedisDistDUnitTest.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
>
[jira] [Created] (GEODE-1697) RedisDistDUnitTest.testConcOps
Kevin Duling created GEODE-1697:
---
Summary: RedisDistDUnitTest.testConcOps
Key: GEODE-1697
URL: https://issues.apache.org/jira/browse/GEODE-1697
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3405:
{noformat}
Error Message
java.lang.AssertionError: An exception occurred during asynchronous invocation.
Stacktrace
java.lang.AssertionError: An exception occurred during asynchronous invocation.
at
com.gemstone.gemfire.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:155)
at
com.gemstone.gemfire.test.dunit.AsyncInvocation.getResult(AsyncInvocation.java:178)
at
org.apache.geode.redis.RedisDistDUnitTest.testConcOps(RedisDistDUnitTest.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
at
[jira] [Updated] (GEODE-1698) PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode
[
https://issues.apache.org/jira/browse/GEODE-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1698:
Labels: ci (was: )
> PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode
> -
>
> Key: GEODE-1698
> URL: https://issues.apache.org/jira/browse/GEODE-1698
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: ci
>
> In Geode_develop_DistributedTests/3398:
> {noformat}
> Error Message
> com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected., caused by
> com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to
> heartbeat requests
> Stacktrace
> com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected., caused by
> com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to
> heartbeat requests
> at
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:790)
> at
> com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1384)
> at
> com.gemstone.gemfire.distributed.internal.ReplyProcessor21.getDistributionManager(ReplyProcessor21.java:369)
> at
> com.gemstone.gemfire.distributed.internal.ReplyProcessor21.postWait(ReplyProcessor21.java:603)
> at
> com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:844)
> at
> com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:796)
> at
> com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:886)
> at
> com.gemstone.gemfire.internal.cache.UpdateAttributesProcessor.waitForProfileResponse(UpdateAttributesProcessor.java:111)
> at
> com.gemstone.gemfire.internal.cache.UpdateAttributesProcessor.distribute(UpdateAttributesProcessor.java:99)
> at
> com.gemstone.gemfire.distributed.internal.DistributionAdvisor.exchangeProfiles(DistributionAdvisor.java:1131)
> at
> com.gemstone.gemfire.distributed.internal.DistributionAdvisor.initializationGate(DistributionAdvisor.java:458)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1096)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:763)
> at
> com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:751)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:181)
> at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:172)
> at
> com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.createCache(JUnit4CacheTestCase.java:120)
> at
> com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:263)
> at
> com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:242)
> at
> com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:234)
> at
> com.gemstone.gemfire.internal.cache.execute.PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode(PRColocationDUnitTest.java:1309)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
>
[jira] [Created] (GEODE-1698) PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode
Kevin Duling created GEODE-1698:
---
Summary:
PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode
Key: GEODE-1698
URL: https://issues.apache.org/jira/browse/GEODE-1698
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3398:
{noformat}
Error Message
com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This
connection to a distributed system has been disconnected., caused by
com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to
heartbeat requests
Stacktrace
com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This
connection to a distributed system has been disconnected., caused by
com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to
heartbeat requests
at
com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:790)
at
com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1384)
at
com.gemstone.gemfire.distributed.internal.ReplyProcessor21.getDistributionManager(ReplyProcessor21.java:369)
at
com.gemstone.gemfire.distributed.internal.ReplyProcessor21.postWait(ReplyProcessor21.java:603)
at
com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:844)
at
com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:796)
at
com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:886)
at
com.gemstone.gemfire.internal.cache.UpdateAttributesProcessor.waitForProfileResponse(UpdateAttributesProcessor.java:111)
at
com.gemstone.gemfire.internal.cache.UpdateAttributesProcessor.distribute(UpdateAttributesProcessor.java:99)
at
com.gemstone.gemfire.distributed.internal.DistributionAdvisor.exchangeProfiles(DistributionAdvisor.java:1131)
at
com.gemstone.gemfire.distributed.internal.DistributionAdvisor.initializationGate(DistributionAdvisor.java:458)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1096)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:763)
at
com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:751)
at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:181)
at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:172)
at
com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.createCache(JUnit4CacheTestCase.java:120)
at
com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:263)
at
com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:242)
at
com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:234)
at
com.gemstone.gemfire.internal.cache.execute.PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode(PRColocationDUnitTest.java:1309)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at
[jira] [Resolved] (GEODE-1680) Change "list regions" to DATA:READ permissions
[ https://issues.apache.org/jira/browse/GEODE-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1680. - Resolution: Fixed > Change "list regions" to DATA:READ permissions > -- > > Key: GEODE-1680 > URL: https://issues.apache.org/jira/browse/GEODE-1680 > Project: Geode > Issue Type: Task > Components: gfsh, security >Reporter: Kevin Duling >Assignee: Kevin Duling > > Currently, "list regions" requires CLUSTER:READ permissions. This should be > DATA:READ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1680) Change "list regions" to DATA:READ permissions
[ https://issues.apache.org/jira/browse/GEODE-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1680: --- Assignee: Kevin Duling > Change "list regions" to DATA:READ permissions > -- > > Key: GEODE-1680 > URL: https://issues.apache.org/jira/browse/GEODE-1680 > Project: Geode > Issue Type: Task > Components: gfsh, security >Reporter: Kevin Duling >Assignee: Kevin Duling > > Currently, "list regions" requires CLUSTER:READ permissions. This should be > DATA:READ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1680) Change "list regions" to DATA:READ permissions
Kevin Duling created GEODE-1680: --- Summary: Change "list regions" to DATA:READ permissions Key: GEODE-1680 URL: https://issues.apache.org/jira/browse/GEODE-1680 Project: Geode Issue Type: Task Components: gfsh, security Reporter: Kevin Duling Currently, "list regions" requires CLUSTER:READ permissions. This should be DATA:READ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1617) Regions can be created with a variety of characters that are unsupported
[
https://issues.apache.org/jira/browse/GEODE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-1617.
-
Resolution: Fixed
Added a test at creation for valid characters in region names for all
non-internal regions.
> Regions can be created with a variety of characters that are unsupported
>
>
> Key: GEODE-1617
> URL: https://issues.apache.org/jira/browse/GEODE-1617
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Kevin Duling
>Assignee: Kevin Duling
>
> Per this
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html],
> and this
> [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html]
> on the dev forums and [geode
> documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html],
> region names may only consist of alphanumeric characters, an underscore, and
> a hyphen. These rules are not enforced.
> E.g., it is possible to create a region with:
> {{gfsh> create region --name=not^good --type=REPLICATE}}
> Some of these regions may be removed with the {{destroy}} command, while
> others cannot be located.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
[
https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reassigned GEODE-746:
--
Assignee: Kevin Duling
> When starting a locator using --bind-address, gfsh prints incorrect connect
> message
> ---
>
> Key: GEODE-746
> URL: https://issues.apache.org/jira/browse/GEODE-746
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Kevin Duling
>
> When starting my locator with {{gfsh start locator --name=locator1
> --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like
> this:
> {noformat}
> ..
> Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1
> is currently online.
> Process ID: 2666
> Uptime: 15 seconds
> GemFire Version: 8.2.0.Beta
> Java Version: 1.7.0_72
> Log File: /Users/jdeppe/debug/locator1/locator1.log
> JVM Arguments: -Dgemfire.enable-cluster-configuration=true
> -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path:
> /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar
> Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the
> locator.
> Failed to connect; unknown cause: Connection refused
> {noformat}
> The connect string shown is just displaying my host address and not the bind
> address.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1709) LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound
[
https://issues.apache.org/jira/browse/GEODE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1709:
Labels: CI (was: )
> LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound
>
>
> Key: GEODE-1709
> URL: https://issues.apache.org/jira/browse/GEODE-1709
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: CI
>
> In Geode_develop_DistributedTests/3421:
> {noformat}
> Error Message
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
> venezuela.gemstone.com with 4 VMs
> Stacktrace
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
> venezuela.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:125)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:118)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:109)
> at
> com.gemstone.gemfire.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.createJMXManager(LuceneIndexCommandsDUnitTest.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
>
[jira] [Updated] (GEODE-1711) PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf
[
https://issues.apache.org/jira/browse/GEODE-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1711:
Labels: CI (was: )
> PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf
> ---
>
> Key: GEODE-1711
> URL: https://issues.apache.org/jira/browse/GEODE-1711
> Project: Geode
> Issue Type: Bug
>Reporter: Kevin Duling
> Labels: CI
>
> In Geode_develop_DistributedTests/3421:
> {noformat}
> Error Message
> com.gemstone.gemfire.cache.DiskAccessException: For DiskStore:
> PersistentRVVRecoveryDUnitTest_testWriteCorrectVersionToKrfRegion: Could not
> schedule asynchronous write because the flusher thread had been terminated.
> Stacktrace
> com.gemstone.gemfire.cache.DiskAccessException: For DiskStore:
> PersistentRVVRecoveryDUnitTest_testWriteCorrectVersionToKrfRegion: Could not
> schedule asynchronous write because the flusher thread had been terminated.
> at
> com.gemstone.gemfire.internal.cache.DiskStoreImpl.checkForFlusherThreadTermination(DiskStoreImpl.java:1223)
> at
> com.gemstone.gemfire.internal.cache.DiskStoreImpl.addAsyncItem(DiskStoreImpl.java:1271)
> at
> com.gemstone.gemfire.internal.cache.DiskStoreImpl.scheduleAsyncWrite(DiskStoreImpl.java:1335)
> at
> com.gemstone.gemfire.internal.cache.DiskRegion.scheduleAsyncWrite(DiskRegion.java:483)
> at
> com.gemstone.gemfire.internal.cache.DiskEntry$Helper.scheduleAsyncWrite(DiskEntry.java:1494)
> at
> com.gemstone.gemfire.internal.cache.DiskEntry$Helper.update(DiskEntry.java:1034)
> at
> com.gemstone.gemfire.internal.cache.AbstractDiskRegionEntry.setValue(AbstractDiskRegionEntry.java:42)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegionEntry.setValueWithTombstoneCheck(AbstractRegionEntry.java:241)
> at
> com.gemstone.gemfire.internal.cache.EntryEventImpl.setNewValueInRegion(EntryEventImpl.java:1614)
> at
> com.gemstone.gemfire.internal.cache.EntryEventImpl.putExistingEntry(EntryEventImpl.java:1482)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegionMap.updateEntry(AbstractRegionMap.java:2882)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2713)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5955)
> at
> com.gemstone.gemfire.internal.cache.DistributedRegion.virtualPut(DistributedRegion.java:348)
> at
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5350)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1668)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1655)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf(PersistentRVVRecoveryDUnitTest.java:824)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
>
[jira] [Created] (GEODE-1711) PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf
Kevin Duling created GEODE-1711:
---
Summary:
PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf
Key: GEODE-1711
URL: https://issues.apache.org/jira/browse/GEODE-1711
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3421:
{noformat}
Error Message
com.gemstone.gemfire.cache.DiskAccessException: For DiskStore:
PersistentRVVRecoveryDUnitTest_testWriteCorrectVersionToKrfRegion: Could not
schedule asynchronous write because the flusher thread had been terminated.
Stacktrace
com.gemstone.gemfire.cache.DiskAccessException: For DiskStore:
PersistentRVVRecoveryDUnitTest_testWriteCorrectVersionToKrfRegion: Could not
schedule asynchronous write because the flusher thread had been terminated.
at
com.gemstone.gemfire.internal.cache.DiskStoreImpl.checkForFlusherThreadTermination(DiskStoreImpl.java:1223)
at
com.gemstone.gemfire.internal.cache.DiskStoreImpl.addAsyncItem(DiskStoreImpl.java:1271)
at
com.gemstone.gemfire.internal.cache.DiskStoreImpl.scheduleAsyncWrite(DiskStoreImpl.java:1335)
at
com.gemstone.gemfire.internal.cache.DiskRegion.scheduleAsyncWrite(DiskRegion.java:483)
at
com.gemstone.gemfire.internal.cache.DiskEntry$Helper.scheduleAsyncWrite(DiskEntry.java:1494)
at
com.gemstone.gemfire.internal.cache.DiskEntry$Helper.update(DiskEntry.java:1034)
at
com.gemstone.gemfire.internal.cache.AbstractDiskRegionEntry.setValue(AbstractDiskRegionEntry.java:42)
at
com.gemstone.gemfire.internal.cache.AbstractRegionEntry.setValueWithTombstoneCheck(AbstractRegionEntry.java:241)
at
com.gemstone.gemfire.internal.cache.EntryEventImpl.setNewValueInRegion(EntryEventImpl.java:1614)
at
com.gemstone.gemfire.internal.cache.EntryEventImpl.putExistingEntry(EntryEventImpl.java:1482)
at
com.gemstone.gemfire.internal.cache.AbstractRegionMap.updateEntry(AbstractRegionMap.java:2882)
at
com.gemstone.gemfire.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2713)
at
com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5955)
at
com.gemstone.gemfire.internal.cache.DistributedRegion.virtualPut(DistributedRegion.java:348)
at
com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
at
com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5350)
at
com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1668)
at
com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1655)
at
com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
at
com.gemstone.gemfire.internal.cache.persistence.PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf(PersistentRVVRecoveryDUnitTest.java:824)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
[jira] [Updated] (GEODE-1615) gfsh unable to destroy region that has an hyphen in its name
[
https://issues.apache.org/jira/browse/GEODE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling updated GEODE-1615:
Summary: gfsh unable to destroy region that has an hyphen in its name
(was: gfsh unable to destroy region that has an hyphen in it's name)
> gfsh unable to destroy region that has an hyphen in its name
>
>
> Key: GEODE-1615
> URL: https://issues.apache.org/jira/browse/GEODE-1615
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Kevin Duling
>
> Can be reproduced as follows:
> {noformat}
> gfsh>list regions
> List of regions
> ---
> region-name
> region_name
> gfsh>destroy region --name=region_name
> "region_name" destroyed successfully.
> gfsh>list regions
> List of regions
> ---
> region-name
> gfsh>destroy region --name=region-name
> Could not find a Region with Region path "region-name" in this Geode cluster.
> If region was recently
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1615) gfsh unable to destroy region that has an hyphen in it's name
[
https://issues.apache.org/jira/browse/GEODE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reassigned GEODE-1615:
---
Assignee: Kevin Duling
> gfsh unable to destroy region that has an hyphen in it's name
> -
>
> Key: GEODE-1615
> URL: https://issues.apache.org/jira/browse/GEODE-1615
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Kevin Duling
>
> Can be reproduced as follows:
> {noformat}
> gfsh>list regions
> List of regions
> ---
> region-name
> region_name
> gfsh>destroy region --name=region_name
> "region_name" destroyed successfully.
> gfsh>list regions
> List of regions
> ---
> region-name
> gfsh>destroy region --name=region-name
> Could not find a Region with Region path "region-name" in this Geode cluster.
> If region was recently
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1615) gfsh unable to destroy region that has an hyphen in its name
[
https://issues.apache.org/jira/browse/GEODE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15357762#comment-15357762
]
Kevin Duling commented on GEODE-1615:
-
Found that internally, the region is stored as {{service=Region,
name="/region-name", type=Member}} and the query to find it is not placing
quotes around the name.
Conversely, non-hyphenated regions do not contain quotes. E.g.,
{{service=Region, name=good, type=Member}}
The mechanism that added quotes during creation is not being triggered when
destroying, therefore the lookup fails.
> gfsh unable to destroy region that has an hyphen in its name
>
>
> Key: GEODE-1615
> URL: https://issues.apache.org/jira/browse/GEODE-1615
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Kevin Duling
>
> Can be reproduced as follows:
> {noformat}
> gfsh>list regions
> List of regions
> ---
> region-name
> region_name
> gfsh>destroy region --name=region_name
> "region_name" destroyed successfully.
> gfsh>list regions
> List of regions
> ---
> region-name
> gfsh>destroy region --name=region-name
> Could not find a Region with Region path "region-name" in this Geode cluster.
> If region was recently
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1466) Branding: rename gemfire.properties file to geode.properties file
[ https://issues.apache.org/jira/browse/GEODE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1466: --- Assignee: Kevin Duling (was: Kirk Lund) > Branding: rename gemfire.properties file to geode.properties file > - > > Key: GEODE-1466 > URL: https://issues.apache.org/jira/browse/GEODE-1466 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Nitin Lamba >Assignee: Kevin Duling > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > Currently, all runtime properties defined at startup are defined in > gemfire.properties file and the namespace also starts with gemfire. It is > desirable to rename this to geode. > This will affect multiple modules (a lot of string literals) across the > project and may create config migration issues later on, hence is important > for the 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1466) Branding: rename gemfire.properties file to geode.properties file
[ https://issues.apache.org/jira/browse/GEODE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530282#comment-15530282 ] Kevin Duling commented on GEODE-1466: - What do you suggest gfsecurity be renamed to? geode-security.properties? > Branding: rename gemfire.properties file to geode.properties file > - > > Key: GEODE-1466 > URL: https://issues.apache.org/jira/browse/GEODE-1466 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Nitin Lamba >Assignee: Kirk Lund > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > Currently, all runtime properties defined at startup are defined in > gemfire.properties file and the namespace also starts with gemfire. It is > desirable to rename this to geode. > This will affect multiple modules (a lot of string literals) across the > project and may create config migration issues later on, hence is important > for the 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility
[ https://issues.apache.org/jira/browse/GEODE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1902: Component/s: docs > Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards > compatibility > --- > > Key: GEODE-1902 > URL: https://issues.apache.org/jira/browse/GEODE-1902 > Project: Geode > Issue Type: Improvement > Components: docs, logging >Reporter: Kirk Lund >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > > If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they > either need to change this to GEODE_VERBOSE or we need to add some sort of > alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility
[ https://issues.apache.org/jira/browse/GEODE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1902. - Resolution: Fixed Fix Version/s: 1.0.0-incubating > Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards > compatibility > --- > > Key: GEODE-1902 > URL: https://issues.apache.org/jira/browse/GEODE-1902 > Project: Geode > Issue Type: Improvement > Components: docs, logging >Reporter: Kirk Lund >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > > If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they > either need to change this to GEODE_VERBOSE or we need to add some sort of > alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility
[ https://issues.apache.org/jira/browse/GEODE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530244#comment-15530244 ] Kevin Duling commented on GEODE-1902: - log4j doesn't allow aliases or synonyms, making two markers behave identically. But it does support a child-parent hierarchy. GEMFIRE_VERBOSE was made the parent of GEODE_VERBOSE so that filtering gemfire would also filter geode. However, if only geode is filters, gemfire messages will not be. GEMFIRE_VERBOSE should be considered to be deprecated and will be removed in the near future. > Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards > compatibility > --- > > Key: GEODE-1902 > URL: https://issues.apache.org/jira/browse/GEODE-1902 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Kirk Lund >Assignee: Kevin Duling > > If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they > either need to change this to GEODE_VERBOSE or we need to add some sort of > alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-136) Fix possible NullPointerException in Gfsh's 'list regions' command's GetRegionsFunction.
[
https://issues.apache.org/jira/browse/GEODE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling reassigned GEODE-136:
--
Assignee: Kevin Duling
> Fix possible NullPointerException in Gfsh's 'list regions' command's
> GetRegionsFunction.
>
>
> Key: GEODE-136
> URL: https://issues.apache.org/jira/browse/GEODE-136
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.0.0-incubating
> Environment: GemFire Manager + Gfsh
>Reporter: John Blum
>Assignee: Kevin Duling
> Labels: ApacheGeode, CLI, GFSH, GetRegionsFunction, list-regions
> Fix For: 1.0.0-incubating
>
>
> The following line
> ([#48|https://github.com/apache/incubator-geode/blob/develop/gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/functions/GetRegionsFunction.java#L48])
> in the {{GetRegionsFunction}} class could possibly lead to a NPE if the
> {{regions}} _Set_ is null since the {{regions.isEmpty()}} call proceeds the
> {{regions == null}} check.
> Of course, one should argue whether {{Cache.rootRegions()}} should be
> returning a null _Set_ at all rather than an empty _Set_ if there are in fact
> no "root" _Regions_ in the Geode _Cache_.
> But then, one could also argue that this {{GetRegionsFunction}} should not be
> returning a null "array" if there are no "root" _Regions_ in the Geode
> _Cache_ either. It too should be returning an "empty" array.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1657) Source files should not contain Windows linefeeds
[
https://issues.apache.org/jira/browse/GEODE-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552589#comment-15552589
]
Kevin Duling commented on GEODE-1657:
-
Depending on how contributors have their git set up, this can be an ongoing
problem. In Geode, there are over 300 files that have Windows linefeeds in
them.
{code}
grep -IlR ^M * | wc -l
319
{code}
This article has suggestions on how to address the issue:
https://help.github.com/articles/dealing-with-line-endings/
> Source files should not contain Windows linefeeds
> -
>
> Key: GEODE-1657
> URL: https://issues.apache.org/jira/browse/GEODE-1657
> Project: Geode
> Issue Type: Bug
> Components: general
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
>
> geode-pulse/src/test/java/com/vmware/gemfire/tools/pulse/tests/Server.java
> contains ^M (Windows linefeeds).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-136) Fix possible NullPointerException in Gfsh's 'list regions' command's GetRegionsFunction.
[
https://issues.apache.org/jira/browse/GEODE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Duling resolved GEODE-136.
Resolution: Fixed
Changed the order of the null test to be sane.
Did not change the results as this is not internal, therefore creating a
broader discussion.
Created the missing unit test for this class.
> Fix possible NullPointerException in Gfsh's 'list regions' command's
> GetRegionsFunction.
>
>
> Key: GEODE-136
> URL: https://issues.apache.org/jira/browse/GEODE-136
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.0.0-incubating
> Environment: GemFire Manager + Gfsh
>Reporter: John Blum
>Assignee: Kevin Duling
> Labels: ApacheGeode, CLI, GFSH, GetRegionsFunction, list-regions
> Fix For: 1.0.0-incubating
>
>
> The following line
> ([#48|https://github.com/apache/incubator-geode/blob/develop/gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/functions/GetRegionsFunction.java#L48])
> in the {{GetRegionsFunction}} class could possibly lead to a NPE if the
> {{regions}} _Set_ is null since the {{regions.isEmpty()}} call proceeds the
> {{regions == null}} check.
> Of course, one should argue whether {{Cache.rootRegions()}} should be
> returning a null _Set_ at all rather than an empty _Set_ if there are in fact
> no "root" _Regions_ in the Geode _Cache_.
> But then, one could also argue that this {{GetRegionsFunction}} should not be
> returning a null "array" if there are no "root" _Regions_ in the Geode
> _Cache_ either. It too should be returning an "empty" array.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1570) developer REST API should be secured
[ https://issues.apache.org/jira/browse/GEODE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1570: --- Assignee: Kevin Duling > developer REST API should be secured > > > Key: GEODE-1570 > URL: https://issues.apache.org/jira/browse/GEODE-1570 > Project: Geode > Issue Type: Sub-task > Components: rest (dev), security >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > > The developer REST API should require authentication when security is > enabled. For authorization, the implementation should use the new > Resource:Operation permissions API that is used by JMX. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1467. - Resolution: Fixed Fix Version/s: 1.0.0-incubating > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: docs, rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility
[ https://issues.apache.org/jira/browse/GEODE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1902: --- Assignee: Kevin Duling > Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards > compatibility > --- > > Key: GEODE-1902 > URL: https://issues.apache.org/jira/browse/GEODE-1902 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Kirk Lund >Assignee: Kevin Duling > > If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they > either need to change this to GEODE_VERBOSE or we need to add some sort of > alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1466) Branding: rename gemfire.properties file to geode.properties file
[ https://issues.apache.org/jira/browse/GEODE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1466: Assignee: Kirk Lund (was: Kevin Duling) > Branding: rename gemfire.properties file to geode.properties file > - > > Key: GEODE-1466 > URL: https://issues.apache.org/jira/browse/GEODE-1466 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Nitin Lamba >Assignee: Kirk Lund > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > Currently, all runtime properties defined at startup are defined in > gemfire.properties file and the namespace also starts with gemfire. It is > desirable to rename this to geode. > This will affect multiple modules (a lot of string literals) across the > project and may create config migration issues later on, hence is important > for the 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1948) Open geode.properties if gemfire.properties is not found
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1948: Labels: branding configuration (was: ) > Open geode.properties if gemfire.properties is not found > > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If gemfire.properties > is specified on startup and cannot be located, fall back to geode.properties > and try to open that file before presenting an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1948) geode.properties should be the default filename
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1948: Summary: geode.properties should be the default filename (was: Open geode.properties if gemfire.properties is not found) > geode.properties should be the default filename > --- > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Labels: branding, configuration, docs > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If gemfire.properties > is specified on startup and cannot be located, fall back to geode.properties > and try to open that file before presenting an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1948) geode.properties should be the default filename
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1948: Description: geode.properties should be the new default filename. If geode.properties cannot be located, fall back to look for an old gemfire.properties. (was: geode.properties should be the new default filename. If gemfire.properties is specified on startup and cannot be located, fall back to geode.properties and try to open that file before presenting an error.) > geode.properties should be the default filename > --- > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Labels: branding, configuration, docs > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If geode.properties > cannot be located, fall back to look for an old gemfire.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1948) Open geode.properties if gemfire.properties is not found
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1948. - Resolution: Fixed > Open geode.properties if gemfire.properties is not found > > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If gemfire.properties > is specified on startup and cannot be located, fall back to geode.properties > and try to open that file before presenting an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1570) developer REST API should be secured
[ https://issues.apache.org/jira/browse/GEODE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1570. - Resolution: Fixed > developer REST API should be secured > > > Key: GEODE-1570 > URL: https://issues.apache.org/jira/browse/GEODE-1570 > Project: Geode > Issue Type: Sub-task > Components: rest (dev), security >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > > The developer REST API should require authentication when security is > enabled. For authorization, the implementation should use the new > Resource:Operation permissions API that is used by JMX. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2014) Upgrade Swagger libraries
[ https://issues.apache.org/jira/browse/GEODE-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-2014. - Resolution: Fixed Fix Version/s: 1.1.0-incubating > Upgrade Swagger libraries > - > > Key: GEODE-2014 > URL: https://issues.apache.org/jira/browse/GEODE-2014 > Project: Geode > Issue Type: Improvement > Components: docs, rest (dev) >Affects Versions: 1.0.0-incubating >Reporter: Kevin Duling >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Upgrade swagger and swagger-springmvc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1959) Prompt for username and password when adding a member
[ https://issues.apache.org/jira/browse/GEODE-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1959. - Resolution: Fixed Fix Version/s: 1.1.0-incubating > Prompt for username and password when adding a member > - > > Key: GEODE-1959 > URL: https://issues.apache.org/jira/browse/GEODE-1959 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Diane Hardman >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > Attachments: gemfire.properties, security.json > > > When you have SecurityManager configured as part of starting a locator, the > administrator currently needs to have either AuthInitialize implemented or > have stored credentials (in plain text) in geode.properties file. In the case > where neither AuthInitialize is implemented NOR are there any credentials > stored in geode.properties, then the administrator should be prompted for > username and password when attempting to start another member in the > distributed system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1993) value returned through /region/key rest service needs to be post processed
[ https://issues.apache.org/jira/browse/GEODE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1993. - Resolution: Fixed Fix Version/s: 1.1.0-incubating > value returned through /region/key rest service needs to be post processed > -- > > Key: GEODE-1993 > URL: https://issues.apache.org/jira/browse/GEODE-1993 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > The new rest security did not use post processor before returning the value > back to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-2084: --- Assignee: Kevin Duling > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Kevin Duling > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2084: Component/s: rest (dev) > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug > Components: rest (dev) >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2084: Component/s: configuration > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug > Components: configuration, rest (dev) >Affects Versions: 1.0.0-incubating >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654789#comment-15654789 ] Kevin Duling commented on GEODE-2084: - Modified RestSecurityConfiguration to not bring up the login form. This will generate the normal Authentication login we expect to see. > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
