Workaround Description: Workaround is to create directory "deploy-hasingleton" under "all" and "production" configurations.
project_key: JBEPP

Directory deploy-hasingleton does not exists in $EPP_HOME/server/all and in $EPP_HOME/server/production . This is causing error during server startup. Seems that it is packaging mistake on our side because in EAP 5.1.1.GA the directory deploy-hasingleton exists in configurations "all" and "production". 

To simulate error:
- Run EPP 5.1.1.CR1 with: ./run.sh -c all
- You will see error:

2011-07-25 07:17:42,240 ERROR [org.jboss.system.server.profileservice.repository.ScopedProfileServiceController] (main) Error installing to Create: name=ProfileKey@a60b09[domain=default, server=default, name
=deploy-hasingleton] state=Configured mode=On Demand requiredState=Installed
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.system.server.profileservice.repository.AbstractProfileLifeCycleAction.invoke(AbstractProfileLifeCycleAction.java:97)
        at org.jboss.system.server.profileservice.repository.AbstractProfileLifeCycleAction.invoke(AbstractProfileLifeCycleAction.java:77)
        at org.jboss.system.server.profileservice.repository.AbstractProfileLifeCycleAction.install(AbstractProfileLifeCycleAction.java:49)
        at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
        at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
        at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
        at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
        at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
        at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
        at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
.........................
Caused by: java.io.FileNotFoundException: deploy-hasingleton doesn't exist. (rootURI: file:/tmp/portall/jboss-epp-5.1/jboss-as/server/all/deploy-hasingleton, file: /tmp/portall/jboss-epp-5.1/jboss-as/server/all/deploy-hasingleton)
        at org.jboss.virtual.plugins.context.file.FileSystemContext.getRoot(FileSystemContext.java:222)
        at org.jboss.virtual.VFS.getRoot(VFS.java:339)
        at org.jboss.virtual.VFS.createNewRoot(VFS.java:229)
        at org.jboss.virtual.VFS.getRoot(VFS.java:244)
        at org.jboss.system.server.profileservice.repository.AbstractVFSProfileSource.getCachedVirtualFile(AbstractVFSProfileSource.java:353)
        at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.load(BasicDeploymentRepository.java:114)
        at org.jboss.system.server.profile.repository.AbstractProfile.create(AbstractProfile.java:158)
        ... 130 more

Workaround is to create directory "deploy-hasingleton" under "all" and "production" configurations.