[jira] [Resolved] (CAMEL-7882) camel-syslog's CamelSyslogTimestamp header is suddenly a GregorianCalendar

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-7882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-7882.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.15.0
                   2.14.1
         Assignee: Claus Ibsen

Ah yeah lets keep it as before, I changed it back to a java.util.Date

> camel-syslog's CamelSyslogTimestamp header is suddenly a GregorianCalendar
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-7882
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7882
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-syslog
>    Affects Versions: 2.14.0
>         Environment: RHEL 2.6.32-431.20.3.el6.x86_64
> Java 8
>            Reporter: Jan-Helge Bergesen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.14.1, 2.15.0
>
>
> This is mostly to help others facing the same issue, as we just spent 4x3 hours figuring this out.
> An app, that consumes syslog entries and forwards JMS (over OpenMQ), was upgraded from camel 2.13.0 to 2.14.0.
> Afterwards many things broke upstream, which was masked by poor logging in some Glassfish servers (truncating stacktraces).
> Turns out that the {{CamelSyslogTimestamp}} header was silently discarded, being a {{java.util.GregorianCalendar}} instance.
> Forcing it into a {{java.util.Date}} before routing to the JMS endpoint restored service throughout the valuechain.
> As I wrote; this is mostly a FYI to others :-).
> But perhaps the documentation might reflect the lack of guaranteed conversion?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)