Bug 779310 (SOA-1698) - Removing an esb archive in the admin console makes it immortal in JON
Summary: Removing an esb archive in the admin console makes it immortal in JON
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1698
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Monitoring and Management
Version: 5.0.0 ER5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-09 17:00 UTC by Jaroslaw Kijanowski
Modified: 2010-01-04 18:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-04 18:59:34 UTC
Type: Bug


Attachments (Terms of Use)
delete.jpg (201.46 KB, image/jpeg)
2009-12-15 20:45 UTC, tcunning
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779378 0 high CLOSED ERROR message shows up when deleting an already deleted esb in JON 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1698 0 None None None Never

Internal Links: 779378

Description Jaroslaw Kijanowski 2009-12-09 17:00:06 UTC
Date of First Response: 2009-12-15 15:45:55
project_key: SOA

I have deleted an esb archive using the admin console. It gets undeployed properly and disappears in the admin console.

In JON it shows up as DOWN, so far so good.

Now I try to remove this resource also in JON and end up with following failure:

===================================

java.lang.Exception: Failed to stop deployment 'null' - cause: java.lang.RuntimeException: java.lang.NullPointerException
	at org.jbosson.plugins.jbossesb.ESB5DeploymentComponent.deleteResource(ESB5DeploymentComponent.java:82)
	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.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)

===================================

SOA-P server log:

11:54:56,458 INFO  [DeployHandler] Stop, [null]
11:54:56,459 INFO  [DeployHandler] Failed to complete command: [stop] for deployment: names=[null]
java.lang.NullPointerException
	at java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:782)
	at org.jboss.profileservice.management.upload.remoting.DeployHandler.resolveDeploymentName(DeployHandler.java:215)
	at org.jboss.profileservice.management.upload.remoting.DeployHandler.scheduleStop(DeployHandler.java:145)
	at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.stop(AbstractDeployHandler.java:338)
	at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.stop(AbstractDeployHandler.java:327)
	at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:211)
	at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:897)
	at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:768)
	at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:721)
	at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548)
	at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)

Comment 1 Kevin Conner 2009-12-14 13:51:34 UTC
Link: Added: This issue depends JBESB-3054


Comment 2 tcunning 2009-12-15 20:45:55 UTC
Tried to reproduce this and I'm having a hard time.     Uploaded a "Quickstart_helloworld.esb" into JON and then tried to delete it in JON - the delete was successful and the ESB file is no longer displayed.    Am I missing steps here?

Comment 3 tcunning 2009-12-15 20:45:55 UTC
Attachment: Added: delete.jpg


Comment 4 Jaroslaw Kijanowski 2009-12-15 21:53:15 UTC
Yep :)
So here's a more detailed list how to reproduce:

1. deploy some QS, make sure it gets discovered in JON
2. go to the *admin-console* (jopr) and delete this QS
3. make sure it gets undeployed
4. go to the JON console and verify that the resource is DOWN

and now:

5. try to remove this resource in JON - no way, this command tries to stop a resource that is no longer available, I guess.

Comment 5 Kevin Conner 2009-12-16 09:40:21 UTC
Can you attach a log file so that we can see what is going on?

From the initial report it looks like this may actually be an issue in JON but the logs can probably show us for definite.

Kev


Comment 6 tcunning 2009-12-17 04:58:34 UTC
JON is now uninventorying the ESB deployment in this instance.       Fix should go into ER6.

Comment 7 Jaroslaw Kijanowski 2010-01-04 18:59:34 UTC
Verified in ER6 - works with zipped and exploded archives.

Comment 8 Jaroslaw Kijanowski 2010-01-04 18:59:57 UTC
Link: Added: This issue related SOA-1768



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