I'm looking for information on how to shut down containers in SonicMQ 8.5 in a scripted fashion from a Linux environment. Thus far we've been able to create a script using the ESB Admin 8.5 tool to generate a container list which then goes through and runs the 'container shutdown containername' commands, but we find that even though the containers appear to shut down in Sonic Management Console, there are still Java processes running on Linux for those containers.
Are we going about this the wrong way, or does anyone have any ideas on why shutting down the container would not also shut down the Java pieces for that container on the backend?
I'm looking for information on how to shut down containers in SonicMQ 8.5 in a scripted fashion from a Linux environment. Thus far we've been able to create a script using the ESB Admin 8.5 tool to generate a container list which then goes through and runs the 'container shutdown containername' commands, but we find that even though the containers appear to shut down in Sonic Management Console, there are still Java processes running on Linux for those containers.
Are we going about this the wrong way, or does anyone have any ideas on why shutting down the container would not also shut down the Java pieces for that container on the backend?
Flag this post as spam/abuse.
I'm looking for information on how to shut down containers in SonicMQ 8.5 in a scripted fashion from a Linux environment. Thus far we've been able to create a script using the ESB Admin 8.5 tool to generate a container list which then goes through and runs the 'container shutdown containername' commands, but we find that even though the containers appear to shut down in Sonic Management Console, there are still Java processes running on Linux for those containers.
Are we going about this the wrong way, or does anyone have any ideas on why shutting down the container would not also shut down the Java pieces for that container on the backend?
Flag this post as spam/abuse.