[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311429#comment-15311429 ] ASF subversion and git services commented on GEODE-1377: Commit 05ed0167821fe16f77ba40447daaa721e71c04a2 in incubator-geode's branch refs/heads/develop from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=05ed016 ] GEODE-1377: Fixed Test > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311428#comment-15311428 ] ASF subversion and git services commented on GEODE-1377: Commit 07ba2864f4cbdb5f44ecf3e6b54da8feaa890cec in incubator-geode's branch refs/heads/develop from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=07ba286 ] GEODE-1377: Initial move of system properties from private to public > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311422#comment-15311422 ] ASF subversion and git services commented on GEODE-1377: Commit 8975cbdf298964eccaaeb9f3777a6624a54ae26c in incubator-geode's branch refs/heads/develop from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=8975cbd ] GEODE-1377: Initial move of system properties from private to public > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311430#comment-15311430 ] ASF subversion and git services commented on GEODE-1377: Commit b42d6e9912f3fe530c5e369df5ce7c22c823e4c3 in incubator-geode's branch refs/heads/develop from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b42d6e9 ] GEODE-1377: Fixed missing import > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311425#comment-15311425 ] ASF subversion and git services commented on GEODE-1377: Commit 0a0598587f5d9386b1a8a8f6fba9f7f2e3f5d4d9 in incubator-geode's branch refs/heads/develop from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=0a05985 ] GEODE-1377: Initial move of system properties from private to public > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311423#comment-15311423 ] ASF subversion and git services commented on GEODE-1377: Commit ff81dbfc6fe193f30d9607fa39be6c8f72b56688 in incubator-geode's branch refs/heads/develop from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=ff81dbf ] GEODE-1377: Initial move of system properties from private to public > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311427#comment-15311427 ] ASF subversion and git services commented on GEODE-1377: Commit 690ca40b9c6dfa41affb31d12c66449c963682f1 in incubator-geode's branch refs/heads/develop from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=690ca40 ] GEODE-1377: Initial move of system properties from private to public > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311426#comment-15311426 ] ASF subversion and git services commented on GEODE-1377: Commit f84b1c084d0497eb196abdeba0282183ff6c3145 in incubator-geode's branch refs/heads/develop from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f84b1c0 ] GEODE-1377: Initial move of system properties from private to public > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1377) Move DistributionConfig constants to a public package
[ https://issues.apache.org/jira/browse/GEODE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311424#comment-15311424 ] ASF subversion and git services commented on GEODE-1377: Commit 03f5e0c0864d4e955029f39fe682723dea0efe71 in incubator-geode's branch refs/heads/develop from [~ukohlmeyer] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=03f5e0c ] GEODE-1377: Initial move of system properties from private to public > Move DistributionConfig constants to a public package > - > > Key: GEODE-1377 > URL: https://issues.apache.org/jira/browse/GEODE-1377 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Bruce Schuchardt > > DistributionConfig contains the names of all distributed-system properties > and their default values. The configuration constants in this class should > be moved to a public interface so that applications can reference the > property names and so not have to spell them out. For instance, > DistributionConfig.LOCATORS_NAME instead of "locators". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311366#comment-15311366 ] Swapnil Bawaskar commented on GEODE-1467: - Just because the Mgmt REST API was implemented first, it is (gemfire/v1) and the dev REST api is (gemfire-api/v1). I think we should take this opportunity to rename the dev rest api to (geode/v1) and the mgmt REST API to something like (geode-mgmt/v1 or geode/manage/v1). Ideally in the long term, we should only expose one REST api for both data access and monitoring. > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement >Reporter: Nitin Lamba > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1494) Allow users to provide callbacks to sample statistics
[
https://issues.apache.org/jira/browse/GEODE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1494:
-
Description:
The Statistics interface has methods to increment, set, and get the value of
various statistics. The statistics are sampled at the sample-rate by the stat
sampling thread.
We should add a way to provide a callback that computes the value of the
statistic. The callback can be called by the stat sampling thread to compute
the value at the sample time.
This is useful because some statistics are hard to update correctly using using
increment operations. For example, tracking the total number of entries in a
parallel async event queue is tricky, because buckets may move on and off of a
node while concurrent operations are also adding entries. But measuring the
current size of the queue is easy by just calling size on the underlying
regions.
Here are the proposed new methods on the statistics interface:
{code}
/**
* Provide a callback to compute the value of this statistic
* every sample interval and use that as the value of the stat.
*
*/
public void sampleInt(int id, IntSupplier supplier);
public void sampleLong(int id, LongSupplier supplier);
public void sampleDouble(int id, DoubleSupplier supplier);
public void sampleInt(String name, IntSupplier supplier);
public void sampleLong(String name, LongSupplier supplier);
public void sampleDouble(String name, DoubleSupplier supplier);
public void sampleInt(StatisticDescriptor descriptor, IntSupplier supplier);
public void sampleLong(StatisticDescriptor descriptor, LongSupplier supplier);
public void sampleDouble(StatisticDescriptor descriptor, DoubleSupplier
supplier);
{code}
was:
The Statistics interface has methods to increment, set, and get the value of
various statistics. The statistics are sampled at the sample-rate by the stat
sampling thread.
We should add a way to provide a callback that computes the value of the
statistic. The callback can be called by the stat sampling thread to compute
the value at the sample time.
This is useful because some statistics are hard to update correctly using using
increment operations. For example, tracking the total number of entries in a
parallel async event queue is tricky, because buckets may move on and off of a
node while concurrent operations are also adding entries. But measuring the
current size of the queue is easy by just calling size on the underlying
regions.
Here are the proposed new methods on the statistics interface:
{code}
/**
* Provide a callback to compute the value of this statistic
* every sample interval and use that as the value of the stat.
*
*/
public void sampleInt(int id, IntSupplier sampler);
public void sampleLong(int id, LongSupplier supplier);
public void sampleDouble(int id, DoubleSupplier supplier);
public void sampleInt(String name, IntSupplier sampler);
public void sampleLong(String name, LongSupplier supplier);
public void sampleDouble(String name, DoubleSupplier supplier);
public void sampleInt(StatisticDescriptor descriptor, IntSupplier sampler);
public void sampleLong(StatisticDescriptor descriptor, LongSupplier supplier);
public void sampleDouble(StatisticDescriptor descriptor, DoubleSupplier
supplier);
{code}
> Allow users to provide callbacks to sample statistics
> -
>
> Key: GEODE-1494
> URL: https://issues.apache.org/jira/browse/GEODE-1494
> Project: Geode
> Issue Type: Improvement
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> The Statistics interface has methods to increment, set, and get the value of
> various statistics. The statistics are sampled at the sample-rate by the stat
> sampling thread.
> We should add a way to provide a callback that computes the value of the
> statistic. The callback can be called by the stat sampling thread to compute
> the value at the sample time.
> This is useful because some statistics are hard to update correctly using
> using increment operations. For example, tracking the total number of entries
> in a parallel async event queue is tricky, because buckets may move on and
> off of a node while concurrent operations are also adding entries. But
> measuring the current size of the queue is easy by just calling size on the
> underlying regions.
> Here are the proposed new methods on the statistics interface:
> {code}
> /**
>* Provide a callback to compute the value of this statistic
>* every sample interval and use that as the value of the stat.
>*
>*/
> public void sampleInt(int id, IntSupplier supplier);
> public void sampleLong(int id, LongSupplier supplier);
> public void sampleDouble(int id, DoubleSupplier supplier);
> public void sampleInt(String name, IntSupplier supplier);
>
[jira] [Assigned] (GEODE-1494) Allow users to provide callbacks to sample statistics
[
https://issues.apache.org/jira/browse/GEODE-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reassigned GEODE-1494:
Assignee: Dan Smith
> Allow users to provide callbacks to sample statistics
> -
>
> Key: GEODE-1494
> URL: https://issues.apache.org/jira/browse/GEODE-1494
> Project: Geode
> Issue Type: Improvement
>Reporter: Dan Smith
>Assignee: Dan Smith
>
> The Statistics interface has methods to increment, set, and get the value of
> various statistics. The statistics are sampled at the sample-rate by the stat
> sampling thread.
> We should add a way to provide a callback that computes the value of the
> statistic. The callback can be called by the stat sampling thread to compute
> the value at the sample time.
> This is useful because some statistics are hard to update correctly using
> using increment operations. For example, tracking the total number of entries
> in a parallel async event queue is tricky, because buckets may move on and
> off of a node while concurrent operations are also adding entries. But
> measuring the current size of the queue is easy by just calling size on the
> underlying regions.
> Here are the proposed new methods on the statistics interface:
> {code}
> /**
>* Provide a callback to compute the value of this statistic
>* every sample interval and use that as the value of the stat.
>*
>*/
> public void sampleInt(int id, IntSupplier sampler);
> public void sampleLong(int id, LongSupplier supplier);
> public void sampleDouble(int id, DoubleSupplier supplier);
> public void sampleInt(String name, IntSupplier sampler);
> public void sampleLong(String name, LongSupplier supplier);
> public void sampleDouble(String name, DoubleSupplier supplier);
> public void sampleInt(StatisticDescriptor descriptor, IntSupplier sampler);
> public void sampleLong(StatisticDescriptor descriptor, LongSupplier
> supplier);
> public void sampleDouble(StatisticDescriptor descriptor, DoubleSupplier
> supplier);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1494) Allow users to provide callbacks to sample statistics
Dan Smith created GEODE-1494:
Summary: Allow users to provide callbacks to sample statistics
Key: GEODE-1494
URL: https://issues.apache.org/jira/browse/GEODE-1494
Project: Geode
Issue Type: Improvement
Reporter: Dan Smith
The Statistics interface has methods to increment, set, and get the value of
various statistics. The statistics are sampled at the sample-rate by the stat
sampling thread.
We should add a way to provide a callback that computes the value of the
statistic. The callback can be called by the stat sampling thread to compute
the value at the sample time.
This is useful because some statistics are hard to update correctly using using
increment operations. For example, tracking the total number of entries in a
parallel async event queue is tricky, because buckets may move on and off of a
node while concurrent operations are also adding entries. But measuring the
current size of the queue is easy by just calling size on the underlying
regions.
Here are the proposed new methods on the statistics interface:
{code}
/**
* Provide a callback to compute the value of this statistic
* every sample interval and use that as the value of the stat.
*
*/
public void sampleInt(int id, IntSupplier sampler);
public void sampleLong(int id, LongSupplier supplier);
public void sampleDouble(int id, DoubleSupplier supplier);
public void sampleInt(String name, IntSupplier sampler);
public void sampleLong(String name, LongSupplier supplier);
public void sampleDouble(String name, DoubleSupplier supplier);
public void sampleInt(StatisticDescriptor descriptor, IntSupplier sampler);
public void sampleLong(StatisticDescriptor descriptor, LongSupplier supplier);
public void sampleDouble(StatisticDescriptor descriptor, DoubleSupplier
supplier);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1372) Geode UDP communications are not secure when SSL is configured
[ https://issues.apache.org/jira/browse/GEODE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311260#comment-15311260 ] ASF subversion and git services commented on GEODE-1372: Commit 667c4259f4dc399766b37b03b999e70fe10761b8 in incubator-geode's branch refs/heads/feature/GEODE-1372 from [~hitesh.khamesra] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=667c425 ] Merge branch 'feature/GEODE-1372' of https://git-wip-us.apache.org/repos/asf/incubator-geode into GEODE-1372 > Geode UDP communications are not secure when SSL is configured > -- > > Key: GEODE-1372 > URL: https://issues.apache.org/jira/browse/GEODE-1372 > Project: Geode > Issue Type: New Feature > Components: membership >Reporter: Bruce Schuchardt >Assignee: Hitesh Khamesra > > Gemfire servers use UDP requests to communicate membership views, suspect > processing and other information. When gemfire SSL is enabled, only the TCP > requests are encrypted and UDP requests are not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1372) Geode UDP communications are not secure when SSL is configured
[ https://issues.apache.org/jira/browse/GEODE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311258#comment-15311258 ] ASF subversion and git services commented on GEODE-1372: Commit b6a734415d1bec96c1f84a51b1fca16165bab0ae in incubator-geode's branch refs/heads/feature/GEODE-1372 from [~hitesh.khamesra] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b6a7344 ] GEODE-1372 added unit test and some more fixes. > Geode UDP communications are not secure when SSL is configured > -- > > Key: GEODE-1372 > URL: https://issues.apache.org/jira/browse/GEODE-1372 > Project: Geode > Issue Type: New Feature > Components: membership >Reporter: Bruce Schuchardt >Assignee: Hitesh Khamesra > > Gemfire servers use UDP requests to communicate membership views, suspect > processing and other information. When gemfire SSL is enabled, only the TCP > requests are encrypted and UDP requests are not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1372) Geode UDP communications are not secure when SSL is configured
[ https://issues.apache.org/jira/browse/GEODE-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311259#comment-15311259 ] ASF subversion and git services commented on GEODE-1372: Commit 667c4259f4dc399766b37b03b999e70fe10761b8 in incubator-geode's branch refs/heads/feature/GEODE-1372 from [~hitesh.khamesra] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=667c425 ] Merge branch 'feature/GEODE-1372' of https://git-wip-us.apache.org/repos/asf/incubator-geode into GEODE-1372 > Geode UDP communications are not secure when SSL is configured > -- > > Key: GEODE-1372 > URL: https://issues.apache.org/jira/browse/GEODE-1372 > Project: Geode > Issue Type: New Feature > Components: membership >Reporter: Bruce Schuchardt >Assignee: Hitesh Khamesra > > Gemfire servers use UDP requests to communicate membership views, suspect > processing and other information. When gemfire SSL is enabled, only the TCP > requests are encrypted and UDP requests are not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311224#comment-15311224 ] ASF subversion and git services commented on GEODE-11: -- Commit 1e97dbb6848fa76663a56900ed8a869d749ba9db in incubator-geode's branch refs/heads/develop from [~upthewaterspout] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=1e97dbb ] GEODE-11: Adding a method to LuceneIndexImpl to dump indexes Adding a method to LuceneIndexImpl to invoke the DumpDirectoryFiles function and dump all of the index files to disk. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1493) config/gemfire.properties that is shipped with the geode distribution contains user specific info
Dan Smith created GEODE-1493:
Summary: config/gemfire.properties that is shipped with the geode
distribution contains user specific info
Key: GEODE-1493
URL: https://issues.apache.org/jira/browse/GEODE-1493
Project: Geode
Issue Type: Bug
Components: build
Reporter: Dan Smith
The geode-assembly/build.gradle file generates a default gemfire.properties and
cache.xml that get included in the config directory in the binary distribution.
See the defaultDistributionConfig target.
However, the generated gemfire.properties file has a bad value for
cluster-configuration-dir. This is the value that shipped with M2:
{noformat}
cluster-configuration-dir=/home/dsmith/data/work/gemfire5/open/geode-assembly/build
{noformat}
The mcast-address is also suspect, because the default mcast address depends on
whether the build system system prefers IPv6 or IPv4 addresses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1493) config/gemfire.properties that is shipped with the geode distribution contains user specific info
[
https://issues.apache.org/jira/browse/GEODE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1493:
-
Fix Version/s: 1.0.0-incubating.M3
> config/gemfire.properties that is shipped with the geode distribution
> contains user specific info
> -
>
> Key: GEODE-1493
> URL: https://issues.apache.org/jira/browse/GEODE-1493
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Dan Smith
> Fix For: 1.0.0-incubating.M3
>
>
> The geode-assembly/build.gradle file generates a default gemfire.properties
> and cache.xml that get included in the config directory in the binary
> distribution. See the defaultDistributionConfig target.
> However, the generated gemfire.properties file has a bad value for
> cluster-configuration-dir. This is the value that shipped with M2:
> {noformat}
> cluster-configuration-dir=/home/dsmith/data/work/gemfire5/open/geode-assembly/build
> {noformat}
> The mcast-address is also suspect, because the default mcast address depends
> on whether the build system system prefers IPv6 or IPv4 addresses.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311120#comment-15311120 ] ASF subversion and git services commented on GEODE-11: -- Commit 6ef7d47542d61e14d266ef72f8b31ebf718d0dc6 in incubator-geode's branch refs/heads/develop from [~huynhja] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=6ef7d47 ] GEODE-11: Resolved compile warning for LuceneQueriesIntegrationTest * Modified LuceneQuery types to match the expectedKeys type > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311067#comment-15311067 ] ASF subversion and git services commented on GEODE-11: -- Commit 7d15174d5cc4ddd829bed704416ded36b1f32c3c in incubator-geode's branch refs/heads/develop from [~upthewaterspout] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=7d15174 ] GEODE-11 - Fixing failure in FileSystemJUnitTest This test was listing files in a directory and making assertions about the order in which they would return. Sorting the list of files before making assertions because the order is not guaranteed. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311016#comment-15311016 ] ASF subversion and git services commented on GEODE-11: -- Commit 1c8688243ae70f8a13977abf9db52edd31fc5ab1 in incubator-geode's branch refs/heads/develop from [~upthewaterspout] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=1c86882 ] GEODE-11 Adding stats for the lucene file system. Adding stats to track changes to the lucene file system. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1492) CI Failure: CompositeTypeTestDUnitTest.testCompositeTypeGetters
[ https://issues.apache.org/jira/browse/GEODE-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh updated GEODE-1492: --- Labels: CI (was: ) > CI Failure: CompositeTypeTestDUnitTest.testCompositeTypeGetters > --- > > Key: GEODE-1492 > URL: https://issues.apache.org/jira/browse/GEODE-1492 > Project: Geode > Issue Type: Bug >Reporter: Jason Huynh > Labels: CI > > This test failed in a private run with the following exception: > 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 635 > [fatal 2016/05/30 03:43:58.791 PDT tid=0x316] > (tid=790 msgId=295) No longer connected to cc2-rh6[27242]. > at org.junit.Assert.fail(Assert.java:88) > at > com.gemstone.gemfire.test.dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:354) > at > com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:540) > at > com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:489) > at > com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.tearDown(JUnit4DistributedTestCase.java:478) > at > com.gemstone.gemfire.test.dunit.internal.JUnit3DistributedTestCase.tearDown(JUnit3DistributedTestCase.java:206) > at junit.framework.TestCase.runBare(TestCase.java:146) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > ... > Previously run tests: [TestSubscriptionsDUnitTest, > SharedConfigurationDUnitTest, SharedConfigurationUsingDirDUnitTest, > MultiUserDUnitTest, CompositeTypeTestDUnitTest] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1492) CI Failure: CompositeTypeTestDUnitTest.testCompositeTypeGetters
Jason Huynh created GEODE-1492: -- Summary: CI Failure: CompositeTypeTestDUnitTest.testCompositeTypeGetters Key: GEODE-1492 URL: https://issues.apache.org/jira/browse/GEODE-1492 Project: Geode Issue Type: Bug Reporter: Jason Huynh This test failed in a private run with the following exception: 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 635 [fatal 2016/05/30 03:43:58.791 PDT tid=0x316] (tid=790 msgId=295) No longer connected to cc2-rh6[27242]. at org.junit.Assert.fail(Assert.java:88) at com.gemstone.gemfire.test.dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:354) at com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:540) at com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:489) at com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.tearDown(JUnit4DistributedTestCase.java:478) at com.gemstone.gemfire.test.dunit.internal.JUnit3DistributedTestCase.tearDown(JUnit3DistributedTestCase.java:206) at junit.framework.TestCase.runBare(TestCase.java:146) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:129) at junit.framework.TestSuite.runTest(TestSuite.java:252) at junit.framework.TestSuite.run(TestSuite.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) ... Previously run tests: [TestSubscriptionsDUnitTest, SharedConfigurationDUnitTest, SharedConfigurationUsingDirDUnitTest, MultiUserDUnitTest, CompositeTypeTestDUnitTest] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1179) gfsh help text: remove references to vsd
[ https://issues.apache.org/jira/browse/GEODE-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-1179: - Assignee: Jens Deppe > gfsh help text: remove references to vsd > > > Key: GEODE-1179 > URL: https://issues.apache.org/jira/browse/GEODE-1179 > Project: Geode > Issue Type: Bug > Components: docs, gfsh >Reporter: Dave Barnes >Assignee: Jens Deppe > > The gfsh messages for 'help' and 'help start' refer to 'start vsd', which is > not a valid command in the open source version of gfsh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-308) Separate hydra from dunit and junit tests in gemfire-core
[ https://issues.apache.org/jira/browse/GEODE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310797#comment-15310797 ] Kevin Duling commented on GEODE-308: Removed several classes. * src/test/java/hydra/GsRandom.java * src/test/java/hydra/HydraRuntimeException.java * src/test/java/hydra/Log.java * src/test/java/hydra/LogVersionHelper.java * src/test/java/hydra/log/AnyLogWriter.java * src/test/java/hydra/log/CircularOutputStream.java These classes need more work to extract them. * src/test/java/hydra/MethExecutor.java * src/test/java/hydra/MethExecutorResult.java * src/test/java/hydra/SchedulingOrder.java > Separate hydra from dunit and junit tests in gemfire-core > - > > Key: GEODE-308 > URL: https://issues.apache.org/jira/browse/GEODE-308 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kevin Duling > Labels: hydra > > Usage of Hydra needs to be removed from dunit and junit tests in gemfire-core > and any other project. > The following hydra classes in gemfire-core should be removed (and replaced > if needed by dunit/junit tests): > src/test/java/hydra/GsRandom.java > src/test/java/hydra/HydraRuntimeException.java > src/test/java/hydra/Log.java > src/test/java/hydra/LogVersionHelper.java > src/test/java/hydra/MethExecutor.java > src/test/java/hydra/MethExecutorResult.java > src/test/java/hydra/SchedulingOrder.java > src/test/java/hydra/log/AnyLogWriter.java > src/test/java/hydra/log/CircularOutputStream.java > The following are also not com.gemstone packages and should be removed if > they're specific to Hydra (or Hydra tests) or repackaged if they're actually > used in dunit/junit tests: > src/test/java/batterytest/greplogs/ExpectedStrings.java > src/test/java/batterytest/greplogs/LogConsumer.java > src/test/java/cacheRunner/Portfolio.java > src/test/java/cacheRunner/Position.java > src/test/java/parReg/query/unittest/NewPortfolio.java > src/test/java/parReg/query/unittest/Position.java > src/test/java/perffmwk/Formatter.java > src/test/java/templates/security/DummyAuthenticator.java > src/test/java/templates/security/DummyAuthorization.java > src/test/java/templates/security/FunctionSecurityPrmsHolder.java > src/test/java/templates/security/LdapUserAuthenticator.java > src/test/java/templates/security/PKCSAuthenticator.java > src/test/java/templates/security/PKCSAuthInt.java > src/test/java/templates/security/PKCSPrincipal.java > src/test/java/templates/security/UsernamePrincipal.java > src/test/java/templates.security/UserPasswordAuthInit.java > src/test/java/templates.security/XmlAuthorization.java > src/test/java/templates.security/XmlErrorHandler.java > src/test/java/util/TestException.java > The following are Hydra-related resources in src/test/resources that also > need to be removed: > src/test/resources/jta/cachejta.xml > src/test/resources/ssl/trusted.keystore > src/test/resources/templates/security/authz5_5.dtd > src/test/resources/templates/security/authz6_0.dtd -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1490) Convert all concrete *OperationContexts into interfaces
Jens Deppe created GEODE-1490: - Summary: Convert all concrete *OperationContexts into interfaces Key: GEODE-1490 URL: https://issues.apache.org/jira/browse/GEODE-1490 Project: Geode Issue Type: Improvement Components: security Reporter: Jens Deppe Currently the hierarchy of OperationContexts (in com.gemstone.gemfire.cache.operations) are a mix of abstract and concrete classes as well as a mix of 'public' and 'internal' packaging. It would be much cleaner if these were converted to interfaces and all of the concrete implementations be made internal. Currently where public packages extend internal packages the javadoc would also be broken as the public packages would reference (internal) packages for which no javadoc links will exist. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1471) GatewayEventFilter callbacks are not invoked when an AsyncEventQueues is configured using xml
[
https://issues.apache.org/jira/browse/GEODE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310614#comment-15310614
]
Anthony Baker commented on GEODE-1471:
--
Is there a test for this behavior?
> GatewayEventFilter callbacks are not invoked when an AsyncEventQueues is
> configured using xml
> -
>
> Key: GEODE-1471
> URL: https://issues.apache.org/jira/browse/GEODE-1471
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>
> None of the {{GatewayEventFilter}} callbacks are invoked when configuring
> {{AsyncEventQueues}} using xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1489) The users' password should not be logged
Jens Deppe created GEODE-1489:
-
Summary: The users' password should not be logged
Key: GEODE-1489
URL: https://issues.apache.org/jira/browse/GEODE-1489
Project: Geode
Issue Type: Improvement
Components: security
Reporter: Jens Deppe
The following currently appears in the member's log file:
{noformat}
[info 2016/05/31 15:15:52.475 PDT locator1 tid=0x14] Logging in root
[info 2016/05/31 15:15:52.665 PDT locator1 tid=0x14] User=root pwd=secret
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1488) Consider making SampleJsonAuthorization dynamic
Jens Deppe created GEODE-1488: - Summary: Consider making SampleJsonAuthorization dynamic Key: GEODE-1488 URL: https://issues.apache.org/jira/browse/GEODE-1488 Project: Geode Issue Type: Improvement Components: security Reporter: Jens Deppe This code is only a sample, but it currently requires a full restart whenever the configuration file changes. It would be useful if it could detect a change and re-read the config file so as to dynamically update it's configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1293) Align code and docs for modules
[ https://issues.apache.org/jira/browse/GEODE-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe resolved GEODE-1293. --- Resolution: Fixed See also GEODE-1410 > Align code and docs for modules > --- > > Key: GEODE-1293 > URL: https://issues.apache.org/jira/browse/GEODE-1293 > Project: Geode > Issue Type: Improvement > Components: docs, extensions, hibernate, http session >Reporter: Jens Deppe >Assignee: Jens Deppe > Fix For: 1.0.0-incubating.M3 > > > Need to ensure that the docs for the modules are correct. There are startup > script changes as well as config changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1487) CI Failure: GemfireDataCommandsDUnitTest.testRebalanceForEntireDS
Udo Kohlmeyer created GEODE-1487: Summary: CI Failure: GemfireDataCommandsDUnitTest.testRebalanceForEntireDS Key: GEODE-1487 URL: https://issues.apache.org/jira/browse/GEODE-1487 Project: Geode Issue Type: Bug Components: management Reporter: Udo Kohlmeyer Build #482 (May 28, 2016 3:42:00 AM) Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097 https://builds.apache.org/job/Geode-nightly/482/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testRebalanceForEntireDS/ com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host asf902.gq1.ygridcore.net with 4 VMs at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308) at com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:126) at com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:115) at com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:106) at com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.setupTestRebalanceForEntireDS(GemfireDataCommandsDUnitTest.java:1882) at com.gemstone.gemfire.management.internal.cli.commands.GemfireDataCommandsDUnitTest.testRebalanceForEntireDS(GemfireDataCommandsDUnitTest.java:1862) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at
[jira] [Created] (GEODE-1486) CI Failure: miscellaneouscommandsexportlogspart3dunittest.testexportlogsformem...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Udo Kohlmeyer created GEODE-1486: Summary: CI Failure: miscellaneouscommandsexportlogspart3dunittest.testexportlogsformem...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest Key: GEODE-1486 URL: https://issues.apache.org/jira/browse/GEODE-1486 Project: Geode Issue Type: Bug Components: management Reporter: Udo Kohlmeyer Build #2697 (May 24, 2016 1:09:14 AM) Revision: 45a4ef29f3c8174281aad667265a0764b0b912a3 https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2697/testReport/com.gemstone.gemfire.management.internal.cli.commands/MiscellaneousCommandsExportLogsPart3DUnitTest/testExportLogsForMember_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/ 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 816 [fatal 2016/05/24 10:42:42.744 PDT tid=0x1985] org.eclipse.jetty.io.EofException at org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) at org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) at javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) at org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) at org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) at org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) 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.doGet(FrameworkServlet.java:860) at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) 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.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1090)
[jira] [Created] (GEODE-1485) CI Failure: gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Udo Kohlmeyer created GEODE-1485: Summary: CI Failure: gemfiredatacommandsdunittest.testgetlocateentryfromregionondifferen...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest Key: GEODE-1485 URL: https://issues.apache.org/jira/browse/GEODE-1485 Project: Geode Issue Type: Bug Components: management Reporter: Udo Kohlmeyer Build #2718 (May 28, 2016 7:09:17 AM) Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097 https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2718/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testGetLocateEntryFromRegionOnDifferentVM_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/ 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 1223 [fatal 2016/05/28 16:52:26.927 PDT tid=0xe2d] org.eclipse.jetty.io.EofException at org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) at org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) at javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) at org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) at org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) at org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) 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.doGet(FrameworkServlet.java:860) at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) 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.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1090)
[jira] [Created] (GEODE-1484) CI Failure: gemfiredatacommandsdunittest.testrebalancecommandforsimul...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Udo Kohlmeyer created GEODE-1484: Summary: CI Failure: gemfiredatacommandsdunittest.testrebalancecommandforsimul...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest Key: GEODE-1484 URL: https://issues.apache.org/jira/browse/GEODE-1484 Project: Geode Issue Type: Bug Components: management Reporter: Udo Kohlmeyer Build #2731 (May 29, 2016 9:09:18 AM) Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097 https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2731/testReport/com.gemstone.gemfire.management.internal.cli.commands/GemfireDataCommandsDUnitTest/testRebalanceCommandForSimulate_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/ 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 1664 [fatal 2016/05/29 18:39:37.663 PDT tid=0xaeb] org.eclipse.jetty.io.EofException at org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) at org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) at javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) at org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) at org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) at org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) 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.doGet(FrameworkServlet.java:860) at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) 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.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1090) at
[jira] [Created] (GEODE-1482) CI Failure: MemberMBeanAttributesDUnitTest.testConfigAttributes
Udo Kohlmeyer created GEODE-1482: Summary: CI Failure: MemberMBeanAttributesDUnitTest.testConfigAttributes Key: GEODE-1482 URL: https://issues.apache.org/jira/browse/GEODE-1482 Project: Geode Issue Type: Bug Components: management Reporter: Udo Kohlmeyer Build #2712 (May 27, 2016 7:09:13 PM) Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097 https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2712/testReport/com.gemstone.gemfire.management/MemberMBeanAttributesDUnitTest/testConfigAttributes/ 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 419 [fatal 2016/05/27 23:43:44.251 PDT tid=0x1b6] (tid=438 msgId=303) No longer connected to cc1-co[24095]. at org.junit.Assert.fail(Assert.java:88) at com.gemstone.gemfire.test.dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:354) at com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:540) at com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:489) at com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.tearDown(JUnit4DistributedTestCase.java:478) at com.gemstone.gemfire.test.dunit.internal.JUnit3DistributedTestCase.tearDown(JUnit3DistributedTestCase.java:206) at junit.framework.TestCase.runBare(TestCase.java:146) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at junit.framework.TestResult.run(TestResult.java:125) at junit.framework.TestCase.run(TestCase.java:129) at junit.framework.TestSuite.runTest(TestSuite.java:252) at junit.framework.TestSuite.run(TestSuite.java:247) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54) at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1477) CI Failure: miscellaneouscommandsexportlogspart1dunittest.testexportlogsforme...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Udo Kohlmeyer created GEODE-1477: Summary: CI Failure: miscellaneouscommandsexportlogspart1dunittest.testexportlogsforme...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest Key: GEODE-1477 URL: https://issues.apache.org/jira/browse/GEODE-1477 Project: Geode Issue Type: Bug Components: management Reporter: Udo Kohlmeyer Build #2710 (May 27, 2016 3:09:17 PM) Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097 https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2710/testReport/com.gemstone.gemfire.management.internal.cli.commands/MiscellaneousCommandsExportLogsPart1DUnitTest/testExportLogsForMerge_com_gemstone_gemfire_management_internal_cli_commands_CommandOverHttpDUnitTest/ com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host cc2-ub.gemstone.com with 4 VMs at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308) at com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:126) at com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:115) at com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:106) at com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsExportLogsPart1DUnitTest.setupForExportLogs(MiscellaneousCommandsExportLogsPart1DUnitTest.java:53) at com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsExportLogsPart1DUnitTest.testExportLogsForMerge(MiscellaneousCommandsExportLogsPart1DUnitTest.java:109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) at
[jira] [Created] (GEODE-1476) CI Failure: SharedConfigurationDUnitTest.testGetHostedLocatorsWithSharedConfiguration
Udo Kohlmeyer created GEODE-1476: Summary: CI Failure: SharedConfigurationDUnitTest.testGetHostedLocatorsWithSharedConfiguration Key: GEODE-1476 URL: https://issues.apache.org/jira/browse/GEODE-1476 Project: Geode Issue Type: Bug Components: management Reporter: Udo Kohlmeyer Build #2729 (May 29, 2016 5:09:11 AM) Revision: 3e8fe7af0ced64d2a15b6c3ce52eb9560a83d097 https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2729/testReport/com.gemstone.gemfire.management.internal.configuration/SharedConfigurationDUnitTest/testGetHostedLocatorsWithSharedConfiguration/ 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 756 [fatal 2016/05/29 09:27:39.228 PDT tid=0x11e] (tid=286 msgId=199) No longer connected to venezuela[23218]. at org.junit.Assert.fail(Assert.java:88) at com.gemstone.gemfire.test.dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:354) at com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:540) at com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:489) at com.gemstone.gemfire.test.dunit.internal.JUnit4DistributedTestCase.tearDown(JUnit4DistributedTestCase.java:478) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at
[jira] [Created] (GEODE-1473) CI Failure: SharedConfigurationCommandsDUnitTest.testExportImportSharedConfiguration
Udo Kohlmeyer created GEODE-1473: Summary: CI Failure: SharedConfigurationCommandsDUnitTest.testExportImportSharedConfiguration Key: GEODE-1473 URL: https://issues.apache.org/jira/browse/GEODE-1473 Project: Geode Issue Type: Bug Components: rest (admin) Reporter: Udo Kohlmeyer Build #2743 (May 30, 2016 9:09:15 AM) Revision: fa3a937508b05ec579f78ed4f0a44278a9665b75 https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2743/testReport/junit/com.gemstone.gemfire.management.internal.cli.commands/SharedConfigurationCommandsDUnitTest/testExportImportSharedConfiguration/ java.lang.AssertionError: expected: but was: at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at com.gemstone.gemfire.management.internal.cli.commands.SharedConfigurationCommandsDUnitTest.testExportImportSharedConfiguration(SharedConfigurationCommandsDUnitTest.java:194) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360) at
