I wonder could you try 4.0.2 or 4.0.1 as a number of stomp related fixes have been made.
We could maybe do with a test case adding to Stomp for empty JMS TextMessages On 9/4/06, Mathias Herberts <[EMAIL PROTECTED]> wrote:
Hi, I have a setup where a Java Producer puts TextMessages in a queue. Those messages might be created with or without a body (using one of the two Session.createTextMessage methods). The Python STOMP client uses stomp.py to connect to the Active MQ 4.0 broker. The Python consumer receives mesages OK as long as they contain a body. As soon as a message created without a body is sent by the producer, the consumer stops receiving messages, even those sent at a later date with a body. The AMQ log does not show any warning/error/fault. A tcpdump on the STOMP connection shows indeed no activity so I guess this problem cannot be blamed on stomp.py. Anybody else noticed this behaviour before? Anything that can be done about it beside making sure all messages have a body? Thanks, Mathias.
-- James ------- http://radio.weblogs.com/0112098/
