Retriever, Workflow, and Dispatcher issues

From DocWiki

Revision as of 06:41, 10 January 2011 by Saychakr (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Primary steps

  • Retriever (Rx) process and instance(s) running? (check from Unified EIM / Unified WIM System Console)
  • Check validity of alias details. Try to telnet to POP3 server using the following command (110 is the POP3 port number) and input alias credentials at login prompt: telnet <server name> 110


Monitoring - Instance Level Information

  • Last Run Time less than Start Time in System Monitor? (see Unified EIM / Unified WIM System Console User Guide for steps to create a monitor).
  • Retriever instance(s) may have hung. Check <Unified EIM / Unified WIM Install Dir>/logs/rx-process.log and <Unified EIM / Unified WIM Install Dir>/logs/eg_log_<server_name>_rx-process.log for JAVA exceptions and time-out messages.

Last Run Time much lesser than Current Time

  • Rx instance hung due to problematic E-Mail or Rx has connection problems.
  • Rx instance crashed due to some error viz. OutOfMemoryError. Check <Unified EIM / Unified WIM Install Dir>/logs/eg_log_<server_name>_rx-process.log and <Unified EIM / Unified WIM Install Dir>/logs/eg_log_<server_name>_rx-process.log for string ‘Instance failed’.

Monitoring - Alias Level Information

  • Check <Unified EIM / Unified WIM Install Dir>/logs/rx-process.log and <Unified EIM / Unified WIM Install Dir>/logs/ eg_log_<server_name>_rx-process.log for alias related errors such as login failures, alias being inactive/disabled, etc. Search for occurrences of the string “RETRIEVER”

Rating: 0.0/5 (0 votes cast)

Personal tools