Capture Problems

The capture component extracts events from named input transports. Typically, capture errors involve either syntax errors in the inbound event data or unknown symbol errors which result from an inbound event not matching expected events. Check the NNSYMessageLog.nml for these types of errors.

Format parse failing


Problem	Several parsing problems can occur: Parsing of a format or NCM fails. XML message that should not be validated is being validated.
Resolution	Monitor the incoming data stream to ensure validity.

Capture thread showing no activity


Problem	Capture thread is showing a 0 throughput.
Resolution	There is a problem with a transport connection or the number of capture threads is not configured. Verify that there is one or more capture threads configured and verify connectivity with the transport.

Grouped messages not being grouped


Problem	WebSphere MQ messages meant to be grouped provide header information that is read by the engine in order for them to be sent as a group.
Resolution	Ensure that the header properties on the import transport are set properly: NNMQS_MSG_GROUP_ID - hex value NNMQS_MSG_FLAGS - MQMF_LAST_MSG_IN_GROUP or MQMF_MSG_IN_GROUP NNMQS_MSG_SEQUENCE_NUMBER - long integer

Business process put into error state


Problem	The process can be put into an error state for numerous reasons.
Resolution	Refer to the NNSYMessageLog.nml file. From the point in the file where the error message displays, read the entries in the file that are around the same timestamp to get the context of the error.