Bug 831193 - [ovirt-engine-core] Engine should not use the same ports that JBoss uses by default
Summary: [ovirt-engine-core] Engine should not use the same ports that JBoss uses by d...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: unspecified
Hardware: x86_64
OS: Linux
high
unspecified
Target Milestone: ---
: 3.2
Assignee: Juan Hernández
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks: 852365
TreeView+ depends on / blocked
 
Reported: 2012-06-12 13:04 UTC by Kiril Nesenko
Modified: 2014-07-11 00:08 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 852365 (view as bug list)
Environment:
Last Closed: 2013-02-15 06:47:40 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Kiril Nesenko 2012-06-12 13:04:45 UTC
Description of problem:
When starting ovirt-engine service it fails to start becuase it tries to use the same ports as jboss.
Engine should not use the same ports that JBoss uses by default. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Itamar Heim 2012-06-12 19:26:32 UTC
not sure this is a high priority.
for now we can release note not to start jbossas service on a machine running ovirt service.

Comment 2 David Botzer 2012-06-17 07:34:12 UTC
How will this affect the work with Reporting Tool ? 
And DWH ?

Dont these two need jboss ?

Comment 3 Juan Hernández 2012-07-16 18:39:50 UTC
The proposed change to fix this bug is here:

http://gerrit.ovirt.org/6348

Comment 4 Juan Hernández 2012-08-28 08:14:30 UTC
The proposed change has been merged upstream:

http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=f493d1945a71d9def9075fb945c99a9d86f6bd30

The default ports are the following now:

http: 8700
https: 8701
ajp: 8702
remoting: 8703
txn-recovery: 8704
txn-status: 8705

Comment 5 Itamar Heim 2013-01-16 16:10:05 UTC
3.2 beta built, moving to ON_QA status to allow testing


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