Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 817519

Summary: [ovirt-dwh] - jbossas cannot start (ETL occupies port 8080)
Product: [Retired] oVirt Reporter: David Botzer <dbotzer>
Component: ovirt-engine-dwhAssignee: Yaniv Lavi <ylavi>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: acathrow, dyasny, iheim, mgoldboi, pstehlik, ykaul
Target Milestone: ---   
Target Release: 3.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-09 07:56:25 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:
Embargoed:
Attachments:
Description Flags
server.log none

Description David Botzer 2012-04-30 11:42:46 UTC
Created attachment 581171 [details]
server.log

Description of problem:
When restarting JBOSSAS service it cannot be started,
port said to be busy 8080 --< This happnes immidiatly

Only when I stop ovirt-etl I can start the jbossas

Version-Release number of selected component (if applicable):
ovirt-engine-3.1.0_0001-6.el6ev.x86_64
ovirt-dwh-3.0.0-1.fc16.noarch

How reproducible:
Always

Steps to Reproduce:
1.Make sure jboss and ETL are both started
2.Stop jboss
3.Start Jboss
  
Actual results:
JBOSSAS service cannot start
I get the following message instantly
"Port 8080 is busy, is there a Tomcat running?"

Expected results:
Should start correctly.

Additional info:
No logs in server.log (jboss log)

Comment 1 Yaniv Lavi 2012-05-23 13:57:26 UTC
Fixed in patch:
http://gerrit.ovirt.org/4705


Yaniv

Comment 2 Itamar Heim 2012-08-09 07:56:25 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/