Bug 849779

+++ This bug was initially created as a clone of Bug #830841 +++

Description of problem:
CLI retrieveBackingContent gives a nullPointerException for 10 minutes after resource was imported. Than it's working fine.

Version-Release number of selected component (if applicable):
3.1.0.GA

How reproducible:
Always

Steps to Reproduce:
1.have a clean JON installation with eap plugin, the eap5 is running in default profile
2.import eap5 to JON inventory
3.create a new child resource (web application) in eap5 (eap5 inventory>create child>web application)
4.find id of this web application
5.launch CLI client in interactive mode (/rhq-cli.sh -u rhqadmin -p rhqadmin)
6.execute following commands:
var webApp = ProxyFactory.getResource(10062);// put there correct resourceId
webApp.retrieveBackingContent("/tmp/webApp.war");

  
Actual results:
Wrapped java.lang.NullPointerException (<Unknown source>#1)
res.retrieveBackingContent("/tmp/neco.war") 
^

Found no errors in logs.

Expected results:
Content is saved to defined location.

Additional info:
NullPointerException is there approximately for next 10 minutes (probably until some periodical job is launched). 

Different approach to reproduce this error:
1- uninventory eap5
2- inventory eap5
3- follow previous scenario from step 4

--- Additional comment from lzoubek on 2012-07-18 05:20:34 EDT ---

I am having same issue with EAP6 and I am able to reproduce it either using UI:
1. import EAP6
2. create deployment child resource
3. wait till it gets discovered
4. check new resoruce's content tab

Both Deployed and History are empty. If I refresh after 2-3 minutes I get expected values. IMHO Once a new deployment resource is discovered and UP it's backing content should be available.

--- Additional comment from ccrouch on 2012-08-02 19:05:40 EDT ---

We are unlikely to be able to speed the discovery process up as part of jon311 but we should hopefully be able to address the NPE

--- Additional comment from snegrea on 2012-08-20 16:19:49 EDT ---

The error was due to the fact that content was not yet available in the content repository when #retrieveBackingContent() was called. Added a descriptive error message to inform the user about this. Also, the message asks the user to try again in a few minutes since the content for a resource is available only after the deployment and discovery process completes.

There is no way to speed the discovery or to make the content available for users before the deployment and discovery process completes.