Red Hat Bugzilla – Bug 1271521
ovirt-engine service cannot detect jboss version if service already run and debug port enabled
Last modified: 2016-02-18 06:22:40 EST
we need to set debug port only for the actual instance.
ovirt-engine 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 ERROR run:532 Error: Cannot detect JBoss version
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.
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.
Should this be MODIFIED?