The analysis component is responsible for the actual processing of the event. Analysis problems typically involve the runtime components, such as a failure to load a dynamic library, or a failure to send information to a transport due to queue full condition. Some of these errors can be remedied at runtime, while others require a shutdown and restart. Both the NNSYMessageLog.nml and the Command and Control interface provide information on the required action and source.
Data Parsing Errors
|
|
|
|
Problem |
The date in the incoming message was not parsed. |
|
Resolution
|
The date/time object was neither in the default format of YYYY-MM-DD HH:MM:SS.mmm, nor was it in one of the possible formats specified in the nnsyreg.dat file. Ensure that possible formats are specified in the DateTimeInputFormat, DateInputFormat, and TimeInputFormat parameters in the nnsyreg.dat file. Note: You cannot use a comma in a format definition because a comma is already used as a list separator. |
|
|
|
|
Problem |
When you are testing your business process, a copied rule set is not showing as validating. |
|
Resolution |
A rule set in a business process was copied and pasted into the same business process (not copied from the Orchestration Navigator, but copied from the business process canvas) and not renamed to a new rule set name. Only the original rule set validates, the second rule set with the same name is ignored. Open the copied rule set, make the necessary edits and save the rule set. The IDs for the rule set are updated and the rule set should work correctly. |
XML Events Errors
|
|
|
|
Problem |
XML events are thrown to the error queue. |
|
Resolution |
Input or output data (such as a context variable) is missing from the business process or is malformed. |
|
|
|