Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 37EF7200B85 for ; Thu, 1 Sep 2016 00:15:59 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 365B9160AB5; Wed, 31 Aug 2016 22:15:59 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7DBB9160AB4 for ; Thu, 1 Sep 2016 00:15:58 +0200 (CEST) Received: (qmail 516 invoked by uid 500); 31 Aug 2016 22:15:57 -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 505 invoked by uid 99); 31 Aug 2016 22:15:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Aug 2016 22:15:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id B31301A00B3 for ; Wed, 31 Aug 2016 22:15:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.427 X-Spam-Level: X-Spam-Status: No, score=-4.427 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id d-eQZjK5IUXn for ; Wed, 31 Aug 2016 22:15:50 +0000 (UTC) Received: from amcrelay1.faa.gov (amcrelay1.faa.gov [162.58.35.109]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id BFD005F21E for ; Wed, 31 Aug 2016 22:15:49 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2FRAgDiVcdXfY8jOqJaAxwBAQQBAYJ5IRIBAQEBAWcOgQONKKVshQ2CAYJmgzYCgUs4FAECAQEBAQEBAQMQAQEWKy+EaBIbXgEVFVYmAQQbGogkAQSfNIQNApptAQEIAQEBAQEijz5FgmaCLwWZUJkihWWQQR6EZYZdfwEBAQ X-IronPort-AV: E=Sophos;i="5.30,264,1470718800"; d="scan'208,217";a="345999195" Received: from unknown (HELO 006-smtp-out.faa.gov) ([162.58.35.143]) by amcrelay1.faa.gov with ESMTP; 31 Aug 2016 17:15:36 -0500 Received: from 006FCH1MMR2-007.006f.mgd2.msft.net (198.252.0.48) by BN1F00601MB001.006f.mgd2.msft.net (23.103.4.21) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.549.15; Wed, 31 Aug 2016 22:15:35 +0000 Received: from 006FCH1MPN2-002.006f.mgd2.msft.net ([fe80::d8e2:111a:5269:443d]) by 006FCH1MMR2-007.006f.mgd2.msft.net ([fe80::8c80:9200:2bd:e17a%11]) with mapi id 14.03.0248.003; Wed, 31 Aug 2016 22:15:35 +0000 From: To: Subject: Need Help With A JMS Exception Thread-Topic: Need Help With A JMS Exception Thread-Index: AdID0lrSMPwlLl6NS62igD03/gKNCA== Date: Wed, 31 Aug 2016 22:15:35 +0000 Message-ID: <66E4D465B7148341A329FEB0ACD5BA1A0116ABC3@006FCH1MPN2-002.006f.mgd2.msft.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.31.19.49] Content-Type: multipart/alternative; boundary="_000_66E4D465B7148341A329FEB0ACD5BA1A0116ABC3006FCH1MPN20020_" MIME-Version: 1.0 X-CFilter-Loop: Reflected archived-at: Wed, 31 Aug 2016 22:15:59 -0000 --_000_66E4D465B7148341A329FEB0ACD5BA1A0116ABC3006FCH1MPN20020_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We had a rather unique situation some time ago where our message broker log= was recording the JMSException for an Invalid acknowledgement. We traced it to the fact that the consumer of the message was using a more = recent version of ActiveMQ than our message broker was running (i.e. messag= e broker was v5.5.1 and the consumer was >v5.5.1). We would like to recreate this error in one of our test environments so tha= t we can learn more about it. It appears that the exception was related to a consumer acknowledging a mes= sage. We determined this from observing that the specific exception that w= as thrown appears to originate in only one place, that is the acknowledge()= function of the TopicSubscription class. I have configured an environment with a v5.5.1 message broker and a consume= r and producer compiled with v5.11.0 of ActiveMQ. The producer sends messa= ges to a topic and the consumer receives these messages and then acknowledg= es those messages. The session was configured for client acknowledgement. = Under these conditions I could not reproduce the exception described above= . I tried looking through the source code for the acknowledge() function of t= he ActiveMQMessage class to see if I could determine how my consumer call t= o acknowkedge() landed on the TopicSubscription acknowledge(), but have bee= n unable to make a connection between the acknowledge() function in ActiveM= QMessage and TopicSubscription even after following the calls starting with= the call to ActiveMQMessage acknowledge(). Can you offer any explanation as to why I am unable to trace the functions = calls to TopicSubscription acknowledge? And more importantly, can you offe= r any advice on how I might recreate the exception condition described here= ? Thanks, Mike Michael Tarullo Contractor (Engility Corp) Software Engineer FAA WJH Technical Center (609)485-5294 --_000_66E4D465B7148341A329FEB0ACD5BA1A0116ABC3006FCH1MPN20020_--