Bug 1271521

Summary:	ovirt-engine service cannot detect jboss version if service already run and debug port enabled
Product:	[oVirt] ovirt-engine	Reporter:	Alon Bar-Lev <alonbl>
Component:	Services	Assignee:	Martin Perina <mperina>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ondra Machacek <omachace>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	bugs, didi, gklein, iheim, lveyde, mperina, rmartins, sbonazzo, stirabos
Target Milestone:	ovirt-3.6.1	Keywords:	CodeChange
Target Release:	3.6.1	Flags:	sbonazzo: ovirt-3.6.z? rule-engine: planning_ack? sbonazzo: devel_ack+ pstehlik: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-18 11:22:40 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alon Bar-Lev 2015-10-14 08:18:29 UTC

we need to set debug port only for the actual instance.

---
ovirt-engine[22164] DEBUG _detectJBossVersion:240 Return code: -6, 
stdout: '[u'FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)'], 
stderr: '[u'ERROR: transport error 202: bind failed: Address already in use', u'ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)', u'JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]']'
ovirt-engine[22164] ERROR run:532 Error: Cannot detect JBoss version
---

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 11:03:16 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Yaniv Lavi 2015-10-29 12:42:39 UTC

In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.

Comment 3 Yaniv Lavi 2015-11-02 15:10:31 UTC

Should this be MODIFIED?