When trying to run *-ssl template flavour or configuring deployment from test code. I can see that readiness probe script is complaining the there's no process listening on SSL ports 61617,...

Readiness probe failed: No transport listening on ports 61617 5672 61613 8883

From the broker's log there're only non-ssl acceptors listed on boot.

Imho this definition substituted by launch.sh script seems a bit problematic. I haven't found any clear evidence that acceptor name should be unique in AMQ broker docs, but it's rather suspicious.

https://github.com/jboss-container-images/jboss-amq-7-broker-openshift-image/blob/amq-broker-71-dev/modules/amq-launch/added/launch.sh#L75