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
7112 payara5 aio #7114
7112 payara5 aio #7114
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.
I didn't test this but it looks good to me. Assuming it works, it probably makes sense to get this in Dataverse 5 since the biggest change is the move to Payara.
|
||
if [ ! -e dv/deps/payara-5.2020.2.zip ]; then | ||
echo "payara dependency prep" | ||
# no more fiddly patching :) |
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.
Hooray! 🎉
# yeah - still not happy if glassfish isn't in /usr/local :< | ||
RUN ln -s /opt/glassfish4 /usr/local/glassfish4 | ||
# keeping the symlink on the off chance that something else is still assuming /usr/local/glassfish4 | ||
RUN ln -s /opt/payara5 /usr/local/glassfish4 |
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 assume it's safe to not create this symlink. But it doesn't hurt to leave it in. I'm glad the comment was updated to described what's going on.
Found that this does not work on a fresh system due to absence of glassfish-setup.sh ; was accidentally working on a dev system that still had a cached copy. |
It's still there but it was renamed to as-setup.sh. |
updated and re-tested |
@pdurbin sorry about that - thanks for catching it! |
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.
Looking good. I see Payara, as expected:
$ curl -i http://localhost:8083/api/info/version
HTTP/1.1 200 OK
Server: Payara Server 5.2020.2 #badassfish
X-Powered-By: Servlet/4.0 JSP/2.3 (Payara Server 5.2020.2 #badassfish Java/Oracle Corporation/1.8)
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: PUT, GET, POST, DELETE, OPTIONS
Access-Control-Allow-Headers: Content-Type, X-Dataverse-Key
Content-Type: application/json;charset=UTF-8
Content-Length: 78
X-Frame-Options: SAMEORIGIN
{"status":"OK","data":{"version":"4.20","build":"7112-payara5_aio-5a77f49f7"}}
What this PR does / why we need it:
switch docker-aio from glassfish to payara
Which issue(s) this PR closes:
Closes #7112
Special notes for your reviewer:
Deferred testing of / changes related to new install script (despite describing it as analogous to an issues that explicitly included testing the new installer); focused on API test suite.
Suggestions on how to test this:
Existing instructions for docker-aio should work unchanged; Server header from
curl -i http://localhost:8083/api/info/version
should report payaraDoes this PR introduce a user interface change? If mockups are available, please link/include them here:
nope
Is there a release notes update needed for this change?:
nope
Additional documentation:
should be none necessary