• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

How to automate the explode process in wildfly deployment?

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Issue: Though the deployment is success, web application is not up and running. It is giving ‘Not Found’ error message inside html tags when we hit the URL in the browser.

<html><head><title>Error</title></head><body>Not Found</body></html>

Note: Application war is deployed using the command mentioned below. nohup sh standalone.sh -b=0.0.0.0 -bmanagement=0.0.0.0 &

Workaround: Only if we explode the war using explode option in Wildlfy console, application will work.

Can someone please suggest how to automate the explode process or any other way to bring up the application?
 
Saloon Keeper
Posts: 24804
172
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is something wrong with your setup if the webapp only works when exploded. The standard for JEE doesn't even mention an option for exploded WARs as far as I know, and the effective operation should be the same in either event unless someone tried to either write data into the WAR directory subtree or use filesystem calls to access WAR resources. Neither of which are good practice.

Your sample command calls a shell script named "standalone.sh". We don't know what it does, but presumably it either calls a web server or does a brute-force jam of the WAR into Wildfly's webapps directory. Without knowing details I cannot say why deployment apparently fails.
 
Jan Priya
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you so much for the reply
Could you please let me know the details which I need to share?
 
Marshal
Posts: 3760
536
Android Eclipse IDE TypeScript Redhat MicroProfile Quarkus Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
standalone.sh is a script which ships with Wildfly to start a single instance of the application server (similar to Tomcat's startup.sh).  It is not a tool to deploy wars.

Look-through the server.log log file to see if the application server recognizes your war, and if it attempts to deploy it.


Possibly you are not dropping the war file in the a directory where the application server is expecting it.
 
Jan Priya
Greenhorn
Posts: 3
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you so much for the reply

I have checked the server.log file and observed that war is getting deployed.

Starting deployment of "Application1.war" (runtime-name: "Application1.war")
Starting deployment of "Application2.ear" (runtime-name: "Application2.ear")
Registered web context: '/app1' for server 'default-server'
Registered web context: '/app2' for server 'default-server'
Deployed "Application1.war" (runtime-name : "Application1.war")
Deployed "Application2.ear" (runtime-name : "Application2.ear")


I am dropping the war file in the following path
<wildflypath>/standalone/deployments
 
reply
    Bookmark Topic Watch Topic
  • New Topic