Bug 793951 (JBEPP-1022)

Summary: Directory deploy-hasingleton does not exists in EPP 5.1.1-CR01
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: mposolda
Component: unspecifiedAssignee: Thomas Heute <theute>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.1.CR01CC: epp-bugs, hfnukal, mcupak
Target Milestone: ---   
Target Release: 5.1.1.GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1022
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-24 13:04:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description mposolda 2011-07-25 11:46:04 UTC
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.

Comment 1 mposolda 2011-07-25 11:48:22 UTC
Link: Added: This issue relates to JBQA-4899


Comment 2 hfnukal@redhat.com 2011-07-29 13:04:55 UTC
EPP 5.1.1.CR01 was built with early EAP 5.1.1 that was CR4 in that moment. I should be only renamed to GA, no changes was promised. It does not contains this folder.

EAP 5.1.1.GA finally contains this folder so if packaged with this it will work.

Comment 3 Scott Mumford 2011-08-09 04:19:17 UTC
Release Notes Docs Status: Added: Not Required


Comment 4 Michal Vanco 2011-08-09 06:20:24 UTC
Honzo, this issues is unfortunately still present (verified with GA). It seems that EAP 5.1.1.GA doesn't contain the folder in case it was bundled properly.

Comment 6 hfnukal@redhat.com 2011-08-10 15:08:16 UTC
Folder was removed during signing.

Comment 7 Michal Vanco 2011-08-15 14:31:16 UTC
Present again with new bundle, please verify signing process. (it's fine at unsigned version)

Comment 8 Thomas Heute 2011-08-18 12:36:42 UTC
Resolved but sign scripts need an update