opt/payara41/bin/asadmin -u admin -passwordfile /asadmin.txt set-log-attributes .=1440 & \
opt/payara41/bin/asadmin -u admin -passwordfile /asadmin.txt set-log-attributes .=1073741824 & \ opt/payara41/bin/asadmin -u admin -passwordfile /asadmin.txt create-jdbc-resource -connectionpoolid COR99TSPool COR99TSDatasource & \ opt/payara41/bin/asadmin -u admin -passwordfile /asadmin.txt create-jdbc-connection-pool -datasourceclassname -restype -property COR99TSPool & \ RUN /opt/payara41/bin/asadmin start-domain & \ Here is the Dockerfile for reference: FROM payara/server-fullĬOPY. I was developing a vaadin-cdi app (using vaadin for the first time) locally in a Payara server running "inside" Eclipse and everything was working fine.īut when i had a couple of views finished and wanted to test the app on our test environment the Jenkins build failed while building a docker image for the Payara server and the app.ĭuring the Docker image build phase the Payara server is basically started, configured with a couple of asadmin calls and the WAR file is deployed, just like you would if you started a Payara server in a non-Docker environment. I noticed something very strange about the vaadin-cdi addon.
0 kommentar(er)
