Re: [wildfly-dev] Deploying app on managed domain
> I started bin/standalone.sh, deployed a WAR file (name is
> http-1.0-SNAPSHOT.war) with just one index.jsp. Accessing
> localhost:8080/http shows the expected results. Tried the same with
> bin/domain.sh but now localhost:8080/http is giving a 404.
How exactly did you deploy it?
- localhost:9990/console
- Manage Deployments
- Deployed the app and it did not ask for server groups.
Redeployed using jboss-cli as:
deploy ~/workspaces/wildfly-lab/samples/javaee7/target/javaee7-1.0-SNAPSHOT.war
--server-groups=main-server-group
and that worked.
However deploying using admin console (following the steps listed
above) does not work for standalone. Or at least the application is
not accessible at http://localhost:8080/javaee7-1.0-SNAPSHOT. What is
the context path of the deployed application ?
Arun
> What are the port number of the servers started in this managed domain
> ? Is Ports +0 and +150 in admin console trying to display that
> information ? If yes, then that is not very intuitive and the exact
> value of the port should be displayed. If not, what are these values ?
> Should this app be accessible on localhost:8080 ?
>
> Tried enabling the app from admin console and got the error:
> Failed to enable http-1.0-SNAPSHOT.war.
>
> Unexpected HTTP response: 500
>
> Request
> {
> "address" => [("deployment" =>
"http-1.0-SNAPSHOT.war")],
> "operation" => "deploy"
> }
>
> Response
>
> Internal Server Error
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014884: No operation named
'deploy'
> exists at address [(\"deployment\" =>
\"http-1.0-SNAPSHOT.war\")]",
> "rolled-back" => true
> }
>
> Is this the correct way to deploy the app on managed domain ?
No, it has to be deployed on server groups.
Alexey
>
> Arun
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
http://blog.arungupta.me
http://twitter.com/arungupta