Issue Details (XML | Word | Printable)

Key: GLASSFISH-18436
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: David Zhao
Reporter: mszalbach
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
glassfish

Unable to send compressed JMS message from client to Glassfish

Created: 01/Mar/12 01:46 PM   Updated: 06/Jun/12 11:34 AM   Resolved: 06/Jun/12 02:37 AM
Component/s: jms
Affects Version/s: v3.0.1, 3.1.2_b23
Fix Version/s: 4.0_b41

Time Tracking:
Not Specified

File Attachments: 1. Zip Archive JmsCompressionTest.zip (240 kB) 01/Mar/12 01:46 PM - mszalbach

Environment:

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

Issue Links:
Related
 

Tags:
Participants: David Zhao, jthoennes, mszalbach and Nigel Deakin


 Description  « Hide

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.



Nigel Deakin added a comment - 09/Mar/12 05:55 PM

This is the same as MQ-155


jthoennes added a comment - 19/May/12 09:04 AM

Hello,

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

Cheers, Jörg


David Zhao added a comment - 06/Jun/12 02:37 AM

The fix in bundled MQ goes into GF b41.


jthoennes added a comment - 06/Jun/12 07:12 AM

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?


David Zhao added a comment - 06/Jun/12 07:24 AM

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


jthoennes added a comment - 06/Jun/12 11:34 AM

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.