Hi Domenico Unfortunately your proposal does not work in our case. It seems that the error handling of a missing JDBC connection is different and is not done by the critical analyzer
Regards REto -----Ursprüngliche Nachricht----- Von: Domenico Francesco Bruscino <[email protected]> Gesendet: Mittwoch, 20. März 2024 14:56 An: [email protected] 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. <critical-analyzer-policy>HALT</critical-analyzer-policy> Regards, Domenico On Wed, 20 Mar 2024 at 12:17, Urfer Reto <[email protected]> wrote: > 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) instead of 1 (FAILURE). Therefore docker-compose does not > restart the artemis container though we have defined the restart > policy to restart the container in case of failure. > > Is there any way to tell artemis to exit with a failure exit code in > case it detects a fatal error like not getting a JDBC connection? > > Regards > Reto > > ---------------------------- > Profidata AG > Reto Urfer > Senior Software Engineer > > Bändliweg 30 > 8048 Zürich > Switzerland > +41 44 736 47 47 > [email protected]<mailto:[email protected]> > www.profidata.com<http://www.profidata.com/> > ---------------------------- > Profidata Group > Investment Management Solutions > ---------------------------- > > CONFIDENTIALITY NOTICE: If you are > not the intended recipient, please notify the sender immediately and > delete this e-mail. > Notice concerning e-mail data protection< > https://www.profidatagroup.com/disclaimer#e-mail-disclaimer> > >
