[jira] [Assigned] (GEODE-1122) Dependency on environment variable GEMFIRE needs to be removed
[ https://issues.apache.org/jira/browse/GEODE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Avinash Dongre reassigned GEODE-1122: - Assignee: Avinash Dongre > Dependency on environment variable GEMFIRE needs to be removed > -- > > Key: GEODE-1122 > URL: https://issues.apache.org/jira/browse/GEODE-1122 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Udo Kohlmeyer >Assignee: Avinash Dongre > > There is still a strong dependency on the environment variable GEMFIRE within > GEODE. This should be replaced with GEODE_HOME or removed completely from the > system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2098) gfsh history should be stored in ~/.geode
[
https://issues.apache.org/jira/browse/GEODE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669446#comment-15669446
]
ASF subversion and git services commented on GEODE-2098:
Commit 216a10917533a2f287d0bf509424f52716b81c6e in incubator-geode's branch
refs/heads/develop from adongre
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=216a109 ]
GEODE-2098: Moved gfsh history file location from .gemfire to .geode
Made the code changes and added a test for the same.
> gfsh history should be stored in ~/.geode
> -
>
> Key: GEODE-2098
> URL: https://issues.apache.org/jira/browse/GEODE-2098
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Anthony Baker
>Assignee: Avinash Dongre
> Fix For: 1.1.0-incubating
>
>
> Currently gfsh stores history in the ~/.gemfire directory. We should change
> that to be ~/.geode.
> {code}
> private static String getHomeGemFireDirectory() {
> String userHome = System.getProperty("user.home");
> String homeDirPath = userHome + "/.gemfire";
> File alternateDir = new File(homeDirPath);
> if (!alternateDir.exists()) {
> if (!alternateDir.mkdirs()) {
> homeDirPath = ".";
> }
> }
> return homeDirPath;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2098) gfsh history should be stored in ~/.geode
[
https://issues.apache.org/jira/browse/GEODE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669437#comment-15669437
]
ASF GitHub Bot commented on GEODE-2098:
---
Github user davinash commented on the issue:
https://github.com/apache/incubator-geode/pull/283
Thanks @kirklund, @metatype I have followed the process from
https://cwiki.apache.org/confluence/display/GEODE/Code+contributions
Please do let me know if everything is correct.
> gfsh history should be stored in ~/.geode
> -
>
> Key: GEODE-2098
> URL: https://issues.apache.org/jira/browse/GEODE-2098
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Anthony Baker
>Assignee: Avinash Dongre
> Fix For: 1.1.0-incubating
>
>
> Currently gfsh stores history in the ~/.gemfire directory. We should change
> that to be ~/.geode.
> {code}
> private static String getHomeGemFireDirectory() {
> String userHome = System.getProperty("user.home");
> String homeDirPath = userHome + "/.gemfire";
> File alternateDir = new File(homeDirPath);
> if (!alternateDir.exists()) {
> if (!alternateDir.mkdirs()) {
> homeDirPath = ".";
> }
> }
> return homeDirPath;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-2098) gfsh history should be stored in ~/.geode
[
https://issues.apache.org/jira/browse/GEODE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Avinash Dongre resolved GEODE-2098.
---
Resolution: Fixed
Fix Version/s: 1.1.0-incubating
> gfsh history should be stored in ~/.geode
> -
>
> Key: GEODE-2098
> URL: https://issues.apache.org/jira/browse/GEODE-2098
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Anthony Baker
>Assignee: Avinash Dongre
> Fix For: 1.1.0-incubating
>
>
> Currently gfsh stores history in the ~/.gemfire directory. We should change
> that to be ~/.geode.
> {code}
> private static String getHomeGemFireDirectory() {
> String userHome = System.getProperty("user.home");
> String homeDirPath = userHome + "/.gemfire";
> File alternateDir = new File(homeDirPath);
> if (!alternateDir.exists()) {
> if (!alternateDir.mkdirs()) {
> homeDirPath = ".";
> }
> }
> return homeDirPath;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2098) gfsh history should be stored in ~/.geode
[
https://issues.apache.org/jira/browse/GEODE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669412#comment-15669412
]
ASF subversion and git services commented on GEODE-2098:
Commit 6e1377a0f3f32aef279e9cbea3741c90aad95f30 in incubator-geode's branch
refs/heads/feature/GEODE-2098 from adongre
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=6e1377a ]
GEODE-2098: Moved gfsh history file location from .gemfire to .geode
Made the code changes and added a test for the same.
> gfsh history should be stored in ~/.geode
> -
>
> Key: GEODE-2098
> URL: https://issues.apache.org/jira/browse/GEODE-2098
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Anthony Baker
>Assignee: Avinash Dongre
>
> Currently gfsh stores history in the ~/.gemfire directory. We should change
> that to be ~/.geode.
> {code}
> private static String getHomeGemFireDirectory() {
> String userHome = System.getProperty("user.home");
> String homeDirPath = userHome + "/.gemfire";
> File alternateDir = new File(homeDirPath);
> if (!alternateDir.exists()) {
> if (!alternateDir.mkdirs()) {
> homeDirPath = ".";
> }
> }
> return homeDirPath;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2104) GFSH parsing of options following --J options are interpreted as part of the --J value
[ https://issues.apache.org/jira/browse/GEODE-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669016#comment-15669016 ] ASF GitHub Bot commented on GEODE-2104: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-geode/pull/286 > GFSH parsing of options following --J options are interpreted as part of the > --J value > -- > > Key: GEODE-2104 > URL: https://issues.apache.org/jira/browse/GEODE-2104 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Jared Stewart > > GFSH parsing of options following --J options are interpreted as part of the > --J value. > $ start server --name=me3 --J=-Dgemfire.jmx-manager=true > --J=-Dgemfire.jmx-manager-start=true --http-service-port=8080` > In the above GFSH does not interpret the `http-service-port` option > correctly. If you look in the log, the value for `gemfire.jmx-manager-start` > is `true --http-service-port=8080` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2104) GFSH parsing of options following --J options are interpreted as part of the --J value
[ https://issues.apache.org/jira/browse/GEODE-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669015#comment-15669015 ] ASF subversion and git services commented on GEODE-2104: Commit 4a913fe7a65ea4d5d91ff04f671bf94205b60b62 in incubator-geode's branch refs/heads/develop from [~jstewart] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=4a913fe ] GEODE-2104: Fix parsing of options following --J This closes #286 > GFSH parsing of options following --J options are interpreted as part of the > --J value > -- > > Key: GEODE-2104 > URL: https://issues.apache.org/jira/browse/GEODE-2104 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Jared Stewart > > GFSH parsing of options following --J options are interpreted as part of the > --J value. > $ start server --name=me3 --J=-Dgemfire.jmx-manager=true > --J=-Dgemfire.jmx-manager-start=true --http-service-port=8080` > In the above GFSH does not interpret the `http-service-port` option > correctly. If you look in the log, the value for `gemfire.jmx-manager-start` > is `true --http-service-port=8080` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2114) Add user and password to gfsh connect docs
[ https://issues.apache.org/jira/browse/GEODE-2114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668973#comment-15668973 ] Karen Smoler Miller commented on GEODE-2114: Note that a gfsh history --file=historyfilename after using doing a gfsh connect that specifies user and password will write the command with user name and password in clear text to the history file. So, I added prose that notes that the password is clear text and may be visible to others. > Add user and password to gfsh connect docs > -- > > Key: GEODE-2114 > URL: https://issues.apache.org/jira/browse/GEODE-2114 > Project: Geode > Issue Type: Task > Components: docs >Reporter: Karen Smoler Miller > > The gfsh connect command has --user and --password options that are not > completely documented. The task here is to complete that documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2116) Ci Failure: HAInterestPart1DUnitTest.testInterstRegistrationOnRecoveredEPbyDSM
Kirk Lund created GEODE-2116:
Summary: Ci Failure:
HAInterestPart1DUnitTest.testInterstRegistrationOnRecoveredEPbyDSM
Key: GEODE-2116
URL: https://issues.apache.org/jira/browse/GEODE-2116
Project: Geode
Issue Type: Bug
Components: client/server, tests
Reporter: Kirk Lund
This seems to be a difficult to reproduce flaky suspect string.
{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1732
[fatal 2016/11/15 21:02:44.368 UTC tid=0x237] Server connection from
[identity(172.17.0.4(1:loner):50303:ed90cc69,connection=1; port=39125] :
Unexpected Error on server
org.apache.geode.InternalGemFireError: No cache client proxy on this node
for proxyId identity(172.17.0.4(1:loner):50303:ed90cc69,connection=1
at
org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.makePrimary(CacheClientNotifier.java:709)
at
org.apache.geode.internal.cache.tier.sockets.command.MakePrimary.cmdExecute(MakePrimary.java:49)
at
org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:776)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:904)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1160)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-2116) Ci Failure: HAInterestPart1DUnitTest.testInterstRegistrationOnRecoveredEPbyDSM
[
https://issues.apache.org/jira/browse/GEODE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-2116:
-
Affects Version/s: 1.1.0-incubating
> Ci Failure:
> HAInterestPart1DUnitTest.testInterstRegistrationOnRecoveredEPbyDSM
> ---
>
> Key: GEODE-2116
> URL: https://issues.apache.org/jira/browse/GEODE-2116
> Project: Geode
> Issue Type: Bug
> Components: client/server, tests
>Affects Versions: 1.1.0-incubating
>Reporter: Kirk Lund
>Priority: Minor
> Labels: CI, Flaky
>
> This seems to be a difficult to reproduce flaky suspect string.
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1732
> [fatal 2016/11/15 21:02:44.368 UTC 0> tid=0x237] Server connection from
> [identity(172.17.0.4(1:loner):50303:ed90cc69,connection=1; port=39125] :
> Unexpected Error on server
> org.apache.geode.InternalGemFireError: No cache client proxy on this node
> for proxyId identity(172.17.0.4(1:loner):50303:ed90cc69,connection=1
> at
> org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.makePrimary(CacheClientNotifier.java:709)
> at
> org.apache.geode.internal.cache.tier.sockets.command.MakePrimary.cmdExecute(MakePrimary.java:49)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:776)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:904)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1160)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-2116) Ci Failure: HAInterestPart1DUnitTest.testInterstRegistrationOnRecoveredEPbyDSM
[
https://issues.apache.org/jira/browse/GEODE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-2116:
-
Priority: Minor (was: Major)
> Ci Failure:
> HAInterestPart1DUnitTest.testInterstRegistrationOnRecoveredEPbyDSM
> ---
>
> Key: GEODE-2116
> URL: https://issues.apache.org/jira/browse/GEODE-2116
> Project: Geode
> Issue Type: Bug
> Components: client/server, tests
>Reporter: Kirk Lund
>Priority: Minor
> Labels: CI, Flaky
>
> This seems to be a difficult to reproduce flaky suspect string.
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1732
> [fatal 2016/11/15 21:02:44.368 UTC 0> tid=0x237] Server connection from
> [identity(172.17.0.4(1:loner):50303:ed90cc69,connection=1; port=39125] :
> Unexpected Error on server
> org.apache.geode.InternalGemFireError: No cache client proxy on this node
> for proxyId identity(172.17.0.4(1:loner):50303:ed90cc69,connection=1
> at
> org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.makePrimary(CacheClientNotifier.java:709)
> at
> org.apache.geode.internal.cache.tier.sockets.command.MakePrimary.cmdExecute(MakePrimary.java:49)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:776)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:904)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1160)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-2116) Ci Failure: HAInterestPart1DUnitTest.testInterstRegistrationOnRecoveredEPbyDSM
[
https://issues.apache.org/jira/browse/GEODE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-2116:
-
Labels: CI Flaky (was: )
> Ci Failure:
> HAInterestPart1DUnitTest.testInterstRegistrationOnRecoveredEPbyDSM
> ---
>
> Key: GEODE-2116
> URL: https://issues.apache.org/jira/browse/GEODE-2116
> Project: Geode
> Issue Type: Bug
> Components: client/server, tests
>Reporter: Kirk Lund
> Labels: CI, Flaky
>
> This seems to be a difficult to reproduce flaky suspect string.
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1732
> [fatal 2016/11/15 21:02:44.368 UTC 0> tid=0x237] Server connection from
> [identity(172.17.0.4(1:loner):50303:ed90cc69,connection=1; port=39125] :
> Unexpected Error on server
> org.apache.geode.InternalGemFireError: No cache client proxy on this node
> for proxyId identity(172.17.0.4(1:loner):50303:ed90cc69,connection=1
> at
> org.apache.geode.internal.cache.tier.sockets.CacheClientNotifier.makePrimary(CacheClientNotifier.java:709)
> at
> org.apache.geode.internal.cache.tier.sockets.command.MakePrimary.cmdExecute(MakePrimary.java:49)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:141)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:776)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:904)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1160)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:519)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-2115) Some GFSH commands may report success even for failures
[ https://issues.apache.org/jira/browse/GEODE-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-2115: Assignee: Kirk Lund > Some GFSH commands may report success even for failures > --- > > Key: GEODE-2115 > URL: https://issues.apache.org/jira/browse/GEODE-2115 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jared Stewart >Assignee: Kirk Lund > > GFSH commands with potentially broken error handling: > * MiscellaneousCommands.exportLogs > Command implementation (ie MiscellaneousCommands) may ignore errors returned > from Function via sendException or lastResult. Function implementation (ie > LogFileFunction) may fail to invoke sendException for caught exceptions. > Functions under `org.apache.geode.management.internal.cli.functions` should > use `ResultSend::sendException` to return full stack trace of caught > exceptions. > Command implementations should read exceptions returned from functions > without discarding the info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2115) Some GFSH commands may report success even for failures
[ https://issues.apache.org/jira/browse/GEODE-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-2115: - Description: GFSH commands with potentially broken error handling: * MiscellaneousCommands.exportLogs Command implementation (ie MiscellaneousCommands) may ignore errors returned from Function via sendException or lastResult. Function implementation (ie LogFileFunction) may fail to invoke sendException for caught exceptions. Functions under `org.apache.geode.management.internal.cli.functions` should use `ResultSend::sendException` to return full stack trace of caught exceptions. Command implementations should read exceptions returned from functions without discarding the info. was: GFSH commands with potentially broken error handling: * MiscellaneousCommands.exportLogs Any Function under `org.apache.geode.management.internal.cli.functions` that does not call `ResultSend::sendException` is possibly broken, as well as Functions that call `lastResult(e.getMessage())` > Some GFSH commands may report success even for failures > --- > > Key: GEODE-2115 > URL: https://issues.apache.org/jira/browse/GEODE-2115 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jared Stewart > > GFSH commands with potentially broken error handling: > * MiscellaneousCommands.exportLogs > Command implementation (ie MiscellaneousCommands) may ignore errors returned > from Function via sendException or lastResult. Function implementation (ie > LogFileFunction) may fail to invoke sendException for caught exceptions. > Functions under `org.apache.geode.management.internal.cli.functions` should > use `ResultSend::sendException` to return full stack trace of caught > exceptions. > Command implementations should read exceptions returned from functions > without discarding the info. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2115) Some GFSH commands may report success even for failures
[ https://issues.apache.org/jira/browse/GEODE-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart updated GEODE-2115: - Summary: Some GFSH commands may report success even for failures (was: GFSH commands report success even for failures) > Some GFSH commands may report success even for failures > --- > > Key: GEODE-2115 > URL: https://issues.apache.org/jira/browse/GEODE-2115 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jared Stewart > > GFSH commands with potentially broken error handling: > * MiscellaneousCommands.exportLogs > Any Function under `org.apache.geode.management.internal.cli.functions` that > does not call > `ResultSend::sendException` > is possibly broken, as well as Functions that call > `lastResult(e.getMessage())` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2115) GFSH commands report success even for failures
Jared Stewart created GEODE-2115: Summary: GFSH commands report success even for failures Key: GEODE-2115 URL: https://issues.apache.org/jira/browse/GEODE-2115 Project: Geode Issue Type: Bug Components: management Reporter: Jared Stewart GFSH commands with potentially broken error handling: * MiscellaneousCommands.exportLogs Any Function under `org.apache.geode.management.internal.cli.functions` that does not call `ResultSend::sendException` is possibly broken, as well as Functions that call `lastResult(e.getMessage())` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2114) Add user and password to gfsh connect docs
Karen Smoler Miller created GEODE-2114: -- Summary: Add user and password to gfsh connect docs Key: GEODE-2114 URL: https://issues.apache.org/jira/browse/GEODE-2114 Project: Geode Issue Type: Task Components: docs Reporter: Karen Smoler Miller The gfsh connect command has --user and --password options that are not completely documented. The task here is to complete that documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2110. Resolution: Fixed > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2113) Implement SSL over NIO
Addison created GEODE-2113: -- Summary: Implement SSL over NIO Key: GEODE-2113 URL: https://issues.apache.org/jira/browse/GEODE-2113 Project: Geode Issue Type: Bug Components: client/server Reporter: Addison Java now has a nifty javax.net.ssl.SSLSocketFactory that can produce an SSLSocket from an existing Socket. This will let us create an SSLSocket that has an NIO SocketChannel and get rid of all of the "Old IO" code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668473#comment-15668473 ] John Blum commented on GEODE-2076: -- No, I was using Gfsh from Apache Geode 1.0.0-incubating, as I demonstrated above. I am always careful to check and report the version I am using. > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > Fix For: 1.1.0-incubating > > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1247) Unable to stop members by name when using gfsh over http
[
https://issues.apache.org/jira/browse/GEODE-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-1247.
Resolution: Fixed
Assignee: Jinmei Liao
Fix Version/s: 1.1.0-incubating
> Unable to stop members by name when using gfsh over http
>
>
> Key: GEODE-1247
> URL: https://issues.apache.org/jira/browse/GEODE-1247
> Project: Geode
> Issue Type: Bug
> Components: gfsh, rest (admin)
>Reporter: Jens Deppe
>Assignee: Jinmei Liao
> Fix For: 1.1.0-incubating
>
>
> I'm connecting to my cluster with http:
> {noformat}
> gfsh>connect --use-http=true --url=http://localhost:7070/gemfire/v1
> {noformat}
> And creating a server...
> {noformat}
> gfsh>start server --name=server1
> Starting a GemFire Server in /Users/jdeppe/debug/server1...
> .
> Server in /Users/jdeppe/debug/server1 on 192.168.99.1[40404] as server1 is
> currently online.
> Process ID: 97639
> Uptime: 2 seconds
> GemFire Version: 1.0.0-incubating.M3-SNAPSHOT
> Java Version: 1.8.0_77
> Log File: /Users/jdeppe/debug/server1/server1.log
> JVM Arguments: -Dgemfire.default.locators=192.168.99.1[19991]
> -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=kill -KILL %p
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path:
> /Users/jdeppe/git/gemfire-develop/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating.M3-SNAPSHOT.jar:/Users/jdeppe/git/gemfire-develop/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> gfsh>list members;
> Name | Id
> | -
> locator1 | 192.168.99.1(locator1:97595:locator):1024
> server1 | 192.168.99.1(server1:97639):1025
> {noformat}
> But cannot stop it...
> {noformat}
> gfsh>stop server --name=server1
> An error occurred while attempting to stop a Cache Server: The HTTP request
> failed with: 500 - Server Error
> {noformat}
> The locator log shows this error:
> {noformat}
> [severe 2016/04/18 13:54:49.754 PDT locator1 tid=0x42]
> org.springframework.http.converter.HttpMessageNotReadableException: Could not
> read document: invalid stream header: 7B226F62; nested exception is
> java.io.StreamCorruptedException: invalid stream header: 7B226F62
> at
> org.springframework.web.servlet.mvc.method.annotation.AbstractMessageConverterMethodArgumentResolver.readWithMessageConverters(AbstractMessageConverterMethodArgumentResolver.java:227)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.readWithMessageConverters(RequestResponseBodyMethodProcessor.java:147)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.resolveArgument(RequestResponseBodyMethodProcessor.java:125)
> at
> org.springframework.web.method.support.HandlerMethodArgumentResolverComposite.resolveArgument(HandlerMethodArgumentResolverComposite.java:78)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.getMethodArgumentValues(InvocableHandlerMethod.java:162)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:129)
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
> at
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969)
> at
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:871)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685)
> at
> org.springframework.web.filt
[jira] [Commented] (GEODE-1247) Unable to stop members by name when using gfsh over http
[
https://issues.apache.org/jira/browse/GEODE-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668457#comment-15668457
]
ASF subversion and git services commented on GEODE-1247:
Commit bb3db4a6a6f5057c8d4ebb87961708d131e5b447 in incubator-geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=bb3db4a ]
GEODE-1247: unable to stop server using http connection
> Unable to stop members by name when using gfsh over http
>
>
> Key: GEODE-1247
> URL: https://issues.apache.org/jira/browse/GEODE-1247
> Project: Geode
> Issue Type: Bug
> Components: gfsh, rest (admin)
>Reporter: Jens Deppe
>
> I'm connecting to my cluster with http:
> {noformat}
> gfsh>connect --use-http=true --url=http://localhost:7070/gemfire/v1
> {noformat}
> And creating a server...
> {noformat}
> gfsh>start server --name=server1
> Starting a GemFire Server in /Users/jdeppe/debug/server1...
> .
> Server in /Users/jdeppe/debug/server1 on 192.168.99.1[40404] as server1 is
> currently online.
> Process ID: 97639
> Uptime: 2 seconds
> GemFire Version: 1.0.0-incubating.M3-SNAPSHOT
> Java Version: 1.8.0_77
> Log File: /Users/jdeppe/debug/server1/server1.log
> JVM Arguments: -Dgemfire.default.locators=192.168.99.1[19991]
> -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=kill -KILL %p
> -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path:
> /Users/jdeppe/git/gemfire-develop/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating.M3-SNAPSHOT.jar:/Users/jdeppe/git/gemfire-develop/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar
> gfsh>list members;
> Name | Id
> | -
> locator1 | 192.168.99.1(locator1:97595:locator):1024
> server1 | 192.168.99.1(server1:97639):1025
> {noformat}
> But cannot stop it...
> {noformat}
> gfsh>stop server --name=server1
> An error occurred while attempting to stop a Cache Server: The HTTP request
> failed with: 500 - Server Error
> {noformat}
> The locator log shows this error:
> {noformat}
> [severe 2016/04/18 13:54:49.754 PDT locator1 tid=0x42]
> org.springframework.http.converter.HttpMessageNotReadableException: Could not
> read document: invalid stream header: 7B226F62; nested exception is
> java.io.StreamCorruptedException: invalid stream header: 7B226F62
> at
> org.springframework.web.servlet.mvc.method.annotation.AbstractMessageConverterMethodArgumentResolver.readWithMessageConverters(AbstractMessageConverterMethodArgumentResolver.java:227)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.readWithMessageConverters(RequestResponseBodyMethodProcessor.java:147)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.resolveArgument(RequestResponseBodyMethodProcessor.java:125)
> at
> org.springframework.web.method.support.HandlerMethodArgumentResolverComposite.resolveArgument(HandlerMethodArgumentResolverComposite.java:78)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.getMethodArgumentValues(InvocableHandlerMethod.java:162)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:129)
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:110)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737)
> at
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969)
> at
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:871)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at
> org.eclipse.jetty.servlet.ServletHolder.han
[jira] [Commented] (GEODE-1955) JMX suspect string causes tests to fail
[ https://issues.apache.org/jira/browse/GEODE-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668451#comment-15668451 ] ASF subversion and git services commented on GEODE-1955: Commit 58e0026c6dda077fbcedea1289993f5d36b67a74 in incubator-geode's branch refs/heads/develop from [~jinmeiliao] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=58e0026 ] GEODE-1955: properly disconnect gfsh session so that it won't leave heartbeat thread around to pollute other tests * fix the test so that it truely tests the jmx ssl > JMX suspect string causes tests to fail > --- > > Key: GEODE-1955 > URL: https://issues.apache.org/jira/browse/GEODE-1955 > Project: Geode > Issue Type: Bug > Components: jmx >Reporter: Bruce Schuchardt >Assignee: Jinmei Liao > Labels: ci > > This suspect string is causing periodic failures in a number of unit tests: > Error Message > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 283 > [fatal 2016/09/29 12:12:03.891 PDT tid=0x18d] > (tid=397 msgId=39) No longer connected to cc6-co6.gemstone.com[27162]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2088) A get in transaction may get incorrect TransactionDataNotColocatedException when bucket is not hosted locally
[
https://issues.apache.org/jira/browse/GEODE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-2088.
-
Resolution: Fixed
> A get in transaction may get incorrect TransactionDataNotColocatedException
> when bucket is not hosted locally
> -
>
> Key: GEODE-2088
> URL: https://issues.apache.org/jira/browse/GEODE-2088
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: Eric Shu
>Assignee: Eric Shu
>
> Currently a get of a PR in transaction on a data node with TXState will first
> check if the bucket is hosted locally by following code.
> {noformat}
> public Object getLocally(int bucketId, final Object key, final Object
> aCallbackArgument,
> boolean disableCopyOnRead, boolean preferCD, ClientProxyMembershipID
> requestingClient,
> EntryEventImpl clientEvent, boolean returnTombstones, boolean
> opScopeIsLocal)
> throws PrimaryBucketException, ForceReattemptException,
> PRLocallyDestroyedException {
> final BucketRegion bucketRegion = getInitializedBucketForId(key,
> Integer.valueOf(bucketId));
> {noformat}
> The BucketNotFoundException is thrown if the node does not host the bucket:
> {noformat}
> public BucketRegion getInitializedBucketForId(Object key, Integer bucketId)
> throws ForceReattemptException {
> final BucketRegion bucketRegion =
> this.localBucket2RegionMap.get(bucketId);
> if (null == bucketRegion) {
> this.partitionedRegion.checkReadiness();
> if (logger.isDebugEnabled()) {
> logger.debug("Got null bucket region for bucketId={}{}{} for
> PartitionedRegion = {}",
> this.partitionedRegion.getPRId(),
> PartitionedRegion.BUCKET_ID_SEPARATOR, bucketId,
> this.partitionedRegion);
> }
> ForceReattemptException fre = new BucketNotFoundException(
>
> LocalizedStrings.PartitionedRegionDataStore_BUCKET_ID_0_NOT_FOUND_ON_VM_1
> .toLocalizedString(
> new Object[]
> {this.partitionedRegion.bucketStringForLogs(bucketId.intValue()),
> this.partitionedRegion.getMyId()}));
> if (key != null) {
> fre.setHash(key.hashCode());
> }
> throw fre;
> }
> {noformat}
> Currently, transaction would fail with the
> TransactionDataNotColocatedException if bucket is not on local data store
> {noformat}
> if (prce instanceof BucketNotFoundException) {
> TransactionException ex = new
> TransactionDataNotColocatedException(
>
> LocalizedStrings.PartitionedRegion_KEY_0_NOT_COLOCATED_WITH_TRANSACTION
> .toLocalizedString(key));
> ex.initCause(prce);
> throw ex;
> }
> {noformat}
> This TransactionDataNotColocatedException is fine if the node never hosts
> bucket, or only previous operations within the transaction touches replicate
> regions earlier. However, if a bucket is moved to another node due to
> rebalance, and previous entry operations within the transaction only touches
> colocated regions, the transaction should fail with
> TransactionDataRebalancedException.
> We do not have a good way currently to throw the correct exception. One idea
> is to iterate through the existing TXRegions in the TXState to see whether we
> should throw TransactionDataRebalancedException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-2088) A get in transaction may get incorrect TransactionDataNotColocatedException when bucket is not hosted locally
[
https://issues.apache.org/jira/browse/GEODE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu reassigned GEODE-2088:
---
Assignee: Eric Shu
> A get in transaction may get incorrect TransactionDataNotColocatedException
> when bucket is not hosted locally
> -
>
> Key: GEODE-2088
> URL: https://issues.apache.org/jira/browse/GEODE-2088
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: Eric Shu
>Assignee: Eric Shu
>
> Currently a get of a PR in transaction on a data node with TXState will first
> check if the bucket is hosted locally by following code.
> {noformat}
> public Object getLocally(int bucketId, final Object key, final Object
> aCallbackArgument,
> boolean disableCopyOnRead, boolean preferCD, ClientProxyMembershipID
> requestingClient,
> EntryEventImpl clientEvent, boolean returnTombstones, boolean
> opScopeIsLocal)
> throws PrimaryBucketException, ForceReattemptException,
> PRLocallyDestroyedException {
> final BucketRegion bucketRegion = getInitializedBucketForId(key,
> Integer.valueOf(bucketId));
> {noformat}
> The BucketNotFoundException is thrown if the node does not host the bucket:
> {noformat}
> public BucketRegion getInitializedBucketForId(Object key, Integer bucketId)
> throws ForceReattemptException {
> final BucketRegion bucketRegion =
> this.localBucket2RegionMap.get(bucketId);
> if (null == bucketRegion) {
> this.partitionedRegion.checkReadiness();
> if (logger.isDebugEnabled()) {
> logger.debug("Got null bucket region for bucketId={}{}{} for
> PartitionedRegion = {}",
> this.partitionedRegion.getPRId(),
> PartitionedRegion.BUCKET_ID_SEPARATOR, bucketId,
> this.partitionedRegion);
> }
> ForceReattemptException fre = new BucketNotFoundException(
>
> LocalizedStrings.PartitionedRegionDataStore_BUCKET_ID_0_NOT_FOUND_ON_VM_1
> .toLocalizedString(
> new Object[]
> {this.partitionedRegion.bucketStringForLogs(bucketId.intValue()),
> this.partitionedRegion.getMyId()}));
> if (key != null) {
> fre.setHash(key.hashCode());
> }
> throw fre;
> }
> {noformat}
> Currently, transaction would fail with the
> TransactionDataNotColocatedException if bucket is not on local data store
> {noformat}
> if (prce instanceof BucketNotFoundException) {
> TransactionException ex = new
> TransactionDataNotColocatedException(
>
> LocalizedStrings.PartitionedRegion_KEY_0_NOT_COLOCATED_WITH_TRANSACTION
> .toLocalizedString(key));
> ex.initCause(prce);
> throw ex;
> }
> {noformat}
> This TransactionDataNotColocatedException is fine if the node never hosts
> bucket, or only previous operations within the transaction touches replicate
> regions earlier. However, if a bucket is moved to another node due to
> rebalance, and previous entry operations within the transaction only touches
> colocated regions, the transaction should fail with
> TransactionDataRebalancedException.
> We do not have a good way currently to throw the correct exception. One idea
> is to iterate through the existing TXRegions in the TXState to see whether we
> should throw TransactionDataRebalancedException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668383#comment-15668383 ] ASF subversion and git services commented on GEODE-2110: Commit b35e2a448311db6994f907464528266e897f0a46 in incubator-geode's branch refs/heads/feature/GEODE-288 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b35e2a4 ] GEODE-2110 Revised wording of gfsh start server --password Added a note to make it clear that specifying --password on the command line means that a clear text password is visible. > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-288) Remove deprecated Admin API
[ https://issues.apache.org/jira/browse/GEODE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668385#comment-15668385 ] ASF subversion and git services commented on GEODE-288: --- Commit b6c305f88b9708d8bfeb9d5d8bff9fc950bf4d5c in incubator-geode's branch refs/heads/feature/GEODE-288 from [~apa...@the9muses.net] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b6c305f ] GEODE-288: move admin packages to internal * org.apache.geode.admin (old Admin API) moves to org.apache.geode.internal.admin.api * org.apache.geode.admin.internal (old Amin API implementation) moves to org.apache.geode.internal.admin.api.impl * org.apache.geode.admin.jmx (old JMX API) moves to org.apache.geode.internal.admin.api.jmx * org.apache.geode.admin.jmx.internal (old JMX API implementation) moves to org.apache.geode.internal.admin.api.jmx.impl > Remove deprecated Admin API > --- > > Key: GEODE-288 > URL: https://issues.apache.org/jira/browse/GEODE-288 > Project: Geode > Issue Type: Sub-task > Components: docs, jmx >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kirk Lund > > The Admin API (com.gemstone.gemfire.admin) and old JMX Agent have been > deprecated since GemFire 7.0. The Admin API was retired in favor of using the > new Management JMX API (com.gemstone.gemfire.management) and GFSH. > #1) move some Admin classes used internally by non-Admin code: > move com.gemstone.gemfire.admin.BackupStatus > move com.gemstone.gemfire.admin.OperationCancelledException > move com.gemstone.gemfire.admin.RegionNotFoundException > move > com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.backupAllMembers > move > com.gemstone.gemfire.admin.internal.AdminDistributedSystemImpl.compactAllDiskStores > move com.gemstone.gemfire.admin.internal.FinishBackupRequest > move com.gemstone.gemfire.admin.internal.FlushToDiskRequest > move com.gemstone.gemfire.admin.internal.InetAddressUtil > move com.gemstone.gemfire.admin.internal.PrepareBackupRequest > #2) move com.gemstone.gemfire.admin to > com.gemstone.gemfire.internal.admin.api (temporarily) > #3) remove com.gemstone.gemfire.cache.* usage of admin > #4) remove com.gemstone.gemfire.distributed.* usage of admin > #5) remove com.gemstone.gemfire.internal.* usage of admin (except for > internal.admin.*) > #6) remove com.gemstone.gemfire.management.* usage of admin > #7) remove com.gemstone.gemfire.internal.admin.api if possible > #8) remove unused classes from com.gemstone.gemfire.internal.admin.* > Breakdown by package and class: > com.gemstone.gemfire > --change DataSerializer to use moved RegionNotFoundException > com.gemstone.gemfire.cache > com.gemstone.gemfire.cache.persistence > com.gemstone.gemfire.cache.util > --remove com.gemstone.gemfire.cache.util.UniversalMembershipListenerAdapter > com.gemstone.gemfire.distributed > --remove Admin API from javadocs in Locator and DistributedSystem > com.gemstone.gemfire.distributed.internal > --remove > com.gemstone.gemfire.distributed.internal.DistributionManager.createHealthMonitor > --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitor > --remove remove com.gemstone.gemfire.distributed.internal.HealthMonitorImpl > --change > com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.hasAlertListenerFor > to not use AlertLevel > com.gemstone.gemfire.internal > --remove DSFIDFactory support for admin messages > --remove com.gemstone.gemfire.admin.jmx.internal.AgentLauncher from > GemFireUtilLauncher > --change MigrationServer to use moved InetAddressUtil > --change SocketCreator to use moved InetAddressUtil > --remove SystemAdmin.backup > --remove SystemAdmin.compactAllDiskStores > --remove SystemAdmin.shutDownAll > --remove SystemAdmin.listMissingDiskStores > --remove SystemAdmin.revokeMissingDiskStores > com.gemstone.gemfire.internal.cache > --replace use of com.gemstone.gemfire.admin.OperationCancelledException > --remove use of > com.gemstone.gemfire.admin.internal.SystemMemberCacheEventProcessor > com.gemstone.gemfire.internal.cache.partitioned > --replace use of com.gemstone.gemfire.admin.OperationCancelledException > com.gemstone.gemfire.internal.cache.snapshot > --replace use of com.gemstone.gemfire.admin.RegionNotFoundException > com.gemstone.gemfire.internal.tools.gfsh.app.command.task > --reimplement PartitionedRegionAttributeTask > com.gemstone.gemfire.internal.tools.gfsh.util > --reimplement RegionUtil > com.gemstone.gemfire.management.internal.beans > --change DistributedSystemBridge to use moved classes > com.gemstone.gemfire.management.internal.cli.commands > --change DiskStoreCommands to use moved classes > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15668384#comment-15668384
]
ASF subversion and git services commented on GEODE-1617:
Commit 0c9002b205e64cb248ab6ab26f2df27bf821c54c in incubator-geode's branch
refs/heads/feature/GEODE-288 from [~kduling]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0c9002b ]
GEODE-1617: add test for region names
Added comprehensive test to validate region names
This closes #285
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Commented] (GEODE-2112) UITests are failing due to insufficient tearDown
[
https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668382#comment-15668382
]
ASF subversion and git services commented on GEODE-2112:
Commit cc996a61d72123c358ced362fb884169e068bcff in incubator-geode's branch
refs/heads/feature/GEODE-288 from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=cc996a6 ]
GEODE-2112: Improved cleanup for UITests
UITests were failing when more than one was run because
they all share a base class that was not properly cleaned up.
This closes #284
> UITests are failing due to insufficient tearDown
>
>
> Key: GEODE-2112
> URL: https://issues.apache.org/jira/browse/GEODE-2112
> Project: Geode
> Issue Type: Bug
> Components: pulse, tests
>Reporter: Kirk Lund
>Assignee: Jared Stewart
> Fix For: 1.1.0-incubating
>
>
> UITests are failing due to insufficient tearDown
> {noformat}
> INFO: Connecting to jmxURL :
> service:jmx:rmi://localhost/jndi/rmi://localhost:/jmxrmi
> [info 2016/11/14 15:51:15.940 PST
> tid=0x14] Logging in admin
> [warn 2016/11/14 15:51:15.940 PST
> tid=0x14] Authentication failed for token submission
> [org.apache.geode.internal.security.shiro.GeodeAuthenticationToken - admin,
> rememberMe=false]. Possible unexpected error? (Typical or expected login
> exceptions should extend from AuthenticationException).
> org.apache.geode.security.AuthenticationFailedException:
> SampleSecurityManager: wrong username/password
> at
> org.apache.geode.security.templates.SampleSecurityManager.authenticate(SampleSecurityManager.java:146)
> at
> org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:66)
> at
> org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
> at
> org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
> at
> org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:151)
> at
> org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:58)
> at
> javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
> at
> javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-79) Provide utility to collect log artifacts
[ https://issues.apache.org/jira/browse/GEODE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668376#comment-15668376 ] ASF subversion and git services commented on GEODE-79: -- Commit ddc4819b01470825997b8504c0971d04ddfab2f3 in incubator-geode's branch refs/heads/feature/GEODE-288 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=ddc4819 ] GEODE-2105 Remove docs about log collection utility The log collection utility is not part of the release, so remove the documentation. The content removed by this commit has been placed on the feature/GEODE-79 branch. > Provide utility to collect log artifacts > > > Key: GEODE-79 > URL: https://issues.apache.org/jira/browse/GEODE-79 > Project: Geode > Issue Type: New Feature > Components: general >Reporter: Darrel Schneider >Assignee: Vincent Ford >Priority: Minor > > A utility named "gfe-sendlogs.py" exists and can be used to collect all the > log files of a distributed system so they can be easily collected and sent to > support. This task tracks the donation of the code to Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2105) Remove documentation of Log Collection Utility
[ https://issues.apache.org/jira/browse/GEODE-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668375#comment-15668375 ] ASF subversion and git services commented on GEODE-2105: Commit ddc4819b01470825997b8504c0971d04ddfab2f3 in incubator-geode's branch refs/heads/feature/GEODE-288 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=ddc4819 ] GEODE-2105 Remove docs about log collection utility The log collection utility is not part of the release, so remove the documentation. The content removed by this commit has been placed on the feature/GEODE-79 branch. > Remove documentation of Log Collection Utility > -- > > Key: GEODE-2105 > URL: https://issues.apache.org/jira/browse/GEODE-2105 > Project: Geode > Issue Type: Task >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > The log collection utility is not part of Geode releases, so remove it from > the documentation. > https://issues.apache.org/jira/browse/GEODE-79 and the feature/GEODE-79 > branch has the code for the Log Collection Utility, but exists from a time > when the Geode docs were not yet donated to the ASF. The existing > documentation in file log_collection_utility.html.md.erb will be placed onto > that branch so it is not lost. No testing or checks will be done on the > feature/GEODE-79 branch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2101) Improve WAN topology terminology in docs
[ https://issues.apache.org/jira/browse/GEODE-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668377#comment-15668377 ] ASF subversion and git services commented on GEODE-2101: Commit c9e3b05405a2e82a00f9b3ac15ed259a2829a053 in incubator-geode's branch refs/heads/feature/GEODE-288 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=c9e3b05 ] GEODE-2101 Improve WAN topology terminology in docs The terms parallel and serial are not right, so change them: - a parallel multi-site topology is a fully connected mesh - a serial multi-site topology is a ring > Improve WAN topology terminology in docs > > > Key: GEODE-2101 > URL: https://issues.apache.org/jira/browse/GEODE-2101 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Minor > Fix For: 1.1.0-incubating > > > In our documentation description of WAN topologies, the term "parallel > multi-site topology" is a fully connected mesh. The "serial multi-site > topology" is a ring. It will improve the docs to change our descriptions to > use the common and accepted terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2088) A get in transaction may get incorrect TransactionDataNotColocatedException when bucket is not hosted locally
[
https://issues.apache.org/jira/browse/GEODE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668379#comment-15668379
]
ASF subversion and git services commented on GEODE-2088:
Commit 139398a1f5af656c59eeacdb2dd9283a7145d992 in incubator-geode's branch
refs/heads/feature/GEODE-288 from [~eshu]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=139398a ]
GEODE-2088: Correctly throw TransactionDataRebalancedException when bucket is
moved during rebalance.
Turns out the transaction layer code has already handled when to throw
TransactionDataNotColocatedException in getTransactionException method call in
TXStateProxyImpl by checking whether the key is colocated with the keys already
touched in the transaction. Only need to make sure that piece of code will be
executed by throwing correct TransactionException.
> A get in transaction may get incorrect TransactionDataNotColocatedException
> when bucket is not hosted locally
> -
>
> Key: GEODE-2088
> URL: https://issues.apache.org/jira/browse/GEODE-2088
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: Eric Shu
>
> Currently a get of a PR in transaction on a data node with TXState will first
> check if the bucket is hosted locally by following code.
> {noformat}
> public Object getLocally(int bucketId, final Object key, final Object
> aCallbackArgument,
> boolean disableCopyOnRead, boolean preferCD, ClientProxyMembershipID
> requestingClient,
> EntryEventImpl clientEvent, boolean returnTombstones, boolean
> opScopeIsLocal)
> throws PrimaryBucketException, ForceReattemptException,
> PRLocallyDestroyedException {
> final BucketRegion bucketRegion = getInitializedBucketForId(key,
> Integer.valueOf(bucketId));
> {noformat}
> The BucketNotFoundException is thrown if the node does not host the bucket:
> {noformat}
> public BucketRegion getInitializedBucketForId(Object key, Integer bucketId)
> throws ForceReattemptException {
> final BucketRegion bucketRegion =
> this.localBucket2RegionMap.get(bucketId);
> if (null == bucketRegion) {
> this.partitionedRegion.checkReadiness();
> if (logger.isDebugEnabled()) {
> logger.debug("Got null bucket region for bucketId={}{}{} for
> PartitionedRegion = {}",
> this.partitionedRegion.getPRId(),
> PartitionedRegion.BUCKET_ID_SEPARATOR, bucketId,
> this.partitionedRegion);
> }
> ForceReattemptException fre = new BucketNotFoundException(
>
> LocalizedStrings.PartitionedRegionDataStore_BUCKET_ID_0_NOT_FOUND_ON_VM_1
> .toLocalizedString(
> new Object[]
> {this.partitionedRegion.bucketStringForLogs(bucketId.intValue()),
> this.partitionedRegion.getMyId()}));
> if (key != null) {
> fre.setHash(key.hashCode());
> }
> throw fre;
> }
> {noformat}
> Currently, transaction would fail with the
> TransactionDataNotColocatedException if bucket is not on local data store
> {noformat}
> if (prce instanceof BucketNotFoundException) {
> TransactionException ex = new
> TransactionDataNotColocatedException(
>
> LocalizedStrings.PartitionedRegion_KEY_0_NOT_COLOCATED_WITH_TRANSACTION
> .toLocalizedString(key));
> ex.initCause(prce);
> throw ex;
> }
> {noformat}
> This TransactionDataNotColocatedException is fine if the node never hosts
> bucket, or only previous operations within the transaction touches replicate
> regions earlier. However, if a bucket is moved to another node due to
> rebalance, and previous entry operations within the transaction only touches
> colocated regions, the transaction should fail with
> TransactionDataRebalancedException.
> We do not have a good way currently to throw the correct exception. One idea
> is to iterate through the existing TXRegions in the TXState to see whether we
> should throw TransactionDataRebalancedException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668380#comment-15668380 ] ASF subversion and git services commented on GEODE-2110: Commit 6118a6a95cad3bc4708c535cabb9f9bdc9d10738 in incubator-geode's branch refs/heads/feature/GEODE-288 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=6118a6a ] GEODE-2110 Add gfsh start server user and password options Modifies gfsh start server command reference page to add the two missing options: --user and --password > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668265#comment-15668265 ] ASF subversion and git services commented on GEODE-2110: Commit 6118a6a95cad3bc4708c535cabb9f9bdc9d10738 in incubator-geode's branch refs/heads/feature/GEODE-1930 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=6118a6a ] GEODE-2110 Add gfsh start server user and password options Modifies gfsh start server command reference page to add the two missing options: --user and --password > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15668268#comment-15668268
]
ASF subversion and git services commented on GEODE-1617:
Commit 0c9002b205e64cb248ab6ab26f2df27bf821c54c in incubator-geode's branch
refs/heads/feature/GEODE-1930 from [~kduling]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0c9002b ]
GEODE-1617: add test for region names
Added comprehensive test to validate region names
This closes #285
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Commented] (GEODE-2088) A get in transaction may get incorrect TransactionDataNotColocatedException when bucket is not hosted locally
[
https://issues.apache.org/jira/browse/GEODE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668264#comment-15668264
]
ASF subversion and git services commented on GEODE-2088:
Commit 139398a1f5af656c59eeacdb2dd9283a7145d992 in incubator-geode's branch
refs/heads/feature/GEODE-1930 from [~eshu]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=139398a ]
GEODE-2088: Correctly throw TransactionDataRebalancedException when bucket is
moved during rebalance.
Turns out the transaction layer code has already handled when to throw
TransactionDataNotColocatedException in getTransactionException method call in
TXStateProxyImpl by checking whether the key is colocated with the keys already
touched in the transaction. Only need to make sure that piece of code will be
executed by throwing correct TransactionException.
> A get in transaction may get incorrect TransactionDataNotColocatedException
> when bucket is not hosted locally
> -
>
> Key: GEODE-2088
> URL: https://issues.apache.org/jira/browse/GEODE-2088
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: Eric Shu
>
> Currently a get of a PR in transaction on a data node with TXState will first
> check if the bucket is hosted locally by following code.
> {noformat}
> public Object getLocally(int bucketId, final Object key, final Object
> aCallbackArgument,
> boolean disableCopyOnRead, boolean preferCD, ClientProxyMembershipID
> requestingClient,
> EntryEventImpl clientEvent, boolean returnTombstones, boolean
> opScopeIsLocal)
> throws PrimaryBucketException, ForceReattemptException,
> PRLocallyDestroyedException {
> final BucketRegion bucketRegion = getInitializedBucketForId(key,
> Integer.valueOf(bucketId));
> {noformat}
> The BucketNotFoundException is thrown if the node does not host the bucket:
> {noformat}
> public BucketRegion getInitializedBucketForId(Object key, Integer bucketId)
> throws ForceReattemptException {
> final BucketRegion bucketRegion =
> this.localBucket2RegionMap.get(bucketId);
> if (null == bucketRegion) {
> this.partitionedRegion.checkReadiness();
> if (logger.isDebugEnabled()) {
> logger.debug("Got null bucket region for bucketId={}{}{} for
> PartitionedRegion = {}",
> this.partitionedRegion.getPRId(),
> PartitionedRegion.BUCKET_ID_SEPARATOR, bucketId,
> this.partitionedRegion);
> }
> ForceReattemptException fre = new BucketNotFoundException(
>
> LocalizedStrings.PartitionedRegionDataStore_BUCKET_ID_0_NOT_FOUND_ON_VM_1
> .toLocalizedString(
> new Object[]
> {this.partitionedRegion.bucketStringForLogs(bucketId.intValue()),
> this.partitionedRegion.getMyId()}));
> if (key != null) {
> fre.setHash(key.hashCode());
> }
> throw fre;
> }
> {noformat}
> Currently, transaction would fail with the
> TransactionDataNotColocatedException if bucket is not on local data store
> {noformat}
> if (prce instanceof BucketNotFoundException) {
> TransactionException ex = new
> TransactionDataNotColocatedException(
>
> LocalizedStrings.PartitionedRegion_KEY_0_NOT_COLOCATED_WITH_TRANSACTION
> .toLocalizedString(key));
> ex.initCause(prce);
> throw ex;
> }
> {noformat}
> This TransactionDataNotColocatedException is fine if the node never hosts
> bucket, or only previous operations within the transaction touches replicate
> regions earlier. However, if a bucket is moved to another node due to
> rebalance, and previous entry operations within the transaction only touches
> colocated regions, the transaction should fail with
> TransactionDataRebalancedException.
> We do not have a good way currently to throw the correct exception. One idea
> is to iterate through the existing TXRegions in the TXState to see whether we
> should throw TransactionDataRebalancedException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668267#comment-15668267 ] ASF subversion and git services commented on GEODE-2110: Commit b35e2a448311db6994f907464528266e897f0a46 in incubator-geode's branch refs/heads/feature/GEODE-1930 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b35e2a4 ] GEODE-2110 Revised wording of gfsh start server --password Added a note to make it clear that specifying --password on the command line means that a clear text password is visible. > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2112) UITests are failing due to insufficient tearDown
[
https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668266#comment-15668266
]
ASF subversion and git services commented on GEODE-2112:
Commit cc996a61d72123c358ced362fb884169e068bcff in incubator-geode's branch
refs/heads/feature/GEODE-1930 from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=cc996a6 ]
GEODE-2112: Improved cleanup for UITests
UITests were failing when more than one was run because
they all share a base class that was not properly cleaned up.
This closes #284
> UITests are failing due to insufficient tearDown
>
>
> Key: GEODE-2112
> URL: https://issues.apache.org/jira/browse/GEODE-2112
> Project: Geode
> Issue Type: Bug
> Components: pulse, tests
>Reporter: Kirk Lund
>Assignee: Jared Stewart
> Fix For: 1.1.0-incubating
>
>
> UITests are failing due to insufficient tearDown
> {noformat}
> INFO: Connecting to jmxURL :
> service:jmx:rmi://localhost/jndi/rmi://localhost:/jmxrmi
> [info 2016/11/14 15:51:15.940 PST
> tid=0x14] Logging in admin
> [warn 2016/11/14 15:51:15.940 PST
> tid=0x14] Authentication failed for token submission
> [org.apache.geode.internal.security.shiro.GeodeAuthenticationToken - admin,
> rememberMe=false]. Possible unexpected error? (Typical or expected login
> exceptions should extend from AuthenticationException).
> org.apache.geode.security.AuthenticationFailedException:
> SampleSecurityManager: wrong username/password
> at
> org.apache.geode.security.templates.SampleSecurityManager.authenticate(SampleSecurityManager.java:146)
> at
> org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:66)
> at
> org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
> at
> org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
> at
> org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:151)
> at
> org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:58)
> at
> javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
> at
> javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2101) Improve WAN topology terminology in docs
[ https://issues.apache.org/jira/browse/GEODE-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668263#comment-15668263 ] ASF subversion and git services commented on GEODE-2101: Commit c9e3b05405a2e82a00f9b3ac15ed259a2829a053 in incubator-geode's branch refs/heads/feature/GEODE-1930 from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=c9e3b05 ] GEODE-2101 Improve WAN topology terminology in docs The terms parallel and serial are not right, so change them: - a parallel multi-site topology is a fully connected mesh - a serial multi-site topology is a ring > Improve WAN topology terminology in docs > > > Key: GEODE-2101 > URL: https://issues.apache.org/jira/browse/GEODE-2101 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Minor > Fix For: 1.1.0-incubating > > > In our documentation description of WAN topologies, the term "parallel > multi-site topology" is a fully connected mesh. The "serial multi-site > topology" is a ring. It will improve the docs to change our descriptions to > use the common and accepted terms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2104) GFSH parsing of options following --J options are interpreted as part of the --J value
[ https://issues.apache.org/jira/browse/GEODE-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668250#comment-15668250 ] ASF GitHub Bot commented on GEODE-2104: --- Github user jinmeiliao commented on the issue: https://github.com/apache/incubator-geode/pull/286 LGTM. build it and start up gfsh and play with it with different options and see if it's not having some side effects. After that I can pull this in. > GFSH parsing of options following --J options are interpreted as part of the > --J value > -- > > Key: GEODE-2104 > URL: https://issues.apache.org/jira/browse/GEODE-2104 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Jared Stewart > > GFSH parsing of options following --J options are interpreted as part of the > --J value. > $ start server --name=me3 --J=-Dgemfire.jmx-manager=true > --J=-Dgemfire.jmx-manager-start=true --http-service-port=8080` > In the above GFSH does not interpret the `http-service-port` option > correctly. If you look in the log, the value for `gemfire.jmx-manager-start` > is `true --http-service-port=8080` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668236#comment-15668236 ] Jinmei Liao commented on GEODE-2076: The error you encounter must be because of the gfsh parsing issue we've just discovered: GEODE-2104. > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > Fix For: 1.1.0-incubating > > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2075) --disable-default-server does not prevent "Geode Server" from attempting the default CacheServer port (40404)
[
https://issues.apache.org/jira/browse/GEODE-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668232#comment-15668232
]
Jinmei Liao commented on GEODE-2075:
actually the error must be because of the parsing error.
> --disable-default-server does not prevent "Geode Server" from attempting the
> default CacheServer port (40404)
> --
>
> Key: GEODE-2075
> URL: https://issues.apache.org/jira/browse/GEODE-2075
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Diane Hardman
>Assignee: Jared Stewart
> Fix For: 1.1.0-incubating
>
>
> This is a follow-up bug from issues reported in GEODE-1986 from John Blum.
> "--disable-default-server does not prevent the "Geode Server" from trying to
> start on the default CacheServer port (40404) anyway
> When I attempt to start my second server ("Server2") the firs time if failed
> with..."
> --disable-default-server should choose a different port
> Steps to reproduce:
> gfsh>start server --name=Server1 --log-level=config
> --J=-Dgemfire.start-locator=localhost[10334]
> gfsh>start server --name=Server2 --log-level=config
> --J=-Dgemfire.locators=localhost[10334] --disable-default-server
> Starting a Geode Server in /Users/jblum/pivdev/lab/Server2...
> The Cache Server process terminated unexpectedly with exit status 1. Please
> refer to the log file in /Users/jblum/pivdev/lab/Server2 for full details.
> Exception in thread "main" java.lang.RuntimeException: An IO error occurred
> while starting a Server in /Users/jblum/pivdev/lab/Server2 on
> 10.99.199.3[40404]: Network is unreachable; port (40404) is not available on
> localhost.
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:735)
> at
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:633)
> at
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:184)
> Caused by: java.net.BindException: Network is unreachable; port (40404) is
> not available on localhost.
> at
> org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:127)
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:688)
> ... 2 more
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668227#comment-15668227 ] Jinmei Liao commented on GEODE-2076: Must be you are using an older version of gfsh. I'll close this for now. > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > Fix For: 1.1.0-incubating > > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2075) --disable-default-server does not prevent "Geode Server" from attempting the default CacheServer port (40404)
[
https://issues.apache.org/jira/browse/GEODE-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668229#comment-15668229
]
Jinmei Liao commented on GEODE-2075:
close this for now according to [~jblum]'s comment in GEODE-2076
> --disable-default-server does not prevent "Geode Server" from attempting the
> default CacheServer port (40404)
> --
>
> Key: GEODE-2075
> URL: https://issues.apache.org/jira/browse/GEODE-2075
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Diane Hardman
>Assignee: Jared Stewart
> Fix For: 1.1.0-incubating
>
>
> This is a follow-up bug from issues reported in GEODE-1986 from John Blum.
> "--disable-default-server does not prevent the "Geode Server" from trying to
> start on the default CacheServer port (40404) anyway
> When I attempt to start my second server ("Server2") the firs time if failed
> with..."
> --disable-default-server should choose a different port
> Steps to reproduce:
> gfsh>start server --name=Server1 --log-level=config
> --J=-Dgemfire.start-locator=localhost[10334]
> gfsh>start server --name=Server2 --log-level=config
> --J=-Dgemfire.locators=localhost[10334] --disable-default-server
> Starting a Geode Server in /Users/jblum/pivdev/lab/Server2...
> The Cache Server process terminated unexpectedly with exit status 1. Please
> refer to the log file in /Users/jblum/pivdev/lab/Server2 for full details.
> Exception in thread "main" java.lang.RuntimeException: An IO error occurred
> while starting a Server in /Users/jblum/pivdev/lab/Server2 on
> 10.99.199.3[40404]: Network is unreachable; port (40404) is not available on
> localhost.
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:735)
> at
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:633)
> at
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:184)
> Caused by: java.net.BindException: Network is unreachable; port (40404) is
> not available on localhost.
> at
> org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:127)
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:688)
> ... 2 more
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-2076. Resolution: Fixed Fix Version/s: 1.1.0-incubating > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > Fix For: 1.1.0-incubating > > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[
https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668214#comment-15668214
]
John Blum edited comment on GEODE-2076 at 11/15/16 8:34 PM:
[~jinmeiliao] - Hmmm
Well, I cannot seem to reproduce this now
{code}
$ echo $GEMFIRE
/Users/jblum/pivdev/apache-geode-1.0.0-incubating
$ gfsh
_ __
/ _/ __/ __/ // /
/ / __/ /___ /_ / _ /
/ /__/ / / _/ / // /
/__/_/ /__/_//_/1.0.0-incubating
Monitor and Manage Apache Geode (incubating)
gfsh>start server --name=ServerX --log-level=config
--J=-Dgemfire.start-locator=localhost[10334]
--J=-Dgemfire.enable-cluster-configuration=false --J=-Dgemfire.jmx-manager=true
--J=-Dgemfire.jmx-manager-start=true
Starting a Geode Server in /Users/jblum/pivdev/lab/ServerX...
..
Server in /Users/jblum/pivdev/lab/ServerX on 10.99.199.3[40404] as ServerX is
currently online.
Process ID: 18873
Uptime: 5 seconds
GemFire Version: 1.0.0-incubating
Java Version: 1.8.0_72
Log File: /Users/jblum/pivdev/lab/ServerX/ServerX.log
JVM Arguments: -Dgemfire.use-cluster-configuration=true
-Dgemfire.http-service-port=8080 -Dgemfire.start-dev-rest-api=false
-Dgemfire.log-level=config -Dgemfire.start-locator=localhost[10334]
-Dgemfire.enable-cluster-configuration=false -Dgemfire.jmx-manager=true
-Dgemfire.jmx-manager-start=true -XX:OnOutOfMemoryError=kill -KILL %p
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path:
/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-core-1.0.0-incubating.jar:/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-dependencies.jar
gfsh>start server --name=ServerY --log-level=config --disable-default-server
--locators=localhost[10334]
Starting a Geode Server in /Users/jblum/pivdev/lab/ServerY...
.
Server in /Users/jblum/pivdev/lab/ServerY on 10.99.199.3 as ServerY is
currently online.
Process ID: 18916
Uptime: 3 seconds
GemFire Version: 1.0.0-incubating
Java Version: 1.8.0_72
Log File: /Users/jblum/pivdev/lab/ServerY/ServerY.log
JVM Arguments: -Dgemfire.locators=localhost[10334]
-Dgemfire.use-cluster-configuration=true -Dgemfire.http-service-port=8080
-Dgemfire.start-dev-rest-api=false -Dgemfire.log-level=config
-XX:OnOutOfMemoryError=kill -KILL %p
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path:
/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-core-1.0.0-incubating.jar:/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-dependencies.jar
gfsh>connect
Connecting to Locator at [host=localhost, port=10334] ..
Connecting to Manager at [host=10.99.199.3, port=1099] ..
Successfully connected to: [host=10.99.199.3, port=1099]
gfsh>list members
Name | Id
--- | ---
ServerX | 10.99.199.3(ServerX:18873):1024
ServerY | 10.99.199.3(ServerY:18916):1025
gfsh>
{code}
I may have encountered a _race condition_ or just a simple anomaly the last
time I hit this problem, but I did encounter it and the problem persisted
through several attempts. Perhaps my _Gfsh_ session was corrupted; I am not
sure what happened.
Interestingly enough, I also did not encounter the problem with the cache
server port, i.e. the {{--disable-default-server}} option worked as expected
when starting the second server ({{ServerY}}) as well. I am baffled and not
sure what was happening before, but, I did encounter those errors.
I say close this bug for now and we can reopen it if someone encounters these
problems again.
was (Author: jblum):
[~jinmeiliao] - Hmmm
Well, I cannot seem to reproduce this now
{code}
$ echo $GEMFIRE
/Users/jblum/pivdev/apache-geode-1.0.0-incubating
$ gfsh
_ __
/ _/ __/ __/ // /
/ / __/ /___ /_ / _ /
/ /__/ / / _/ / // /
/__/_/ /__/_//_/1.0.0-incubating
Monitor and Manage Apache Geode (incubating)
gfsh>start server --name=ServerX --log-level=config
--J=-Dgemfire.start-locator=localhost[10334]
--J=-Dgemfire.enable-cluster-configuration=false --J=-Dgemfire.jmx-manager=true
--J=-Dgemfire.jmx-manager-start=true
Starting a Geode Server in /Users/jblum/pivdev/lab/ServerX...
..
Server in /Users/jblum/pivdev/lab/ServerX on 10.99.199.3[40404] as ServerX is
currently online.
Process ID: 18873
Uptime: 5 seconds
GemFire Version: 1.0.0-incubating
Java Version: 1.8.0_72
Log File: /Users/jblum/pivdev/lab/ServerX/ServerX.log
JVM Arguments: -Dgemfire.use-cluster-configuration=true
-Dgemfire.http-service-port=8080 -Dgemfire.start-dev-rest-api=false
-Dgemfire.log-level=config -Dgemfire.start-locator=localhost[10334]
-Dgemfire.enable-cluster-c
[jira] [Assigned] (GEODE-2092) Security examples should not be in the product code
[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-2092: --- Assignee: Kevin Duling > Security examples should not be in the product code > --- > > Key: GEODE-2092 > URL: https://issues.apache.org/jira/browse/GEODE-2092 > Project: Geode > Issue Type: Bug > Components: security >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kevin Duling > > These three classes are currently in geode-core product package which implies > they are fully supported user API. They cannot be released in a user API > package. They must be moved to geode-examples: > geode-core/src/main/java/org/apache/geode/security/templates/SampleSecurityManager.java > geode-core/src/main/java/org/apache/geode/security/templates/SamplePostProcessor.java > geode-core/src/main/java/org/apache/geode/security/templates/SimpleSecurityManager.java > If they need to be available within a jar, then geode-examples should be > altered to build a jar can be added to the classpath of a running application. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[
https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668214#comment-15668214
]
John Blum commented on GEODE-2076:
--
[~jinmeiliao] - Hmmm
Well, I cannot seem to reproduce this now
{code}
$ echo $GEMFIRE
/Users/jblum/pivdev/apache-geode-1.0.0-incubating
$ gfsh
_ __
/ _/ __/ __/ // /
/ / __/ /___ /_ / _ /
/ /__/ / / _/ / // /
/__/_/ /__/_//_/1.0.0-incubating
Monitor and Manage Apache Geode (incubating)
gfsh>start server --name=ServerX --log-level=config
--J=-Dgemfire.start-locator=localhost[10334]
--J=-Dgemfire.enable-cluster-configuration=false --J=-Dgemfire.jmx-manager=true
--J=-Dgemfire.jmx-manager-start=true
Starting a Geode Server in /Users/jblum/pivdev/lab/ServerX...
..
Server in /Users/jblum/pivdev/lab/ServerX on 10.99.199.3[40404] as ServerX is
currently online.
Process ID: 18873
Uptime: 5 seconds
GemFire Version: 1.0.0-incubating
Java Version: 1.8.0_72
Log File: /Users/jblum/pivdev/lab/ServerX/ServerX.log
JVM Arguments: -Dgemfire.use-cluster-configuration=true
-Dgemfire.http-service-port=8080 -Dgemfire.start-dev-rest-api=false
-Dgemfire.log-level=config -Dgemfire.start-locator=localhost[10334]
-Dgemfire.enable-cluster-configuration=false -Dgemfire.jmx-manager=true
-Dgemfire.jmx-manager-start=true -XX:OnOutOfMemoryError=kill -KILL %p
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path:
/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-core-1.0.0-incubating.jar:/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-dependencies.jar
gfsh>start server --name=ServerY --log-level=config --disable-default-server
--locators=localhost[10334]
Starting a Geode Server in /Users/jblum/pivdev/lab/ServerY...
.
Server in /Users/jblum/pivdev/lab/ServerY on 10.99.199.3 as ServerY is
currently online.
Process ID: 18916
Uptime: 3 seconds
GemFire Version: 1.0.0-incubating
Java Version: 1.8.0_72
Log File: /Users/jblum/pivdev/lab/ServerY/ServerY.log
JVM Arguments: -Dgemfire.locators=localhost[10334]
-Dgemfire.use-cluster-configuration=true -Dgemfire.http-service-port=8080
-Dgemfire.start-dev-rest-api=false -Dgemfire.log-level=config
-XX:OnOutOfMemoryError=kill -KILL %p
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806
Class-Path:
/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-core-1.0.0-incubating.jar:/Users/jblum/pivdev/apache-geode-1.0.0-incubating/lib/geode-dependencies.jar
gfsh>connect
Connecting to Locator at [host=localhost, port=10334] ..
Connecting to Manager at [host=10.99.199.3, port=1099] ..
Successfully connected to: [host=10.99.199.3, port=1099]
gfsh>list members
Name | Id
--- | ---
ServerX | 10.99.199.3(ServerX:18873):1024
ServerY | 10.99.199.3(ServerY:18916):1025
gfsh>
{code}
I may have encountered an race condition or just a simple anomaly that last
time I encountered this problem, but I did encounter it and the problem
persisted through several attempts. Perhaps my _Gfsh_ session was corrupted; I
am not sure what happened.
Interestingly enough, I also did not encounter the problem with the cache
server port, i.e. the {{--disable-default-server}} option worked as expected
when starting the second server as well. I am baffled and not sure what was
happening before, but, I did encounter those errors.
I say close this bug for now and we can reopen it if someone encounters these
problems again.
> --locators option on start server is broken when specifying an embedded
> locator
> ---
>
> Key: GEODE-2076
> URL: https://issues.apache.org/jira/browse/GEODE-2076
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Diane Hardman
>Assignee: Jinmei Liao
>
> This is a follow-on bug from comments in GEODE-1986 from John Blum.
> "2. Second, the --locators option on start server is broken, hence the reason
> I specified --server-port for both servers on start to avoid bind Exceptions
> and used the --J option to specify the embedded Locator of "Server1" with the
> gemfire.locators System property when starting "Server2".
> Otherwise, "Server2" starts in standalone mode!"
> Steps to reproduce:
> gfsh>start server --name=Server1 --log-level=config
> --locators=localhost[10334]
> Starting a Geode Server in /Users/dhardman/test/Server1...
> The Cache Server process terminated unexpectedly with exit status 1. Please
> refer to the log file in /Users/dhardman/test/Server1 for full details.
> objc[9851]: Class JavaLaunchHelper is implem
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15668156#comment-15668156
]
ASF GitHub Bot commented on GEODE-1617:
---
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-geode/pull/285
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=15668155#comment-15668155
]
ASF GitHub Bot commented on GEODE-1617:
---
Github user kirklund commented on the issue:
https://github.com/apache/incubator-geode/pull/285
Pushed to develop. Thanks!
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=15668152#comment-15668152
]
ASF subversion and git services commented on GEODE-1617:
Commit 0c9002b205e64cb248ab6ab26f2df27bf821c54c in incubator-geode's branch
refs/heads/develop from [~kduling]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0c9002b ]
GEODE-1617: add test for region names
Added comprehensive test to validate region names
This closes #285
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Resolved] (GEODE-2075) --disable-default-server does not prevent "Geode Server" from attempting the default CacheServer port (40404)
[
https://issues.apache.org/jira/browse/GEODE-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jared Stewart resolved GEODE-2075.
--
Resolution: Duplicate
Assignee: Jared Stewart
Fix Version/s: 1.1.0-incubating
> --disable-default-server does not prevent "Geode Server" from attempting the
> default CacheServer port (40404)
> --
>
> Key: GEODE-2075
> URL: https://issues.apache.org/jira/browse/GEODE-2075
> Project: Geode
> Issue Type: Bug
> Components: configuration
>Reporter: Diane Hardman
>Assignee: Jared Stewart
> Fix For: 1.1.0-incubating
>
>
> This is a follow-up bug from issues reported in GEODE-1986 from John Blum.
> "--disable-default-server does not prevent the "Geode Server" from trying to
> start on the default CacheServer port (40404) anyway
> When I attempt to start my second server ("Server2") the firs time if failed
> with..."
> --disable-default-server should choose a different port
> Steps to reproduce:
> gfsh>start server --name=Server1 --log-level=config
> --J=-Dgemfire.start-locator=localhost[10334]
> gfsh>start server --name=Server2 --log-level=config
> --J=-Dgemfire.locators=localhost[10334] --disable-default-server
> Starting a Geode Server in /Users/jblum/pivdev/lab/Server2...
> The Cache Server process terminated unexpectedly with exit status 1. Please
> refer to the log file in /Users/jblum/pivdev/lab/Server2 for full details.
> Exception in thread "main" java.lang.RuntimeException: An IO error occurred
> while starting a Server in /Users/jblum/pivdev/lab/Server2 on
> 10.99.199.3[40404]: Network is unreachable; port (40404) is not available on
> localhost.
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:735)
> at
> org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:633)
> at
> org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:184)
> Caused by: java.net.BindException: Network is unreachable; port (40404) is
> not available on localhost.
> at
> org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:127)
> at
> org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:688)
> ... 2 more
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2104) GFSH parsing of options following --J options are interpreted as part of the --J value
[ https://issues.apache.org/jira/browse/GEODE-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668006#comment-15668006 ] ASF GitHub Bot commented on GEODE-2104: --- GitHub user jaredjstewart opened a pull request: https://github.com/apache/incubator-geode/pull/286 GEODE-2104: Fix parsing of options following --J You can merge this pull request into a Git repository by running: $ git pull https://github.com/jaredjstewart/incubator-geode feature/GEODE-2104 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-geode/pull/286.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #286 commit b4f1596bac584a1e0a82cb4a1065df5f496f1ee9 Author: Jared Stewart Date: 2016-11-15T18:57:11Z GEODE-2104: Fix parsing of options following --J > GFSH parsing of options following --J options are interpreted as part of the > --J value > -- > > Key: GEODE-2104 > URL: https://issues.apache.org/jira/browse/GEODE-2104 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Jared Stewart > > GFSH parsing of options following --J options are interpreted as part of the > --J value. > $ start server --name=me3 --J=-Dgemfire.jmx-manager=true > --J=-Dgemfire.jmx-manager-start=true --http-service-port=8080` > In the above GFSH does not interpret the `http-service-port` option > correctly. If you look in the log, the value for `gemfire.jmx-manager-start` > is `true --http-service-port=8080` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667973#comment-15667973 ] ASF subversion and git services commented on GEODE-2110: Commit b35e2a448311db6994f907464528266e897f0a46 in incubator-geode's branch refs/heads/develop from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b35e2a4 ] GEODE-2110 Revised wording of gfsh start server --password Added a note to make it clear that specifying --password on the command line means that a clear text password is visible. > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2112) UITests are failing due to insufficient tearDown
[
https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jared Stewart resolved GEODE-2112.
--
Resolution: Fixed
> UITests are failing due to insufficient tearDown
>
>
> Key: GEODE-2112
> URL: https://issues.apache.org/jira/browse/GEODE-2112
> Project: Geode
> Issue Type: Bug
> Components: pulse, tests
>Reporter: Kirk Lund
>Assignee: Jared Stewart
> Fix For: 1.1.0-incubating
>
>
> UITests are failing due to insufficient tearDown
> {noformat}
> INFO: Connecting to jmxURL :
> service:jmx:rmi://localhost/jndi/rmi://localhost:/jmxrmi
> [info 2016/11/14 15:51:15.940 PST
> tid=0x14] Logging in admin
> [warn 2016/11/14 15:51:15.940 PST
> tid=0x14] Authentication failed for token submission
> [org.apache.geode.internal.security.shiro.GeodeAuthenticationToken - admin,
> rememberMe=false]. Possible unexpected error? (Typical or expected login
> exceptions should extend from AuthenticationException).
> org.apache.geode.security.AuthenticationFailedException:
> SampleSecurityManager: wrong username/password
> at
> org.apache.geode.security.templates.SampleSecurityManager.authenticate(SampleSecurityManager.java:146)
> at
> org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:66)
> at
> org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
> at
> org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
> at
> org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:151)
> at
> org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:58)
> at
> javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
> at
> javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-2104) GFSH parsing of options following --J options are interpreted as part of the --J value
[ https://issues.apache.org/jira/browse/GEODE-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jared Stewart reassigned GEODE-2104: Assignee: Jared Stewart (was: Kirk Lund) > GFSH parsing of options following --J options are interpreted as part of the > --J value > -- > > Key: GEODE-2104 > URL: https://issues.apache.org/jira/browse/GEODE-2104 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Jared Stewart > > GFSH parsing of options following --J options are interpreted as part of the > --J value. > $ start server --name=me3 --J=-Dgemfire.jmx-manager=true > --J=-Dgemfire.jmx-manager-start=true --http-service-port=8080` > In the above GFSH does not interpret the `http-service-port` option > correctly. If you look in the log, the value for `gemfire.jmx-manager-start` > is `true --http-service-port=8080` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2112) UITests are failing due to insufficient tearDown
[
https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jared Stewart updated GEODE-2112:
-
Fix Version/s: 1.1.0-incubating
> UITests are failing due to insufficient tearDown
>
>
> Key: GEODE-2112
> URL: https://issues.apache.org/jira/browse/GEODE-2112
> Project: Geode
> Issue Type: Bug
> Components: pulse, tests
>Reporter: Kirk Lund
>Assignee: Jared Stewart
> Fix For: 1.1.0-incubating
>
>
> UITests are failing due to insufficient tearDown
> {noformat}
> INFO: Connecting to jmxURL :
> service:jmx:rmi://localhost/jndi/rmi://localhost:/jmxrmi
> [info 2016/11/14 15:51:15.940 PST
> tid=0x14] Logging in admin
> [warn 2016/11/14 15:51:15.940 PST
> tid=0x14] Authentication failed for token submission
> [org.apache.geode.internal.security.shiro.GeodeAuthenticationToken - admin,
> rememberMe=false]. Possible unexpected error? (Typical or expected login
> exceptions should extend from AuthenticationException).
> org.apache.geode.security.AuthenticationFailedException:
> SampleSecurityManager: wrong username/password
> at
> org.apache.geode.security.templates.SampleSecurityManager.authenticate(SampleSecurityManager.java:146)
> at
> org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:66)
> at
> org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
> at
> org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
> at
> org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:151)
> at
> org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:58)
> at
> javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
> at
> javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15667883#comment-15667883
]
ASF GitHub Bot commented on GEODE-1617:
---
Github user kjduling commented on a diff in the pull request:
https://github.com/apache/incubator-geode/pull/285#discussion_r88080988
--- Diff:
geode-core/src/test/java/org/apache/geode/cache/RegionNameValidationJUnitTest.java
---
@@ -0,0 +1,75 @@
+package org.apache.geode.cache;
+
+import static org.junit.Assert.fail;
+
+import org.apache.geode.internal.cache.InternalRegionArguments;
+import org.apache.geode.internal.cache.LocalRegion;
+import org.apache.geode.test.junit.categories.UnitTest;
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import java.util.regex.Matcher;
+import java.util.regex.Pattern;
+
+@Category(UnitTest.class)
+public class RegionNameValidationJUnitTest {
+ private static final Pattern NAME_PATTERN =
Pattern.compile("[aA-zZ0-9-_.]+");
+ private static final String REGION_NAME = "MyRegion";
+
+
+ @Test
+ public void testInvalidNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(false);
+try {
+ LocalRegion.validateRegionName(null, ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+try {
+ LocalRegion.validateRegionName("", ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+try {
+ LocalRegion.validateRegionName("FOO" + Region.SEPARATOR, ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+
+ }
+
+ @Test
+ public void testExternalRegionNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(false);
+validateCharacters(ira);
+try {
+ LocalRegion.validateRegionName("__InvalidInternalRegionName", ira);
--- End diff --
Yes, fixed.
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=15667885#comment-15667885
]
ASF GitHub Bot commented on GEODE-1617:
---
Github user kjduling commented on a diff in the pull request:
https://github.com/apache/incubator-geode/pull/285#discussion_r88081170
--- Diff:
geode-core/src/test/java/org/apache/geode/cache/RegionNameValidationJUnitTest.java
---
@@ -0,0 +1,75 @@
+package org.apache.geode.cache;
+
+import static org.junit.Assert.fail;
+
+import org.apache.geode.internal.cache.InternalRegionArguments;
+import org.apache.geode.internal.cache.LocalRegion;
+import org.apache.geode.test.junit.categories.UnitTest;
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import java.util.regex.Matcher;
+import java.util.regex.Pattern;
+
+@Category(UnitTest.class)
+public class RegionNameValidationJUnitTest {
+ private static final Pattern NAME_PATTERN =
Pattern.compile("[aA-zZ0-9-_.]+");
+ private static final String REGION_NAME = "MyRegion";
+
+
+ @Test
+ public void testInvalidNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(false);
+try {
+ LocalRegion.validateRegionName(null, ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+try {
+ LocalRegion.validateRegionName("", ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+try {
+ LocalRegion.validateRegionName("FOO" + Region.SEPARATOR, ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+
+ }
+
+ @Test
+ public void testExternalRegionNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(false);
+validateCharacters(ira);
+try {
+ LocalRegion.validateRegionName("__InvalidInternalRegionName", ira);
+} catch (IllegalArgumentException ignore) {
+}
+ }
+
+ @Test
+ public void testInternalRegionNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(true);
+LocalRegion.validateRegionName("__ValidInternalRegionName", ira);
+ }
+
+ private void validateCharacters(InternalRegionArguments ira) {
+for (int x = 0; x < Character.MAX_VALUE; x++) {
+ String name = (char) x + REGION_NAME;
+ Matcher matcher = NAME_PATTERN.matcher(name);
+ if (matcher.matches()) {
+LocalRegion.validateRegionName(name, ira);
+ } else {
+try {
+ LocalRegion.validateRegionName(name, ira);
+ fail("Should have received an IllegalArgumentException");
--- End diff --
I added printing the offending character and the numeric value of it.
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Reopened] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reopened GEODE-2110: Reopening this story to add a note that a user that specifies the password on the command line is specifying their password in the clear. > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15667814#comment-15667814
]
ASF GitHub Bot commented on GEODE-1617:
---
Github user kirklund commented on a diff in the pull request:
https://github.com/apache/incubator-geode/pull/285#discussion_r88075502
--- Diff:
geode-core/src/test/java/org/apache/geode/cache/RegionNameValidationJUnitTest.java
---
@@ -0,0 +1,75 @@
+package org.apache.geode.cache;
+
+import static org.junit.Assert.fail;
+
+import org.apache.geode.internal.cache.InternalRegionArguments;
+import org.apache.geode.internal.cache.LocalRegion;
+import org.apache.geode.test.junit.categories.UnitTest;
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import java.util.regex.Matcher;
+import java.util.regex.Pattern;
+
+@Category(UnitTest.class)
+public class RegionNameValidationJUnitTest {
+ private static final Pattern NAME_PATTERN =
Pattern.compile("[aA-zZ0-9-_.]+");
+ private static final String REGION_NAME = "MyRegion";
+
+
+ @Test
+ public void testInvalidNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(false);
+try {
+ LocalRegion.validateRegionName(null, ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+try {
+ LocalRegion.validateRegionName("", ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+try {
+ LocalRegion.validateRegionName("FOO" + Region.SEPARATOR, ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+
+ }
+
+ @Test
+ public void testExternalRegionNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(false);
+validateCharacters(ira);
+try {
+ LocalRegion.validateRegionName("__InvalidInternalRegionName", ira);
+} catch (IllegalArgumentException ignore) {
+}
+ }
+
+ @Test
+ public void testInternalRegionNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(true);
+LocalRegion.validateRegionName("__ValidInternalRegionName", ira);
+ }
+
+ private void validateCharacters(InternalRegionArguments ira) {
+for (int x = 0; x < Character.MAX_VALUE; x++) {
+ String name = (char) x + REGION_NAME;
+ Matcher matcher = NAME_PATTERN.matcher(name);
+ if (matcher.matches()) {
+LocalRegion.validateRegionName(name, ira);
+ } else {
+try {
+ LocalRegion.validateRegionName(name, ira);
+ fail("Should have received an IllegalArgumentException");
--- End diff --
Recommend adding which character to the message so we get instant info
about which character should have been illegal but was allowed.
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Commented] (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:comment-tabpanel&focusedCommentId=15667806#comment-15667806
]
ASF GitHub Bot commented on GEODE-1617:
---
Github user kirklund commented on a diff in the pull request:
https://github.com/apache/incubator-geode/pull/285#discussion_r88075036
--- Diff:
geode-core/src/test/java/org/apache/geode/cache/RegionNameValidationJUnitTest.java
---
@@ -0,0 +1,75 @@
+package org.apache.geode.cache;
+
+import static org.junit.Assert.fail;
+
+import org.apache.geode.internal.cache.InternalRegionArguments;
+import org.apache.geode.internal.cache.LocalRegion;
+import org.apache.geode.test.junit.categories.UnitTest;
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import java.util.regex.Matcher;
+import java.util.regex.Pattern;
+
+@Category(UnitTest.class)
+public class RegionNameValidationJUnitTest {
+ private static final Pattern NAME_PATTERN =
Pattern.compile("[aA-zZ0-9-_.]+");
+ private static final String REGION_NAME = "MyRegion";
+
+
+ @Test
+ public void testInvalidNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(false);
+try {
+ LocalRegion.validateRegionName(null, ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+try {
+ LocalRegion.validateRegionName("", ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+try {
+ LocalRegion.validateRegionName("FOO" + Region.SEPARATOR, ira);
+ fail();
+} catch (IllegalArgumentException ignore) {
+}
+
+ }
+
+ @Test
+ public void testExternalRegionNames() {
+InternalRegionArguments ira = new InternalRegionArguments();
+ira.setInternalRegion(false);
+validateCharacters(ira);
+try {
+ LocalRegion.validateRegionName("__InvalidInternalRegionName", ira);
--- End diff --
Aren't you missing a fail() stmt here?
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Commented] (GEODE-2112) UITests are failing due to insufficient tearDown
[
https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1566#comment-1566
]
ASF GitHub Bot commented on GEODE-2112:
---
Github user kirklund commented on the issue:
https://github.com/apache/incubator-geode/pull/284
I reworded your commit message (including line feed):
```
GEODE-2112: Improved cleanup for UITests
UITests were failing when more than one was run because
they all share a base class that was not properly cleaned up.
This closes #284
```
> UITests are failing due to insufficient tearDown
>
>
> Key: GEODE-2112
> URL: https://issues.apache.org/jira/browse/GEODE-2112
> Project: Geode
> Issue Type: Bug
> Components: pulse, tests
>Reporter: Kirk Lund
>Assignee: Jared Stewart
>
> UITests are failing due to insufficient tearDown
> {noformat}
> INFO: Connecting to jmxURL :
> service:jmx:rmi://localhost/jndi/rmi://localhost:/jmxrmi
> [info 2016/11/14 15:51:15.940 PST
> tid=0x14] Logging in admin
> [warn 2016/11/14 15:51:15.940 PST
> tid=0x14] Authentication failed for token submission
> [org.apache.geode.internal.security.shiro.GeodeAuthenticationToken - admin,
> rememberMe=false]. Possible unexpected error? (Typical or expected login
> exceptions should extend from AuthenticationException).
> org.apache.geode.security.AuthenticationFailedException:
> SampleSecurityManager: wrong username/password
> at
> org.apache.geode.security.templates.SampleSecurityManager.authenticate(SampleSecurityManager.java:146)
> at
> org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:66)
> at
> org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
> at
> org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
> at
> org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:151)
> at
> org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:58)
> at
> javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
> at
> javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15667773#comment-15667773
]
ASF GitHub Bot commented on GEODE-1617:
---
Github user kirklund commented on the issue:
https://github.com/apache/incubator-geode/pull/285
I reworded your commit message:
```
GEODE-1617: add test for region names
Added comprehensive test to validate region names
This closes #285
```
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Commented] (GEODE-2112) UITests are failing due to insufficient tearDown
[
https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667767#comment-15667767
]
ASF subversion and git services commented on GEODE-2112:
Commit cc996a61d72123c358ced362fb884169e068bcff in incubator-geode's branch
refs/heads/develop from [~jstewart]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=cc996a6 ]
GEODE-2112: Improved cleanup for UITests
UITests were failing when more than one was run because
they all share a base class that was not properly cleaned up.
This closes #284
> UITests are failing due to insufficient tearDown
>
>
> Key: GEODE-2112
> URL: https://issues.apache.org/jira/browse/GEODE-2112
> Project: Geode
> Issue Type: Bug
> Components: pulse, tests
>Reporter: Kirk Lund
>Assignee: Jared Stewart
>
> UITests are failing due to insufficient tearDown
> {noformat}
> INFO: Connecting to jmxURL :
> service:jmx:rmi://localhost/jndi/rmi://localhost:/jmxrmi
> [info 2016/11/14 15:51:15.940 PST
> tid=0x14] Logging in admin
> [warn 2016/11/14 15:51:15.940 PST
> tid=0x14] Authentication failed for token submission
> [org.apache.geode.internal.security.shiro.GeodeAuthenticationToken - admin,
> rememberMe=false]. Possible unexpected error? (Typical or expected login
> exceptions should extend from AuthenticationException).
> org.apache.geode.security.AuthenticationFailedException:
> SampleSecurityManager: wrong username/password
> at
> org.apache.geode.security.templates.SampleSecurityManager.authenticate(SampleSecurityManager.java:146)
> at
> org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:66)
> at
> org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
> at
> org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
> at
> org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:151)
> at
> org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:58)
> at
> javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
> at
> javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2098) gfsh history should be stored in ~/.geode
[
https://issues.apache.org/jira/browse/GEODE-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667765#comment-15667765
]
ASF GitHub Bot commented on GEODE-2098:
---
Github user kirklund commented on the issue:
https://github.com/apache/incubator-geode/pull/283
+1 looks ready to push to develop.
Once it's committed on develop, then mark the Jira ticket Resolved (not
Closed) and Fix Version(s) should say 1.1.0-incubating. When 1.1.0 is released,
all Resolved tickets are moved to Closed (all such tickets will be part of
release notes automatically I think).
> gfsh history should be stored in ~/.geode
> -
>
> Key: GEODE-2098
> URL: https://issues.apache.org/jira/browse/GEODE-2098
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Anthony Baker
>Assignee: Avinash Dongre
>
> Currently gfsh stores history in the ~/.gemfire directory. We should change
> that to be ~/.geode.
> {code}
> private static String getHomeGemFireDirectory() {
> String userHome = System.getProperty("user.home");
> String homeDirPath = userHome + "/.gemfire";
> File alternateDir = new File(homeDirPath);
> if (!alternateDir.exists()) {
> if (!alternateDir.mkdirs()) {
> homeDirPath = ".";
> }
> }
> return homeDirPath;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15667757#comment-15667757
]
ASF GitHub Bot commented on GEODE-1617:
---
Github user kirklund commented on the issue:
https://github.com/apache/incubator-geode/pull/285
+1
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Updated] (GEODE-2112) UITests are failing due to insufficient tearDown
[
https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-2112:
-
Assignee: Jared Stewart
> UITests are failing due to insufficient tearDown
>
>
> Key: GEODE-2112
> URL: https://issues.apache.org/jira/browse/GEODE-2112
> Project: Geode
> Issue Type: Bug
> Components: pulse, tests
>Reporter: Kirk Lund
>Assignee: Jared Stewart
>
> UITests are failing due to insufficient tearDown
> {noformat}
> INFO: Connecting to jmxURL :
> service:jmx:rmi://localhost/jndi/rmi://localhost:/jmxrmi
> [info 2016/11/14 15:51:15.940 PST
> tid=0x14] Logging in admin
> [warn 2016/11/14 15:51:15.940 PST
> tid=0x14] Authentication failed for token submission
> [org.apache.geode.internal.security.shiro.GeodeAuthenticationToken - admin,
> rememberMe=false]. Possible unexpected error? (Typical or expected login
> exceptions should extend from AuthenticationException).
> org.apache.geode.security.AuthenticationFailedException:
> SampleSecurityManager: wrong username/password
> at
> org.apache.geode.security.templates.SampleSecurityManager.authenticate(SampleSecurityManager.java:146)
> at
> org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:66)
> at
> org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
> at
> org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
> at
> org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:151)
> at
> org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:58)
> at
> javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
> at
> javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2112) UITests are failing due to insufficient tearDown
Kirk Lund created GEODE-2112:
Summary: UITests are failing due to insufficient tearDown
Key: GEODE-2112
URL: https://issues.apache.org/jira/browse/GEODE-2112
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Kirk Lund
UITests are failing due to insufficient tearDown
{noformat}
INFO: Connecting to jmxURL :
service:jmx:rmi://localhost/jndi/rmi://localhost:/jmxrmi
[info 2016/11/14 15:51:15.940 PST
tid=0x14] Logging in admin
[warn 2016/11/14 15:51:15.940 PST
tid=0x14] Authentication failed for token submission
[org.apache.geode.internal.security.shiro.GeodeAuthenticationToken - admin,
rememberMe=false]. Possible unexpected error? (Typical or expected login
exceptions should extend from AuthenticationException).
org.apache.geode.security.AuthenticationFailedException: SampleSecurityManager:
wrong username/password
at
org.apache.geode.security.templates.SampleSecurityManager.authenticate(SampleSecurityManager.java:146)
at
org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:66)
at
org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
at
org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
at
org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
at
org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
at
org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
at
org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
at
org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
at
org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:151)
at
org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:58)
at
javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
at
javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-2112) UITests are failing due to insufficient tearDown
[
https://issues.apache.org/jira/browse/GEODE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-2112:
-
Component/s: pulse
> UITests are failing due to insufficient tearDown
>
>
> Key: GEODE-2112
> URL: https://issues.apache.org/jira/browse/GEODE-2112
> Project: Geode
> Issue Type: Bug
> Components: pulse, tests
>Reporter: Kirk Lund
>
> UITests are failing due to insufficient tearDown
> {noformat}
> INFO: Connecting to jmxURL :
> service:jmx:rmi://localhost/jndi/rmi://localhost:/jmxrmi
> [info 2016/11/14 15:51:15.940 PST
> tid=0x14] Logging in admin
> [warn 2016/11/14 15:51:15.940 PST
> tid=0x14] Authentication failed for token submission
> [org.apache.geode.internal.security.shiro.GeodeAuthenticationToken - admin,
> rememberMe=false]. Possible unexpected error? (Typical or expected login
> exceptions should extend from AuthenticationException).
> org.apache.geode.security.AuthenticationFailedException:
> SampleSecurityManager: wrong username/password
> at
> org.apache.geode.security.templates.SampleSecurityManager.authenticate(SampleSecurityManager.java:146)
> at
> org.apache.geode.internal.security.shiro.CustomAuthRealm.doGetAuthenticationInfo(CustomAuthRealm.java:66)
> at
> org.apache.shiro.realm.AuthenticatingRealm.getAuthenticationInfo(AuthenticatingRealm.java:568)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doSingleRealmAuthentication(ModularRealmAuthenticator.java:180)
> at
> org.apache.shiro.authc.pam.ModularRealmAuthenticator.doAuthenticate(ModularRealmAuthenticator.java:267)
> at
> org.apache.shiro.authc.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:198)
> at
> org.apache.shiro.mgt.AuthenticatingSecurityManager.authenticate(AuthenticatingSecurityManager.java:106)
> at
> org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:270)
> at
> org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)
> at
> org.apache.geode.internal.security.IntegratedSecurityService.login(IntegratedSecurityService.java:151)
> at
> org.apache.geode.internal.security.shiro.JMXShiroAuthenticator.authenticate(JMXShiroAuthenticator.java:58)
> at
> javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:232)
> at
> javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:324)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15667746#comment-15667746
]
ASF GitHub Bot commented on GEODE-1617:
---
GitHub user kjduling opened a pull request:
https://github.com/apache/incubator-geode/pull/285
GEODE-1617: Regions can be created with a variety of characters that …
…are unsupported
Added comprehensive test to validate region names
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kjduling/incubator-geode feature/GEODE-1617
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-geode/pull/285.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #285
commit 1672018170c979a4104dce83224a3d697becfe13
Author: Kevin Duling
Date: 2016-11-15T17:33:59Z
GEODE-1617: Regions can be created with a variety of characters that are
unsupported
Added comprehensive test to validate region names
> 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
> Fix For: 1.0.0-incubating
>
>
> 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] [Resolved] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller resolved GEODE-2110. Resolution: Fixed Fix Version/s: 1.1.0-incubating > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > Fix For: 1.1.0-incubating > > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1896) unable to specify a PartitionResolver in gfsh
[
https://issues.apache.org/jira/browse/GEODE-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-1896:
---
Component/s: docs
> unable to specify a PartitionResolver in gfsh
> -
>
> Key: GEODE-1896
> URL: https://issues.apache.org/jira/browse/GEODE-1896
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Avinash Dongre
> Fix For: 1.1.0-incubating
>
>
> While creating a region in gfsh, users should be able to provide a
> PartitionResolver, something like:
> {noformat}
> gfsh>create region --name=myRegion --type=PARTITION
> --partition-resolver=com.mycompany.MyCustomPartitionResolver
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-2110) Add user and password to gfsh start server docs
[ https://issues.apache.org/jira/browse/GEODE-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667633#comment-15667633 ] ASF subversion and git services commented on GEODE-2110: Commit 6118a6a95cad3bc4708c535cabb9f9bdc9d10738 in incubator-geode's branch refs/heads/develop from [~karensmolermiller] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=6118a6a ] GEODE-2110 Add gfsh start server user and password options Modifies gfsh start server command reference page to add the two missing options: --user and --password > Add user and password to gfsh start server docs > --- > > Key: GEODE-2110 > URL: https://issues.apache.org/jira/browse/GEODE-2110 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller > > Options to the gfsh start server command specify the user and password to use > as credentials in authentication. These options are nicely printed in the > gfsh help option, but they did not make it into the command reference page > for the gfsh start server command. Thus, they need to be added. > From the help output: > user > User name to securely connect to the cluster. If the --password > parameter is not specified then it will be prompted for. > Required: false > password > Password to securely connect to the cluster. > Required: false -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2088) A get in transaction may get incorrect TransactionDataNotColocatedException when bucket is not hosted locally
[
https://issues.apache.org/jira/browse/GEODE-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667602#comment-15667602
]
ASF subversion and git services commented on GEODE-2088:
Commit 139398a1f5af656c59eeacdb2dd9283a7145d992 in incubator-geode's branch
refs/heads/develop from [~eshu]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=139398a ]
GEODE-2088: Correctly throw TransactionDataRebalancedException when bucket is
moved during rebalance.
Turns out the transaction layer code has already handled when to throw
TransactionDataNotColocatedException in getTransactionException method call in
TXStateProxyImpl by checking whether the key is colocated with the keys already
touched in the transaction. Only need to make sure that piece of code will be
executed by throwing correct TransactionException.
> A get in transaction may get incorrect TransactionDataNotColocatedException
> when bucket is not hosted locally
> -
>
> Key: GEODE-2088
> URL: https://issues.apache.org/jira/browse/GEODE-2088
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Reporter: Eric Shu
>
> Currently a get of a PR in transaction on a data node with TXState will first
> check if the bucket is hosted locally by following code.
> {noformat}
> public Object getLocally(int bucketId, final Object key, final Object
> aCallbackArgument,
> boolean disableCopyOnRead, boolean preferCD, ClientProxyMembershipID
> requestingClient,
> EntryEventImpl clientEvent, boolean returnTombstones, boolean
> opScopeIsLocal)
> throws PrimaryBucketException, ForceReattemptException,
> PRLocallyDestroyedException {
> final BucketRegion bucketRegion = getInitializedBucketForId(key,
> Integer.valueOf(bucketId));
> {noformat}
> The BucketNotFoundException is thrown if the node does not host the bucket:
> {noformat}
> public BucketRegion getInitializedBucketForId(Object key, Integer bucketId)
> throws ForceReattemptException {
> final BucketRegion bucketRegion =
> this.localBucket2RegionMap.get(bucketId);
> if (null == bucketRegion) {
> this.partitionedRegion.checkReadiness();
> if (logger.isDebugEnabled()) {
> logger.debug("Got null bucket region for bucketId={}{}{} for
> PartitionedRegion = {}",
> this.partitionedRegion.getPRId(),
> PartitionedRegion.BUCKET_ID_SEPARATOR, bucketId,
> this.partitionedRegion);
> }
> ForceReattemptException fre = new BucketNotFoundException(
>
> LocalizedStrings.PartitionedRegionDataStore_BUCKET_ID_0_NOT_FOUND_ON_VM_1
> .toLocalizedString(
> new Object[]
> {this.partitionedRegion.bucketStringForLogs(bucketId.intValue()),
> this.partitionedRegion.getMyId()}));
> if (key != null) {
> fre.setHash(key.hashCode());
> }
> throw fre;
> }
> {noformat}
> Currently, transaction would fail with the
> TransactionDataNotColocatedException if bucket is not on local data store
> {noformat}
> if (prce instanceof BucketNotFoundException) {
> TransactionException ex = new
> TransactionDataNotColocatedException(
>
> LocalizedStrings.PartitionedRegion_KEY_0_NOT_COLOCATED_WITH_TRANSACTION
> .toLocalizedString(key));
> ex.initCause(prce);
> throw ex;
> }
> {noformat}
> This TransactionDataNotColocatedException is fine if the node never hosts
> bucket, or only previous operations within the transaction touches replicate
> regions earlier. However, if a bucket is moved to another node due to
> rebalance, and previous entry operations within the transaction only touches
> colocated regions, the transaction should fail with
> TransactionDataRebalancedException.
> We do not have a good way currently to throw the correct exception. One idea
> is to iterate through the existing TXRegions in the TXState to see whether we
> should throw TransactionDataRebalancedException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-2111) Add gfsh recommendation to put all --J options at end of command line
Diane Hardman created GEODE-2111: Summary: Add gfsh recommendation to put all --J options at end of command line Key: GEODE-2111 URL: https://issues.apache.org/jira/browse/GEODE-2111 Project: Geode Issue Type: Bug Components: docs Reporter: Diane Hardman This is a follow-on bug to GEODE-2104. Due to command line parsing irregularities (which are being worked on), we should recommend in the docs that any --J options should be placed at the end of the command line. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15667453#comment-15667453 ] Jinmei Liao commented on GEODE-2076: [~jblum] I tried the following gfsh commands, it's working, please let me know what I need to do to reproduce the error. thanks! gfsh>start server --name=server1 --J=-Dgemfire.start-locator=localhost[10334] gfsh>start server --name=server2 --locators=localhost[10334] --server-port=40405 > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2076) --locators option on start server is broken when specifying an embedded locator
[ https://issues.apache.org/jira/browse/GEODE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao reassigned GEODE-2076: -- Assignee: Jinmei Liao > --locators option on start server is broken when specifying an embedded > locator > --- > > Key: GEODE-2076 > URL: https://issues.apache.org/jira/browse/GEODE-2076 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Diane Hardman >Assignee: Jinmei Liao > > This is a follow-on bug from comments in GEODE-1986 from John Blum. > "2. Second, the --locators option on start server is broken, hence the reason > I specified --server-port for both servers on start to avoid bind Exceptions > and used the --J option to specify the embedded Locator of "Server1" with the > gemfire.locators System property when starting "Server2". > Otherwise, "Server2" starts in standalone mode!" > Steps to reproduce: > gfsh>start server --name=Server1 --log-level=config > --locators=localhost[10334] > Starting a Geode Server in /Users/dhardman/test/Server1... > The Cache Server process terminated unexpectedly with exit status 1. Please > refer to the log file in /Users/dhardman/test/Server1 for full details. > objc[9851]: Class JavaLaunchHelper is implemented in both > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/bin/java > and > /Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/Contents/Home/jre/lib/libinstrument.dylib. > One of the two will be used. Which one is undefined. > Exception in thread "main" org.apache.geode.GemFireConfigException: Unable to > join the distributed system. Operation either timed out, was stopped or > Locator does not exist. > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.join(GMSMembershipManager.java:659) > at > org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.joinDistributedSystem(GMSMembershipManager.java:745) > at > org.apache.geode.distributed.internal.membership.gms.Services.start(Services.java:181) > at > org.apache.geode.distributed.internal.membership.gms.GMSMemberFactory.newMembershipManager(GMSMemberFactory.java:102) > at > org.apache.geode.distributed.internal.membership.MemberFactory.newMembershipManager(MemberFactory.java:89) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1112) > at > org.apache.geode.distributed.internal.DistributionManager.(DistributionManager.java:1160) > at > org.apache.geode.distributed.internal.DistributionManager.create(DistributionManager.java:531) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:683) > at > org.apache.geode.distributed.internal.InternalDistributedSystem.newInstance(InternalDistributedSystem.java:297) > at > org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:202) > at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:216) > at > org.apache.geode.distributed.internal.DefaultServerLauncherCacheProvider.createCache(DefaultServerLauncherCacheProvider.java:52) > at > org.apache.geode.distributed.ServerLauncher.createCache(ServerLauncher.java:857) > at > org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:769) > at > org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:696) > at > org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:228) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
