Return-Path: 
 <activemq-users-return-3495-apmail-geronimo-activemq-users-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org
Received: (qmail 73543 invoked from network); 5 Aug 2006 06:02:59 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 5 Aug 2006 06:02:59 -0000
Received: (qmail 71087 invoked by uid 500); 5 Aug 2006 06:02:59 -0000
Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org
Received: (qmail 71068 invoked by uid 500); 5 Aug 2006 06:02:58 -0000
Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:activemq-users-help@geronimo.apache.org>
List-Unsubscribe: <mailto:activemq-users-unsubscribe@geronimo.apache.org>
List-Post: <mailto:activemq-users@geronimo.apache.org>
List-Id: <activemq-users.geronimo.apache.org>
Reply-To: activemq-users@geronimo.apache.org
Delivered-To: mailing list activemq-users@geronimo.apache.org
Received: (qmail 71059 invoked by uid 99); 5 Aug 2006 06:02:58 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Aug 2006 23:02:58 -0700
X-ASF-Spam-Status: No, hits=1.9 required=10.0
	tests=DNS_FROM_RFC_ABUSE,SPF_PASS,SUBJECT_FUZZY_TION
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of james.strachan@gmail.com
 designates 64.233.182.184 as permitted sender)
Received: from [64.233.182.184] (HELO nf-out-0910.google.com) (64.233.182.184)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Aug 2006 23:02:57 -0700
Received: by nf-out-0910.google.com with SMTP id l36so1530483nfa
        for <activemq-users@geronimo.apache.org>;
 Fri, 04 Aug 2006 23:02:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=HaqjWXOdQpMReKtFsPwPNJ5S6BgxwXRSmzLuBR4KK/5mi+usYm/bQ1kbUPyN9CMNq/gHQpADCp8p+UPjUFN1pJ+25Y0QKxAsHPBq1vr1mE8p4IOIyQSQmElalkarLzdYZV5miMmZMZvjOh932Jl/KHT7Vq+DXAHszBltJJmkBGw=
Received: by 10.78.177.3 with SMTP id z3mr1815437hue;
        Fri, 04 Aug 2006 23:02:36 -0700 (PDT)
Received: by 10.78.174.8 with HTTP; Fri, 4 Aug 2006 23:02:36 -0700 (PDT)
Message-ID: <ec6e67fd0608042302y4b914357k54a765cc4d780261@mail.gmail.com>
Date: Sat, 5 Aug 2006 07:02:36 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Re: Bad AcitveMQ 4 and Jacorb 1.3.30 Interactio0n
In-Reply-To: <5659124.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5659124.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

The quickest way to disable JMX is via the <broker useJmx="false">...
option in the XML (or the BrokerService.setUseJmx(false) if you are
using Java code)..

Your issue is probably that by default the remote management context XML
http://incubator.apache.org/activemq/xml-configuration.html

defines a naming server. So you could change the port....

managementContext>
       <managementContext connectorPort="1099"
jmxDomainName="org.apache.activemq"/>
    </managementContext>

and keep the JMX functionality

On 8/5/06, Dave Cameron <david.a.cameron@lmco.com> wrote:
>
> I'm trying to migrate our application framework from ActiveMQ 3 to ActiveMQ 4
> and am having trouble with an interaction with Jacorb.
>
> What I see is a Jacorb client cannot connect to it's server now that the
> project has been migrated to ActiveMQ 4.
>
> What I think is going on is the JMX functionality has messed with the JVM
> config in such a way that Jacorb can no longer configure itself properly.
> Doesn't JMX use RMI over IIOP for communications???
>
> I've been able to initialize Jacrob first then bring up ActiveMQ with
> settings that I thought disabled the JMX functionality.  ActiveMQ comes up
> but throws strange exceptions related to jmx even though I thought I shut it
> off.
>
> What I am wanting to know is if there is a way to cleanly remove the JMX
> functionality completely.
>
> Another thought is if there is a way to run JMX over some other transport so
> it stops bothering Jacorb.
>
> Getting rid of Jacorb is not a solution since it is required for
> intergrating with a product we don't make the decisions on.
>
> The 4 series looks great otherwise.  My team will be pleased if we can make
> the migration.
>
> Thanks in advance for any ideas.
> --
> View this message in context: http://www.nabble.com/Bad-AcitveMQ-4-and-Jacorb-1.3.30-Interactio0n-tf2053977.html#a5659124
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>


-- 

James
-------
http://radio.weblogs.com/0112098/