Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-8370

Large JMS ObjectMessage types result in UTFDataFormatException when deserialized on client side

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None

      When an activemq classic client uses the compression option to create a connection with the Artemis broker, ObjectMessage types greater than 1024 bytes have a problem being deserialized on the consumer side. The process consuming the message attempts to reconstruct the Java object from the data contained in the received ObjectMessage, but then throws a UTFDataFormatException.

              csuconic@redhat.com Clebert Suconic
              rh-messaging-ci Messaging CI
              Samuel Gajdos Samuel Gajdos
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: