-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timestamp Exception with ACI Plugin #5
Comments
I developed the ACI / OpenNMS integration while working there at Cerner. The code running at Cerner is not the same as what is in this project. That code only exists in a Cerner owned fork of the opennms project. As for the error, this code merely receives Faults from the APIC controller, parses them, and converts them into ONMS events. It's hard to tell from that error message exactly where this is occurring, but I would suspect this is date string coming from the APIC controller that is in a format that the code isn't expecting. These events are json objects and the java code attempts to convert the date string into a java.util.Date object. If the date string is formatted differently than it is coded for, it may not be creating a valid Date object. This opennms-aci-plugin project was created during a OpenNMS DevJam 2 years ago and probably still needs more work before it would be production ready. Again, this is different than the code you are running there at Cerner. |
Hi Tim, Thank you for the clarification!
We wanted to understand the flow of the ACI code, so that we able to debug
the Timestamp issue and find out the root cause of the problem.
Is it possible for us to connect over a call may be through WebEx or any
other mode.
It would be really helpful.
Thank you in advance.
…On Fri, Jan 22, 2021, 8:44 PM tcfite ***@***.***> wrote:
I developed the ACI / OpenNMS integration while working there at Cerner.
The code running at Cerner is not the same as what is in this project. That
code only exists in a Cerner owned fork of the opennms project.
As for the error, this code merely receives Faults from the APIC
controller, parses them, and converts them into ONMS events. It's hard to
tell from that error message exactly where this is occurring, but I would
suspect this is date string coming from the APIC controller that is in a
format that the code isn't expecting. These events are json objects and the
java code attempts to convert the date string into a java.util.Date object.
If the date string is formatted differently than it is coded for, it may
not be creating a valid Date object.
This opennms-aci-plugin project was created during a OpenNMS DevJam 2
years ago and probably still needs more work before it would be production
ready. Again, this is different than the code you are running there at
Cerner.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AL74PBOBJNQ2Y7YC7SIMXYTS3GI55ANCNFSM4WOKHFRQ>
.
|
Hi @tcfite, I am working for Cerner. We had the ACI code integrated with OpenNMS and we are using it for a long time now.
Recently on eventd.log logs we have started getting below timestamp issue. I am not sure if the malformed timestamp is getting from the APIC or at the OpenNMS while processing the raw event. Do you have any idea on the below error?
ERROR [pool-38-thread-1] o.h.u.JDBCExceptionReporter: ERROR: timestamp out of range: "185151249-10-01 22:00:25.805-06 BC"
Also is this opennms-aci-plugin code ready for use? There was no release/tag available, not sure if it's launched already. Could you confirm on that and the branch to be used
Thank you!
The text was updated successfully, but these errors were encountered: