| Author |
Message
|
| mbguy |
 Posted: Tue Mar 10, 2009 3:01 am Post subject: how do i know whether my eg is running or not..? |
 |
|
Apprentice
Joined: 23 Jul 2008
Posts: 25
|
how do i know whether my eg is running or not..?
I had a problem in Production env where one of my flow is not running (all the messages are struck in the inputQ)
i had to restart the broker for it to work .this is happening frequently for diff flows .
(messages are stuck in one flow and other flows are running).I had only one EG where all my flows are deployed.
I am planning to create new EG's for Each flow bcos i think that the load on the EG is more as it is handling 20 flows.
will there be any Problem if i create 20 EG's and deploy one flow in one EG
All the flows are using the same Database,so will there be any DB deadlocks.
Can anyone suggest me a better option for solving this problem.
My Prod env is :MB5.0
Broker on Unix and ConfMgr on windows |
|
| Back to top |
|
 |
| gs |
| Posted: Tue Mar 10, 2009 3:29 am Post subject: |
|
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
Use mqsilist to list EG's and their process id's.
Regarding the message flow...first of all look into the issue that causes it to stop. There are many reasons why you do NOT want to create 20 EG's. |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Tue Mar 10, 2009 3:38 am Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
| mbguy wrote: |
I am planning to create new EG's for Each flow bcos i think that the load on the EG is more as it is handling 20 flows.
will there be any Problem if i create 20 EG's and deploy one flow in one EG |
Each instance flow runs as operating system thread... 20 threads under a EG(OS Process) should not be a problem..
This link may be helpful...
_________________
-----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Mar 10, 2009 3:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Check if you had a core dump. You may have to reboot the machine to clear shared memory. I had a problem where after a core dump a publish flow would no longer work as advertised. Needed to reboot the machine to get it to work right again. Anyway if you do find a core dump you should open a PMR on it. Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mbguy |
| Posted: Tue Mar 10, 2009 3:54 am Post subject: |
|
|
Apprentice
Joined: 23 Jul 2008
Posts: 25
|
| gs wrote: |
Use mqsilist to list EG's and their process id's.
Regarding the message flow...first of all look into the issue that causes it to stop. There are many reasons why you do NOT want to create 20 EG's. |
My problem is i am having only one EG and there are 20 flows deployed in that EG .Only one flow is giving this kind of problem(the messages ar a stuck in Inputq).While all other are working fine.
Will there be any other reason for messages get stuck in inputQ other than Broker/Flow/EG not Running...? |
|
| Back to top |
|
|
| mbguy |
| Posted: Tue Mar 10, 2009 4:01 am Post subject: |
|
|
Apprentice
Joined: 23 Jul 2008
Posts: 25
|
| fjb_saper wrote: |
| Check if you had a core dump. You may have to reboot the machine to clear shared memory. I had a problem where after a core dump a publish flow would no longer work as advertised. Needed to reboot the machine to get it to work right again. Anyway if you do find a core dump you should open a PMR on it. Have fun |
hi fjb_saper,
Can u tell me where actually these core dumps are created in AIX
MQEnthu,
i could not find the link ,can you repost it.. |
|
| Back to top |
|
|
| gs |
| Posted: Tue Mar 10, 2009 4:31 am Post subject: |
|
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
| mbguy wrote: |
My problem is i am having only one EG and there are 20 flows deployed in that EG .Only one flow is giving this kind of problem(the messages ar a stuck in Inputq).While all other are working fine.
|
If all other flows work fine, it leads my suspicions to your flow rather than the broker/EG.
| mbguy wrote: |
Will there be any other reason for messages get stuck in inputQ other than Broker/Flow/EG not Running...? |
Do the error logs indicate anything? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 10, 2009 5:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mbguy wrote: |
| Will there be any other reason for messages get stuck in inputQ other than Broker/Flow/EG not Running...? |
Make sure there's a backout queue defined for the input queue. If all these "stuck" messages migrate to that, you've found your problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gs |
| Posted: Tue Mar 10, 2009 6:50 am Post subject: |
|
|
Master
Joined: 31 May 2007
Posts: 254
Location: Sweden
|
| Vitor wrote: |
| mbguy wrote: |
| Will there be any other reason for messages get stuck in inputQ other than Broker/Flow/EG not Running...? |
Make sure there's a backout queue defined for the input queue. If all these "stuck" messages migrate to that, you've found your problem. |
If not, they would end up on the defined SDLQ. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 10, 2009 7:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gs wrote: |
| Vitor wrote: |
| mbguy wrote: |
| Will there be any other reason for messages get stuck in inputQ other than Broker/Flow/EG not Running...? |
Make sure there's a backout queue defined for the input queue. If all these "stuck" messages migrate to that, you've found your problem. |
If not, they would end up on the defined SDLQ. |
If the queue manager's been defined with a dead letter queue; remember that while SDLQ is one of the objects defined at qmgr creation, it's not automatically added to the DEADQ attribute of the qmgr.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vairavan |
| Posted: Tue Mar 10, 2009 7:34 am Post subject: |
|
|
Apprentice
Joined: 22 Apr 2008
Posts: 42
|
First of all, My basic and simple question...
The flow which is not running properly... Is that been configures with the correct queue name?
I hope you have backout queues connected to all the queues. If the flow is wrong, then you will get some exceptions that will go to backout queues.
If it stays in the input queue forever, then I doubt the queue name given in the flow is same... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Mar 10, 2009 6:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
In case of a core dump everything was configured fine and running fine before the dump. After the dump a publishing flow just refused to consume messages... Until we recycled the machine...
The core dump can be found in any of the directories you started the broker from.... by default check the broker's service user home directory...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| WMBEAI |
| Posted: Tue Mar 10, 2009 8:26 pm Post subject: |
|
|
Acolyte
Joined: 02 Mar 2009
Posts: 66
|
20 flows in an execution group should work fine.
Check the following.
DLQ defined for QM
BackOut Requeue defined
Check the Backout count if it 0 then no issues greater than it is trying to post the message but due to some reason fails.
In that particular flow are u trying to access the database?if db is down and u try to access i flow may get stopped.Better check your Broker logs.
If u get messgae in DLQ we can find out the problem |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Tue Mar 10, 2009 8:29 pm Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
|
| Back to top |
|
|
| mbguy |
| Posted: Wed Mar 11, 2009 11:02 pm Post subject: |
|
|
Apprentice
Joined: 23 Jul 2008
Posts: 25
|
Thank u all for ur replies and sorry fro the late reply..
My problem is that not a particular flow is giving this problem .. from last week iam getting mails saying that some flow are not running ,when i check the inputq the message will be there in the input q and broker will also be running.There is a dead Letter defined for the Queuemanager .
Also the Backout queues are defined for all the inputq.These flows are working perfectly before .but nowadays every day i am getting this kind of problem with some flow.
any other suggesttions..?
any answer for my question ..
if i create 20 EG's for 20 flows and all the flows are accessing the same database then will there be any problem with the database (any DB locks)..? |
|
| Back to top |
|
|
|
|
