-
Notifications
You must be signed in to change notification settings - Fork 492
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
Upgrade to Payara 6.2024.6 #10495
Merged
Merged
Upgrade to Payara 6.2024.6 #10495
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
2a4e380
refactor(ct): remove workaround for FISH-7722 from base image
poikilotherm 18fd8ec
fix(ct): re-align payara-api package with upstream BOM
poikilotherm 56e2f9c
docs: fix link to Payara docs to not include a version
poikilotherm f7b6d94
docs: update to reference Payara 6.2024.4 as requirement
poikilotherm b061b91
build: upgrade to Payara 6.2024.4 #10494
poikilotherm 76a9ef3
build: remove phased out Payara dependency repo on GitHub
poikilotherm 77a5c41
refactor(install): remove workaround for FISH-7722
poikilotherm 222b326
doc(deps): add release note about Payara upgrade #10494
poikilotherm 081f141
Merge branch 'develop' into 10494-payara-6.2024.4
poikilotherm c1d581e
build,doc: update with Payara 6.2024.6 release
poikilotherm 7dd1f05
refactor: remove stale property for Jakarta EE API version
poikilotherm 10b63fe
doc: add upgrade instructions for Payara 6.2024.6 #10494
poikilotherm 65b2dcb
Update 10494-payara-upgrade.md
landreev 7b7f2e3
Update 10494-payara-upgrade.md
landreev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,119 @@ | ||
# Upgrade Payara to v6.2024.6 | ||
|
||
With this version of Dataverse, we encourage you to upgrade to version 6.2024.6. | ||
This will address security issues accumulated since the release of 6.2023.8, which was required since Dataverse release 6.0. | ||
|
||
## Instructions for Upgrading | ||
|
||
If you are using GDCC containers, this upgrade is included when pulling new release images. | ||
No manual intervention is necessary. | ||
|
||
We recommend you ensure you followed all update instructions from the past releases regarding Payara. | ||
(Latest Payara update was for [v6.0](https://github.com/IQSS/dataverse/releases/tag/v6.0)) | ||
|
||
Upgrading requires a maintenance window and downtime. Please plan ahead, create backups of your database, etc. | ||
|
||
The steps below are a simple matter of reusing your existing domain directory with the new distribution. | ||
But we also recommend that you review the Payara upgrade instructions as it could be helpful during any troubleshooting: | ||
[Payara Release Notes](https://docs.payara.fish/community/docs/Release%20Notes/Release%20Notes%206.2024.6.html) | ||
We assume you are already on a Dataverse 6.x installation, using a Payara 6.x release. | ||
|
||
```shell | ||
export PAYARA=/usr/local/payara6 | ||
``` | ||
|
||
(or `setenv PAYARA /usr/local/payara6` if you are using a `csh`-like shell) | ||
|
||
1\. Undeploy the previous version | ||
|
||
```shell | ||
$PAYARA/bin/asadmin list-applications | ||
$PAYARA/bin/asadmin undeploy dataverse<-version> | ||
``` | ||
|
||
2\. Stop Payara | ||
|
||
```shell | ||
service payara stop | ||
rm -rf $PAYARA/glassfish/domains/domain1/generated | ||
rm -rf $PAYARA/glassfish/domains/domain1/osgi-cache | ||
rm -rf $PAYARA/glassfish/domains/domain1/lib/databases | ||
``` | ||
|
||
3\. Move the current Payara directory out of the way | ||
|
||
```shell | ||
mv $PAYARA $PAYARA.MOVED | ||
``` | ||
|
||
4\. Download the new Payara version (6.2024.6), and unzip it in its place | ||
|
||
5\. Replace the brand new payara/glassfish/domains/domain1 with your old, preserved domain1 | ||
|
||
6\. Make sure that you have the following `--add-opens` options in your domain.xml. If not present, add them: | ||
poikilotherm marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
```diff | ||
--- payara-6.2023.8/glassfish/domains/domain1/config/domain.xml | ||
+++ payara-6.2024.6/glassfish/domains/domain1/config/domain.xml | ||
@@ -212,12 +212,16 @@ | ||
<jvm-options>--add-opens=java.naming/javax.naming.spi=ALL-UNNAMED</jvm-options> | ||
<jvm-options>--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED</jvm-options> | ||
<jvm-options>--add-opens=java.logging/java.util.logging=ALL-UNNAMED</jvm-options> | ||
+ <jvm-options>--add-opens=java.management/javax.management=ALL-UNNAMED</jvm-options> | ||
+ <jvm-options>--add-opens=java.management/javax.management.openmbean=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-exports=java.base/sun.net.www=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-exports=java.base/sun.security.util=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-opens=java.base/java.lang.invoke=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-opens=java.desktop/java.beans=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED</jvm-options> | ||
+ <jvm-options>[17|]--add-opens=java.base/java.io=ALL-UNNAMED</jvm-options> | ||
+ <jvm-options>[21|]--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED</jvm-options> | ||
<jvm-options>-Xmx512m</jvm-options> | ||
<jvm-options>-XX:NewRatio=2</jvm-options> | ||
<jvm-options>-XX:+UnlockDiagnosticVMOptions</jvm-options> | ||
@@ -447,12 +451,16 @@ | ||
<jvm-options>--add-opens=java.naming/javax.naming.spi=ALL-UNNAMED</jvm-options> | ||
<jvm-options>--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED</jvm-options> | ||
<jvm-options>--add-opens=java.logging/java.util.logging=ALL-UNNAMED</jvm-options> | ||
+ <jvm-options>--add-opens=java.management/javax.management=ALL-UNNAMED</jvm-options> | ||
+ <jvm-options>--add-opens=java.management/javax.management.openmbean=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-exports=java.base/sun.net.www=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-exports=java.base/sun.security.util=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-opens=java.base/java.lang.invoke=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-opens=java.desktop/java.beans=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED</jvm-options> | ||
+ <jvm-options>[17|]--add-opens=java.base/java.io=ALL-UNNAMED</jvm-options> | ||
+ <jvm-options>[21|]--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED</jvm-options> | ||
<jvm-options>-Xmx512m</jvm-options> | ||
<jvm-options>-XX:NewRatio=2</jvm-options> | ||
<jvm-options>-XX:+UnlockDiagnosticVMOptions</jvm-options> | ||
``` | ||
(You can also save this as a patch file and try to apply it.) | ||
|
||
TODO: For the combined 6.3 release note, I would consider replacing the patch format above with just the 4 specific options, for clarity etc. (L.A.) As in: | ||
``` | ||
<jvm-options>--add-opens=java.management/javax.management=ALL-UNNAMED</jvm-options> | ||
<jvm-options>--add-opens=java.management/javax.management.openmbean=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[17|]--add-opens=java.base/java.io=ALL-UNNAMED</jvm-options> | ||
<jvm-options>[21|]--add-opens=java.base/jdk.internal.misc=ALL-UNNAMED</jvm-options> | ||
``` | ||
|
||
7\. Start Payara | ||
|
||
```shell | ||
service payara start | ||
``` | ||
|
||
8\. Deploy this version. | ||
|
||
```shell | ||
$PAYARA/bin/asadmin deploy dataverse-6.3.war | ||
``` | ||
|
||
9\. Restart payara | ||
|
||
```shell | ||
service payara stop | ||
service payara start |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Should note that the release instructions need to add the standard Payara update steps. With this one, I think copying the domain works fine, i.e. like the instructions for Dataverse 5.6 rather than from our 5->6 transition.
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.
As requested, I added the instructions. Feel free to take a look.