+1 for looking into the mP health check API.
In fact, I don't even think that Hibernate would have to implement any sort
of looping itself. Instead, the orchestration layer would check the health
check endpoint and automatically restart the service if it's not in a
healthy state. That way, the ord
Hi Sanne,
whatever you consider to implement in Hibernate ORM/Search/OMG
I think you should use/follow the MicroProfile Health spec [1].
As far as I know WildFly Swarm supports already this spec.
Best regards,
Andrej Golovnin
[1] https://github.com/eclipse/microprofile-health/
> On 31. May 2018
See inline
On 06/01/2018 03:00 AM, Yoann Rodiere wrote:
>> We could do it via the Statistics mechanism which can be made available
> via
> JMX.
>
> >From what I understand it would be an explicit call from the user
> (OpenShift in this case) that would trigger an active check, like a request
> to
This ties to the lazy database discovery in Cloud environments. The
issue related to that also mentions a health check API.
I don't think it ties to the Stats or JMX API as at least for the
initial start, this API should be able to provide feedback while
Hibernate engine is starting (and looping).
> We could do it via the Statistics mechanism which can be made available
via
JMX.
>From what I understand it would be an explicit call from the user
(OpenShift in this case) that would trigger an active check, like a request
to the database. Not sure the statistics are the best place to put such
