[jboss-jira] [JBoss JIRA] (WFLY-5321) Deploying a war to wildfly should mention the localhost url including context root of that war in the log
Geoffrey De Smet (JIRA)
issues at jboss.org
Fri Sep 11 03:34:01 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107740#comment-13107740 ]
Geoffrey De Smet edited comment on WFLY-5321 at 9/11/15 3:33 AM:
-----------------------------------------------------------------
That log line doesn't show up, not in a fresh install of 9.0.1.Final (downloaded again this morning), nor in 8.1.0.Final. In the wildfly admin console I can see the deployment listed as succeeded, but I again don't find any reference to the web context nor the localhost url, not even in the undertow component. Seeing as I can't guess it either, I think the http service isn't actually there - but it would be nice to somehow confirm this.
Note: this issue is NOT about whatever is causing my http service to be not available (I must have made a mistake somewhere), instead it's about me not having enough feedback from wildfly 9 to determine what's going on: it says it's deployed, it's a war with html files, but I can't find it. It should it say where it is or why it's failed.
Especially because deploying a war is a typical first user action, the error message experience is important to improve adoption.
was (Author: ge0ffrey):
That log line doesn't show up, not in a fresh install of 9.0.1.Final (downloaded again this morning), nor in 8.1.0.Final. In the wildfly admin console I can see the deployment listed as succeeded, but I again don't find any reference to the web context nor the localhost url, not even in the undertow component. Seeing as I can't guess it either, I think the http service isn't actually there - but it would be nice to somehow confirm this.
Note: this issue is NOT about whatever is causing my http service to be not available (I must have made a mistake somewhere), instead it's about me not having enough feedback from wildfly to determine what's going on: it says it's deployed, it's a war with html files, but I can't find it. It should it say where it is or why it's failed.
Especially because deploying a war is a typical first user action, the error message experience is important to improve adoption.
> Deploying a war to wildfly should mention the localhost url including context root of that war in the log
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5321
> URL: https://issues.jboss.org/browse/WFLY-5321
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (Undertow)
> Reporter: Geoffrey De Smet
> Assignee: Tomaz Cerar
> Priority: Minor
>
> Here what I see now in the log:
> {code}
> [2015-09-10 04:56:44,211] Artifact optaconf-webapp:war exploded: Artifact is being deployed, please wait...
> 16:56:44,235 INFO [org.jboss.weld.deployer] (MSC service thread 1-9) JBAS016009: Stopping weld service for deployment optaconf-webapp-0.1.0-SNAPSHOT
> 16:56:44,244 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment optaconf-webapp-0.1.0-SNAPSHOT (runtime-name: optaconf-webapp-0.1.0-SNAPSHOT) in 15ms
> 16:56:44,255 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "optaconf-webapp-0.1.0-SNAPSHOT" (runtime-name: "optaconf-webapp-0.1.0-SNAPSHOT")
> 16:56:44,322 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "optaconf-webapp-0.1.0-SNAPSHOT" (runtime-name: "optaconf-webapp-0.1.0-SNAPSHOT")
> ...
> 16:56:44,508 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559: Deployed "optaconf-webapp-0.1.0-SNAPSHOT" (runtime-name : "optaconf-webapp-0.1.0-SNAPSHOT")
> [2015-09-10 04:56:44,519] Artifact optaconf-webapp:war exploded: Artifact is deployed successfully
> [2015-09-10 04:56:44,519] Artifact optaconf-webapp:war exploded: Deploy took 308 milliseconds
> {code}
> But as a developer, it's very hard to figure out the url to test the app, especially if someone changed it recently. Note that in my case it could be any of these, depending on the state of the jboss-web.xml, war file name (potentially exploded), IDE configuration, etc:
> - http://localhost:8080/optaconf-webapp-0.1.0-SNAPSHOT/
> - http://localhost:8080/optaconf-webapp/
> - http://localhost:8080/optaconf/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list