[Created on 12 August, 2020, and updated on 22 January, 2021]
Original post is on Medium.
https://logico-jp.medium.com/using-jms-2-0-apis-to-access-azure-service-bus-9f458ec2bf20
Japanese e...
Thank you for reaching out and sorry for my late reply.
I have no idea to debug this issue happened in your environment. As "catch( Exception e )" is in your code, JMSException and JMSSecurityException should be caught here. Standard output is not properly for debugging, but it does not seem relevant.
# Indeed, if you created dependencies by yourself locally, you would get better information for debugging your code. However, I understand you don't want to do so!
If possible, could you please check if you can access your Service Bus instance with qpid-jms-1.6.0 API? Apache Qpid APIs are used in Service Bus JMS APIs, so if you could access the instance with only Apache Qpid APIs, you might find some hints.
Additionally, I ran cargo tracker app which contained modified JmsApplicationEvents.java and dependencies on Service Bus (com.microsoft.azure.azure-servicebus-jms:0.0.9) on Payara Server 5 (Payara Server 5.2022.1), and I confirmed the app worked fine.