Announcement

Collapse
No announcement yet.

postprocessor not called

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • postprocessor not called

    I have a channel with source set as Channel Reader, and one SOAP sender destination.

    In the Preprocessor script I have:
    logger.error("Message pre processor");
    return message;

    In the Postprocessor I have:
    logger.error("Message post processor");
    return;

    When send a message to that channel, I only ever see the pre processor statement in the log, so it looks like the post processor is not running. Would there be a reason for this?

  • #2
    Reostprocessor not called

    IIRC when an error is thrown the channel halts.
    Jon Bartels

    Zen is hiring!!!!
    http://consultzen.com/careers/
    Talented healthcare IT professionals wanted. Engineers to sales to management.
    Good benefits, great working environment, genuinely interesting work.

    Comment


    • #3
      Reostprocessor not called

      Does logging an error actually throw the error? I didn't know that.

      So I took out the logging from the pre processor and filter, and it still doesn't log in the post processor. this is strange.

      Comment


      • #4
        Reostprocessor not called

        What mith are you using? I think the logger is not avaiable in the postprocessor for all versions try with a System.out

        Comment


        • #5
          Reostprocessor not called

          If you are using a channel with "Syncronize" off, the postprocessor script is not available.

          Comment

          Working...
          X