You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Pulkit Chandra (Jira)" <ji...@apache.org> on 2020/02/04 14:27:00 UTC

[jira] [Comment Edited] (GEODE-7200) Geode should not try to prefill any declared Pool (e.g. DEFAULT, or otherwise) if a client is running in a local-only capacity

    [ https://issues.apache.org/jira/browse/GEODE-7200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029877#comment-17029877 ] 

Pulkit Chandra edited comment on GEODE-7200 at 2/4/20 2:26 PM:
---------------------------------------------------------------

Current output: Currently when you run Spring Boot application locally, we get an exception "{color:#1d1c1d}could not connect to: localhost:40404{color}" even though the app is running fine

Expected Output : We should not be getting this exception at all unless the app is failing


was (Author: pchandra):
Current output: Currently when you run Spring Boot application locally, we get an exception "{color:#1d1c1d}could not connect to: localhost:40404{color}".

Expected Output : Spring boot app successfully runs and connects.

> Geode should not try to prefill any declared Pool (e.g. DEFAULT, or otherwise) if a client is running in a local-only capacity
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-7200
>                 URL: https://issues.apache.org/jira/browse/GEODE-7200
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: John Blum
>            Priority: Major
>              Labels: affects-spring
>
> See https://github.com/spring-projects/spring-boot-data-geode/issues/53 for more details.
> This really client-only and not the traditional client/server topology, which is a very valid and useful client arrangement.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)