add upgrade instructions for Payara 5 to 6#9774
Conversation
pdurbin
left a comment
There was a problem hiding this comment.
@donsizemore your edits look great. I added a few more questions and suggestions.
|
Issues found: [x] 1. You should add some additional detail saying add jvm-options to 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: Before deploying war file [x] 3. App doesn't load, returns 503 error: 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: |
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.