felixif
commented
1 year ago Hello @cidylong,
I have tested the issue on a VM as similar to your setup as possible (Rocky Linux 9.2 and Oracle JDK 17.0.6), and I managed to reproduce the issue using your reproducer easily. I have escalated the issue (FISH-7761) to the engineering team, who is going to deal with the issue in due course. Also, thank you for bringing to my attention Rocky Linux! I've read about the CentOS situation and it seems like a very cool open-source project to keep enterprise-level Linux free for everyone.
Best regards, Felix
Brief Summary
Payara 6.2023.8 fish.payara.notification.jms.JmsNotifierService is trying to lookup 'jms/_defaultConnectionFactory' in SerialContext. but it is not existing.
The correct jms lookup JNDI name will be "jms/__defaultConnectionFactory".
Expected Outcome
fish.payara.notification.jms.JmsNotifierService should lookup defaultConnectFactory by name "jms/__defaultConnectionFactory" instead of 'jms/_defaultConnectionFactory'
Please note: one underscore missed in code.
Current Outcome
SEVERE error thrown and DAS server not start properly, NO AdminUI shows
Reproducer
Add some jms notifier service resource and add it to newly created payara instance.
Restart all payara instances and domain. Payara will try to lookup defaultConnectFactory. SEVERE error thrown and DAS server not start properly(NO AdminUI shows).
Compare with error message by run: $PAYARA_HOME/glassfish/lib/nadmin --passwordfile list-resource-refs .......... jms/__defaultConnectionFactory .......... Command list-resource-refs executed successfully.
That means, fish.payara.notification.jms.JmsNotifierService lookup defaultConnectionFactory by using wrong JNDI name
Operating System
Rocky Linux 9
JDK Version
Oracle JDK 17.0.6
Payara Distribution
Payara Server Full Profile