Kafka InstanceAlreadyExistsException

I recognize that this problem is unlikely to be related to Axon explicitly but at the moment we’re scratching our heads to the root cause.
In our local environment everything as expected. When we push the same application to PCF. The first event that’s fired causes the following error:
2019-02-08T16:01:49.97-0500 [APP/PROC/WEB/0] OUT 2019-02-08 21:01:49.971 INFO 16 --- [nio-8080-exec-7] o.a.kafka.common.utils.AppInfoParser : Kafka version : 1.0.2 2019-02-08T16:01:49.97-0500 [APP/PROC/WEB/0] OUT 2019-02-08 21:01:49.971 INFO 16 --- [nio-8080-exec-7] o.a.kafka.common.utils.AppInfoParser : Kafka commitId : 2a121f7b1d402825 2019-02-08T16:01:49.97-0500 [APP/PROC/WEB/0] OUT 2019-02-08 21:01:49.973 WARN 16 --- [nio-8080-exec-7] o.a.kafka.common.utils.AppInfoParser : Error registering AppInfo mbean 2019-02-08T16:01:49.97-0500 [APP/PROC/WEB/0] OUT javax.management.InstanceAlreadyExistsException: kafka.producer:type=app-info,id=a73701f6-19db-4913-821e-adba73eb07db 2019-02-08T16:01:49.97-0500 [APP/PROC/WEB/0] OUT at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) ~[na:1.8.0_192] 2019-02-08T16:01:49.97-0500 [APP/PROC/WEB/0] OUT at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) ~[na:1.8.0_192]

We have only a single instance of Kafka and only a single instance of the application. Which eliminates most theories.
Client-id is heavily referenced when searching online but is randomly generated in our application.yml which is as follows:

axon:
  kafka:
    default-topic: axon-events
    producer:
      retries: 5
      transaction-id-prefix: esstx
    consumer:
      group-id: external-sync-group
    client-id: ${random.uuid}
    bootstrap-servers: ${KAFKA_URL}:9092
  distributed:
    enabled: true
  serializer:
    messages: jackson
    events: jackson
    general: jackson
  eventhandling:
    processors:
      syncsaga:
        mode: tracking
        source: kafkaMessageSource

I’m hoping someone will provide clarity to where mistakes have been made and why we are seeing this issue, If you require the full stake trace I can provide as well.

Thank you!