Bug 900775 (JBPAPP6-872)

Summary:	JBoss EAP6.0 GA does not allow adding system property org.apache.tomcat.util.ENABLE_MODELER=true
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Jay SenSharma <jsenshar>
Component:	JMX	Assignee:	Tom WELLS <twells>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	aogburn, jfclere, jsenshar, lcarlon, sjadhav, tfonteyn, twells
Target Milestone:	---
Target Release:	EAP 6.0.1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBPAPP6-872
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-10-19 00:02:39 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:

Description Jay SenSharma 2012-08-07 11:16:23 UTC

Affects: Release Notes
SourceForge Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000Asd1t&sfdc.override=1
Steps to Reproduce: Step1). In EAP6.0 GA Enable the following system property in standalone-full.xml

~~~
<system-properties>
    <property name="org.apache.tomcat.util.ENABLE_MODELER" value="true"/>
</system-properties>
~~~

Step2). Simply restart JBoss EAP6.0 GA 
project_key: JBPAPP6

After Enabling the System property in "standalone.xml" or "standalone-full.xml"  in order to access the "jboss.web:type=*" mbeans through JConsole or using jmx client code  JBoss EAP6.0.0 GA  is not booting up where as the same thing is working perfectly fine in "JBoss EAP6 beta1 (JBossAS7.1.0 and JBoss AS7.1.1)   the issue is seen only in JBoss EAP6.0 GA"

~~~
<system-properties>
    <property name="org.apache.tomcat.util.ENABLE_MODELER" value="true"/>
</system-properties>
~~~


After enabling the above mentioned properties we get the following error while booting the JBoss EAP6.0 GA

~~~
10:35:14,337 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-8) Can't register endpoint
10:35:14,354 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
	at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
Caused by: LifecycleException:  service.getName(): "jboss.web";  Protocol handler start failed: javax.management.MalformedObjectNameException: Invalid character ':' in value part of property
	at org.apache.catalina.connector.Connector.start(Connector.java:1065)
	at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:268)
	... 5 more
~~~

Comment 1 Jean-Frederic Clere 2012-08-09 15:07:45 UTC

Fix in jbossweb by r2059. You need the tag 7.0.17.Final

Comment 2 Tom WELLS 2012-10-04 10:29:46 UTC

Does this need a release note for EAP 6.0.1? The issue needs to be re-opened if it does, and the release notes flags set (Affects Release Notes, Not Yet Documented).

Comment 3 Jean-Frederic Clere 2012-10-04 10:59:29 UTC

Probably so that the customer gets the information it has been fixed.

Comment 4 Jean-Frederic Clere 2012-10-04 11:01:35 UTC

Affects: Added: Release Notes

Comment 5 Jean-Frederic Clere 2012-10-04 11:02:07 UTC

Release Notes Docs Status: Added: Not Yet Documented

Comment 6 Dana Mison 2012-10-16 06:19:54 UTC

Writer: Added: tomwells

Comment 7 Tom WELLS 2012-10-19 00:02:08 UTC

Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: When enabled, the system property org.apache.tomcat.util.ENABLE_MODELER was causing an error that prevented JBoss Enterprise Application Platform 6 from booting. This was because the name of the connector was not consistent with JMX naming requirements. The name of the connector has been changed, and the property now performs as expected.

Comment 8 Anne-Louise Tangring 2012-11-13 20:07:41 UTC

Release Notes Docs Status: Removed: Documented as Resolved Issue 
Writer: Removed: tomwells 
Release Notes Text: Removed: When enabled, the system property org.apache.tomcat.util.ENABLE_MODELER was causing an error that prevented JBoss Enterprise Application Platform 6 from booting. This was because the name of the connector was not consistent with JMX naming requirements. The name of the connector has been changed, and the property now performs as expected. 
Docs QE Status: Removed: NEW