Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug Report: JmsNotifierService trying lookup 'jms/_defaultConnectionFactory' (is not existing) #6368

Open
cidylong opened this issue Aug 17, 2023 · 1 comment
Assignees
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

Comments

@cidylong
Copy link

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
Screenshot 2023-08-18 at 9 34 32 am

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

@cidylong cidylong added Status: Open Issue has been triaged by the front-line engineers and is being worked on verification Type: Bug Label issue as a bug defect labels Aug 17, 2023
@felixif
Copy link

felixif commented Aug 28, 2023

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

@felixif felixif added Status: Accepted Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev and removed Status: Open Issue has been triaged by the front-line engineers and is being worked on verification labels Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants