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 07688200BA0 for ; Fri, 14 Oct 2016 11:42:53 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 05DA9160ADD; Fri, 14 Oct 2016 09:42:53 +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 4E9FB160AD9 for ; Fri, 14 Oct 2016 11:42:52 +0200 (CEST) Received: (qmail 25496 invoked by uid 500); 14 Oct 2016 09:42:51 -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 25485 invoked by uid 99); 14 Oct 2016 09:42:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2016 09:42:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 80ADDC0B0C for ; Fri, 14 Oct 2016 09:42:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.157 X-Spam-Level: *** X-Spam-Status: No, score=3.157 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URI_HEX=1.313, URI_TRY_3LD=0.065] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id FFriMQu_VD3z for ; Fri, 14 Oct 2016 09:42:48 +0000 (UTC) Received: from mail-it0-f49.google.com (mail-it0-f49.google.com [209.85.214.49]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 099455F1BE for ; Fri, 14 Oct 2016 09:42:48 +0000 (UTC) Received: by mail-it0-f49.google.com with SMTP id m138so6450449itm.0 for ; Fri, 14 Oct 2016 02:42:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=fwGLABdVsyx4D04ojtXQUaoc2ix3+SUmxeDnnd3HKcQ=; b=UFHm24B+BfzZd+mRMSY9FhXSbTuCGnzqwBLIlPoDsntvJR/HShrROEK7wtYjA+iwmc ZqaJE2eMjKlWIWVwzHLh/afCZZgGFBqkDS8bk0tNfAQGKY2zTcRClTgPmyE+Agn1xesk SJJG9bwYp5zckIeEcLo9TPpgPUixAMKdA7VW06PcRzek0NvDiiXEjSWgOVZlTvSfZQbA pZlKzWabpprEze9xVJvcJRuxG8HpCtsVfekQ7uyr9rfGDOvyCUKKiLoXwT65CTxIACJm 7tiygKGfmgS2+U6mF9wGkqpqIeD+tW85VoWR4jTWi1Oe6ExRK9uRYpo0cV7h5EQfZ7FD n2IA== X-Gm-Message-State: AA6/9RnzJ5+9vmumIweSRQywvHWKhVG6pML8HZntvVvcyu80wg3iKp56v9qSsVf504efmlIg4H+7FpnKnSr3/Jhw X-Received: by 10.36.144.68 with SMTP id x65mr11484710itd.12.1476438167205; Fri, 14 Oct 2016 02:42:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.15.34 with HTTP; Fri, 14 Oct 2016 02:42:46 -0700 (PDT) In-Reply-To: <1476368727377-4717861.post@n4.nabble.com> References: <1476368727377-4717861.post@n4.nabble.com> From: Martyn Taylor Date: Fri, 14 Oct 2016 10:42:46 +0100 Message-ID: Subject: Re: HornetQ client connect to Artemis server To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=94eb2c07e8067d5220053ed00c87 archived-at: Fri, 14 Oct 2016 09:42:53 -0000 --94eb2c07e8067d5220053ed00c87 Content-Type: text/plain; charset=UTF-8 Hi, Artemis does support HornetQ 2.4.7.final clients and should work out of the box. Could you provide a reproducer? We actually have some tests under /tests/extra-tests/protocols/hornetq that test the HornetQ client against the latest broker. If you could contribute a test here that'd be perfect. Once I have this I will investigate. Otherwise just your broker config + some java reproducer should suffice. Thanks On Thu, Oct 13, 2016 at 3:25 PM, hcrobison wrote: > We are in the process upgrading from HornetQ (2.4.7) to Artemis (1.4.0). > Artemis server migration itself is working - server running and Artemis > client can talk to server. However, we still need to support clients who > use > HornetQ client. We need HornetQ clients to be able to talk to the Artemis > server. The current problem I am running into is the following > exception.org.hornetq.api.core.HornetQConnectionTimedOutException: > HQ119013: > Timed out waiting to receive cluster topology. Group:null at > org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory( > ServerLocatorImpl.java:946) > ~[hornetq-core-client-2.4.7.Final.jar:na]Please let me know what I need to > provide for further investigation. > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/HornetQ-client-connect-to-Artemis-server-tp4717861.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. --94eb2c07e8067d5220053ed00c87--