java.io.FileNotFoundException during JBoss EAP startup

Solution Verified - Updated -

Issue

During the bootup process, JBoss EAP throws java.io.FileNotFoundException, and there is no server.log file in the target directory. Even creating a server.log manually, JBoss EAP does not write any log to it.

log4j:ERROR Failed to create directory structure: /var/log/sample_path
log4j error: setFile(null,true) call failed.
java.io.FileNotFoundException: /var/log/sample_path/server.log (No such file or directory)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:142)
    at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
  • The JBoss EAP does not start correctly, the error appears when we try to start a deploy called Example.war. That is when the log shows a timeout of 300 seconds and does not allow to deploy contexts.
07:20:39,267 WARNING [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Failed to parse WSDL: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing 'WEB-INF/wsdl/example.wsdl'.: java.io.FileNotFoundException: /path/to/jboss-eap/bin/WEB-INF/wsdl/example.wsdl (No such file or directory)
        at com.example.wsdl.xml.WSDLReaderImpl.getDocument(WSDLExampleImpl.java:2198) [wsdl4j-1.6.3.redhat-1.jar:1.6.3.redhat-1]
...
Caused by: java.io.FileNotFoundException: /path/to/jboss-eap/bin/WEB-INF/wsdl/example.wsdl (No such file or directory)

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 5.x
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In