Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 12988 invoked from network); 26 Jun 2008 05:35:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jun 2008 05:35:46 -0000 Received: (qmail 9328 invoked by uid 500); 26 Jun 2008 05:35:45 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 9266 invoked by uid 500); 26 Jun 2008 05:35:45 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 9255 invoked by uid 99); 26 Jun 2008 05:35:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2008 22:35:45 -0700 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.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jun 2008 05:34:55 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0B9F7234C14C for ; Wed, 25 Jun 2008 22:34:45 -0700 (PDT) Message-ID: <1734469996.1214458485033.JavaMail.jira@brutus> Date: Wed, 25 Jun 2008 22:34:45 -0700 (PDT) From: "Deepal Jayasinghe (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Created: (AXIS2-3874) MTOM duplicate messages with JMS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org MTOM duplicate messages with JMS --------------------------------- Key: AXIS2-3874 URL: https://issues.apache.org/jira/browse/AXIS2-3874 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Deepal Jayasinghe We have been using Axis2 v1.3 for SOAP/JMS. Up until now we have had no problem using MTOM for MIME attachments. Our solution runs inside Websphere 6.1 and Axis2 queries the WAS JNDI server for its JMS Queue resources. Recently we upgraded to Axis2 v1.4. Immediately we saw problems with the MTOM support. For each JMS request 2 identical duplicate messages are placed on the queue instead of the epected 1. Has anyone seen this behaviour? What could have been introduced in Axis2 v1.4 to cause this? Thanks, Cathal http://www.theserverside.com/news/thread.tss?thread_id=49704 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org For additional commands, e-mail: axis-dev-help@ws.apache.org