Skip to content

Comments

add upgrade instructions for Payara 5 to 6#9774

Merged
kcondon merged 12 commits intodevelopfrom
9340-payara5to6
Aug 22, 2023
Merged

add upgrade instructions for Payara 5 to 6#9774
kcondon merged 12 commits intodevelopfrom
9340-payara5to6

Conversation

@pdurbin
Copy link
Member

@pdurbin pdurbin commented Aug 11, 2023

What this PR does / why we need it:

Dataverse installations will need to upgrade from Payara 5 to 6.

Which issue(s) this PR closes:

Special notes for your reviewer:

I tested this on https://dev1.dataverse.org and it seemed to work.

Suggestions on how to test this:

Try the instructions.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No.

Is there a release notes update needed for this change?:

It is a release note.

Additional documentation:

None.

@pdurbin pdurbin added this to the 6.0 milestone Aug 11, 2023
@pdurbin pdurbin assigned pdurbin and unassigned pdurbin Aug 14, 2023
Copy link
Member Author

@pdurbin pdurbin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@donsizemore your edits look great. I added a few more questions and suggestions.

@coveralls
Copy link

coveralls commented Aug 18, 2023

Coverage Status

coverage: 20.37%. remained the same when pulling b894e6d on 9340-payara5to6 into 45a3936 on develop.

@donsizemore donsizemore removed their assignment Aug 18, 2023
@kcondon kcondon self-assigned this Aug 21, 2023
@kcondon
Copy link
Contributor

kcondon commented Aug 21, 2023

Issues found:
[x] 0. When copying p6 domain.xml to domain.xml.ORIG, leaves file owned by root in p6 structure.
sudo cp /usr/local/payara6/glassfish/domains/domain1/config/domain.xml /usr/local/payara6/glassfish/domains/domain1/config/domain.xml.orig

[x] 1. You should add some additional detail saying add jvm-options to <java-config...> section under <configs><config name="server-config"> as opposed to <config name="default-config"...

The Xmx value should also go in the same server-config section.

If in addition to the above detail you want to include an example domain.xml/skeleton, that's fine

[x] 2. Need to specify the workaround, otherwise war file will fail to deploy:
asadmin create-jvm-options --add-opens=java.base/java.io=ALL-UNNAMED
asadmin restart-domain

Before deploying war file

[x] 3. App doesn't load, returns 503 error:
503_on_deploy_after_upgrade.txt

This is a result of the apache proxy, it works when going directly to port 8080. Is there something apache related we need to include? I restarted httpd but it made no difference.

I see, it is probably the next to last step, jk-connector. It is a little confusing that the app isn't accessible on port 80 once deployed.

[x] 4. Might want to put the two "restart" commands on separate lines (start/stop) or just use restart.

[x] 5. Upgrade fails smoketest:
-Remains on create user page, throws server.log error but does create user:
create_usr_err_upgrade.txt
-Can't create dataverse, same ejb log error as create user but shows create ejb err in ui, leaves on create dv page. Also does create dv,

@kcondon kcondon assigned pdurbin and unassigned kcondon Aug 21, 2023
@kcondon kcondon merged commit d14a54c into develop Aug 22, 2023
@kcondon kcondon deleted the 9340-payara5to6 branch August 22, 2023 21:11
@pdurbin pdurbin removed their assignment Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

determine upgrade path from Payara 5 to 6

4 participants