Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1065352 - It takes up to 8 minutes for a new EAP6 deployment to become UP
Summary: It takes up to 8 minutes for a new EAP6 deployment to become UP
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Content, Plugins
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
Depends On:
TreeView+ depends on / blocked
Reported: 2014-02-14 13:01 UTC by Filip Brychta
Modified: 2014-02-25 15:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)
deployment (deleted)
2014-02-14 13:01 UTC, Filip Brychta
no flags Details

Description Filip Brychta 2014-02-14 13:01:08 UTC
Created attachment 863274 [details]

Description of problem:
When you create a new EAP6 deployment (Create Child->Deployment) it takes > 7 minutes until the deployment is reported as UP when oracle DB is used. For postgresql it is lest then 2 minutes.

I tried it 3 times with similar results.

There are no exceptions in RHQ server or agent log.

Version-Release number of selected component (if applicable):
Version :	
Build Number :	

How reproducible:

Steps to Reproduce:
1. set up oracle xe according to RHQ installation manual
2. install and start RHQ + EAP6 standalone
3. deploy attached war (navigate to eap6 resource->Inventory->Create Child->Deployment)
4. wait until the deployment become UP

Actual results:
It takes more than 7 minutes which is comparing to postgresql ~4 times more

Expected results:
Similar result like for postgresql

Additional info:
Agent's Availability scan operation doesn't change status of the deployment, but 'avail -f' does.

Comment 1 Filip Brychta 2014-02-25 15:32:29 UTC
This issue is probably not related to Oracle directly. It took > 5 minutes on postgresql as well. After discussion with jkremser and lkrejci following could be a cause:
Avail scan scheduled specially for newly created resource is missed and the resource stays in status UNKNOWN until the regular avail scan is launched which could take up to 10 minutes.

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