-
Notifications
You must be signed in to change notification settings - Fork 494
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
8947 Update to Payara 5.2022.3 #8949
Conversation
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.
Looks like a find/replace of all instances of 5.2021.6 - except
// of properties can be found at https://docs.payara.fish/community/docs/5.2021.6/documentation/payara-server/jdbc/advanced-connection-pool-properties.html#full-list-of-properties |
|
||
*NOTE: this might be rephrased to "required" depending on https://github.com/IQSS/dataverse/pull/8915 being merged.* | ||
|
||
With lots of bug and security fixes included, we encourage everyone to update to Payara 5.2022.3 as soon as possible. |
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.
I expect others will want to wordsmith the release notes more, but I'll note that we should probably not make this optional - while I think v5.12 will be compatible with earlier versions, after this PR we're not testing that anymore.
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.
I absolutely agree!
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.
Actually that one was on purpose. The docs links changed upstream and I was really hoping for #8915 being merged as it is fairly small and helps people. That PR is already updating this place. |
I'm pulling this out of QA and assigning it to @poikilotherm because he offered to document the extra steps around I assume this should go in the guides? I found a few related references:
There's also stuff in "scripts":
@PaulBoon thanks for pinging us about this. |
0cd17e8
to
3a67df6
Compare
@pdurbin @qqmyers @donsizemore I added the notes and modifications regarding #8230. Please take a look. |
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.
I added a suggestion.
@poikilotherm thanks for the updates. At standup we talked about how next we need someone to review this so I unassigned you. On a related note, @donsizemore is testing with Ansible. Thanks, Don! |
6167940
to
f2ddc04
Compare
With the update to a Payara version past 5.2021.8, the `lib/databases` folder needs to be removed by scripts etc (as with osgi-cache and generated folders) during rebuild/upgrade of a domain to avoid incompatibilities. See also: IQSS#8230
f2ddc04
to
46f6066
Compare
I'm sorry but I had to force push this after rebasing on latest |
3. Move the current Payara directory out of the way | ||
|
||
```shell | ||
mv $PAYARA $PAYARA.MOVED |
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.
Where does PAYARA.MOVED get set/exported?
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.
Oh this was just copy-pasta from the v5.6 instructions.
The shell expansion will stop at the ".", so if $PAYARA
is "x", it'll be "x.MOVED".
With the merge of IQSS#8949 the custom version is no longer necessary.
What this PR does / why we need it:
Upgrade to Payara 5.2022.3. Security and bug fixing.
Which issue(s) this PR closes:
Closes #8947
Closes IQSS/dataverse-security#66
Special notes for your reviewer:
None.
Suggestions on how to test this:
Follow instructions. @donsizemore says to check for greatly increased logging when using S3 (#8219). We might need to document how to lower the logging level.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
None.
Is there a release notes update needed for this change?:
Yes. 🔋 included.
Additional documentation:
None.