[jboss-jira] [JBoss JIRA] (AS7-6009) JBAS018040: Failed to start context

[B K (JIRA)]

B K created AS7-6009:
------------------------

             Summary: JBAS018040: Failed to start context
                 Key: AS7-6009
                 URL: https://issues.jboss.org/browse/AS7-6009
             Project: Application Server 7
          Issue Type: Bug
          Components: Console
    Affects Versions: 7.1.1.Final
         Environment: Redhat Linux 4 (??). Kernel version is: 2.6.18-194.26.1.el5
            Reporter: B K
            Assignee: Heiko Braun


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 only 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 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