-
Notifications
You must be signed in to change notification settings - Fork 306
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
FISH-773 Fix EJB Scheduler / ApplicationID in TIMER_TBL #5406
Conversation
Hi @alexk201 Thank you for the PR! We're happy to receive your contribution, however, before we can proceed you will need to sign the CLA and send it to us. Regards |
Oh yeah sorry, just sent it over... |
Thanks CLA has been received |
Jenkins test please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
FISH-773 Fix EJB Scheduler / ApplicationID in TIMER_TBL
FISH-773 Fix EJB Scheduler / ApplicationID in TIMER_TBL
Description
Fixed the EJB timer bug introduced in #3b2dd29 / reported in #4650. We've manually patched the 'ejb-container' and 'payara-micro-service' module since Payara version 5.201 and it seems to be working very well.
Testing
Testing Performed
Manually deployed a sample application using persistent EJB timers. Performed multiple redeployments to see if the application id is preserved and the timers get removed:
1st redeploy
2nd redeploy
Testing Environment
Zulu JDK 1.8.0_302 on Windows 10 with Maven 3.8.1