Home

 

Problem determination

 

This chapter suggests reasons for some of the problems you might experience using WebSphere MQ. You usually start with a symptom, or set of symptoms, and trace them back to their cause.

Problem determination is not problem solving. However, the process of problem determination often enables you to solve a problem. For example, if you find that the cause of the problem is an error in an application program, we can solve the problem by correcting the error.

Not all problems can be solved immediately, for example, performance problems caused by the limitations of your hardware. Also, if you think that the cause of the problem is in the WebSphere MQ code, contact your IBM Support Center. This chapter contains these sections:

• Preliminary checks

• Looking at problems in more detail

• Application design considerations

• Error logs

• Dead-letter queues

• Configuration files and problem determination

• Tracing

• First-failure support technology (FFST)

• Problem determination with WebSphere MQ clients

• Java diagnostics

• Preliminary checks
  

• Looking at problems in more detail
  

• Application design considerations
  

• Error logs
  

• Dead-letter queues
  

• Configuration files and problem determination
  

• Tracing
  

• First-failure support technology (FFST)
  

• Problem determination with WebSphere MQ clients
  

• Java diagnostics
  

 

Parent topic:

Recovery and problem determination

fa14820_

 

Home