JMS problems when running locally

[edburns]

When running locally using the steps in Appendix 3 of the README the JMS integration shows these errors:

[INFO] [WARNING ] CNTR4016W: The message endpoint for the RejectedRegistrationAttemptsConsumer message-driven bean cannot be activated because the java:app/jms/RejectedRegistrationAttemptsQueue destination is not available. The message endpoint will not receive messages until the destination becomes available.
[INFO] [WARNING ] CNTR4016W: The message endpoint for the MisdirectedCargoConsumer message-driven bean cannot be activated because the java:app/jms/MisdirectedCargoQueue destination is not available. The message endpoint will not receive messages until the destination becomes available.
[INFO] [WARNING ] CNTR4016W: The message endpoint for the DeliveredCargoConsumer message-driven bean cannot be activated because the java:app/jms/DeliveredCargoQueue destination is not available. The message endpoint will not receive messages until the destination becomes available.
[INFO] [WARNING ] CNTR4016W: The message endpoint for the CargoHandledConsumer message-driven bean cannot be activated because the java:app/jms/CargoHandledQueue destination is not available. The message endpoint will not receive messages until the destination becomes available.
[INFO] [WARNING ] CNTR4016W: The message endpoint for the HandlingEventRegistrationAttemptConsumer message-driven bean cannot be activated because the java:app/jms/HandlingEventRegistrationAttemptQueue destination is not available. The message endpoint will not receive messages until the destination becomes available.

The assignee of this issue is asked to fix these errors.

[edburns]

Will compare and contrast output from https://github.com/azure-javaee/cargotracker-liberty-aks/actions/runs/11562412567 .

[backwind1233]

I got the same issue within the aks cluster, so it's not just a local running issue.

[backwind1233]

I got the same warning when running https://github.com/eclipse-ee4j/cargotracker/ with openliberty

[backwind1233]

In this case, we should define jms JNDI with global names instead of app level names.