-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
Future GA, A-MQ 7.0.0.ER14
-
None
-
Compatibility/Configuration
Make broker/xml unparsable (create error anywhere).
Start it as a service and notice, that no error is reported and even PID is printed.
Although, the broker is actually dead.
su - jamq -c "/opt/artemis-200-i0/bin/artemis-service restart"Restarting artemis-service
artemis-service is now running (28117)
[0,root@r7x1_mtoth opt]$ ps uax |grep java
root 28142 0.0 0.0 112648 924 pts/1 R+ 10:57 0:00 grep --color=auto java
[jamq@dhcp-lab-254 artemis-200-i0]$ /opt/artemis-200-i0/bin/artemis run [Fatal Error] :253:18: The end-tag for element type "address" must end with a '>' delimiter. Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 253; columnNumber: 18; The end-tag for element type "address" must end with a '>' delimiter. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339) at org.apache.activemq.artemis.utils.XMLUtil.readerToElement(XMLUtil.java:89) at org.apache.activemq.artemis.utils.XMLUtil.stringToElement(XMLUtil.java:55) at org.apache.activemq.artemis.core.config.FileDeploymentManager.readConfiguration(FileDeploymentManager.java:76) at org.apache.activemq.artemis.cli.commands.Configurable.getFileConfiguration(Configurable.java:93) at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:64) at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:130) at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:87) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129) at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49)
I am strongly convinced this issue is in ER13 and earlier brokers as well.
- is related to
-
ENTMQBR-524 Artemis-service is not returning correct error codes / does not detect broker failures
- Closed