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.
### Description of problem:
JBoss EAP 6.x/JBOSSWEB_7.2.x APR connector does not allow adding system property org.apache.tomcat.util.ENABLE_MODELER=true.
### Version-Release number of selected component (if applicable):
JBOSSWEB_7.2.x in EAP 6.1.0 / EAP 6.1.1 (As far as I check source code, also EAP 6.2.0)
### Steps to Reproduce:
1. Enable APR connector
2. Add system property org.apache.tomcat.util.ENABLE_MODELER=true
3. Start EAP 6
### Actual results:
JBoss start-up fails with the following ERROR.
~~~
ERROR [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003044: Threadpool JMX registration failed: javax.management.MalformedObjectNameException: Invalid character ':' in value part of property
at javax.management.ObjectName.construct(ObjectName.java:618) [rt.jar:1.7.0_25]
at javax.management.ObjectName.<init>(ObjectName.java:1382) [rt.jar:1.7.0_25]
at org.apache.coyote.http11.Http11AprProtocol.start(Http11AprProtocol.java:120) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.connector.Connector.start(Connector.java:1051) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:274) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) 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:277)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
Caused by: LifecycleException: JBWEB000024: Protocol handler start failed
at org.apache.catalina.connector.Connector.start(Connector.java:1053)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:274)
... 5 more
~~~
Expected results:
JBoss start-up without ERROR.
Daniel,
Please open a support ticket from Red Hat Customer Portal[1] for such request. Generally, we will evaluate such request and judge providing an individual patch through support case.
Until this is fixed, please do not set org.apache.tomcat.util.ENABLE_MODELER=true when you are using Native APR connector and NIO connector. Or please use Java connector instead as a workaround. It can be used with org.apache.tomcat.util.ENABLE_MODELER=true.
[1] Red Hat Customer Portal - Open a New Support Case
https://access.redhat.com/support/cases/new/
Comment 10Radim Hatlapatka
2014-05-06 13:43:48 UTC