I suspect this is the cause, not loading the profile first.
-------- Original Message --------
[ https://jira.jboss.org/jira/browse/JBAS-5370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12438006#action_12438006 ]
Scott M Stark commented on JBAS-5370:
-------------------------------------
In updating the DeploymentManager logging and error checking, this can also happen if the profile has not been loaded. You first need to call
DeploymentManager.loadProfile(ProfileKey key, boolean allowHotDeployments). If a profile has not been loaded any DeploymentManager method now
throws a NoSuchProfileException.
> Deploy an ear/war app through ProfileService
> --------------------------------------------
>
> Key: JBAS-5370
> URL: https://jira.jboss.org/jira/browse/JBAS-5370
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Mark Spritzler
> Assignee: Scott M Stark
> Priority: Critical
> Fix For: JBossAS-5.0.0.GA
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira