Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-7882

camel-syslog's CamelSyslogTimestamp header is suddenly a GregorianCalendar

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.14.0
    • Fix Version/s: 2.14.1, 2.15.0
    • Component/s: camel-syslog
    • Labels:
      None
    • Environment:

      RHEL 2.6.32-431.20.3.el6.x86_64
      Java 8

    • Estimated Complexity:
      Unknown

      Description

      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?

        Attachments

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              jhberges Jan-Helge Bergesen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: