Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08D7A107E0 for ; Tue, 12 Nov 2013 14:50:42 +0000 (UTC) Received: (qmail 89130 invoked by uid 500); 12 Nov 2013 14:50:39 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 88046 invoked by uid 500); 12 Nov 2013 14:50:32 -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 87759 invoked by uid 99); 12 Nov 2013 14:50:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Nov 2013 14:50:25 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of dwhitney67@gmail.com does not designate 216.139.250.139 as permitted sender) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Nov 2013 14:50:20 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VgFHb-000606-AI for users@activemq.apache.org; Tue, 12 Nov 2013 06:49:35 -0800 Date: Tue, 12 Nov 2013 06:49:20 -0800 (PST) From: dwhitney67 To: users@activemq.apache.org Message-ID: <1384267760272-4674212.post@n4.nabble.com> Subject: How can I check that client is compatible with a broker? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I support a project which employs the use of many C++ client applications that rely on ActiveMQ CPP library to interface to the ActiveMQ broker. Some of the applications, which have been fielded to customer sites, were built/compiled years ago. In certain cases, customers want to upgrade to a newer version of the AMQ broker (e.g. 3.5.9), but are uncertain if there existing client applications would be compatible. Typically, on the Release Documentation page, for say, AMQ C++ 3.8.1, there's a note indicating the following: NOTE: Compatible with ActiveMQ Broker versions in the 4.X and 5.X family Whereas this is nice to know, is there any way to for client application to check, during run-time, that the AMQ CPP library is compatible with the AMQ broker in use? -- View this message in context: http://activemq.2283324.n4.nabble.com/How-can-I-check-that-client-is-compatible-with-a-broker-tp4674212.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.