| Author |
Message
|
| Ranodip Basu |
 Posted: Wed Sep 20, 2006 6:46 am Post subject: Even After Deletion of Exc Grp - Message Flow Still Running |
 |
|
Apprentice
Joined: 23 Sep 2004
Posts: 48
|
Hi All,
We are using WMB 6.0.1 installed in windows 2003 (toolkit & config manager) and Suse linux(broker).
We are basically facing an unexpected issue as described in below:
We have created a message set and message flow and deployed the .bar file to a particular execution group which worked fine. We have removed all the deployed children under this particular execution group and deployed some new bar file. Now we have found that though there are no trace of those old message flows running under the broker but still messages from input queue are being consumed by some processes and going to the output queue as mentioned in MQ output node of the old message flow. We have also deleted the execution group and made sure by executing the command mqsilist BROKER_NAME that the deleted execution group is no more running. But still we are facing the same problem that messages are processed from input queue and going to the output queue as mentioned in the old message flow. So that means by anyhow the old message flow is running under the broker.
Could you please let me know your suggestions ?
Thanks in advance.
Ranodip Basu |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Sep 20, 2006 6:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What does dis qstatus(<input_queue>) type(handle) show for the input queue?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Ranodip Basu |
| Posted: Wed Sep 20, 2006 7:01 am Post subject: |
|
|
Apprentice
Joined: 23 Sep 2004
Posts: 48
|
Hi Jefflowrey,
Thanks for reply. Here is the status of the queue. I have changed the queue and user name in the list below.
[quote]AMQ8450: Display queue status details.
QUEUE(QUEUE_NAME) TYPE(HANDLE)
APPLTAG(DataFlowEngine) APPLTYPE(USER)
BROWSE(NO) CHANNEL( )
CONNAME( ) HSTATE(ACTIVE)
INPUT(SHARED) INQUIRE(YES)
OUTPUT(NO) PID(1927)
QMURID(0.2199375) SET(NO) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 20, 2006 7:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What does Task Manager show for PID 1927?
Which EG does mqsilist show has a PID of 1927?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Ranodip Basu |
| Posted: Wed Sep 20, 2006 7:25 am Post subject: |
|
|
Apprentice
Joined: 23 Sep 2004
Posts: 48
|
Ok I have get the process id 1927 from both mqsilist and ps -fu USER_NAME|grep Data and will execute kill -9 1927.
Please let me know your feedback if this is the right way.
Thanks,
Ranodip Basu |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 20, 2006 7:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Does that mean that mqsilist is still showing the execution group that you thought you deleted?
Or is the 1927 for a different execution group?
Also, sorry, I missed that your broker was on linux. So, yes, use ps-ef instead of "task manager".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ydsk |
| Posted: Wed Sep 20, 2006 1:33 pm Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
my 2 cents ...
I remember seeing the problem on Windows brokers a few times.
Even if we delete the Exec Group it gets recreated again sometimes.
The best solution I know of is to simply delete all the execution groups in the broker from a toolkit ( right-click-->Remove Deployed Children ).
Wait a few seconds, and then re-create whatever execution groups you want and re-deploy.
The root cause of the issue as far as I know is that developers are too eager to do things quickly. They don't wait for a response from the configmgr for their deploys, and try to deploy bar files or deploy some configuration changes while the broker is busy doing the previous deploy.
Thanks.
ydsk. |
|
| Back to top |
|
|
| rshephard59 |
| Posted: Fri Sep 22, 2006 5:09 am Post subject: |
|
|
Novice
Joined: 09 Jan 2003
Posts: 10
|
We experienced the same problem when the Rational Agent Controller is installed. The RAC will keep an instance of the execution group running and if you kill the process it just keeps restarting.
We had to update the toolkit to the latest fixpack, delete all of the deployed message flows in the execution group, shut everything down, and then bring it back up.
Haven't any problems since then. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 22, 2006 5:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yeah, if someone has forgotten to detach the debugger from the execution group you may have some issues deleting it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
