| Author |
Message
|
| MQ123 |
 Posted: Mon May 26, 2008 1:01 am Post subject: Top Ten reasons to bring MQ down |
 |
|
Novice
Joined: 05 Jun 2007
Posts: 11
|
May be this is a little bit silly, but I want to ask you:
What are from your point of view and based upon your experiences the top ten reason which coud hurt MQ Series operations ?
Ok, I start with
1. Hardware failure and no HA
2. Running out of diskspace for log files
3. network problems (DNS Server problems)
4. .... |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Mon May 26, 2008 1:45 am Post subject: Re: Top Ten reasons to bring MQ down |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
1. Hardware failure and no HA
2. Running out of diskspace for log files
3. network problems (DNS Server problems)
4. Queue manager/Queue gets corrupted
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| MQ123 |
| Posted: Mon May 26, 2008 2:06 am Post subject: |
|
|
Novice
Joined: 05 Jun 2007
Posts: 11
|
Thanks Gayathri - but can you classify this more in detail ?
What can cause a QM to come in a corrupted state ? |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Mon May 26, 2008 5:54 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
On number 4, there can be disk failures of the integrity type that would corrupt files.
#5, Operators that delete files.
#6, WebSphere MQ Admins that think it is a good idea to have more then two QMGRs in a cluster be Full Repositories.
#7, WMQ Admins that foolishly issue cluster refresh commands on full repositories
#8, Managers that will not upgrade to Version 6
#9, Managers that will not apply maintenance
#10, Teams that do not appropriately plan and test their configurations |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Mon May 26, 2008 8:34 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
11. Applications that won't test against a QMgr restart. A properly coded / configured application should automatically reconnect to the QMgr in a reasonable amount of time.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon May 26, 2008 9:22 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
12. two queue managers in a cluster with the same name
13. two queue managers outside of a cluster talking to each other, both with the same name.
14. client apps that don't disconnect when they are done
15. not properly using DISCINT, HeartBeats, KeepAlive, AdoptNewMCA.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon May 26, 2008 11:43 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
16. No disaster recovery policy and process.
17. A disaster recovery policy and process that is not tested.
18. No security policy.
19. End-users (including programmers) in the MQM (or admin) groups.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| jcv |
| Posted: Mon May 26, 2008 3:49 pm Post subject: |
|
|
Chevalier
Joined: 07 May 2007
Posts: 411
Location: Zagreb
|
| 20. options which are provided, but not recommendable under any circumstances, be they just simply pointless or something worse, always make you wonder why are they made in the first place, or not removed afterwards, or turned into something useful |
|
| Back to top |
|
|
| MQ123 |
| Posted: Mon May 26, 2008 10:59 pm Post subject: |
|
|
Novice
Joined: 05 Jun 2007
Posts: 11
|
|
| Back to top |
|
|
|
|
