| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Common Production Issues in WMB Project |
« View previous topic :: View next topic » |
| Author |
Message
|
| 999999 |
 Posted: Wed Oct 24, 2012 7:24 pm Post subject: Common Production Issues in WMB Project |
 |
|
Newbie
Joined: 24 Oct 2012
Posts: 2
|
Dear All,
I am new to WebSphere Message Broker. Can someone pls let me what all common issues we face in production environment(apart from wrong input data). I mean what different problem we generally face, while supporting WMB project in production environment. I tried to google it out, but couldn't find satisfactory answers.
Thanks in advance. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Oct 24, 2012 11:59 pm Post subject: Re: Common Production Issues in WMB Project |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| 999999 wrote: |
Dear All,
I am new to WebSphere Message Broker. Can someone pls let me what all common issues we face in production environment(apart from wrong input data). I mean what different problem we generally face, while supporting WMB project in production environment. I tried to google it out, but couldn't find satisfactory answers.
Thanks in advance. |
The biggest one we see here is lack of training and lack of knowledge... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| 999999 |
| Posted: Thu Oct 25, 2012 4:29 am Post subject: Re: Common Production Issues in WMB Project |
|
|
Newbie
Joined: 24 Oct 2012
Posts: 2
|
| fjb_saper wrote: |
| 999999 wrote: |
Dear All,
I am new to WebSphere Message Broker. Can someone pls let me what all common issues we face in production environment(apart from wrong input data). I mean what different problem we generally face, while supporting WMB project in production environment. I tried to google it out, but couldn't find satisfactory answers.
Thanks in advance. |
The biggest one we see here is lack of training and lack of knowledge... |
Hi..u r right...I have never been trained on WMB..nor I have worked on this technology. Actually all these years I am working on SeeBeyond/JCAPS and my company is paying me peanuts. Now I wan't to switch my company with WMB technology. I have downloaded WMB and went throught the tutorials and Help contents, so quiet familier with the theoretical concepts. But in the interview they are asking me this question  and I don't have the answer  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 25, 2012 5:06 am Post subject: Re: Common Production Issues in WMB Project |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| 999999 wrote: |
| fjb_saper wrote: |
| 999999 wrote: |
Dear All,
I am new to WebSphere Message Broker. Can someone pls let me what all common issues we face in production environment(apart from wrong input data). I mean what different problem we generally face, while supporting WMB project in production environment. I tried to google it out, but couldn't find satisfactory answers.
Thanks in advance. |
The biggest one we see here is lack of training and lack of knowledge... |
Hi..u r right...I have never been trained on WMB..nor I have worked on this technology. Actually all these years I am working on SeeBeyond/JCAPS and my company is paying me peanuts. Now I wan't to switch my company with WMB technology. I have downloaded WMB and went throught the tutorials and Help contents, so quiet familier with the theoretical concepts. But in the interview they are asking me this question and I don't have the answer |
And you still don't have the answer.
Which means you were not clear in the interview about your specific skills and knowledge.
If the question was about JCAPS, how would you have answered the question? Would you have been able to make a distinction between production issues that were experienced because of the *product* in question from issues that were experienced because of the *practices* of the company involved? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Oct 25, 2012 5:10 am Post subject: Re: Common Production Issues in WMB Project |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| fjb_saper wrote: |
| 999999 wrote: |
Dear All,
I am new to WebSphere Message Broker. Can someone pls let me what all common issues we face in production environment(apart from wrong input data). I mean what different problem we generally face, while supporting WMB project in production environment. I tried to google it out, but couldn't find satisfactory answers.
Thanks in advance. |
The biggest one we see here is lack of training and lack of knowledge... |
WMB is not like Java. Stick to Java and you will have more success. {see previous post for training URLs}.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mayheminMQ |
| Posted: Mon Nov 05, 2012 9:47 am Post subject: |
|
|
Voyager
Joined: 04 Sep 2012
Posts: 77
Location: UK beyond the meadows of RocknRoll
|
Just stumbled on this post now.
The nerve is all I can think  |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Wed Nov 07, 2012 12:00 am Post subject: Re: Common Production Issues in WMB Project |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
| 999999 wrote: |
| Can someone pls let me what all common issues we face in production environment(apart from wrong input data). I mean what different problem we generally face, while supporting WMB project in production environment. |
A broker platform should have no problems/issues normally. Something must happen that your run into problems (probably your platform also has known issues (that cannot/have not been resolved yet), but then hopefully there are also known workarounds to them).
Wrong input data: When data comes out of computer-systems it is likely formatted o.k. We faced only issue when the business-data (content of xml-attributes/elements) was wrong. This especially occurs, when a partner extends (introduces new data/enums) or changed/migrates their system. This may go down your error handler and end up e.g. in a db-table. You just look into that table "SELECT * FROM MY_ERROR_TABLE DESC CREATED_TIME" ... probably this (error table) (also) gets reported e.g. on a html-page (but that is not for techies, that is for management: YOU work with SQLDeveloper, Toad or DBVisualizer and real SQL-Statements!). Or your platform/interface(s) is/are not validating (certain/some/all aspects) and erroneous data gets through (your platform) and the receiving partner will start to complain (about the sending partner): So they might contact you (instead of the sender)... then just kindly forward them and mediate between the two  .
MQ to MQ (Sender&Receiver- or Cluster-channels) is reliable (but costs money), Adapters are quite reliable (but cost money) and there are other connections which are less reliable e.g. ftp (costs nothing): Messages are not transmitted fully (truncated in the middle) or transmitted twice or not transmitted at all.... or the process/(shell-)script stops working. In general (AIX-)processes can crash (you should monitor if they are there. Manually you do e.g. for MQ: "ps -eaf | grep mqm" ). Infrastructure people tend to do work (update the network-components) on the weekend, which can effect your production-environment (on a Monday morning).
They might send too big messages. The total queue limit is 100 MB (and the default is 4 MB). Big messages may also cause execution groups to abend. Input-Data may also cause an infinite loop in your flow (thus abend it... but well... this is unlikely in production). Execution-Group-Abends (because one of the flows in it brings it to 100%-CPU or its mem-limit) might also occur due to the way the flow is coded. In that case you need to contact the developer / open an issue.
After new deployments... issues may occur. Messages may end up on Backout queues. The error table fills up. Error logs are written. AIX error log, FFDCs, probably "core"-files (core dumps). But you should have tested that on Pre-Production, Integration and Test environments (and probably had these severe errors there and fixed them before moving on to production)... still issues may also occur in production. They are called (production-)incident then. There are priorities assigned (e.g. 1 (high), ..., 5(low)) to them. On errors after deployments a questions is: was the deployment done correctly... or is the error in the (newly) deployed flow/message-set or mqsc-scripts.
AIX file systems can fill up (test with "df -g" and look at the "%Used"-column). Channels can stop working (only with a reason) (making the xmit queue fill up, and then the dead letter queue). A message can get stuck in a channel: Then you may have to "resolve" the channel (commit or back-out). Channels may also get "out of sync" during maintenance-work: There is a counter at each end (sender and receiver). In that case you may have to reset the counter on the sender and on the receiver channel.
A component may just stop working (e.g. picking up files). Or a flow is stopped/blocked. Monitoring software can detect that. But sometimes the problem with monitoring software is: Does it monitor the right thing, who monitors the monitoring software and who updates/maintainces it (it's settings/thresholds). So: your platform may have stopped (processing messages) and it goes unnoticed (for some time). Then you have to improve your monitoring 
Besides WebSphere MQ Explorer and WebSphere Message Broker Explorer you can use MQMON (Support Pack "MO71", free), MQJExplorer (free) and probably WMQTool (paid) for operations and monitoring. Other paid (and more expensive) tools (e.g IBM Tivoli) are available (also search this forum).
Someone send a msg and insists that you received it, but there is no message on your side neither any log-file/table-entry (or someone isn't receiving msgs that he expects). So you start searching for a msg / msgs ("MQ doesn't lose msgs" )... probably the solution is: they totally misconfigured the connection to MQ and actually did never send you one.
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
