SonicMQ 8.5 - Scripting Shutdown of Containers

Posted by lozonjh on 09-Apr-2014 18:20

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?

Posted by Srinivas Munigala on 10-Apr-2014 00:44

Hi lozonjh,
 
We use the following script to shutdown an ESB Container, it shuts down the container in SMC as well as the Java process:
 
echo "connect Domain1 tcp://localhost:2506 Administrator Administrator" > stopCntnr.txt
echo "container shutdown testContainer" >>  stopCntnr.txt
echo "Disconnect"                       >> stopCntnr.txt
echo "bye"                      >> stopCntnr.txt
 
$SONIC_HOME/ESB$SONICVER/bin/esbadmin.sh < stopCntnr.txt
 
Thanks,
Srinivas Munigala.
 
[collapse]
From: lozonjh [mailto:bounce-lozonjh@community.progress.com]
Sent: Thursday, April 10, 2014 4:51 AM
To: TU.OE.Tech.Partner@community.progress.com
Subject: SonicMQ 8.5 - Scripting Shutdown of Containers
 
Thread created by lozonjh

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?

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

All Replies

Posted by Srinivas Munigala on 10-Apr-2014 00:44

Hi lozonjh,
 
We use the following script to shutdown an ESB Container, it shuts down the container in SMC as well as the Java process:
 
echo "connect Domain1 tcp://localhost:2506 Administrator Administrator" > stopCntnr.txt
echo "container shutdown testContainer" >>  stopCntnr.txt
echo "Disconnect"                       >> stopCntnr.txt
echo "bye"                      >> stopCntnr.txt
 
$SONIC_HOME/ESB$SONICVER/bin/esbadmin.sh < stopCntnr.txt
 
Thanks,
Srinivas Munigala.
 
[collapse]
From: lozonjh [mailto:bounce-lozonjh@community.progress.com]
Sent: Thursday, April 10, 2014 4:51 AM
To: TU.OE.Tech.Partner@community.progress.com
Subject: SonicMQ 8.5 - Scripting Shutdown of Containers
 
Thread created by lozonjh

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?

Stop receiving emails on this subject.

Flag this post as spam/abuse.

[/collapse]

This thread is closed