Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 93924 invoked from network); 14 Jan 2008 17:32:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jan 2008 17:32:33 -0000 Received: (qmail 43202 invoked by uid 500); 14 Jan 2008 17:32:22 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 43175 invoked by uid 500); 14 Jan 2008 17:32:22 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 43166 invoked by uid 99); 14 Jan 2008 17:32:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2008 09:32:22 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of esammer@cheetahmail.com designates 206.252.205.125 as permitted sender) Received: from [206.252.205.125] (HELO mtx.cheetahmail.com) (206.252.205.125) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jan 2008 17:32:08 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mtx.cheetahmail.com (Postfix) with ESMTP id 094F3286C73 for ; Mon, 14 Jan 2008 12:32:22 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at cheetahmail.com Received: from mtx.cheetahmail.com ([127.0.0.1]) by localhost (mtx.cheetahmail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JS3Lzr5-inf for ; Mon, 14 Jan 2008 12:32:21 -0500 (EST) Received: from [192.168.6.128] (unknown [38.96.160.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mtx.cheetahmail.com (Postfix) with ESMTP id E3F8B286C5D for ; Mon, 14 Jan 2008 12:32:21 -0500 (EST) Message-ID: <478B9C4C.2050701@cheetahmail.com> Date: Mon, 14 Jan 2008 12:30:52 -0500 From: Eric Sammer User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: users@activemq.apache.org Subject: Stomp clients and message-id Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello: I'm working in a situation where I have Stomp clients (perl, using Net::Stomp) connecting to ActiveMQ (4.1.1, java 1.5.x on Linux). I need to use the standard request / response pattern with the reply-to, message-id, and correlation-id headers. The problem I find is that the message-id field isn't populated in the message object after send(). The JMS spec states the following: "When a message is sent, JMSMessageID is ignored. When the send method returns, the field contains a provider-assigned value." (Section 3.4.3, paragraph 2 of the JMS specification version 1.1 April 2002) The problem is that the Stomp protocol doesn't seem to support a response to the SEND message that would allow the API to return the provider assigned message-id[1]. There is a provision for the RECEIPT frame, but it seems to only return the receipt-id field, as specified by the client; a kind of echo response confirmation which isn't rich enough, in this case. This seems like an oversight in the Stomp protocol, more so than ActiveMQ. Am I reading this correctly? Should the message-id field of the sent message be populated after invocation of the send method (in whatever form it takes)? Should this be addressed with the AMQ team or with the Stomp protocol team? Any thoughts or opinions are appreciated. Thanks in advance! [1] - The Stomp Protocol - http://stomp.codehaus.org/Protocol -- Eric Sammer System Architect CheetahMail, an Experian Company +1.212.863.4642 - esammer@cheetahmail.com