Closed iariasleon closed 10 years ago
Having the full log is fine to have all the information. However, it would be great if we can also know the section in which the bug manisfest. E.g. the JSON string that is causing the problem (usually a "wire" debug arround the 404 error).
Just for clarification, the error loop is due to the main reliability mechanism given by Flume, based on re-injecting an event in the channel if it could not be processed. Nevertheless, we are currently abusing of such mechanism, since we re-inject all the not processed events, even those that are malformed and will never be processed althought they are re-injected forever :)
There is an issue regarding this: https://github.com/telefonicaid/fiware-connectors/issues/52
I think this should be fixed in PR #97. Let's merge that PR into develop, then evaluate if the bug still happening again.
It could be related with issue #106
LGTM
Severity: Major (6) - BUG Cygnus version used: cygnus-0.4_SNAPSHOT-14.gd553b14.x86_64.rpm Log mode: DEBUG Script executed: notification-xml-compound.sh 127.0.0.1:5050/notify org58
When we process a compound notification, ex:
Cygnus does not process this notification, showing this error indefinitely: