-
Notifications
You must be signed in to change notification settings - Fork 307
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: EJB Timer Service is not available? / FISH-7815 #6381
Comments
@cidylong You are mixing CDI and EJB annotations with your provided code example class. Please remove the ApplicationScoped annotation and try again. |
@svendiedrichsen , Thank you for your advice, ApplicationScoped removed, re-compile, re-deploy it, failed again, same error. "EJB Timer Service is not available" |
@svendiedrichsen , from server log, we can see:
EclipseLink, version: Eclipse Persistence Services - 4.0.1.payara-p1.v202304041433]] seems EJB Time service is fine, very confused. |
@cidylong I don't know about how to configure the timer service. I have always used the default configured one. |
Please help on this issue anyone if you have an idea? this is quite important for regular application. |
Hi @cidylong, I have been able to reproduce this issue and have raised |
@kalinchan, When the bug will be fixed or which version expected? |
Brief Summary
Create an EJB module (jar), deploy it to a payara service instance, payara server throws:
"remote failure: Error occurred during deployment: Failed to create automatic timers for ThssAppScheduler -- EJB Timer Service is not available. Please see server.log for more details.
Command deploy failed."
Expected Outcome
EJB timer should works fine
Current Outcome
"remote failure: Error occurred during deployment: Failed to create automatic timers for ThssAppScheduler -- EJB Timer Service is not available. Please see server.log for more details.
Command deploy failed."
Reproducer
Develop a simple EJB module with maven build by NetBeans -18
compile and deploy it to payara server instance result as:
server log as:
server_293.log
tired to configure payara server instance by add-opens and checked payara server instance configure, seems --add-opens is fine,
tried to re-configure payara-executor-service-configuration as well. configure as:
restart-domain and redeploy it to server instance.
There is nothing changed, same error.
Operating System
Rocky Linux 9
JDK Version
Oracle JDK 17.0.7
Payara Distribution
Payara Server Full Profile
The text was updated successfully, but these errors were encountered: