[Migrated content. Thread originally posted on 01 March 2012]
Our environment: Windows XP server 2003 and windows only platform.
This has abeen a thorn for over a year where neither support nor my staff have nee able to come up with an acceptable resolution. Let me clarify my staff: 2 cobol programmers thrown into dot net, networking, dba etc in other words clueless. In that year we've learned a lot. Suppoprts answer to the problem was to run a utility against one the existing cascd processes in a DOS command window where the result would be the region name. However, in our case rarely do we have a cascd or casmgr running in task manager. We/support have not figured that out, but it also leaves anywhere from 1 to hundreds of "cassi" processes to be terminated. SO the question remains, how do you tell when a region is running or not. I have discovered a microsoft command called "NETSTAT" which will show active connections. Actually it shows the connection's IP and listener ports. Since we already know the ports because we have to identofy the ports on the admin page. A simple script to execute the dos command "netstat -a" list is produced and a perusal for known or missing ports tells you what regions are up or down.
I thought I'd pass this simple solution on for anyone else that may end up with this problem because support and I Have spent over a year trying to resolve the problem.
If some one has another perspective on a resolution, I would appreciate a response and your example.
#EnterpriseDeveloperIf the cascd or casmgr process isn't running, then the region isn't running. They're mandatory. If other processes from that region are still around, then those are orphaned processes and the region did not shut down cleanly; Customer Care should have opened an RPI for the appropriate development team, and asked you to collect diagnostics.
netstat is sometimes OK as a heuristic for determining what regions are running, but it has a lot of limitations. Only one region process (mfcs) holds TCP/IP sockets, so if it's gone, netstat won't show you anything for that region; you might still have orphaned cassi, castsc, and other processes. If you're not using fixed port assignments, then you can't tell much from the netstat port output. And nothing prevents non-ES processes from binding to those same ports, so netstat can give you false positives.
If the problem you're dealing with is actually "I have a bunch of cassi.exe processes and I need to know what region they belong to", then querying process data is the only reliable way to answer that. Task Manager and tasklist.exe don't give you enough information, so your choices are third-party tools or the WMI interface.
Some people like the wmic command for this purpose. For example:
wmic PROCESS get Caption,Commandline,Processid /format:list | findstr /i cassi
[Migrated content. Thread originally posted on 01 March 2012]
Our environment: Windows XP server 2003 and windows only platform.
This has abeen a thorn for over a year where neither support nor my staff have nee able to come up with an acceptable resolution. Let me clarify my staff: 2 cobol programmers thrown into dot net, networking, dba etc in other words clueless. In that year we've learned a lot. Suppoprts answer to the problem was to run a utility against one the existing cascd processes in a DOS command window where the result would be the region name. However, in our case rarely do we have a cascd or casmgr running in task manager. We/support have not figured that out, but it also leaves anywhere from 1 to hundreds of "cassi" processes to be terminated. SO the question remains, how do you tell when a region is running or not. I have discovered a microsoft command called "NETSTAT" which will show active connections. Actually it shows the connection's IP and listener ports. Since we already know the ports because we have to identofy the ports on the admin page. A simple script to execute the dos command "netstat -a" list is produced and a perusal for known or missing ports tells you what regions are up or down.
I thought I'd pass this simple solution on for anyone else that may end up with this problem because support and I Have spent over a year trying to resolve the problem.
If some one has another perspective on a resolution, I would appreciate a response and your example.
#EnterpriseDeveloperi thought there were other resonses on this thread but i dont see any.
While you'd think that if you dont see a casmgr (out of 2 that should be showing) in the tasklist, the service and application are not running however the service is running. We have it happen. While writing vbs or c# to parse and peruse the cassi's may be the ultimate correct thing to do, for us the netstat command is at least showing who owns the displaying casmgr. What we've done is written a c# to read the console logs and compare that to the task manager list, so we know who started what and therefore we have a basic knowledge of what to kill. netstat may not be the perfect tool but its cheaper than 3rd party pkgs.
[Migrated content. Thread originally posted on 01 March 2012]
Our environment: Windows XP server 2003 and windows only platform.
This has abeen a thorn for over a year where neither support nor my staff have nee able to come up with an acceptable resolution. Let me clarify my staff: 2 cobol programmers thrown into dot net, networking, dba etc in other words clueless. In that year we've learned a lot. Suppoprts answer to the problem was to run a utility against one the existing cascd processes in a DOS command window where the result would be the region name. However, in our case rarely do we have a cascd or casmgr running in task manager. We/support have not figured that out, but it also leaves anywhere from 1 to hundreds of "cassi" processes to be terminated. SO the question remains, how do you tell when a region is running or not. I have discovered a microsoft command called "NETSTAT" which will show active connections. Actually it shows the connection's IP and listener ports. Since we already know the ports because we have to identofy the ports on the admin page. A simple script to execute the dos command "netstat -a" list is produced and a perusal for known or missing ports tells you what regions are up or down.
I thought I'd pass this simple solution on for anyone else that may end up with this problem because support and I Have spent over a year trying to resolve the problem.
If some one has another perspective on a resolution, I would appreciate a response and your example.
#EnterpriseDeveloperi thought there were other resonses on this thread but i dont see any.
While you'd think that if you dont see a casmgr (out of 2 that should be showing) in the tasklist, the service and application are not running however the service is running. We have it happen. While writing vbs or c# to parse and peruse the cassi's may be the ultimate correct thing to do, for us the netstat command is at least showing who owns the displaying casmgr. What we've done is written a c# to read the console logs and compare that to the task manager list, so we know who started what and therefore we have a basic knowledge of what to kill. netstat may not be the perfect tool but its cheaper than 3rd party pkgs.
[Migrated content. Thread originally posted on 01 March 2012]
Our environment: Windows XP server 2003 and windows only platform.
This has abeen a thorn for over a year where neither support nor my staff have nee able to come up with an acceptable resolution. Let me clarify my staff: 2 cobol programmers thrown into dot net, networking, dba etc in other words clueless. In that year we've learned a lot. Suppoprts answer to the problem was to run a utility against one the existing cascd processes in a DOS command window where the result would be the region name. However, in our case rarely do we have a cascd or casmgr running in task manager. We/support have not figured that out, but it also leaves anywhere from 1 to hundreds of "cassi" processes to be terminated. SO the question remains, how do you tell when a region is running or not. I have discovered a microsoft command called "NETSTAT" which will show active connections. Actually it shows the connection's IP and listener ports. Since we already know the ports because we have to identofy the ports on the admin page. A simple script to execute the dos command "netstat -a" list is produced and a perusal for known or missing ports tells you what regions are up or down.
I thought I'd pass this simple solution on for anyone else that may end up with this problem because support and I Have spent over a year trying to resolve the problem.
If some one has another perspective on a resolution, I would appreciate a response and your example.
#EnterpriseDeveloperi thought there were other resonses on this thread but i dont see any.
While you'd think that if you dont see a casmgr (out of 2 that should be showing) in the tasklist, the service and application are not running however the service is running. We have it happen. While writing vbs or c# to parse and peruse the cassi's may be the ultimate correct thing to do, for us the netstat command is at least showing who owns the displaying casmgr. What we've done is written a c# to read the console logs and compare that to the task manager list, so we know who started what and therefore we have a basic knowledge of what to kill. netstat may not be the perfect tool but its cheaper than 3rd party pkgs.
