Re: Addition of rmi-io library

As far as I can see, we are utilizing the streaming capability provided by the rmi-io, the content is going over the wire on whatever port that was port before. When streaming content from the gfsh to the jmxManager, it's using the jmx port; when getting jars between locator/servers, it's using the

Re: [VOTE] Apache Geode release - 1.4.0 RC1

This release candidate does have the rmi-io changes. I think we need to sort out if we are creating insecure sockets due to those changes - if so we need to fix that before releasing. -Dan On Tue, Jan 23, 2018 at 2:32 PM, Swapnil Bawaskar wrote: > This is the first release candidate for Apache

Geode unit tests completed in 'develop/AcceptanceTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/177

Re: Geode enterprise support

Hello Vladi, There are no enterprise support services provided by Pivotal Customer Support at least. https://discuss.pivotal.io/hc/en-us/articles/206097347-How-can-I-get-support-for-Geode- Currently, Apache Geode and Pivotal GemFire are same things. If you need enterprise support services, why d

Re: Addition of rmi-io library

I don't have an issue with the dependency. But if we are opening up new ports for RMI connections, that seems like a potential security risk. If someone has enabled cluster SSL we shouldn't be opening up an insecure port for RMI connections. We should also make sure this is not leaking open socket

Proposal: GEODE-4367 - Return PDXInstance when Domain Object can't be found

Hi Geode Devs, I'm proposing the following change to how we handle deserialization when Domain Objects can't be found and pdx-serialize=false. https://issues.apache.org/jira/browse/GEODE-4367 Looking forward to the discussion. \ah

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #806 was SUCCESSFUL (with 2324 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #806 was successful. --- Scheduled 2326 tests in total. https://build.spring.io/browse/SGF-NAG-806/ -- This

Addition of rmi-io library

Apologies that this was not raised earlier in discussion but I'm happy to describe it now. *Background:* When deploying jars into Geode they are moved through the system as simple byte[] blobs. This obviously consumes memory. The various affected areas are: - gfsh reads the jars into memory - th

[VOTE] Apache Geode release - 1.4.0 RC1

This is the first release candidate for Apache Geode, version 1.4.0. Thanks to all the community members for their contributions to this release! *** Please download, test and vote by Friday, January 26, 1200 hrs US Pacific. *** It fixes 277 issues. release notes can be found at: https://issues.a

Re: build is broken

I agree with Kirk. A simple notice to the dev list to say what dependency and why it is being added, this would also be an opportunity to make sure the dependency is not using a Cat-X license [1]. --Mark [1] https://www.apache.org/legal/resolved.html#category-x On Tue, Jan 23, 2018 at 2:09 PM, K

Re: build is broken

Discussing the addition of new dependencies is something the community should be doing on the dev-list regardless of how many git repos we have. It's part of the Apache Way that we are beholden to as an Apache project. On Tue, Jan 23, 2018 at 11:25 AM, Udo Kohlmeyer wrote: > This really just ano

Failed: jinmeiliao/geode#189 (expiry - 0b1f73d)

Build Update for jinmeiliao/geode - Build: #189 Status: Failed Duration: 15 minutes and 43 seconds Commit: 0b1f73d (expiry) Author: Jinmei Liao Message: GEODE-3915: use ClassName type for cache-loader, writer and listeners Signed-off-by: Patrick Rhomberg Vie

Geode enterprise support

Hi Is there a company giving enterprise support of Apache Geode? (not Gemfire) Regards Vladi This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer

Re: build is broken

This really just another reason that we should be pushing for the separation of Geode into different (independent) modules with potentially separate repos. This way modules can advance and iterate faster without having to be influenced by external factors causing unrelated failures. I would push f

Re: build is broken

I have it working now. My IntelliJ project was using JDK1.8.0_66 for Gradle which prevented updating of dependencies which then caused compilation in IntelliJ to fail on that new dependency. This doesn't resolve my main issue here which is this: *all new dependencies should be discussed on the dev

Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/142

Re: build is broken

I just ran `gradle clean build` from HEAD and did not get any errors. > On Jan 23, 2018, at 10:08 AM, Jens Deppe wrote: > > The dependency is the rmi-io library. It provides functionality for > streaming data over RMI. > > It was added a few weeks ago, so I'm not sure why your build is breaking

Re: build is broken

The dependency is the rmi-io library. It provides functionality for streaming data over RMI. It was added a few weeks ago, so I'm not sure why your build is breaking now. --Jens On Tue, Jan 23, 2018 at 9:41 AM, Kirk Lund wrote: > Looks like this dependency is Jackcess (used for reading and wri

Re: build is broken

Looks like this dependency is Jackcess (used for reading and writing MS Access databases). I cannot find any discussion about adding this dependency on the dev-list. Why does Geode need to talk to MS Access databases for Cluster Configuration? It does have an Apache 2.0 license, but I think there

build is broken

I just tried to compile Geode develop. ClusterConfigurationService has two broken imports that don't exist: import com.healthmarketscience.rmiio.RemoteInputStream; import com.healthmarketscience.rmiio.RemoteInputStreamClient; Was there a new dependency added to Geode?