Application not being auto deployed - Docker - Payara Server 5.2021.6 - Application not being deployed

1,294 views

Skip to first unread message

Clifton Mtengezo

unread,

Aug 20, 2021, 9:39:50 AM8/20/21

to Payara Forum

1. I have created a docker image from a Dockerfile as below:

FROM payara/server-full

COPY bwbportal.war $DEPLOY_DIR

RUN echo 'healthcheck-configure --dynamic=true --enabled=true'

2. I have created a Docker image as below:

docker build -t bwbportal .

I am running this command from a folder that has the following contents:

D:\dockerdeploy>dir

Volume in drive D is DATADRIVE1

Volume Serial Number is 103C-0289

Directory of D:\dockerdeploy

19/08/2021 02:35 pm <DIR> .

19/08/2021 02:35 pm <DIR> ..

03/01/2019 09:35 am 24,827,324 bwbportal.war

20/08/2021 01:24 pm 143 Dockerfile

2 File(s) 24,827,467 bytes

2 Dir(s) 719,423,074,304 bytes free

3. Then I am running the following command to create the container:

D:\>docker run -i --rm --name bwbportal -p 54848:4848 -p 58080:8080 -p 58181:8181 -- bwbportal

4. Container is starting ok. But when I check the list of deployed applications, the application (bwbportal) is not there.

QUESTIONS:

a. How can I troubleshoot to find out why the application is not being autodeployed.

b. Advise where I am going wrong and how I can make the application to autodeploy.

I am new to working with Docker and Payara. Sorry for my ignorance.

Regards

Clifton

Gregor Kovač

unread,

Aug 20, 2021, 9:52:41 AM8/20/21

to Clifton Mtengezo, Payara Forum

Hi!

I'm not sure about the Docker image, but if you go to admin console - Domain - Applications Configuration, there are Auto Deploy settings and you can turn on or off auto deploy. Maybe in the image the auto deploy is turned off.

Best regards,

Gregor

Clifton Mtengezo je 20. 08. 21 ob 15:39 napisal:

--
You received this message because you are subscribed to the Google Groups "Payara Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to payara-forum...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/payara-forum/5a0884bb-b202-4adc-9586-28d30441215en%40googlegroups.com.

-- 
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
|  In A World Without Fences Who Needs Gates?  |
|              Experience Linux.               |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~

Clifton Mtengezo

unread,

Aug 20, 2021, 1:14:13 PM8/20/21

to Payara Forum

Gregor,

Thank you for pointing me in the right direction.

1. Autodeploy is enabled.

2. When I put my application in the folder specified in the autodeploy directory, ${com.sun.aas.instanceRoot}/autodeploy the application is being autodeployed.

3. However, according to the document "Using-Payara-Server-With-Docker" downloaded at https://info.payara.fish/using-payara-server-with-docker-guide and also this link https://blog.payara.fish/flexibility-first-payara-docker-images-allow-a-completely-custom-start-up-configuration, which state that "running the container produced from this image will also deploy the application on startup", the options stated I am not able to make payara auto deploy the applicaion.

"The default entrypoint for the container will deploy all deployment files found in /opt/payara/deployments,

so mounting a directory there that contains an application will deploy it on startup.

Alternatively, you can build your own Docker image from a Dockerfile to do the same:

FROM payara/server-full

COPY application.war $DEPLOY_DIR

Running the container produced from this image will also deploy the application on startup. The

image will need rebuilding when the application changes."

I have tried the first option: mounting directory to /opt/payara/deployments but still does not deploy the applications. I have also tried the option of building the Docker image from a docker file that contains COPY bwbportal.war $DEPLOY_DIR, and still it doesn't work.

Note the environment variable $DEPLOY_DIR contains the value /opt/payara/deployments while autodeploy directory in the payara is /opt/payara/appserver/glassfish/domains/domain1/autodeploy. As stated above when I copy the application to /opt/payara/appserver/glassfish/domains/domain1/autodeploy, its being autodeployed (see logs below).

Loading application [bwbportal] at [/bwbportal]|#]

bwbportal was successfully deployed in 6,261 milliseconds.|#]

[AutoDeploy] Successfully autodeployed : /opt/payara/appserver/glassfish/domains/domain1/autodeploy/bwbportal.war.|#]

Then there must be something that I am not doing correct, may be a certain script is not being run that deploys the application using asadmin deploy command or that copies the application from /opt/payara/deployments to /opt/payara/appserver/glassfish/domains/domain1/autodeploy.

Regards

Clifton

Rudy De Busscher

unread,

Aug 23, 2021, 3:24:58 AM8/23/21

to Payara Forum

Hi,

You should use the Postboot Command option to enable the health check. I assume the RUN command in the docker file is interfering with the scripts to deploy the application.

Regards

Rudy

Clifton Mtengezo

unread,

Aug 24, 2021, 7:53:22 AM8/24/21

to Payara Forum

Thank you for your feedback. The application is still not being deployed automatically

1. I changed my Dockerfile to as follows:

FROM payara/server-full

COPY bwbportal.war $DEPLOY_DIR

2. Then i run the build command as follows:

docker build -t bwbportal .

3. Then I executed the docker run command as follows:

D:\dockerdeploy>docker run -i --rm --name bwbportal -p 54848:4848 -p 58080:8080 -p 58181:8181 bwbportal

4. Here is the log displayed after the run command:

[Entrypoint] running /opt/payara/scripts/init_1_generate_deploy_commands.sh

Adding deployment target /opt/payara/deployments/bwbportal.war to post boot commands

[Entrypoint] ignoring /opt/payara/scripts/init.d/*

Executing Payara Server with the following command line:

/usr/lib/jvm/zulu8-ca-amd64/bin/java

-cp

/opt/payara/appserver/glassfish/modules/glassfish.jar

-XX:+UnlockDiagnosticVMOptions

-XX:NewRatio=2

-XX:+UseContainerSupport

-XX:MaxRAMPercentage=70.0

-Xbootclasspath/a:/opt/payara/appserver/glassfish/lib/grizzly-npn-api.jar

-Xss512k

-server

-javaagent:/opt/payara/appserver/glassfish/lib/monitor/flashlight-agent.jar

-Djavax.xml.accessExternalSchema=all

-Djavax.net.ssl.trustStore=/opt/payara/appserver/glassfish/domains/domain1/config/cacerts.jks

-Djdk.tls.rejectClientInitiatedRenegotiation=true

-Djdk.corba.allowOutputStreamSubclass=true

-Dfelix.fileinstall.dir=/opt/payara/appserver/glassfish/modules/autostart/

-Dorg.glassfish.additionalOSGiBundlesToStart=org.apache.felix.shell,org.apache.felix.gogo.runtime,org.apache.felix.gogo.shell,org.apache.felix.gogo.command,org.apache.felix.shell.remote,org.apache.felix.fileinstall

-Dcom.sun.aas.installRoot=/opt/payara/appserver/glassfish

-Dfelix.fileinstall.poll=5000

-Djava.security.policy=/opt/payara/appserver/glassfish/domains/domain1/config/server.policy

-Djava.endorsed.dirs=/opt/payara/appserver/glassfish/modules/endorsed:/opt/payara/appserver/glassfish/lib/endorsed

-Dosgi.shell.telnet.maxconn=1

-Dfelix.fileinstall.bundles.startTransient=true

-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory

-Dfelix.fileinstall.log.level=2

-Djavax.net.ssl.keyStore=/opt/payara/appserver/glassfish/domains/domain1/config/keystore.jks

-Djava.security.auth.login.config=/opt/payara/appserver/glassfish/domains/domain1/config/login.conf

-Dfelix.fileinstall.disableConfigSave=false

-Dorg.glassfish.grizzly.DEFAULT_MEMORY_MANAGER=org.glassfish.grizzly.memory.HeapMemoryManager

-Dfelix.fileinstall.bundles.new.start=true

-Dcom.sun.aas.instanceRoot=/opt/payara/appserver/glassfish/domains/domain1

-Dosgi.shell.telnet.port=6666

-Dgosh.args=--nointeractive

-Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as

-Dorg.jboss.weld.serialization.beanIdentifierIndexOptimization=false

-Dosgi.shell.telnet.ip=127.0.0.1

-DANTLR_USE_DIRECT_CLASS_LOADING=true

-Djava.awt.headless=true

-Dcom.ctc.wstx.returnNullForDefaultNamespace=true

-Djava.ext.dirs=/usr/lib/jvm/zulu8-ca-amd64/lib/ext:/usr/lib/jvm/zulu8-ca-amd64/jre/lib/ext:/opt/payara/appserver/glassfish/domains/domain1/lib/ext

-Djdbc.drivers=org.h2.Driver

-Dorg.glassfish.grizzly.nio.DefaultSelectorHandler.force-selector-spin-detection=true

-Djava.library.path=/opt/payara/appserver/glassfish/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib

com.sun.enterprise.glassfish.bootstrap.ASMain

-prebootcommandfile

/opt/payara/config/pre-boot-commands-final.asadmin

-upgrade

false

-read-stdin

true

-postbootcommandfile

/opt/payara/config/post-boot-commands-final.asadmin

-domainname

domain1

-domaindir

/opt/payara/appserver/glassfish/domains/domain1

-asadmin-args

--host,,,localhost,,,--port,,,4848,,,--user,,,admin,,,--passwordfile,,,/opt/payara/passwordFile,,,--secure=false,,,--terse=false,,,--extraterse=false,,,--echo=false,,,--interactive=false,,,--autoname=false,,,start-domain,,,--verbose=false,,,--watchdog=false,,,--debug=false,,,--domaindir,,,/opt/payara/appserver/glassfish/domains,,,domain1

-instancename

server

-type

DAS

-verbose

false

-asadmin-classpath

/opt/payara/appserver/glassfish/lib/client/appserver-cli.jar

-debug

false

-asadmin-classname

com.sun.enterprise.admin.cli.AdminMain

-watchdog

false

Launching Payara Server on Felix platform

Aug 24, 2021 11:28:40 AM com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner createBundleProvisioner

INFO: Create bundle provisioner class = class com.sun.enterprise.glassfish.bootstrap.osgi.BundleProvisioner.

Registered com.sun.enterprise.glassfish.bootstrap.osgi.EmbeddedOSGiGlassFishRuntime@36627446 in service registry.

Reading in commandments from /opt/payara/config/pre-boot-commands-final.asadmin

#!## LogManagerService.postConstruct : rootFolder=/opt/payara/appserver/glassfish

#!## LogManagerService.postConstruct : templateDir=/opt/payara/appserver/glassfish/lib/templates

#!## LogManagerService.postConstruct : src=/opt/payara/appserver/glassfish/lib/templates/logging.properties

#!## LogManagerService.postConstruct : dest=/opt/payara/appserver/glassfish/domains/domain1/config/logging.properties

Running Payara Version: Payara Server 5.2021.6 #badassfish (build 4579)|#]

Server log file is using Formatter class: com.sun.enterprise.server.logging.ODLLogFormatter|#]

Registered fish.payara.ha.hazelcast.store.HazelcastBackingStoreFactoryProxy for persistence-type = hazelcast in BackingStoreFactoryRegistry|#]

Hazelcast Instance Bound to JNDI at payara/Hazelcast|#]

JSR107 Caching Provider Bound to JNDI at payara/CachingProvider|#]

JSR107 Default Cache Manager Bound to JNDI at payara/CacheManager|#]

Network Listener http-listener-1 started in: 16ms - bound to [/0.0.0.0:8080]|#]

HV000001: Hibernate Validator 6.1.5.Final|#]

Network Listener http-listener-2 started in: 8ms - bound to [/0.0.0.0:8181]|#]

HTTP/2 (enabled by default) is unsupported with port unification and will be disabled for network listener admin-listener.|#]

Network Listener admin-listener started in: 10ms - bound to [/0.0.0.0:4848]|#]

Grizzly 2.4.4 started in: 3,513ms - bound to [http-listener-1:8080, http-listener-2:8181, admin-listener:4848]|#]

Network Listener iiop-service started in: 9ms - bound to [/0.0.0.0:3700]|#]

Payara Server 5.2021.6 #badassfish (4579) startup time : Felix (2,627ms), startup services(4,293ms), total(6,920ms)|#]

Data Grid Status

Payara Data Grid State: DG Version: 4 DG Name: development DG Size: 1

Instances: {

DataGrid: development Name: server Lite: false This: true UUID: 0e1a7ed0-987b-4659-a9d0-3c83656b50ad Address: /172.17.0.2:4900

}|#]

Payara Notification Service bootstrapped.|#]

Bootstrapping Monitoring Console Runtime|#]

Starting monitoring data collection for server|#]

Starting monitoring watch collection for server|#]

Creating a SecureRMIServerSocketFactory @ 0.0.0.0 with ssl config = GlassFishConfigBean.org.glassfish.grizzly.config.dom.Ssl|#]

All SSL cipher suites disabled for network-listener(s). Using SSL implementation specific defaults|#]

Network Listener JMS_PROXY_default_JMS_host started in: 14ms - bound to [/0.0.0.0:7676]|#]

[#|2021-08-24T11:28:47.884+0000|INFO|Payara 5.2021.6||_ThreadID=1;_ThreadName=main;_TimeMillis=1629804527884;_LevelValue=800;|

Reading in commandments from /opt/payara/config/post-boot-commands-final.asadmin|#]

All SSL cipher suites disabled for network-listener(s). Using SSL implementation specific defaults|#]

SSLServerSocket /0.0.0.0:8686 and [SSL: ServerSocket[addr=/0.0.0.0,localport=8686]] created|#]

JMXStartupService has started JMXConnector on JMXService URL service:jmx:rmi://0.0.0.0:8686/jndi/rmi://0.0.0.0:8686/jmxrmi|#]

Skipping registration of inhabitant for service reference [org.osgi.service.metatype.MetaTypeProvider] as the service object could not be obtained.|#]

5. Here is how I checked to see if the application has been deployed automatically.

COMMAND 1 - login in to the container shell

C:\windows\system32>docker exec -it bwbportal /bin/bash

COMMAND 2 - Checking container environmental variables

payara@fe75584ec9ec:~$ env

LC_ALL=en_US.UTF-8

PAYARA_ARGS=

LANG=en_US.UTF-8

DEPLOY_PROPS=

HOSTNAME=fe75584ec9ec

PREBOOT_COMMANDS_FINAL=/opt/payara/config/pre-boot-commands-final.asadmin

JAVA_HOME=/usr/lib/jvm/zulu8-ca-amd64

HOME_DIR=/opt/payara

PWD=/opt/payara

POSTBOOT_COMMANDS=/opt/payara/config/post-boot-commands.asadmin

HOME=/opt/payara

DEPLOY_DIR=/opt/payara/deployments

ADMIN_USER=admin

DOMAIN_NAME=domain1

PREBOOT_COMMANDS=/opt/payara/config/pre-boot-commands.asadmin

JVM_ARGS=

MEM_XSS=512k

TERM=xterm

PASSWORD_FILE=/opt/payara/passwordFile

ADMIN_PASSWORD=admin

CONFIG_DIR=/opt/payara/config

SCRIPT_DIR=/opt/payara/scripts

SHLVL=1

LANGUAGE=en_US:en

POSTBOOT_COMMANDS_FINAL=/opt/payara/config/post-boot-commands-final.asadmin

MEM_MAX_RAM_PERCENTAGE=70.0

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/payara/appserver/bin

PAYARA_DIR=/opt/payara/appserver

_=/usr/bin/env

COMMAND 3 - Changing directory to payara home directory

payara@fe75584ec9ec:~$ cd $PAYARA_DIR

COMMAND 4 - Listing contents of payara home directory

payara@fe75584ec9ec:~/appserver$ ls

bin glassfish h2db META-INF mq README.txt

COMMAND 5 - Changing directory to bin directory in payara home

payara@fe75584ec9ec:~/appserver$ cd bin

COMMAND 6 - running payara list-applications command to show list of deployed applications

payara@fe75584ec9ec:~/appserver/bin$ asadmin list-applications

Do you trust the above certificate [y|N] -->y

Enter admin user name> admin

Enter admin password for user "admin">

Nothing to list.

No applications are deployed to this target server.

Command list-applications executed successfully.

payara@fe75584ec9ec:~/appserver/bin$

Rudy De Busscher

unread,

Aug 25, 2021, 3:13:11 AM8/25/21

to Payara Forum

Hi,

Can you open an issue on GitHub[1] as it seems that the /opt/payara/config/post-boot-commands-final.asadmin file is empty.

[1] https://github.com/payara/Payara/issues

Thank you

Rudy

Clifton Mtengezo

unread,

Aug 25, 2021, 3:54:12 AM8/25/21

to Rudy De Busscher, Payara Forum

Rudy,

I hope I have a reputation to open an issue on this esteemed website. :). But I will do.

Thank you.

Clifton

To view this discussion on the web, visit https://groups.google.com/d/msgid/payara-forum/86a235e5-8bae-4d42-94d9-30b2f7fef22bn%40googlegroups.com.

Reply all

Reply to author

Forward

0 new messages