glassfish
  1. glassfish
  2. GLASSFISH-18436

Unable to send compressed JMS message from client to Glassfish

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: v3.0.1, 3.1.2_b23
    • Fix Version/s: 4.0_b41
    • Component/s: jms
    • Labels:
      None
    • Environment:

      Solaris 32-bit, linux Ubuntu 32-bit, Java 1.6_21/30

      Description

      I have encountered a problem when sending compressed JMS ObjectMessages from a client to Glassfish. In the GLassfish log file we see a "java.io.StreamCorruptedException: invalid stream header: 789C5BF3" exception.
      I did not have this problem when changing the MQ broker to LOCAL/REMOTE in Glassfish.
      Further analysis shows that the client and the LOCAL/REMOTE broker sends there jms messages as com.sun.messaging.jmq.jmsclient.ObjectMessageImpl. The embedded MQ broker uses com.sun.messaging.jms.ra.DirectObjectPacket. The message classes are the same for compressed and uncompressed. However when using compressed messages the embedded broker could not deserialize it.

      We also tested this with Glassfish v3.1.2. When we use a TextMessage instead of ObjectMessage, the message can be processed but the Text is corrupted.

      The problem can be reproduced with the attached maven project. You need to create a JMS queue with name "TestQueue" and deploy the ejb jar file. The UnitTest can be used to send a compressed and uncompressed message to Glassfish. In the server.log you will get the StreamCorruptedException for the compressed message.

        Issue Links

          Activity

          Hide
          Nigel Deakin added a comment -

          This is the same as MQ-155

          Show
          Nigel Deakin added a comment - This is the same as MQ-155
          Hide
          jthoennes added a comment -

          Hello,

          with the closure of MQ-155 this issue can be also closed.
          What is the FixVersion?

          Cheers, Jörg

          Show
          jthoennes added a comment - Hello, with the closure of MQ-155 this issue can be also closed. What is the FixVersion? Cheers, Jörg
          Hide
          David Zhao added a comment -

          The fix in bundled MQ goes into GF b41.

          Show
          David Zhao added a comment - The fix in bundled MQ goes into GF b41.
          Hide
          jthoennes added a comment -

          In reply to comment #3:
          > The fix in bundled MQ goes into GF b41.

          Thanks, will this be MQ 4.3 or MQ 5.0?

          Show
          jthoennes added a comment - In reply to comment #3: > The fix in bundled MQ goes into GF b41. Thanks, will this be MQ 4.3 or MQ 5.0?
          Hide
          David Zhao added a comment -

          Referring to /trunk/main/pom.xml, it should be 5.0 by "<mq.version>5.0-002</mq.version>".

          Show
          David Zhao added a comment - Referring to /trunk/main/pom.xml, it should be 5.0 by "<mq.version>5.0-002</mq.version>".
          Hide
          jthoennes added a comment -

          In reply to comment #5:
          > Referring to /trunk/main/pom.xml, it should be 5.0 by
          > "<mq.version>5.0-002</mq.version>".

          Thanks, David.

          Show
          jthoennes added a comment - In reply to comment #5: > Referring to /trunk/main/pom.xml, it should be 5.0 by > "<mq.version>5.0-002</mq.version>". Thanks, David.

            People

            • Assignee:
              David Zhao
              Reporter:
              mszalbach
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: