[jbosstools-issues] [JBoss JIRA] (JBIDE-11454) Make the status of modules be closer to reality

Rob Stryker (JIRA) jira-events at lists.jboss.org
Wed May 22 09:03:06 EDT 2013 

    [ https://issues.jboss.org/browse/JBIDE-11454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775986#comment-12775986 ] 

Rob Stryker commented on JBIDE-11454:
-------------------------------------

Steps to reproduce are:

1) Create your server
2) Create a web app, simple, maybe add a servlet, whatever you want
3) Deploy it, verify state is started, verify it shows in browser, etc
4) Add a web.xml (or modify existing web.xml). MAKE SURE the new web.xml DOES NOT PARSE.  For example,  <web></somethingElse>
5) Try to publish
6) Observe console...

The piece you'll find burried in the log is:

{code}
21:00:42,351 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015863: Replacement of deployment "FailProj.war" by deployment "FailProj.war" was rolled back with the following failure message: 
{code}

Full log of successful publish followed by broken publish below:


{code}
21:00:22,094 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS018224: Unregister web context: /FailProj
21:00:22,107 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment FailProj.war (runtime-name: FailProj.war) in 134ms
21:00:22,108 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "FailProj.war" (runtime-name: "FailProj.war")
21:00:22,163 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS018210: Register web context: /FailProj
21:00:22,278 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018565: Replaced deployment "FailProj.war" with deployment "FailProj.war"



21:00:42,329 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS018224: Unregister web context: /FailProj
21:00:42,338 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment FailProj.war (runtime-name: FailProj.war) in 11ms
21:00:42,339 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "FailProj.war" (runtime-name: "FailProj.war")
21:00:42,345 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."FailProj.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."FailProj.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "FailProj.war"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_04]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_04]
	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017302: Failed to parse XML descriptor "/home/rob/apps/eclipse/workspaces/runtime-New_configuration/.metadata/.plugins/org.jboss.ide.eclipse.as.core/wildfly_Server1368806953669/deploy/FailProj.war/WEB-INF/web.xml" at [2,3]
	at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:123)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
	... 5 more

21:00:42,347 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"FailProj.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"FailProj.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"FailProj.war\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017302: Failed to parse XML descriptor \"/home/rob/apps/eclipse/workspaces/runtime-New_configuration/.metadata/.plugins/org.jboss.ide.eclipse.as.core/wildfly_Server1368806953669/deploy/FailProj.war/WEB-INF/web.xml\" at [2,3]"}}
21:00:42,350 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment FailProj.war (runtime-name: FailProj.war) in 0ms
21:00:42,351 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "FailProj.war" (runtime-name: "FailProj.war")
21:00:42,351 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015863: Replacement of deployment "FailProj.war" by deployment "FailProj.war" was rolled back with the following failure message: 
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"FailProj.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"FailProj.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"FailProj.war\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017302: Failed to parse XML descriptor \"/home/rob/apps/eclipse/workspaces/runtime-New_configuration/.metadata/.plugins/org.jboss.ide.eclipse.as.core/wildfly_Server1368806953669/deploy/FailProj.war/WEB-INF/web.xml\" at [2,3]"}}
21:00:42,357 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."FailProj.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."FailProj.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "FailProj.war"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_04]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_04]
	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017302: Failed to parse XML descriptor "/home/rob/apps/eclipse/workspaces/runtime-New_configuration/.metadata/.plugins/org.jboss.ide.eclipse.as.core/wildfly_Server1368806953669/deploy/FailProj.war/WEB-INF/web.xml" at [2,3]
	at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:123)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha1-SNAPSHOT.jar:8.0.0.Alpha1-SNAPSHOT]
	... 5 more

21:00:42,359 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.deployment.unit."FailProj.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."FailProj.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "FailProj.war"
      service jboss.deployment.unit."FailProj.war".PARSE
{code}

                
> Make the status of modules be closer to reality
> -----------------------------------------------
>
>                 Key: JBIDE-11454
>                 URL: https://issues.jboss.org/browse/JBIDE-11454
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>         Environment: JBoss Developer Studio 5 Beta
> JBoss Enterprise Application 6 Beta
>            Reporter: Mustafa Musaji
>            Assignee: Rob Stryker
>            Priority: Minor
>              Labels: new_and_noteworthy
>             Fix For: 4.1.0.Beta2
>
>
> When deployment of an application fails on JBoss EAP, JBoss Tools doesn't recognize this as failure and continues to report the status as [Started, Synchronized].
> This a request to add the ability for JBDS to report back via the console when a deployment fails due to application errors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbosstools-issues mailing list