Bug when TextMessage payload is NULL?
2 posts in topic
Flat View  Flat View
Older Post First |   Reply to Topic
TOPIC ACTIONS:
 

Posted By:   Matthew_Clark
Posted On:   Friday, April 28, 2006 07:37 AM

Hi there,

I have an issue that presents in both 5.2.5 and the latest 6.0 release whereby if we send a TextMessage with a NULL payload to a queue, I can no longer use the explorer in any way on the queue - it times out all requests (drain, delete, execute select).

Setting the payload to the empty string fixes the problem but according to the JMS spec, the payload can be null...

I haven't tried replicating with other Message Interfaces.

Regards,

Matthew.

Report | Quote This | Send private message | Reply | Print

Re: Bug when TextMessage payload is NULL?

Posted By:   Andreas_Mueller  
Posted On:   Wednesday, May 3, 2006 05:11 AM

It was a bug in the message viewer and effects SwiftMQ Explorer/CLI only. A JMS client is able to send / receive TextMessages with a null body. Has been fixed and will be available for the next release.
Report | Quote This | Send private message | Reply | Print

Re: Bug when TextMessage payload is NULL?

Posted By:   Andreas_Mueller  
Posted On:   Friday, April 28, 2006 09:54 AM

We will check that. If that is a bug, it will be fixed for the next release.


Thanks!
Report | Quote This | Send private message | Reply | Print
About | Sitemap | Contact