| Summary: | Can't delete esb resource in JON once it has been removed in a different way | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jaroslaw Kijanowski <kijanowski> |
| Component: | JON | Assignee: | Kevin Conner <kevin.conner> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0 ER6 | CC: | pkralik |
| Target Milestone: | --- | ||
| Target Release: | 5.1.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1815 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-02-11 06:43:03 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
Jaroslaw Kijanowski
2010-01-11 16:54:20 UTC
Kevin to investigate for SOA 5.1.0. Candidate only. Link: Added: This issue depends JBESB-3492 Checked into ESB in revision 35368. Writer: Added: dlesage Tested with JON 2.4.1.GA and SOA-P 5.1.0.ER9. I deployed resource and undeployed by 'ant undeploy' and then removed successfully with delete button in JON. JON server log: 2011-02-09 18:15:57,322 INFO [org.rhq.enterprise.server.resource.ResourceManagerBean] User [org.rhq.core.domain.auth.Subject[id=1,name=admin]] is marking resource [Resource[id=10277, type=Services, key=jboss.esb:category=MessageCounter,deployment=Quickstart_helloworld_failing.esb,service-category=FirstFailingServiceESB,service-name=SimpleFailingListener, name=SimpleFailingListener Service, parent=Quickstart_helloworld_failing.esb, version=5.1.0.ER9]] for asynchronous uninventory JON agent log: 2011-02-09 18:15:57,273 ERROR [ResourceContainer.invoker.nonDaemon-9] (org.rhq.plugins.jmx.MBeanResourceComponent)- Failed to stop deployment 'vfszip:/home/pkralik/jon_test/soa/jboss-soa-p-5/jboss-as/server/production/deploy/Quickstart_helloworld_failing.esb/'. java.lang.RuntimeException: org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/home/pkralik/jon_test/soa/jboss-soa-p-5/jboss-as/server/production/deploy/Quickstart_helloworld_failing.esb/ at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:312) at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.stop(StreamingDeploymentTarget.java:207) at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.stop(DeploymentProgressImpl.java:277) at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:92) at org.jbosson.plugins.jbossesb.ESB5DeploymentComponent.deleteResource(ESB5DeploymentComponent.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) SOA-P server log: 2011-02-09 18:14:43,968 WARN [org.jboss.on.embedded.ui.NavigationContent] (InventoryManager.discovery-1) Unable to find node for deleted resource [Resource[id=-17, type=Queue, key=/queue/quickstart_helloworld_failing_Request_gw, name=quickstart_helloworld_failing_Request_gw, parent=JBoss Messaging]]. 2011-02-09 18:15:57,268 INFO [org.jboss.profileservice.management.upload.remoting.DeployHandler] (WorkerThread#0[127.0.0.1:45645]) Stop, [vfszip:/home/pkralik/jon_test/soa/jboss-soa-p-5/jboss-as/server/production/deploy/Quickstart_helloworld_failing.esb/] 2011-02-09 18:15:57,268 INFO [org.jboss.profileservice.management.upload.remoting.DeployHandler] (WorkerThread#0[127.0.0.1:45645]) Failed to complete command: [stop] for deployment: names=[vfszip:/home/pkralik/jon_test/soa/jboss-soa-p-5/jboss-as/server/production/deploy/Quickstart_helloworld_failing.esb/] org.jboss.profileservice.spi.NoSuchDeploymentException: Failed to find deployment in file: vfszip:/home/pkralik/jon_test/soa/jboss-soa-p-5/jboss-as/server/production/deploy/Quickstart_helloworld_failing.esb/ at org.jboss.system.server.profileservice.repository.AbstractDeploymentRepository.getDeployment(AbstractDeploymentRepository.java:134) at org.jboss.profileservice.management.upload.remoting.DeployHandler.scheduleStop(DeployHandler.java:156) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.stop(AbstractDeployHandler.java:369) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.stop(AbstractDeployHandler.java:358) at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:242) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:930) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) Temporarily reopening to update release notes info. Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3492 If the user deleted a missing deployment, an exception occurred. This happened if the user launched a quick start, imported the SOA Platform into JON, removed the quick start (via ant undeploy) and then tried to remove it again via the JON console. To fix this problem, the software has been changed to catch NoSuchDeployment exceptions. |