| Author |
Message
|
| jcv |
 Posted: Thu Aug 06, 2009 3:50 am Post subject: Informational probe |
 |
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
| Is there a way to configure ffst to suppress FDC generation with probe severity of level 4? If it were possible, would you do it? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Aug 06, 2009 6:40 am Post subject: Re: Informational probe |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jcv wrote: |
| Is there a way to configure ffst to suppress FDC generation with probe severity of level 4? |
AFAIK No.
| jcv wrote: |
| If it were possible, would you do it? |
No.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Aug 06, 2009 4:17 pm Post subject: Re: Informational probe |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| jcv wrote: |
| Is there a way to configure ffst to suppress FDC generation with probe severity of level 4? If it were possible, would you do it? |
Why? Do you have an issue with an excessive number of FDC filess being generated? You should investigate the root cause to eliminate their creation.
_________________
Glenn |
|
| Back to top |
|
|
| jcv |
| Posted: Fri Aug 07, 2009 1:43 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
No, I have an issue with losing my time while investigating the root cause, if that happens to be an unexpected application behaviour which can impact MQ, to throw some exception (informational), if something like this is possible (is it?). I would rather focus on unexpected MQ behaviour which can impact applications. That's why I thought it would be good to lower the level of fdc dumping, because I would also like to treat them as an indicator of severe problems within MQ.
Last edited by jcv on Sat Aug 08, 2009 2:22 am; edited 1 time in total |
|
| Back to top |
|
|
| jcv |
| Posted: Fri Aug 07, 2009 1:55 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
| I also trust IBM's judgment when they say that a certain probe is Informational, that is, that there is a gradation with respect to severity of probes. That is a part of information I would like to rely on, even when I don't know the exact root cause of the exception reported. Sometimes, I can live with that. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Aug 09, 2009 3:36 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| jcv wrote: |
| No, I have an issue with losing my time while investigating the root cause, if that happens to be an unexpected application behaviour which can impact MQ, to throw some exception (informational), if something like this is possible (is it?). I would rather focus on unexpected MQ behaviour which can impact applications. That's why I thought it would be good to lower the level of fdc dumping, because I would also like to treat them as an indicator of severe problems within MQ. |
All FDCs are cause for concern. They should all be investigated and resolved. Any time you spend in investiging the root cause will pay off in the long term because you will probably eliminate sources of repeating problems that will impact applications and MQ.
_________________
Glenn |
|
| Back to top |
|
|
| jcv |
| Posted: Mon Aug 10, 2009 4:55 am Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
|
| Back to top |
|
|
|
|
