krupalibshah
Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
As anyone faced issue with XML parser
I see below error on xml parser snap and the document is missing in the output view. “Process”: “XML Parser:Get data[3b123c40-ba74-4d20-b272-0a5c987dd2c9 – 7151c974-da69-4ab5-a9eb-f9c50b3df996]” “TimeStamp”: “12/27/2018, 2:30:18 PM” “RuntimeID”: “3b123c40-ba74-4d20-b272-0a5c987dd2c9” “File”: “LLMessageManager.java:320” “Message”: “Pipeline did not produce a response for message: c0e526535f7229ecaf720b44f7fd81b91204e3d9-69061@hc4t04353” “SnapLabel”: “XML+Parser%3AGet+data” “Exception”: “” so the documents input to xml parser is 5 output to XML parser is 4 no data in error view I see above error in logs need help if this is an issue with the snap?2KViews0likes0CommentsRe: Has anyone observed issues with dashboard and logging?
Not worried about the other snap’s behavior but the error message here is irrelevant. Mapper snap can not get REST API 503 error REST SNAP can not give error for mapper. The sequence is mapper->rest get so if mapper fails due to $payload is undefined that error can not go to rest get. Also the above screenshots are from different execution cycle due to same error, so both behavior is expected to be same.1.3KViews0likes0CommentsHas anyone observed issues with dashboard and logging?
We observe the error if occurs should occur at the first snap but what is shown in pipeline statistics it is appearing in after 1st snap. The errors occurring on REST snap is shown on MAPPER and vice versa. Please see the screenshots.1.9KViews0likes2Comments