osdir.com

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error communication to Eureka


Hi Markus,

I am not using demo server. I am running each microservice separately for
production as required by the GSoC project.
Here is the yaml file for the Eureka server:

server:
  port: 8761
eureka:
  client:
    register-with-eureka: false
    fetch-registry: false
  server:
    enable-self-preservation: false


Thanks,
Courage.

On Mon, Jun 25, 2018 at 7:53 PM Markus Geiss <mage@xxxxxxxxxx> wrote:

> Hey Courage,
>
> can you share the settings in the application.yml file that points to
> eureka.
>
> Seems like there is a mismatch in the configuration, but to be sure it
> woulde be good to see the see the config.
>
> In addition I'm not 100% sure if TestEnvironment used by the demo server is
> overriding this.
>
> Cheers
>
> Markus
>
> On Mon, Jun 25, 2018, 20:40 Courage Angeh <courageangeh@xxxxxxxxx> wrote:
>
> > Hi Alek,
> >
> > Hope this message reaches you well.
> > I know you have have been working on setting up Fineract CN on demo
> server
> > and you are using Docker.
> > I am facing alittle problem with the communication between a
> containerized
> > Eureka server and a containerized Fineract microservice.
> > Here is the link to the error that I get, https://pastebin.com/UgQZhmSt
> >
> > Here is the section of my docker-compose file that configures the Eureka
> > server.
> >
> > eureka:
> > build: ../eureka_server
> > container_name: eureka
> > ports:
> > - "8761:8761"
> > networks:
> > app_net:
> > ipv4_address: 172.16.238.2
> >
> >
> > I will appreciate your help. Or that of anyone who can help.
> >
> > Thanks,
> > Courage
> >
>