Hi user group: If you ever want to run activemq under daemontools control you cannot simply use /opt/activemq/bin/activemq start in your run script. If you use the normal start you will notice a defunct process every second or so and it can drive you nuts. If you setup activemq to be under daemontools you obviously need something like a /services/activemqservice/rub script. In the run script for activemq instead of /opt/activemq/bin/activemq start replace it with /opt/activemq/bin/activemq console.
If youn use the normal 'start' mode, /opt/activemq/bin/activemq will exit after starting the activemq jar file. That makes the daemontools supervise to think the program exited and it will restart. So use console mode to avoid the constant cycle of activemq script cycle Thanks Mukund
