Operations Troubleshooting

In case of operational errors, you can go through a series of steps to determine what the problem is and how to fix it. TIBCO MDM attempts to alert you in as many ways as possible when an error occurs.

Operations Troubleshooting
Issue Description Solution
An error message, or event status is set to an error, or an email is sent to the specified email address. For operational error messages, you can copy the relevant error information and send to the technical support team. Check the error log file: $MQ_HOME/log/error.log.

If the system recognized an error, the error message will be listed here. If you need more detail, check the $MQ_HOME/log/elink.log file. Do this as soon as possible; the log files rotate, and if you wait too long, the elink.log file could be deleted by the time you look at it. Make a copy of the file in case you need to send it to TIBCO Technical Support.

Check the Application Server log files:

  1. WebSphere Application Server 7: 
$WAS_HOME/profiles/<profilename>/logs/server1/SystemOut.log and SystemErr.log
  2. WebLogic Application Server 10.3: 
$BEA_HOME/user_projects/domains/<DomainName>/<DomainName>.log
  3. JBoss WildFly Application Server
$JBOSS_HOME/standalone/log

    Check the Queue Manager error log files: 
<Websphere MQ Home>/qmgrs/<QM_NAME>/errors.

    The name and location will vary depending on your installation.