[jboss-jira] [JBoss JIRA] Commented: (JBAS-6724) ProfileService's capabilities don't match JBoss deployer's ones

Mon Apr 6 10:50:22 EDT 2009

    [ https://jira.jboss.org/jira/browse/JBAS-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460749#action_12460749 ] 

Ondrej Žižka commented on JBAS-6724:
------------------------------------

On DeploymentScanner's RecursiveSearch param:  http://www.jboss.org/community/docs/DOC-9552

> ProfileService's capabilities don't match JBoss deployer's ones
> ---------------------------------------------------------------
>
>                 Key: JBAS-6724
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6724
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ProfileService
>    Affects Versions: JBossAS-5.1.0.CR1
>            Reporter: Ondrej Žižka
>            Assignee: Emanuel Muckenhuber
>
> JBoss AS allows to deploy an app in ZIP archive with unusual structure. But ProfileService seems not to support this well.
> Let's have a WAR in an archive "hellothere-DUD_RETRY.zip", which contains hellothere-DUD_RETRY directory with the actual web app content. So the path is hellothere-DUD_RETRY.zip/hellothere-DUD_RETRY/hello.jsp
> This zip archive is deployed succesfully **using hot-deploy**.
> ProfileService reports the app without an extension - "hellothere-DUD_RETRY".
> I've found this behavior when testing EmbJopr.
> When I try to do some operation with it (undeploy, stop), I get an exception - see below.
> -----------------------------------------------------------------------------------------------------------------------
> 	Failed to delete Web Application (WAR) 'hellothere-DUD_RETRY' - java.lang.Exception
> 	at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:101)
> 	at org.rhq.plugins.jbossas5.ManagedDeploymentComponent.deleteResource(ManagedDeploymentComponent.java:203)
> 	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:585)
> 	at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: java.lang.RuntimeException: org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere-DUD_RETRY.zip/hellothere-DUD_RETRY/
> 	at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:313)
> 	at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.remove(StreamingDeploymentTarget.java:229)
> 	at org.jboss.profileservice.management.upload.DeploymentProgressImpl.remove(DeploymentProgressImpl.java:318)
> 	at org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:94)
> 	at org.rhq.plugins.jbossas5.util.DeploymentUtils.run(DeploymentUtils.java:97)
> 	... 11 more
> Caused by: org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere-DUD_RETRY.zip/hellothere-DUD_RETRY/
> 	at org.jboss.system.server.profileservice.repository.AbstractDeploymentRepository.getDeployment(AbstractDeploymentRepository.java:134)
> 	at org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.removeDeployment(BasicDeploymentRepository.java:208)
> 	at org.jboss.profileservice.management.upload.remoting.DeployHandler.removeDeployment(DeployHandler.java:171)
> 	at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.remove(AbstractDeployHandler.java:322)
> 	at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:185)
> 	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
> 	at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
> 	at org.jboss.remoting.Client.invoke(Client.java:1708)
> 	at org.jboss.remoting.Client.invoke(Client.java:612)
> 	at org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:305)
> 	... 15 more

-- 
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