Bug 779378 (SOA-1768)

Summary: ERROR message shows up when deleting an already deleted esb in JON
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jaroslaw Kijanowski <kijanowski>
Component: Monitoring and ManagementAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER6   
Target Milestone: ---   
Target Release: 5.0.0 GA, 5.0.0 ER8   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1768
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-03 15:36:36 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-04 18:59:01 UTC
Date of First Response: 2010-01-19 08:59:17
project_key: SOA

This is similar to SOA-1698:

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
5. remove this resource in JON - works fine, resource gets uninventored successfully, but this is what I get in the SOA server and JON agent logs:

server log:

13:56:02,838 INFO  [DeployHandler] Stop, [null]
13:56:02,840 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)




agent log:

2010-01-04 13:56:02,748 INFO  [ResourceFactory.executor-1] (rhq.core.pc.inventory.DeleteResourceRunner)- Deleting resource from request: 10013
2010-01-04 13:56:02,857 ERROR [ResourceContainer.invoker.nonDaemon-2] (org.rhq.plugins.jmx.MBeanResourceComponent)- Failed to stop deployment 'null'.
java.lang.RuntimeException: java.lang.NullPointerException
	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:77)
	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)
Caused by: 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)
	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:213)
	at org.jboss.remoting.Client.invoke(Client.java:1917)
	at org.jboss.remoting.Client.invoke(Client.java:768)
	at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.invoke(StreamingDeploymentTarget.java:304)
	... 14 more

Comment 1 Jaroslaw Kijanowski 2010-01-04 18:59:57 UTC
Link: Added: This issue is related to SOA-1698


Comment 2 Kevin Conner 2010-01-19 13:55:17 UTC
Link: Added: This issue depends JBESB-3132


Comment 3 Kevin Conner 2010-01-19 13:59:17 UTC
I have attached a new plugin to the ESB issue which may fix this, could you retest and see if it helps?

If not, do you have a system that I can access?

Comment 4 Jaroslaw Kijanowski 2010-01-19 15:34:37 UTC
Sure, I'll take care

Comment 5 Jaroslaw Kijanowski 2010-01-19 17:54:54 UTC
fixed with the plugin attached to the linked JBESB jira:

jon server log:
2010-01-19 12:51:40,980 INFO  [org.rhq.enterprise.server.resource.ResourceFactoryServerServiceImpl] Received delete resource response: DeleteResourceResponse[RequestId=10002, Status=Success]
2010-01-19 12:51:41,123 INFO  [org.rhq.enterprise.server.resource.ResourceManagerBean] User [org.rhq.core.domain.auth.Subject[id=1,name=admin]] is marking resource [Resource[id=10243, type=Services, key=jboss.esb:category=MessageCounter,deployment=Quickstart_helloworld.esb,service-category=FirstServiceESB,service-name=SimpleListener, name=SimpleListener Service, parent=Quickstart_helloworld.esb, version=5.0.0.ER7]] for asychronous deletion


agent log:
2010-01-19 12:51:40,946 INFO  [ResourceFactory.executor-1] (rhq.core.pc.inventory.DeleteResourceRunner)- Deleting resource from request: 10002


Comment 6 Kevin Conner 2010-01-19 17:58:41 UTC
Fantastic, thanks for the verification.

Comment 7 Jaroslaw Kijanowski 2010-02-03 15:36:36 UTC
Verified in ER8