Re: Orphaned Server processes

Also, don't forget that you can start a server in a 'wait for locator' mode (I forget the actual option) which should be distinguished from an actual 'orphaned' instance. --Jens On Wed, Apr 5, 2017 at 3:54 PM, Michael Stolz wrote: > I think the current behavior is probably

Re: Review Request 58225: GEODE-2757: netsearch has a race that may return null object incorrectly

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58225/#review171175 ---

[jira] [Commented] (GEODE-2732) after auto-reconnect a server is restarted on the default port of 40404

[ https://issues.apache.org/jira/browse/GEODE-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958054#comment-15958054 ] ASF subversion and git services commented on GEODE-2732: Commit

[jira] [Commented] (GEODE-2684) org.apache.geode.internal.tcp.Connection & ConnectionTable cleanup

[ https://issues.apache.org/jira/browse/GEODE-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958053#comment-15958053 ] ASF subversion and git services commented on GEODE-2684: Commit

Re: Review Request 58155: GEODE-2653: fix a flaky test.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58155/ --- (Updated April 5, 2017, 11:44 p.m.) Review request for geode, Bruce

Re: Review Request 58187: GEODE-2732 after auto-reconnect a server is restarted on the default port of 40404

> On April 5, 2017, 11:24 p.m., Galen O'Sullivan wrote: > > geode-core/src/main/java/org/apache/geode/internal/tcp/Connection.java > > Line 1288 (original) > > > > > > No more JRockit! I'm hoping we've officially

Re: Review Request 58187: GEODE-2732 after auto-reconnect a server is restarted on the default port of 40404

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58187/#review171087 --- Looks good. I left a few questions on the test, but the non-test

Re: Orphaned Server processes

I think the current behavior is probably left over from the multicast member discovery days, which are...thankfully...behind us. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-631-835-4771 On Wed, Apr 5, 2017 at 6:53 PM, Michael Stolz wrote: > Anyway,

Re: Orphaned Server processes

Anyway, at the very least it's an unusual configuration, so it would be best if it required some explicit option to start server to say "Yes I know what I'm doing...I really want a server that has no peers and no locator." Without that explicit acknowledgement it should just fail and report the

Re: Orphaned Server processes

I disagree +1 you can use stop/status by pointing at the directory where the server is logging. -1 You cannot connect to the server and issue the command "create region" or at the simplest "list members". The GFSH/management behavior should exactly the same as what one would have when

Re: Orphaned Server processes

"--start-locator=" was originally present on "start server" but was commented out for some reason. You can find the lines in CliStrings.java: // public static final String START_SERVER__START_LOCATOR = "start-locator"; // public static final String START_SERVER__START_LOCATOR__HELP = // "To start

Re: Orphaned Server processes

But you can interact with it... 1) You can issue "stop server --dir=server1" which will stop it 2) You can issue "status server --dir=server1" which will show the status for it 3) You can attach with JConsole and manipulate the MBeans. If the MBeans have operations to create something you can

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

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

Re: Orphaned Server processes

My apologies, "you" should not be interpreted as personal. I'm highlighting that a server can be created without any configuration, which allows for an orphan server. A solution should be found for that either through failing or starting a means that can correctly administer the server.

[jira] [Resolved] (GEODE-2751) UniversalMembershipListenerAdapterDUnitTest.testSystemClientEventsInServer fails on Jenkins

[ https://issues.apache.org/jira/browse/GEODE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2751. - Resolution: Fixed Fix Version/s: 1.2.0 >

[jira] [Resolved] (GEODE-2684) org.apache.geode.internal.tcp.Connection & ConnectionTable cleanup

[ https://issues.apache.org/jira/browse/GEODE-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2684. - Resolution: Fixed Fix Version/s: 1.2.0 > org.apache.geode.internal.tcp.Connection

[jira] [Resolved] (GEODE-2732) after auto-reconnect a server is restarted on the default port of 40404

[ https://issues.apache.org/jira/browse/GEODE-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-2732. - Resolution: Fixed Fix Version/s: 1.2.0 > after auto-reconnect a server is

[jira] [Commented] (GEODE-2485) CacheTransactionManager suspend/resume can leak memory for 30 minutes

[ https://issues.apache.org/jira/browse/GEODE-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957925#comment-15957925 ] Darrel Schneider commented on GEODE-2485: - It looks like a simple way to optimize code that

[jira] [Commented] (GEODE-2684) org.apache.geode.internal.tcp.Connection & ConnectionTable cleanup

[ https://issues.apache.org/jira/browse/GEODE-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957921#comment-15957921 ] ASF subversion and git services commented on GEODE-2684: Commit

[jira] [Commented] (GEODE-2732) after auto-reconnect a server is restarted on the default port of 40404

[ https://issues.apache.org/jira/browse/GEODE-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957919#comment-15957919 ] ASF subversion and git services commented on GEODE-2732: Commit

Re: Orphaned Server processes

Udo, I was commenting on the statement: >> Current Geode allows a user to start a server without being linked to a Locator. Not specifically starting server with gfsh... -Anil. On Wed, Apr 5, 2017 at 3:18 PM, Udo Kohlmeyer wrote: > Once again.. > > you missing

Review Request 58225: GEODE-2757: netsearch has a race that may return null object incorrectly

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58225/ --- Review request for geode, anilkumar gingade and Darrel Schneider. Bugs:

Re: Orphaned Server processes

+1 to add a "--start-locator=" option for starting an embedded locator. However, I can easily see a user starting two servers and expecting to form a distributed system, but if we start the embedded locator by default, they won't. So, I think we should prevent the server from starting up, but give

Re: Orphaned Server processes

Once again.. you missing the point... starting a server with "start server --name=server1" without a locator or cache.xml or jmx-manager you have created a useless server which you cannot interact with We need to avoid that... All the other discussions of how we can start an

[jira] [Assigned] (GEODE-2485) CacheTransactionManager suspend/resume can leak memory for 30 minutes

[ https://issues.apache.org/jira/browse/GEODE-2485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-2485: --- Assignee: Darrel Schneider > CacheTransactionManager suspend/resume can leak memory

[jira] [Assigned] (GEODE-2757) Netsearch may return a null object when there are other replicates available in the cluster

[ https://issues.apache.org/jira/browse/GEODE-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu reassigned GEODE-2757: --- Assignee: Eric Shu > Netsearch may return a null object when there are other replicates available >

[jira] [Created] (GEODE-2757) Netsearch may return a null object when there are other replicates available in the cluster

Eric Shu created GEODE-2757: --- Summary: Netsearch may return a null object when there are other replicates available in the cluster Key: GEODE-2757 URL: https://issues.apache.org/jira/browse/GEODE-2757

Re: Orphaned Server processes

You can still control a lone server with GFSH. And if you configure it up front, then you can still have Regions for a Client to use. $ start server --name=server1 --cache-xml-file=mycachefile.xml $ stop server --dir=server1 You could also start a JMX Manager in the server or an embedded

[jira] [Commented] (GEODE-2716) export logs should honor the log level set on the server

[ https://issues.apache.org/jira/browse/GEODE-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957605#comment-15957605 ] ASF GitHub Bot commented on GEODE-2716: --- GitHub user PurelyApplied opened a pull request:

[GitHub] geode pull request #439: GEODE-2716: export logs default behavior changed fr...

GitHub user PurelyApplied opened a pull request: https://github.com/apache/geode/pull/439 GEODE-2716: export logs default behavior changed from filtering at log level INFO to ALL. Moved location of export default log level constant from LogService to ExportLogCommand. Updated

Re: Orphaned Server processes

One could create data model using cache.xml or embedded application/api...The server/node could be used as front-end cache for database to handle peek loads (or streamed data)Client application can connect to the server and register interest, execute queries, function -Anil. On Wed, Apr

[jira] [Commented] (GEODE-2749) git and rat should ignore out/ and bin/ directories created by IDEs

[ https://issues.apache.org/jira/browse/GEODE-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957526#comment-15957526 ] ASF subversion and git services commented on GEODE-2749: Commit

[jira] [Created] (GEODE-2756) export logs integration with security

Swapnil Bawaskar created GEODE-2756: --- Summary: export logs integration with security Key: GEODE-2756 URL: https://issues.apache.org/jira/browse/GEODE-2756 Project: Geode Issue Type:

[jira] [Resolved] (GEODE-2755) Solaris images need Oracle support certificate/key

[ https://issues.apache.org/jira/browse/GEODE-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-2755. - Resolution: Fixed > Solaris images need Oracle support certificate/key >

Re: Orphaned Server processes

Thanks Jinmei! You are right. I missed that. Thanks, Jianxia On Wed, Apr 5, 2017 at 12:24 PM, Jinmei Liao wrote: > for your #1, there is a --properties-file option when you do "start > server". > > On Wed, Apr 5, 2017 at 12:20 PM, Jianxia Chen wrote: > > >

Re: Orphaned Server processes

for your #1, there is a --properties-file option when you do "start server". On Wed, Apr 5, 2017 at 12:20 PM, Jianxia Chen wrote: > Thank you William! > > I tried with it. It works. But there is something tricky in order to start > the embedded locator. > > 1) the

[jira] [Commented] (GEODE-2755) Solaris images need Oracle support certificate/key

[ https://issues.apache.org/jira/browse/GEODE-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957485#comment-15957485 ] ASF subversion and git services commented on GEODE-2755: Commit

Re: Orphaned Server processes

Thank you William! I tried with it. It works. But there is something tricky in order to start the embedded locator. 1) the gemfire.properties file has to be in the right place, either in the server directory or home directory. Looks like this is not documented. I was trying to specify the

[jira] [Created] (GEODE-2755) Solaris images need Oracle support certificate/key

Jacob S. Barrett created GEODE-2755: --- Summary: Solaris images need Oracle support certificate/key Key: GEODE-2755 URL: https://issues.apache.org/jira/browse/GEODE-2755 Project: Geode Issue

Re: Orphaned Server processes

That could be another option that could be pursued... On 4/5/17 12:05, Michael Stolz wrote: Actually, the server KNOWS it is all by itself, and since that puts into an unusable state, why not just default to starting an embedded locator on the default port? Instant single-node GemFire. --

Re: Orphaned Server processes

Actually, the server KNOWS it is all by itself, and since that puts into an unusable state, why not just default to starting an embedded locator on the default port? Instant single-node GemFire. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-631-835-4771 On Wed, Apr 5, 2017

Re: Orphaned Server processes

We should add a "--start-locator=" option to the gfsh start server command with the same semantics as the start-locator property -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-631-835-4771 On Wed, Apr 5, 2017 at 2:03 PM, William Markito Oliveira < william.mark...@gmail.com>

Re: Review Request 58187: GEODE-2732 after auto-reconnect a server is restarted on the default port of 40404

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58187/#review171159 --- Ship it! Ship It! - Hitesh Khamesra On April 4, 2017, 8:46

[jira] [Commented] (GEODE-2751) UniversalMembershipListenerAdapterDUnitTest.testSystemClientEventsInServer fails on Jenkins

[ https://issues.apache.org/jira/browse/GEODE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957351#comment-15957351 ] ASF subversion and git services commented on GEODE-2751: Commit

Re: Orphaned Server processes

@Anil, I agree... quick start to evaluate the product... "start server --name=server1" is the simplest way to start a server... BUT there are no regions or anything ... So we really only have a GemFire process that does not allow you to do anything with it... except connect to it from a

Re: Orphaned Server processes

Jianxia, you can set the property "start-locator" in gemfire.properties as below... So the server then will have an embedded locator. http://geode.apache.org/docs/guide/11/reference/topics/gemfire_properties.html start-locator If set, automatically starts a locator in the current process when

Re: Orphaned Server processes

I think an embedded server makes sense. No locator required, UNLESS you want to form a cluster and then I think you need a locator. (haven't tried this without multicast) Shutting down a server with --pid or --dir works. BUT... One cannot connect to a default server "start server

Re: Global PDX Types -> Move to Region Level?

Well said, Mike. We should document that as best practices. As Anthony mentioned, we should look for fuzzy type checking, atleast for numbers. I did consider this some time back. But It is tedious to support backward compability, unless we say pdx version 2.  From: Anthony Baker

Re: Orphaned Server processes

>> But does a use case for a server with no locator exist? What about ease of development? >> I could see that it would be easier to start just a single server process instead of two (locator and server). Agree with Darrel, for someone who is evaluating the product, it helps to build quick

Re: Orphaned Server processes

Hi Darrel, How to configure a colocated locator in the same server process? Just curious. What I understand is that the locator is in its own process. Thanks, Jianxia On Wed, Apr 5, 2017 at 10:36 AM, Darrel Schneider wrote: > I like the idea of servers failing to start

Re: Orphaned Server processes

I'd like the server to refuse to start from gfsh if it can't reach a locator. That seems like exactly the correct behavior. If you want to run a single node system for development, embedding a locator makes sense. Funny thing is, I don't know how to do that. Probably want an example for that

Re: Orphaned Server processes

I like the idea of servers failing to start if no locator exists. But does a use case for a server with no locator exist? What about ease of development? I could see that it would be easier to start just a single server process instead of two (locator and server). But for this use case couldn't

[jira] [Commented] (GEODE-2713) Function execution can lead to passing the address of a stack variable

[ https://issues.apache.org/jira/browse/GEODE-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957288#comment-15957288 ] ASF subversion and git services commented on GEODE-2713: Commit

Re: Review Request 58213: GEODE-2749: don't ignore bin/ because we have bin/ in src

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58213/#review171148 --- Ship it! I missed geode-assembly/src/main/dist/bin/ in my

Re: Review Request 58213: GEODE-2749: don't ignore bin/ because we have bin/ in src

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58213/#review171146 --- Ship it! Ship It! - Anthony Baker On April 5, 2017, 5:19

Re: Orphaned Server processes

Without connecting to the server, I think you can still stop it by specifying --pid or --dir in "stop server" command. On Wed, Apr 5, 2017 at 10:15 AM, Udo Kohlmeyer wrote: > Hey there, > > Current Geode allows a user to start a server without being linked to a > Locator.

Broken: apache/geode#2294 (develop - 02a31e2)

Build Update for apache/geode - Build: #2294 Status: Broken Duration: 6 minutes and 14 seconds Commit: 02a31e2 (develop) Author: Bruce Schuchardt Message: GEODE-2751 UniversalMembershipListenerAdapterDUnitTest.testSystemClientEventsInServer This forces the

Re: Review Request 58158: GEODE-2749: ignore bin/ and out/ which are commonly created by IDEs

> On April 5, 2017, 2:31 p.m., Anthony Baker wrote: > > -1 > > > > There are several bin/ dirs with source files: > > > > ``` > > ~/code/incubator-geode (develop)$ find . -name bin -type d > > ./extensions/geode-modules-assembly/release/session/bin > > ./geode-assembly/src/main/dist/bin > >

Review Request 58213: GEODE-2749: don't ignore bin/ because we have bin/ in src

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58213/ --- Review request for geode, Anthony Baker, Avinash Dongre, Mark Bretl, and Udo

Orphaned Server processes

Hey there, Current Geode allows a user to start a server without being linked to a Locator. Which in itself is not incorrect, but once started there is no way to connect to that server to manage it. I know that we have taken an opinionated view that member discovery can only now happen

Re: [DISCUSS] security threats (was Re: [CVE-2017-5649] Apache Geode information disclosure vulnerability)

Looks like a great wiki page to me. ;) Cool summary Anthony! Sent from my iPhone > On Apr 5, 2017, at 11:49 AM, Anthony Baker wrote: > > As a follow up to this CVE, I wanted to share the process for reporting and > responding to security issues: > >

Re: Global PDX Types -> Move to Region Level?

Converting from schema-less (JSON) to schema-typed (PDX) is hard. Perhaps we should explore fuzzy matching or type supersets to better JSON into Geode. Anthony > On Apr 5, 2017, at 9:42 AM, Michael Stolz wrote: > > There's nothing to prevent putting the same object into

Build failed in Jenkins: Geode-nightly #798

See Changes: [klund] GEODE-2748: fix xmlns to specify javaee instead of j2ee [klund] GEODE-2749: ignore bin/ and out/ which are commonly created by IDEs [khowe] GEODE-2420: Add classes to estimated the size of

[DISCUSS] security threats (was Re: [CVE-2017-5649] Apache Geode information disclosure vulnerability)

As a follow up to this CVE, I wanted to share the process for reporting and responding to security issues: https://www.apache.org/security/ https://www.apache.org/security/committers.html Here’s the short version: - Report the vulnerability privately (secur...@apache.org |

Re: Global PDX Types -> Move to Region Level?

There's nothing to prevent putting the same object into multiple regions. The type catalog for a database shouldn't be relative to a table. It should be database wide. The real problem in this case is the proliferation of PDX Types caused by using JSON documents that have only some of their

[jira] [Commented] (GEODE-2736) Native client thread pool get stuck sometimes during rolling restart

[ https://issues.apache.org/jira/browse/GEODE-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957192#comment-15957192 ] ASF GitHub Bot commented on GEODE-2736: --- Github user asfgit closed the pull request at:

[jira] [Commented] (GEODE-2736) Native client thread pool get stuck sometimes during rolling restart

[ https://issues.apache.org/jira/browse/GEODE-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957190#comment-15957190 ] ASF subversion and git services commented on GEODE-2736: Commit

[GitHub] geode-native pull request #82: GEODE-2736: Fixed orphaned worker threads

Github user asfgit closed the pull request at: https://github.com/apache/geode-native/pull/82 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Commented] (GEODE-2713) Function execution can lead to passing the address of a stack variable

[ https://issues.apache.org/jira/browse/GEODE-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957178#comment-15957178 ] ASF GitHub Bot commented on GEODE-2713: --- Github user asfgit closed the pull request at:

[jira] [Commented] (GEODE-2713) Function execution can lead to passing the address of a stack variable

[ https://issues.apache.org/jira/browse/GEODE-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957177#comment-15957177 ] ASF subversion and git services commented on GEODE-2713: Commit

[GitHub] geode-native pull request #74: GEODE-2713: Wrap result collector lock in sha...

Github user asfgit closed the pull request at: https://github.com/apache/geode-native/pull/74 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Commented] (GEODE-2751) UniversalMembershipListenerAdapterDUnitTest.testSystemClientEventsInServer fails on Jenkins

[ https://issues.apache.org/jira/browse/GEODE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957176#comment-15957176 ] ASF subversion and git services commented on GEODE-2751: Commit

[jira] [Created] (GEODE-2754) CI failure: WanAutoDiscoveryDUnitTest

Bruce Schuchardt created GEODE-2754: --- Summary: CI failure: WanAutoDiscoveryDUnitTest Key: GEODE-2754 URL: https://issues.apache.org/jira/browse/GEODE-2754 Project: Geode Issue Type: Bug

[jira] [Commented] (GEODE-2736) Native client thread pool get stuck sometimes during rolling restart

[ https://issues.apache.org/jira/browse/GEODE-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957000#comment-15957000 ] ASF GitHub Bot commented on GEODE-2736: --- Github user echobravopapa commented on a diff in the pull

[GitHub] geode-native pull request #82: GEODE-2736: Fixed orphaned worker threads

Github user echobravopapa commented on a diff in the pull request: https://github.com/apache/geode-native/pull/82#discussion_r109942702 --- Diff: src/cppcache/integration-test/testThinClientPoolExecuteFunctionThrowsException.cpp --- @@ -303,6 +303,7 @@

Re: Review Request 58158: GEODE-2749: ignore bin/ and out/ which are commonly created by IDEs

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58158/#review171122 --- -1 There are several bin/ dirs with source files: ```

[jira] [Commented] (GEODE-2726) Add Packer Build Files for VS 2017

[ https://issues.apache.org/jira/browse/GEODE-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956882#comment-15956882 ] ASF GitHub Bot commented on GEODE-2726: --- Github user mmartell closed the pull request at:

[GitHub] geode-native pull request #76: GEODE-2726: Add Packer Build Files for VS 201...

Github user mmartell closed the pull request at: https://github.com/apache/geode-native/pull/76 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: Global PDX Types -> Move to Region Level?

I do not know about the negative impact but could you elaborate about the DLock? thx. On Fri, Mar 31, 2017 at 7:48 PM, Real Wes wrote: > > Would there be a negative impact in moving PDXType’s to the region level > instead of the cache level? On the positive side, when