Announcement Announcement Module
Collapse
No announcement yet.
SerializationFailedException Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • SerializationFailedException

    I have the following configuration for the global error channel:
    <si:channel id="errorChannel">
    <si:queue capacity="1" />
    <si:interceptors>
    <ref bean="GlobalErrChnlMsgInterceptor" />
    </si:interceptors>
    </si:channel>

    When a message fails to deserialize(due to changes in class/any other problem) I get an ErrorMessage in post send of the interceptor configured. The ErrorMessage carries a throwable(SerializationFailedException) which is not an instance of MessagingException.

    Hence I am not able to identify the message which failed.

    Can anyone advise?

  • #2
    Will this be fixed in the next release?
    Is there a workaround I can apply?

    Comment


    • #3
      Can you provide more of your configuration as well as the stacktrace. I'm specifically interested in where the serialization exception is occurring.

      Thanks,
      Mark

      Comment


      • #4
        Mark the exception occurs when
        Here is my queue and publsub channels configuration:
        <si:channel id="EntityUpdatedEventQ">
        <si:queue message-store="DispacthUpdatedEventMsgStore" capacity="10" />
        </si:channel>

        <si:chain input-channel="EntityUpdatedEventQ" output-channel="EntityUpdatedEventPubSubChnl">
        <sioller fixed-rate="30000" max-messages-per-poll="1">
        <si:transactional transaction-manager="txManager" />
        </sioller>
        <si:filter ref="GlobalMsgSelector" />
        </si:chain>


        The error occurs when the poller picks a message and tries to deserialize it. The class with which the message was created was moved to a different package. Hence deserialization fails.
        The exception is given to the error channel interceptor as ErrorMessage.

        Please let me know if you need more details.

        Comment


        • #5
          Can you please create a JIRA? We can wrap the exception that occurs within the poller if necessary.

          Also, when posting code excerpts be sure to use the [ CODE ] [ /CODE ] tags (without spaces).

          Comment


          • #6
            thanks Mark.
            I have already created one yesterday. Here it is https://jira.springsource.org/browse/INT-2139
            Last edited by ravikr02; Sep 23rd, 2011, 12:02 AM.

            Comment


            • #7
              Nevertheless, can you show your stacktrace?

              Artem Bilan

              Comment

              Working...
              X