CODEWITHSUNDEEP
restjakarta-eeejb-3.1message-driven-bean
Thomas Naskali
Thomas Naskali

Reputation: 581

Health check API for message-driven beans

I'd like to be able to do a health check on a deployed Message-Driven Bean in Production. My initial idea was to add a health() method ensuring that the JMS Queue (for reading) and the Database (for writing) are both available, and then expose this health method as a REST API. Unfortunately as a MDB isn't injectable like the other types of EJBs I cannot get a reference to it from my REST controller...

Is there a way to expose a message-driven bean's methods through a REST API ? Or any other way to achieve my initial goal ?

EDIT

A little precision : I don't want to just check that the resources are available, but also that the EJB can communicate with them (by pinging them from inside the EJB instance). This would not only validate that the resources are available (which could indeed be done some other way), but more importantly for me also that the resources bindings are valid and that the resources injection is working.

Upvotes: 2

Views: 696

Answers (1)

Alexander Rühl
Alexander Rühl

Reputation: 6939

I think it's not possible the way you want to have it. The reason is, that unlike other EJBs, a MDB solely acts upon arrival of a message and not by any other call to it.

But you may do it the other way round and inject some class into the MDB which you call on any message you receive. That way you'd have a constant "I'm alive" ping, provided that you get messages continuously.

Other than that your only chance is to use the mechanisms of your container which usually can provide some information about its deployed and running components which you may query.

Upvotes: 1

Related Questions