The event in question came in from localhost via send-event.pl through eventd's TCP event receiver:
> 2010-02-18 17:14:53,999 DEBUG [Event TCP > Receiver[5817][127.0.0.1:55773]] TcpStreamHandler: Event record > converted ... > 2010-02-18 17:14:53,999 DEBUG [EventHandlerPool-fiber1] > DefaultEventHandlerImpl: src = perl_send_event It looks like send-event.pl might not encode the date right as you point out: > 2010-02-18 17:14:54,001 WARN [EventHandlerPool-fiber1] > JdbcEventWriter: Failed to convert time Thursday, February 18, 2010 > 5:14:53 PM GMT to Timestamp, setting current time instead. Exception: > java.text.ParseException: Unparseable date: "Thursday, February 18, > 2010 5:14:53 PM GMT" Please open a bug and we'll take a look at it. I wonder if the problem might be that the time is encoded as "5:14:53 PM" instead of "17:14:53". Regarding this question: > * Question: Is there any particular reason the Date is stored this > way internally? In this case, the date is coming in via XML, so we have to convert what comes in via XML into Java objects, and this is where the exception is happening in your case. - djg ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel