I managed to overcome this problem myself.
I think it was caused by following value in Dockerfile:
rhythm.beatCheckRate=10
When I replaced it with
rhythm.beatCheckRate=60
the problem disappeared.
Juhan
Kontakt Juhan Aasaru () kirjutas kuupäeval K, 18.
september 2019 kell 14:18:
> Hi!
>
>
Hi!
Sorry about the late reply.
1. In my opinion it is not question about provisioning as as soon as the
rhythym application starts up, it tries to select from khepri_beats (see
logs below).
I'm not using demo server at all. I use Postman scripts for provisioning. I
wonder if I should run some
Thanks for the update,
1. For the error below, I believe that is because you didn't provision the
microservices. Can you please confirm if you set
-Ddemoserver.provision=true on the first run. Also, you can use
Hi Graham and Isaac!
Great progress and excellent work regarding Postgresql and EclipseLink
migration!
I did some tests (using the official docker images I'm working on). This is
what I found
1. Rhythm keeps giving me this error:
rhythm-ms_1 | Internal Exception:
Thank you for the update.
I will resolve the conflicts on the notification service and revert to you.
On Mon, 2 Sep 2019, 03:52 Isaac Kamga, wrote:
> Hello Graham,
>
> That's some very good work you've done so far.
>
> I have executed the script and everything works well on my end right
>
Hello Graham,
That's some very good work you've done so far.
I have executed the script and everything works well on my end right
through to the fims-web-app.
EclipseLink configurations was merged into PostgreSQL library last week and
the changes to fineract-cn-test library on FINCN-114 which
Good work Graham,
Has anyone been able to test Graham's work?
When can we have this merged into develop ? so we can make a release
Fineract CN v1 before December 2019
On Sun, Aug 25, 2019 at 2:43 PM Ebenezer Graham
wrote:
> Hello Devs,
>
> I would like to revive the topic discussed in the
Hello Devs,
I would like to revive the topic discussed in the previous mail.
I have been running Fineract CN on EclipseLink and PostgreSQL for a
while now and I believe it's ready to be merged into the develop branches.
But before that, it is paramount that other experienced developers in the
