According to the log the engine is not starting correctly because one of the modules is missing a .jar file. The module file that is failing is /var/tmp/ovirt-engine/modules/org/apache/james/mime4j/main/module.xml. This is a symlink created by the engine during startup wich should poit to /usr/share/jboss-as/modules/org/apache/james/mime4j/main/module.xml. Can you check that? The content of that file as installed by the jboss-as RPM should be this:

<?xml version="1.0" encoding="UTF-8"?>

<module xmlns="urn:jboss:module:1.1" name="org.apache.james.mime4j">
    <properties>
        <property name="jboss.api" value="private"/>
    </properties>

    <resources>
        <resource-root path="core.jar"/>
        <resource-root path="dom.jar"/>
        <resource-root path="storage.jar"/>
        <!-- Insert resources here -->
    </resources>

    <dependencies>
        <module name="javax.api"/>
        <module name="org.apache.commons.logging"/>
    </dependencies>
</module>

As you can see this module references the .jar files core.jar, dom.jar and storage.jar, that should be in the same directory, but it looks that in you case the module references apache-mime4j-core.jar. This file name doesn't match any version of JBoss that I am aware off. I would suggest to remove completely the jboss-as installation, at least the module



# rm -rf /usr/share/jboss-as/modules
# yum reinstall jboss-as

Then restart the engine and try again.

If you still have problems please report the specific version of the jboss-as package that you are using and the content of the /usr/share/jboss-as/modules/org/apache/james/mime4j/main/module.xml file and the /usr/share/jboss-as/modules/org/apache/james/mime4j/main directory:

# ls -l /usr/share/jboss-as/modules/org/apache/james/mime4j/main
# cat /usr/share/jboss-as/modules/org/apache/james/mime4j/main/module.xml

I think that this issue was solved in jboss-as-7.1.1-20. I'm closing the bug. If it isn't solved please reopen.