Project: talendesb
Issue TESB-3856: ActiveMQ should not be automatically active when starting the TESB container
After start-up of a TESB container activemq is active and running. I doubt that this is a good idea. Infrastructure components like SAM server, the backend database (derby), Zookeeper or similar should not be up and running automatically when the container is been started. And they are not. In my view this should also regard to activemq. There can be more than one container installation within an environment (even a single host). And there also should only be one infrastructure service (if it is not clustered... which is a completely different story). The user should not be forced to shutdown unwanted infrastructure services within the container after start-up. It would be a better approach to let the user explicitly start the infrastructure services he needs in whatever container instance(s) he wants them to run. This should also regard to activemq in both editions TESB SE and TESB EE.
Story points: 1