then terminates
> with success instead of failure which can then not be detected by restart
> handlers of container administration tools like docker-compose, podman,
> Kubernetes, etc.
>
>
> -Ursprüngliche Nachricht-
> Von: Clebert Suconic
> Gesendet: Samstag, 23. März 2
docker-compose, podman, Kubernetes, etc.
-Ursprüngliche Nachricht-
Von: Clebert Suconic
Gesendet: Samstag, 23. März 2024 23:05
An: users@activemq.apache.org
Betreff: Re: Exit code in case of failure
It’s not the critical analyzer. It’s the critical IO Error
An IO exception happened
s not done
> by
> > the critical analyzer
> >
> > Regards
> > REto
> >
> > -Ursprüngliche Nachricht-
> > Von: Domenico Francesco Bruscino
> > Gesendet: Mittwoch, 20. März 2024 14:56
> > An: users@activemq.apache.org
> > Betreff
ifferent and is not done by
> the critical analyzer
>
> Regards
> REto
>
> -Ursprüngliche Nachricht-
> Von: Domenico Francesco Bruscino
> Gesendet: Mittwoch, 20. März 2024 14:56
> An: users@activemq.apache.org
> Betreff: Re: Exit code in case of failure
&
2024 14:56
An: users@activemq.apache.org
Betreff: Re: Exit code in case of failure
Hi Reto,
you could use use the HALT critical analyzer policy to force artemis to exit
with the exit code 70, i.e.
HALT
Regards,
Domenico
On Wed, 20 Mar 2024 at 12:17, Urfer Reto wrote:
> Hi
>
> We
Hi Reto,
you could use use the HALT critical analyzer policy to force artemis to
exit with the exit code 70, i.e.
HALT
Regards,
Domenico
On Wed, 20 Mar 2024 at 12:17, Urfer Reto wrote:
> Hi
>
> We are using activemq artemis 2.31.2 as a container managed by
> docker-compose/podman. For persist
Hi
We are using activemq artemis 2.31.2 as a container managed by
docker-compose/podman. For persistence we have to use JDBC. If, for any reason
(eventually a short network unavailablility), artemis fails to get the JDBC
connection it executes a graceful shutdown and exists with 0 (SUCCESS) ins
