Bug Report: JmsNotifierService trying lookup 'jms/_defaultConnectionFactory' (is not existing) #6368
Labels
Status: Accepted
Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev
Type: Bug
Label issue as a bug defect
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
The text was updated successfully, but these errors were encountered: