Author |
Message
|
narki |
Posted: Mon Sep 24, 2007 5:27 pm Post subject: One of the broker is not proceeing messages |
|
|
Acolyte
Joined: 19 Dec 2005 Posts: 67
|
There are two brokers A and B. One of the message flow in broker A stops processing messages every day. It is 2.1 brokers. Where as B broker always works fine. The execution group on A abends. we are not able to fugre out the problem. To restrt processing from A we have to restart broker.Please provide the help. |
|
Back to top |
|
 |
AkankshA |
Posted: Mon Sep 24, 2007 7:41 pm Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
what does the abend file says??? _________________ Cheers |
|
Back to top |
|
 |
elvis_gn |
Posted: Mon Sep 24, 2007 9:23 pm Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi narki,
Saying that your execution group abends is not going to help us help you...
What is going wrong in which flow ? Are you writing any logs, do you have any exception handling ? What does broker log say ?
Regards. |
|
Back to top |
|
 |
Gaya3 |
Posted: Mon Sep 24, 2007 9:52 pm Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Hi
Whats the version of MBIMB? as i saw you mentioned ( It is 2.1 brokers) 2.1 are you using MQSI 2.1 itself or what.
Try to find out which business logic leads this?
Thanks and Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Sep 25, 2007 3:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Of course, when you get an abend, you should open a PMR.
Of course you can't open a PMR because 2.1 is no longer supported.
What happens if you deploy the whole execution group that abends on A, but on B instead?
And I'm with elvis_gn...
what does the log say? Always start there! _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
narki |
Posted: Tue Sep 25, 2007 5:15 pm Post subject: |
|
|
Acolyte
Joined: 19 Dec 2005 Posts: 67
|
Today also this has happned but there was no abend file genrated. There are exception on syslog, but this same kind of exception is happening on both the broker. Is there anyway we can find whether message flow is processing messages or not. Also is it possible that because of the resouce constarint this may be happening. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Sep 25, 2007 5:23 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
There's all kinds of ways you can find out if a message flow is processing messages.
Most of them involve, in some way, knowing what the flow is supposed to do.
It seems like you're having lots of problems with an environment that is not supported and poorly monitored.
It also seems that you're facing problems that are significantly beyond your training and experience have left you prepared for.
Maybe you should hire a consultant. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
narki |
Posted: Tue Sep 25, 2007 5:36 pm Post subject: |
|
|
Acolyte
Joined: 19 Dec 2005 Posts: 67
|
Thanks for you response. As far as broker is concerned i would like to challenge you right in your backyard. we tried various options to find out details. But we can not trace it and sent it to the IBM because it is not suipported software. It is well monitored infrastucture that is why if the messages are not dequeued there are alert. Only concern is after looking at various log like database broker log there is no clue why this is happening in one of the broker. |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Sep 25, 2007 6:15 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I can only respond based on the information you've given.
You ask how to monitor a flow to find out if it's processing messages... you don't say that you have monitoring in place and you don't say that it is or is not sending out alerts.
You say that there are exceptions in the logs, but don't say what they are. You don't say what you've done to try and troubleshoot them.
You also haven't given US any clue about why you're having issues with a particular broker. More particularly, you have not said whether you have tried to deploy the flows that are failing on this broker to another broker that doesn't have the problem - to find out if the problem is with the BROKER or with the FLOW.
In general, all you end up saying is "things are broken - how do I find out why".
Most of my experience here tells me that people who say that do not have the training or the experience to try and solve the problems that you are having.
Also, I live in the city. I don't have a backyard. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Sep 25, 2007 10:57 pm Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
narki wrote: |
we tried various options to find out details. |
Yes, but what??
narki wrote: |
But we can not trace it and sent it to the IBM because it is not suipported software. |
So is it 2.1?? You've still not said. On what platform? When did the trouble start? Was there a deploy just before the trouble? Some details please.
I have a small backyard. I don't keep a broker in it. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|