Bug 788554 - [eap6] NPE when deploying to server group
Summary: [eap6] NPE when deploying to server group
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: RHQ Project
Classification: Other
Component: Agent, Plugins
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: ---
Assignee: Heiko W. Rupp
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: as7-plugin
TreeView+ depends on / blocked
 
Reported: 2012-02-08 13:02 UTC by Libor Zoubek
Modified: 2015-11-02 00:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-14 15:25:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Libor Zoubek 2012-02-08 13:02:48 UTC
Description of problem: I got NPE when I try to deploy war having on HC to server group


Version-Release number of selected component (if applicable):
Version: 4.3.0-SNAPSHOT
Build Number: b4761de
EAP6 DR12

How reproducible:always


Steps to Reproduce:
1. inventory eap6 DomainController
2. deploy war to DomainController using JON
3. wait 'till war is discovered, deploy it to server group (using Operations tab on that war)
  
Actual results: operation fails

2012-02-08 13:50:06,128 DEBUG [OperationManager.invoker-1] (rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler)- Call 
to [org.rhq.modules.plugins.jbossas7.DomainDeploymentComponent.invokeOperation()] with args [[domain-deployment:promote, Configuration[id=1336
6]]] failed.
java.util.concurrent.ExecutionException: java.lang.NullPointerException
        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:262)
        at java.util.concurrent.FutureTask.get(FutureTask.java:119)
        at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:473)
        at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invoke(ResourceContainer.java:461)
        at $Proxy96.invokeOperation(Unknown Source)
        at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:217)
        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)
Caused by: java.lang.NullPointerException
        at org.rhq.modules.plugins.jbossas7.BaseComponent.invokeOperation(BaseComponent.java:594)
        at org.rhq.modules.plugins.jbossas7.DeploymentComponent.invokeOperation(DeploymentComponent.java:69)
        at sun.reflect.GeneratedMethodAccessor165.invoke(Unknown Source)
        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:552)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        ... 3 more



Expected results:


Additional info: This must have been introduced by some recent commit, it did not happen, on yesterday's build

Comment 1 Heiko W. Rupp 2012-02-08 13:26:21 UTC
Not sure from when your build is 

Interesting as no activity in git has happened since last week until hudson build 963, which is one version after the one you have.

I'll look into it.

Comment 2 Heiko W. Rupp 2012-02-08 14:02:53 UTC
Could it be that the server was not reachable?
Can you still reproduce the agent.log for said time?

Comment 3 Libor Zoubek 2012-02-08 15:16:56 UTC
I'll try to repro again, tests are running, I'll wait for results and check again

Comment 5 Libor Zoubek 2012-02-08 18:15:10 UTC
Yes, it was because of server was not reachable. In fact, I had a bug in script setting cleaning EAP instances, and there were 4 domain controllers running trying to listen on same ports. So unless we want as7 plugin to be more robust, I'd propose this as NOTABUG


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