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 EC17610269 for ; Sat, 11 Jan 2014 19:44:08 +0000 (UTC) Received: (qmail 16719 invoked by uid 500); 11 Jan 2014 19:44:04 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 16668 invoked by uid 500); 11 Jan 2014 19:43:59 -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 16660 invoked by uid 99); 11 Jan 2014 19:43:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 19:43:58 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [153.97.7.23] (HELO mail-edgeS23.fraunhofer.de) (153.97.7.23) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 11 Jan 2014 19:43:49 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiEFAMOd0VKZYQca/2dsb2JhbABagmohOFa5ZoEHFnSCJwWBCwEqfAEEG4d7AQEDCZl3qXyOVoJnD2aBEwSJC5A8hRCLVYMtgio X-IronPort-AV: E=Sophos;i="4.95,644,1384297200"; d="scan'208";a="22180311" Received: from mail-mtas26.fraunhofer.de ([153.97.7.26]) by mail-edgeS23.fraunhofer.de with ESMTP/TLS/RC4-SHA; 11 Jan 2014 20:43:28 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiEFAMOd0VLBr6JK/2dsb2JhbABagmohOFa5ZoEHFnSCJwWBCwEqfAEEG4d8AQMJmXepfI5WgmcPZoETBIkLkDyFEItVgy2CKg X-IronPort-AV: E=Sophos;i="4.95,644,1384297200"; d="scan'208";a="60456354" Received: from smtps.iais.fraunhofer.de ([193.175.162.74]) by mail-mtaS26.fraunhofer.de with ESMTP; 11 Jan 2014 20:43:26 +0100 Received: from exchange-cas1.iais.fraunhofer.de (exchange-cas1.iais.fraunhofer.de [129.26.64.90]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "exchange.iais.fraunhofer.de", Issuer "Fraunhofer Service CA - G01" (verified OK)) by smtps.iais.fraunhofer.de (Postfix) with ESMTPS id 7B7FD40050 for ; Sat, 11 Jan 2014 20:43:26 +0100 (CET) Received: from exchange-ms1.iais.fraunhofer.de ([fe80::7503:ceb3:ede1:834f]) by exchange-cas1.iais.fraunhofer.de ([fe80::215c:ac36:308d:4281%10]) with mapi id 14.03.0174.001; Sat, 11 Jan 2014 20:43:25 +0100 From: =?iso-8859-1?Q?Genc=2C_=D6mer?= To: "users@activemq.apache.org" Subject: Broker URI Configuration in Apache Geronimo Thread-Topic: Broker URI Configuration in Apache Geronimo Thread-Index: Ac8PBWH4BIx1b/1nQNOwl3kUJBAeRA== Date: Sat, 11 Jan 2014 19:43:24 +0000 Message-ID: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [37.24.148.194] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hey folks, currently I am trying to configure ActiveMQ in Apache Geronimo. I deploy my= own custom module on Geronimo. In the deployment descriptor of this module= I would like to configure an ActiveMQ broker using a broker URI in the res= ource adapter of ActiveMQ. I am especially interested in configuring Networ= kConnector using the Broker URI. I found the documentation and an example h= ere: http://activemq.apache.org/broker-uri.html The corresponding entry in my deployment descriptor looks like this: vm:broker:(tcp://localhost:61616,network:static://(tcp://remoteHost-1:61616= ,tcp:// remoteHost-2:61616))/DefaultActiveMQBroker?broker.create=3Dyes&= jms.watchTopicAdvisories=3Dfalse&jms.copyMessageOnSend=3Dfalse&jms.= persistent=3Dfalse However the configuration using the broker URI does not seem to work, by st= epping through the code, I can see that no NetworkConnectors are added to t= he DefaultActiveMQBroker. Please note, the =BBDefaultActiveMQBroker=AB is d= efault created by the Geronimo application server and is already running wh= en my module is deployed. When I change the above code to create a new broker and add my NetworkConne= ctor to it, everything works as expected. I changed the port number of the = transport connector and the broker name, therefore a new broker is created = when I deploy my custom module. For example the following code works: vm:broker:(tcp://localhost:61636,network:static://(tcp://remoteHost-1:61616= ,tcp:// remoteHost-2:61616))/MyCustomActiveMQBroker?broker.create=3Dyes&= ;jms.watchTopicAdvisories=3Dfalse&jms.copyMessageOnSend=3Dfalse&jms= .persistent=3Dfalse I am also able to modify the activemq.xml included in the ActiveMQ resource= adapter module of Geronimo . This file is used by Geronimo to configure th= e =BBDefaultActiveMQBroker=AB on start up. When adding my NetworkConnectors= there, erveything works correct and my NetworkConnector are added. But I n= eed to use the broker URI configuration from above. It seems, that it is not possible to add NetworkConnector using the broker = URI on already running brokers. Is this a known bug? Am I missing something? Any suggestion is greatly appreciated. Cheers, =D6mer