Details
-
Bug
-
Resolution: Obsolete
-
Minor
-
None
-
AMQ 7.5.0.GA, AMQ 7.6.0.GA
-
None
Description
When one of the "persistent" OpenShift templates for AMQ 7.5 is deployed into a project/namespace containing two hyphens --, the AMQ Console fails to start with an error:
[Fatal Error] :26:84: The string "--" is not permitted within comments.
This is because the pod's full hostname is inserted into a comment in jolokia-access.xml. In the case of a statefulset, this includes the pod's namespace which contains the invalid string.
sh-4.2$ hostname -f
broker-amq-0.broker-amq-headless.rhsm--prototype.svc.cluster.local
sh-4.2$ cat ~/broker/etc/jolokia-access.xml
<?xml version="1.0" encoding="utf-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!-- This policy file controls the Jolokia JMX-HTTP bridge security options for the web console.
see: https://jolokia.org/reference/html/security.html -->
<restrict>
<cors>
<!-- Allow cross origin access from broker-amq-0.broker-amq-headless.rhsm--prototype.svc.cluster.local ... -->
<allow-origin>*://broker-amq-0.broker-amq-headless.rhsm--prototype.svc.cluster.local*</allow-origin>
<!-- Options from this point on are auto-generated by Create.java from the Artemis CLI -->
<!-- Check for the proper origin on the server side, too -->
</cors>
</restrict>
Can the template for jolokia-access.xml be updated so that the pod's hostname is not substituted in that comment?
