JBoss EAP 4.3 throws errors about missing tags when ports-03 binding set is used.
Issue
- Edited
$JBOSS_HOME/$profile/conf/jboss-service.xmlto use the service binding manager for ports-03 - Errors are thrown at launch.
15:41:59,359 ERROR [STDERR] [Fatal Error] :35:15: The element type "config" must be terminated by the matching end-tag "</config>".
15:41:59,370 WARN [ServiceConfigurator] Failed to apply service binding override
org.jboss.util.NestedRuntimeException: The element type "config" must be terminated by the matching end-tag "</config>".; - nested throwable: (org.xml.sax.SAXParseException: The element type "config" must be terminated by the matching end-tag "</config>".)
at org.jboss.util.propertyeditor.DocumentEditor.getAsDocument(DocumentEditor.java:88)
at org.jboss.util.propertyeditor.ElementEditor.setAsText(ElementEditor.java:41)
at org.jboss.services.binding.AttributeMappingDelegate.createAtribute(AttributeMappingDelegate.java:169)
at org.jboss.services.binding.AttributeMappingDelegate.applyConfig(AttributeMappingDelegate.java:130)
at org.jboss.services.binding.ServiceBindingManager.applyServiceConfig(ServiceBindingManager.java:270)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
Environment
- JBoss Enterprise Application Platform (EAP)
- 4.3.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.