Bug 920229

Summary:	[IPv6] web http connector is incorrectly discovered
Product:	[JBoss] JBoss Operations Network	Reporter:	Libor Zoubek <lzoubek>
Component:	Plugin -- JBoss EAP 6	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED EOL	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	theute
Target Milestone:	---
Target Release:	JON 4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-24 15:06:11 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:
Bug Depends On:
Bug Blocks:	919199

Description Libor Zoubek 2013-03-11 15:41:57 UTC

Version-Release number of selected component (if applicable):
JON 3.2.0.Alpha + EAP 6.0.GA

How reproducible:always


Steps to Reproduce:
1. start EAP6 standalone listening on IPv6 : standalone.sh -Djava.net.preferIPv4Stack=false -bmanagement ::1
2. Import it
3. navigate to web->http, open up configuration
  
Actual results:there are errors, missing default values, This is the result of fact, that http connector is discovered as jca connector, which has different config properties


Expected results: http connector configuration contains no errors


Additional info:

Comment 1 Libor Zoubek 2013-03-11 15:43:07 UTC

Errors reported by opening http connector configuration	

The following configuration properties have invalid values: [Default Workmanager Short Running Thread Pool, Default Workmanager Long Running Thread Pool, Bean Validation Enabled, Archive Validation Enabled]. The values must be corrected before the configuration can be saved.

Comment 4 Filip Brychta 2019-06-24 15:06:11 UTC

JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.