MQSeries.net :: View topic

Prahasith · Posted: Mon Dec 29, 2003 7:45 pm Post subject: problem determination

FYI----> thought this might be useful for beginners

Where can I look for information when doing problem determination with MQSeries Workflow?

A: First, find the answers to the following questions:
What is your MQSeries Workflow environment? For example, know,
What version of the product you are running?
What operating system is being used?
What database product and version is being used?
What level of MQSeries is being used?
Where are all the workflow components installed (2-tier, 3-tier, Web client)?
Whether there are one or more workflow servers?
What is the exact scenario that caused the problem and the exact error that results.
Next check various log files for messages and return codes.

Run the command, fmczchk -d and review the resulting log file, fmczchk.log.
Check the MQSeries Workflow log files:
fmcerr.log
fmcsys.log
\mqwfinstdir\cfgs\FMC\log\*.log
\mqwfinstdir\log\*.log (only if having problems doing install and configuration)
Check MQSeries logs (especially when a client cannot connect to the server):
\mqseries\errors\AMQERR01.LOG
\mqseries\errors\AMQ*.0.FDC
\mqseries\qmgrs\FMCQM\errors\AMQERR01.LOG
Check database logs:
DB2
db2diag.log
Oracle
alert_SID.log
log files that are specified in the INIT.ORA file. Look for lines that start with:
user_dump_dest=
background_dump_dest=
If using the Web client, check the servlet.log file:
servlet.log file specified in the WebClient.properties file.
Know your level of JDK and if it is IBM or SUN.
Know your Web server and its level.
Are you using JNDI and, if so, how is it setup?
As a last resort, run the trace utility.
Set trace using command: fmczchk -dc trc:99,tracefilename
Stop and restart the workflow server.
Reproduce the error.
Stop trace by entering command: fmczchk -c trc:0