Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of mathias.herberts@gmail.com
 designates 64.233.166.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=iBYn3h830ec4nrDzDtQzPVmuN8BAg/TANk7C/0T9yP2XGgmRHeq0S/dIPO3Q6O6zv+a0HArU3js6C6d6Tl3Y9BWAYv/K0xPwMQu5XoILo5anmpSDAdpjf4tP8T8svzQNi/45HbftcW6JxTnBlXgawSP1JmRM9gp1CJfETLD9Wik=
Message-ID: <1c5747850609040217h6dd73364r5a35e155c31317c5@mail.gmail.com>
Date: Mon, 4 Sep 2006 11:17:09 +0200
From: "Mathias Herberts" <mathias.herberts@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Weird behaviour between Java JMS Producer and Python STOMP Consumer
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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.