[jboss-jira] [JBoss JIRA] (WFCORE-407) Console should display deployment status

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFCORE-407:
-----------------------------------------

I'm going to move this to the HAL project, which is where console changes are made. A deployment resource includes a 'status' attribute, which is distinct information from 'enabled.' The 'status' is a runtime attribute so it is not present on the domain level deployment resources, only those on a server.

> Console should display deployment status
> ----------------------------------------
>
>                 Key: WFCORE-407
>                 URL: https://issues.jboss.org/browse/WFCORE-407
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Domain Management
>         Environment: Redhat Linux 4 (??). Kernel version is: 2.6.18-194.26.1.el5
>            Reporter: B K
>              Labels: jboss
>
> The error found in the server log files was:
> 13:58:40,009 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777:   Services which failed to start:      service jboss.web.deployment.default-host./apex: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./apex: JBAS018040: Failed to start context
> Occurence details:
> 1. The issue occured following a restart of the application server
> Analysis details: 
> 1. From the perspective of the JBOSS 7 admin console ... the admin console shows that the "apex.war" application is deployed and "enabled". I believe it should not display "enabled" as the context has failed to start and it is NOT capable of servicing requests.
> Details to reproduce:
> 1. Download Oracle Apex Listener 1.1.4 from:
> http://www.oracle.com/technetwork/developer-tools/apex-listener/downloads/index.html
> 2. Unzip the war file e.g jar xvf apex.war
> 3. Modify the web.xml by adding:
> 		 	<context-param>
> 		<param-name>config.dir</param-name>
> 		<param-value>/opt/jboss/apex_config_dir</param-value>
> 	</context-param>
> 4. Create the path "/opt/jboss/apex_config_dir".
> 5. Zip the war file. 
>    cd locationContaining the Web-INF directory
>    jar cvf apex.war *
> 6. Deploy war file and enable via admin console. Stop Server. Start server.
> 7. Exception occurs.
> NOTE: there could be an additional step to reproduce. Will detail if above does not work.
> NOTE2: I can redeploy the above application and get it working again by removing some files that are auto generated by apex.war (so a partial bit of this issue is probably application related).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)