Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 88582 invoked from network); 28 Oct 2010 18:12:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Oct 2010 18:12:22 -0000 Received: (qmail 22136 invoked by uid 500); 28 Oct 2010 18:12:22 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 22099 invoked by uid 500); 28 Oct 2010 18:12:21 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 22090 invoked by uid 99); 28 Oct 2010 18:12:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Oct 2010 18:12:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Oct 2010 18:12:20 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o9SIC0gL011756 for ; Thu, 28 Oct 2010 18:12:00 GMT Message-ID: <16292382.1901288289520076.JavaMail.jira@thor> Date: Thu, 28 Oct 2010 14:12:00 -0400 (EDT) From: "Michael Justin (JIRA)" To: dev@activemq.apache.org Subject: [jira] Created: (AMQ-3006) STOMP connector assigns wrong default priority to incoming messages MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c STOMP connector assigns wrong default priority to incoming messages ------------------------------------------------------------------- Key: AMQ-3006 URL: https://issues.apache.org/activemq/browse/AMQ-3006 Project: ActiveMQ Issue Type: Bug Components: Transport Affects Versions: 5.4.1 Environment: Windows Vista Reporter: Michael Justin Priority: Minor If a client sends a Stomp frame without a priority header, the broker does not set the message priority to the default value (4) which is specified in the JMS spec (see http://download.oracle.com/javaee/1.4/api/javax/jms/Message.html: DEFAULT_PRIORITY The message producer's default priority is 4.) As effect, the message will have priority 0 (lowest). Adding a priority header for all messages by the Stomp client, even for default priority, would also cause larger messages to be sent over the wire. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.