Bug 675115 - Can´t deploy EAR on JBoss
Can´t deploy EAR on JBoss
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core UI (Show other bugs)
3.0.0
x86_64 Linux
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-04 06:09 EST by Kleber Rocha
Modified: 2011-05-23 20:55 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
log error (2.66 KB, text/plain)
2011-02-04 06:15 EST, Kleber Rocha
no flags Details

  None (edit)
Description Kleber Rocha 2011-02-04 06:09:44 EST
Description of problem:
I´m trying deploy EAR application, and I´m getting error: 

Failed to create Resource portal-for-ear-1.0.1.ear - cause: org.jboss.profileservice.spi.NoSuchProfileException:Profile does not support deployment actions: ProfileKey@74316bd[domain=default, server=default, name=applications] 

Version-Release number of selected component (if applicable):

RHQ 3.0 and EMBJOPR 1.4.0SP2


How reproducible:

Trying deploy application through the embjopr or in RHQ. I´m using Create New : Enterprise Application (EAR), I´m trying Farmed deploy.


Steps to Reproduce:
1. I selected option Enterprise Application (EAR) on Create New:
2. I uploaded file EAR, the RHQ create schedule.
3. The schedule fail with these message:

Failed to create Resource portal-for-ear-1.0.1.ear - cause: org.jboss.profileservice.spi.NoSuchProfileException:Profile does not support deployment actions: ProfileKey@74316bd[domain=default, server=default, name=applications] 
  
Actual results:


Expected results:


Additional info:
Comment 1 Kleber Rocha 2011-02-04 06:15:40 EST
Created attachment 476974 [details]
log error

Note You need to log in before you can comment on or make changes to this bug.